Sponsored Content
Top Forums Shell Programming and Scripting uuencode and outlook attachment issue Post 302610069 by frank_rizzo on Tuesday 20th of March 2012 08:07:02 PM
Old 03-20-2012
I think you need to format the attachment with a MIME utility. Not sure off hand if you can do this with mail/mailx but a simple Perl script can handle it.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Uuencode problem in mail attachment

I have a unix script that compresses a .txt file using gzip command and then sends it by mail using uuencode. This has been working fine for some time, but lately I've been experiencing some problems, as when I open the mail generated, I don't see the attachment, but instead I get a large amount... (8 Replies)
Discussion started by: mvalonso
8 Replies

2. UNIX for Advanced & Expert Users

send attachment without uuencode

Hello - In unix, can you tell me IF there is a way to send attachments via email without using uuencode command? Thank you (3 Replies)
Discussion started by: panchpan
3 Replies

3. UNIX for Dummies Questions & Answers

uuencode without attachment

Hi All, I'm using uuencode to send out mail from unix to lotus notes,but i dont have any attachment to send out, I'm getting this message in the body of the mail "Usage: uuencode remotedest" however if i dont use uuencode I'm not able to send out mail Please help Thanks (1 Reply)
Discussion started by: gwrm
1 Replies

4. Shell Programming and Scripting

UUEncode Attachment Missing

Hi All, I have created a shell utility that runs various database jobs and then mail the output of the database jobs to the customers. This is a generic utility and executes almost 15 reports and sends the results out. To send the attachment I use uuencode. This had been working fine till... (4 Replies)
Discussion started by: anonymoususer45
4 Replies

5. Shell Programming and Scripting

Unable to see attachment in outlook express sent by UUENCODE through unix script

Hi, I have written one script to send mail with attachment from my unix server, it is working fine, and i am capable to see the attachment in my lotus notes , but when i try to see the same thing in my outlook express ..it is completly garbaled. Please advise how to see proper attachment in... (5 Replies)
Discussion started by: apskaushik
5 Replies

6. Shell Programming and Scripting

attachment and single line using uuencode

I tried using the fllowing command to attach and email a file but the issue is the attach file drops the carriage return or line feed and all the rows appears in single line. uuencode file.txt file.txt | mail user@gmail.com Any solution guys (3 Replies)
Discussion started by: RubinPat
3 Replies

7. Shell Programming and Scripting

Send files as an attachment without uuencode

Hi All, Is there anyway we can send files as an attachment? I tried running uuencode but its giving an error as below: $ uuencode Z1.txt Z1.txt |mailx -s "hi" abc@abc.com ksh: uuencode: not found. Null message body; hope that's ok When i gave which command then it says there is no... (18 Replies)
Discussion started by: HemaV
18 Replies

8. Shell Programming and Scripting

How to send attachment without using uuencode

H All I want to send attachment in mail but I dont have uuencode installed in AIX server, there is any alternative way to send attachment in mail. (2 Replies)
Discussion started by: ns64110
2 Replies

9. Shell Programming and Scripting

Need to send attachment without using uuencode and mutt

Hi, In my Linux am unable to send attachment to mail . Since pkgs for mutt and uuencode is not possible to install any other options for sending attachment will be useful. Tried the below options but its not working. mail -s "testmail" -a <filename> abc@mail.com cat <filename>|mail -s... (4 Replies)
Discussion started by: rogerben
4 Replies

10. Shell Programming and Scripting

Mailx attachment using uuencode issue on Outlook2013

Hello all I am on RHEL 6.4. I have been using my bash script which mails one .csv file after zipping (myfile.csv.zip)to my Lotus Notes ID. I use uuencode with mailx to do this. Here is my command - uuencode myfile.csv.zip myfile.csv.zip | mailx -s "Subject" mailid. This all works very cool. Now... (3 Replies)
Discussion started by: krsnadasa
3 Replies
Cone(C)

CONE(1) 						  Cone: COnsole Newsreader And E						   CONE(1)

NAME
cone - Read and send E-mail messages SYNOPSIS
cone [-r] [-c directory] USAGE
Cone is a console newsreader and E-mail. It is an interactive program for reading and sending E-mail messages. Cone is designed to be intuitive and easy to learn. Starting Cone for the first time displays two links: one for the default system mailbox, and a second link to a quick online tutorial. The online tutorial provides a brief overview of using Cone for reading and sending E-mail. Pressing Q on most screens exits Cone. Cone tries to gracefully log out and shut down all server connections. If Cone cannot log out of a remote server because the remote server is down, press CTRL-C (after Q to terminate Cone). Use CTRL-Z to temporarily suspend Cone and drop back to the shell prompt. Cone remains suspended in the background, and may be restarted by using the shell's fg command. Note Connections to remote mail servers may be disconnected for inactivity if Cone remains suspended for a prolonged period of time. When suspended, Cone cannot maintain any active connections to remote mail servers. The -c option names a directory where Cone saves its configuration files, and defaults to $HOME/.cone. The configuration directory will be created, if necessary. The -r option recovers a backup copy of Cone's configuration file. This option is primarily used when remote configuration is enabled, but the folder that contains Cone's configuration on a remote server was deleted, or is not available. In all cases, Cone makes a daily local configuration file backup. The -r option searches for local configuration file backups, and offers an option to restore the backup copy. Reading local mail with Cone Cone reads local mail from either maildirs (the preferred format) or mailbox files (or "mboxes"). When mboxes are used, Cone does not read the system mailbox file directly (usually /var/spool/something). All messages in the system mailbox are automatically moved to $HOME/Inbox, which is then accessed as if it was the system mailbox. Starting Cone for the first time on an mbox-based system automatically copies all existing mail from the system mailbox file to $HOME/Inbox. This is an intentional design choice. Normal user application cannot create new files in /var/spool; all they can do is read the mailbox file from /var/spool. Therefore, the only way to update the mailbox file is by rewriting it from scratch (more or less). While the mailbox file is in the process of being rewritten, if the Cone process is interrupted, or killed, the resulted in a corrupted system mailbox. There are way to minimize this vulnerability, but it cannot be eliminated completely. Some Linux kernels use an "OOM killer" that may terminate any process when the system memory is low. There is no way to completely prevent corrupted system mailbox files on those kernels. Cone uses an alternative way of updating mboxes. Cone updates mboxes by creating a new mbox file separately, then replacing the original mbox file with the new version. Unfortunately this cannot be done with the system mailbox file, because of the restricted access rights on the system spool directory. To solve this problem Cone automatically copies the system mailbox file to $HOME/Inbox, each time the system mailbox file is opened and whenever new mail is available. Viewing MIME attachments Cone displays text and simple HTML content by itself. Other kinds of attachments may be viewed by using a helper script. Cone invokes a helper script to open a MIME attachment. The helper script's name is "TYPE.SUBTYPE.filter", where "TYPE" and "SUBTYPE" corresponds to the MIME type and subtype, accordingly. Cone looks for helper scripts in $HOME/.cone (or the directory specified by -c) and in /usr/share/cone. For example, a helper script named "IMAGE.GIF.filter", if installed, is invoked to process image/gif MIME attachments. Helper scripts Cone runs each helper script twice: TYPE.SUBTYPE.filter check type/subtype When the first argument is "check", the helper script should terminate with a zero exit code if it is willing to process an attachment whose MIME type is specified by the second argument. A script or a program that's has multiple "TYPE.SUBTYPE.filter" links may use the second argument to identify the attachment's mime type. If the helper script is unable to process the attachment, at this time, it should terminate with a non-zero exit code. The default helper script for image attachments terminates with a non-zero exit code if the DISPLAY environment variable is not initialized. When invoked from an X-Windows terminal, image attachments will be automatically displayed; and image attachments are ignored otherwise on non-graphical consoles. TYPE.SUBTYPE.filter filter type/subtype filename If the helper script initially terminates with a zero exit code, it will be invoked again after the MIME attachment is downloaded and decoded. The first argument will be "filter", and the attachment's filename is specified by the third argument. Note This is a temporary file, whose extension will not necessary be the file extension associated with this MIME type. The helper script should read and process the file specified by the third argument. Cone interprets anything the helper script writes to standard output as HTML. Note Cone waits until the helper script terminates before displaying the rest of the message. Most helper scripts should run in the background. However, note that Cone removes the temporary file when the original message is closed; the temporary file may be removed any time after the helper script terminates. The helper script should make its own private copy of the file, if necessary. Activating URLs Cone has limited ability to activate URLs in HTML messages. Cone handles "mailto:" URLs by itself. For other URLs Cone runs /usr/share/cone/method.handler with the URL passed as an argument. Cone installs http.handler (hard linked to https.handler). This script checks if firefox or mozilla binaries are found in the current PATH, and runs them. Note Cone also looks method.handler in $HOME/.cone (or the directory specified by -c) in addition to /usr/share/cone. FILES
$HOME/.cone Configuration files, and other application data. May be modified by the -c option. /usr/share/cone/IMAGE.GIF.filter, /usr/share/cone/IMAGE.JPEG.filter, /usr/share/cone/IMAGE.PNG.filter, /usr/share/cone/APPLICATION.PDF.filter Default helper scripts distributed with Cone. SEE ALSO
mailtool(1), sendmail(8). AUTHOR
Sam Varshavchik Cone(C) 04/04/2011 CONE(1)
All times are GMT -4. The time now is 02:34 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy