Sponsored Content
Top Forums Shell Programming and Scripting Mailx with attachment and message body Post 302733391 by only4satish on Tuesday 20th of November 2012 10:46:30 AM
Old 11-20-2012
@bipin ......you are awesome ....... thanks
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

email attachment, with a message using mailx

Hi, I am trying to include a message along with an attachment with an email using mailx on AIX. uuencode Test.dat Test.dat| mailx -s 'Testing' mymail@yahoo.com < MESGFILE This only gives me the contents of MESGFILE as my message. If I remove the < FILE I recieve the attachment. What... (4 Replies)
Discussion started by: edog
4 Replies

2. UNIX for Dummies Questions & Answers

AIX send mail with HTML message body and a binary attachment

I'm trying to script sending an e-mail message on an AIX 5.x server with the following requirements: 1. command line switch to specify file name containing message body in HTML format 2. command line switch to specify file name of a binary attachment 3. command line or input file to specify... (4 Replies)
Discussion started by: G-Man
4 Replies

3. Shell Programming and Scripting

mailx: concatenating strings for message body (KSH)

Hi all, Think this is a pretty simple problem, but I've been thinking about it for a few days. Let's say that I'm going to have to output the contents of a file as the body of a mailx message. I'll probably do this: cat <filename> | mailx <extra commands> However, how do I go about doing... (1 Reply)
Discussion started by: rockysfr
1 Replies

4. Shell Programming and Scripting

Problem while sending message and attachment with mailx

Hi All, I am trying to send a mail with an attachment and message. Following command I am using. (cat <messagefile> ; uuencode <attachmentfile> <attachmentfile>)|mailx -s"Subject" dave@email.com In the received mail, message body is appearing fine. But attachment is not coming. Rather... (2 Replies)
Discussion started by: nihar.dutta
2 Replies

5. Shell Programming and Scripting

Adding an attachment as an attachment to mailx

I don't want the attachment embedded in the mail. I would like a file attached. When I do mailx -s "Report, `date +'%D %r` " -r "Notifications" bob@bob.com < /usr/local/bin/myreport.log> /dev/null It gets embedded in my email. I want a file attachment. How do I do that? (2 Replies)
Discussion started by: guessingo
2 Replies

6. Shell Programming and Scripting

Mailx: How to send a attachment using mailx command

Hi All, Can anyone please provide the command for sending an mail with attachment using mailx command. Thanks in Advance :) Regards, Siram. (3 Replies)
Discussion started by: Sriram.Vedula53
3 Replies

7. Shell Programming and Scripting

send attachment and body in one mail using mailx

Hi, Our requirement is to send an attachment and content in a single mail. I am using the below command to send attachement. --------------------- (uuencode $exp_file $exp_file) |mailx -s "$email_subject" $EmailRecipients -------------------- I m not able to send any message in the... (4 Replies)
Discussion started by: ashwin3086
4 Replies

8. UNIX for Dummies Questions & Answers

Mailx empty body message

Hi, Is there a way to suppress this message? Null message body; hope that's ok My email string is: mailx -s "This is my subject" myemail@domain.com < /dev/null It's just an annoyance to me that I would like see go away. (3 Replies)
Discussion started by: bbbngowc
3 Replies

9. UNIX for Dummies Questions & Answers

Send email with attachment and body : mailx , waiting for input , signal Control D

Hi, I am trying to send email with attacment and body using "mailx" (cat body.txt; uuencode attach.txt) | mailx -s "Attachment" abc@xyz.com When i type this command, the shell is still waiting for me to enter something in standard input and press control D before it sends a mail and... (2 Replies)
Discussion started by: aliaszero
2 Replies

10. Red Hat

Sending email with message body and attachment

Hello experts!! I am trying to send an email with message body and attachment.but i am getting any one like message body or attachment. I tried below command: (echo "subject:test";echo "MIME-Version: 1.0";echo "content-transfer-encoding:base 64";echo "content-type:txt;name=test.txt";cat... (2 Replies)
Discussion started by: Devipriya Ch
2 Replies
Config::INI::Writer(3pm)				User Contributed Perl Documentation				  Config::INI::Writer(3pm)

NAME
Config::INI::Writer - a subclassable .ini-file emitter VERSION
version 0.019 SYNOPSIS
If <$hash> contains: { '_' => { admin => 'rjbs' }, rjbs => { awesome => 'yes', height => q{5' 10"}, }, mj => { awesome => 'totally', height => '23"', }, } Then when your program contains: Config::INI::Writer->write_file($hash, 'family.ini'); family.ini will contains: admin = rjbs [rjbs] awesome = yes height = 5' 10" [mj] awesome = totally height = 23" DESCRIPTION
Config::INI::Writer is yet another config module implementing yet another slightly different take on the undeniably easy to read ".ini" file format. Its default behavior is quite similar to that of Config::Tiny, on which it is based. The chief difference is that Config::INI::Writer is designed to be subclassed to allow for side-effects and self-reconfiguration to occur during the course of reading its input. METHODS FOR WRITING CONFIG
There are three writer methods, "write_string", "write_file", and "write_handle". The first two are implemented in terms of the third. It iterates over a collection of data, emitting lines to the filehandle as it goes. The lines are generated by events produced by iterating over the data. Those events are detailed below in the "METHODS FOR SUBCLASSING" section. The given data should be a hashref of hashrefs: { section_name_1 => { prop1 => 'value1', prop2 => 'value2' }, section_name_2 => ... } ...or an arrayref of section name and arrayref pairs: [ section_name_1 => [ prop1 => 'value1', prop2 => 'value2' ], section_name_2 => ... ] ...or a combination of those: [ section_name_1 => { prop1 => 'value1', prop2 => 'value2' }, section_name_2 => [ prop3 => 'value3', prop4 => 'value4' ], section_name_3 => ... ] All the reader methods throw an exception when they encounter an error. write_file Config::INI::Writer->write_file($input, $filename); This method writes out the configuration represented by $data to the file named by $filename. If a file by that name exists, it is overwritten. This method will either succeed or raise an exception. (Its return value is not defined.) write_string my $string = Config::INI::Writer->write_string($input); This method returns a string containing the INI content describing the given data. write_handle Config::INI::Writer->write_handle($input, $handle); This method writes the data in $data to the IO::Handle-like object in $handle. This method should either succeed or throw an exception. METHODS FOR SUBCLASSING
These are the methods you need to understand and possibly change when subclassing Config::INI::Reader to handle a different format of input. preprocess_input my $processed_input = $writer->preprocess_input($input_data); This method is called to ensure that the data given to the "write_*" methods are in a canonical form for processing and emitting. The default implementation converts hashrefs to arrayrefs and, if the input is a hashref, moves the "starting_section" to the beginning of the produced arrayref. In other words, given: { section_1 => { a => 1, b => 2 }, section_2 => { c => 3, c => 4 }, _ => { d => 5, e => 6 }, } This method will return: [ _ => [ d => 5, e => 6 ], section_2 => [ c => 3, c => 4 ], section_1 => [ a => 1, b => 2 ], ] The only guaranteed ordering when hashes are provided as input is that the starting section will appear first. validate_input $writer->validate_input($input); This method is called on the input data once they've been preprocessed by "preprocess_input". It ensures that the processed input is structurally sound before beginning to output it. For example, it ensures that no property is ever assigned more than once in a given section. This method either raises an exception or it doesn't. change_section $writer->change_section($section_name); This method is called each time a new section is going to be written out. If the same section appears twice in a row in the input, this method will still be called between instances of that section. In other words, given this input: [ section_1 => [ a => 1 ], section_1 => [ b => 2 ], ] "change_section" will be called twice: once before the first "section_1" and once before the second "section_1". current_section $writer->current_section This method returns the section currently being written out. finish_section $writer->finish_section This method is called after all of the current section's properties have been written. done_sections my @names = $writer->done_sections; This method returns a list of all sections that have been written out and finished. The fact that a section name is returned by "done_sections" does not mean that there will be no more data for that section, but that at least one entire set of data has been written out for it. stringify_section my $string = $writer->stringify_section($props); This method returns a string assigning all the properties set in the given data. This still will include the section header, if needed. (The only case in which it is not needed is when the "explicit_starting_header" method returns false, no other sections have been done, and the section about to be stringified is the "starting_section". This method is implemented in terms of "stringify_section_header" and "stringify_section_data". stringify_section_data my $string = $writer->stringify_section_data($props) This method returns a string containing a series of lines, each containing a value assignment for the given properties. stringify_value_assignment my $string = $writer->stringify_value_assignment($name => $value); This method returns a string that assigns a value to a named property. If the value is undefined, an empty string is returned. stringify_value my $string = $writer->stringify_value($value); This method returns the string that will represent the given value in a property assignment. stringify_section_header my $string = $writer->stringify_section_header($section_name); This method returns the string (a line) that represents the given section name. Basically, this returns: [section_name] starting_section This method returns the name of the starting section. If this section appears first (as it will, when given a hashref as input) and if "explicit_starting_header" returns false, its section header can be omitted. explicit_starting_header If this method returns true (which it does not, by default), then the section header for the starting section will be emitted, even if it appears first. new my $reader = Config::INI::Writer->new; This method returns a new writer. This generally does not need to be called by anything but the various "write_*" methods, which create a writer object only ephemerally. AUTHOR
Ricardo Signes <rjbs@cpan.org> COPYRIGHT AND LICENSE
This software is copyright (c) 2007 by Ricardo Signes. This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself. perl v5.14.2 2011-12-15 Config::INI::Writer(3pm)
All times are GMT -4. The time now is 03:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy