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
TNEF(3) 						User Contributed Perl Documentation						   TNEF(3)

NAME
Convert::TNEF - Perl module to read TNEF files SYNOPSIS
use Convert::TNEF; $tnef = Convert::TNEF->read($iohandle, \%parms) or die Convert::TNEF::errstr; $tnef = Convert::TNEF->read_in($filename, \%parms) or die Convert::TNEF::errstr; $tnef = Convert::TNEF->read_ent($mime_entity, \%parms) or die Convert::TNEF::errstr; $tnef->purge; $message = $tnef->message; @attachments = $tnef->attachments; $attribute_value = $attachments[$i]->data($att_attribute_name); $attribute_value_size = $attachments[$i]->size($att_attribute_name); $attachment_name = $attachments[$i]->name; $long_attachment_name = $attachments[$i]->longname; $datahandle = $attachments[$i]->datahandle($att_attribute_name); DESCRIPTION
TNEF stands for Transport Neutral Encapsulation Format, and if you've ever been unfortunate enough to receive one of these files as an email attachment, you may want to use this module. read() takes as its first argument any file handle open for reading. The optional second argument is a hash reference which contains one or more of the following keys: output_dir - Path for storing TNEF attribute data kept in files (default: current directory). output_prefix - File prefix for TNEF attribute data kept in files (default: 'tnef'). output_to_core - TNEF attribute data will be saved in core memory unless it is greater than this many bytes (default: 4096). May also be set to 'NONE' to keep all data in files, or 'ALL' to keep all data in core. buffer_size - Buffer size for reading in the TNEF file (default: 1024). debug - If true, outputs all sorts of info about what the read() function is reading, including the raw ascii data along with the data converted to hex (default: false). display_after_err - If debug is true and an error is encountered, reads and displays this many bytes of data following the error (default: 32). debug_max_display - If debug is true then read and display at most this many bytes of data for each TNEF attribute (default: 1024). debug_max_line_size - If debug is true then at most this many bytes of data will be displayed on each line for each TNEF attribute (default: 64). ignore_checksum - If true, will ignore checksum errors while parsing data (default: false). read() returns an object containing the TNEF 'attributes' read from the file and the data for those attributes. If all you want are the attachments, then this is mostly garbage, but if you're interested then you can see all the garbage by turning on debugging. If the garbage proves useful to you, then let me know how I can maybe make it more useful. If an error is encountered, an undefined value is returned and the package variable $errstr is set to some helpful message. read_in() is a convienient front end for read() which takes a filename instead of a handle. read_ent() is another convient front end for read() which can take a MIME::Entity object (or any object with like methods, specifically open("r"), read($buff,$num_bytes), and close ). purge() deletes any on-disk data that may be in the attachments of the TNEF object. message() returns the message portion of the tnef object, if any. The thing it returns is like an attachment, but its not an attachment. For instance, it more than likely does not have a name or any attachment data. attachments() returns a list of the attachments that the given TNEF object contains. Returns a list ref if not called in array context. data() takes a TNEF attribute name, and returns a string value for that attribute for that attachment. Its your own problem if the string is too big for memory. If no argument is given, then the 'AttachData' attribute is assumed, which is probably the attachment data you're looking for. name() is the same as data(), except the attribute 'AttachTitle' is the default, which returns the 8 character + 3 character extension name of the attachment. longname() returns the long filename and extension of an attachment. This is embedded within a MAPI property of the 'Attachment' attribute data, so we attempt to extract the name out of that. size() takes an TNEF attribute name, and returns the size in bytes for the data for that attachment attribute. datahandle() is a method for attachments which takes a TNEF attribute name, and returns the data for that attribute as a handle which is the same as a MIME::Body handle. See MIME::Body for all the applicable methods. If no argument is given, then 'AttachData' is assumed. EXAMPLES
# Here's a rather long example where mail is retrieved # from a POP3 server based on header information, then # it is MIME parsed, and then the TNEF contents # are extracted and converted. use strict; use Net::POP3; use MIME::Parser; use Convert::TNEF; my $mail_dir = "mailout"; my $mail_prefix = "mail"; my $pop = new Net::POP3 ( "pop3server_name" ); my $num_msgs = $pop->login("user_name","password"); die "Can't login: $!" unless defined $num_msgs; # Get mail by sender and subject my $mail_out_idx = 0; MESSAGE: for ( my $i=1; $i<= $num_msgs; $i++ ) { my $header = join "", @{$pop->top($i)}; for ($header) { next MESSAGE unless /^from:.*someone@somewhere.net/im && /^subject:s*important stuff/im } my $fname = $mail_prefix."-".$$.++$mail_out_idx.".doc"; open (MAILOUT, ">$mail_dir/$fname") or die "Can't open $mail_dir/$fname: $!"; # If the get() complains, you need the new libnet bundle $pop->get($i, *MAILOUT) or die "Can't read mail"; close MAILOUT or die "Error closing $mail_dir/$fname"; # If you want to delete the mail on the server # $pop->delete($i); } close MAILOUT; $pop->quit(); # Parse the mail message into separate mime entities my $parser=new MIME::Parser; $parser->output_dir("mimemail"); opendir(DIR, $mail_dir) or die "Can't open directory $mail_dir: $!"; my @files = map { $mail_dir."/".$_ } sort grep { -f "$mail_dir/$_" and /$mail_prefix-$$-/o } readdir DIR; closedir DIR; for my $file ( @files ) { my $entity=$parser->parse_in($file) or die "Couldn't parse mail"; print_tnef_parts($entity); # If you want to delete the working files # $entity->purge; } sub print_tnef_parts { my $ent = shift; if ( $ent->parts ) { for my $sub_ent ( $ent->parts ) { print_tnef_parts($sub_ent); } } elsif ( $ent->mime_type =~ /ms-tnef/i ) { # Create a tnef object my $tnef = Convert::TNEF->read_ent($ent,{output_dir=>"tnefmail"}) or die $Convert::TNEF::errstr; for ($tnef->attachments) { print "Title:",$_->name," "; print "Data: ",$_->data," "; } # If you want to delete the working files # $tnef->purge; } } SEE ALSO
perl(1), IO::Wrap(3), MIME::Parser(3), MIME::Entity(3), MIME::Body(3) CAVEATS
The parsing may depend on the endianness (see perlport) and width of integers on the system where the TNEF file was created. If this proves to be the case (check the debug output), I'll see what I can do about it. AUTHOR
Douglas Wilson, dougw@cpan.org perl v5.18.2 2012-07-23 TNEF(3)
All times are GMT -4. The time now is 12:19 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy