11-20-2012
@bipin ......you are awesome ....... thanks
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
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
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
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
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
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
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
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
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
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
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
flaw(7) Miscellaneous Information Manual flaw(7)
NAME
flaw - a Lua OO management framework for awesome WM widgets
DESCRIPTION
flaw stands for Fully Loaded AWesome. It is a LUA object oriented library providing a thin abstraction layer above awesome widgets. It is
aimed at being simple and resources efficient.
To achieve these goals, flaw provides the following concepts.
gadgets
To add functionality to awesome widgets, flaw defines gadget objects, which are a wrapper around a widget. All gadgets have proper-
ties, events, a refresh mechanism and a data provider (see below). Gadgets can wrap all awesome widget type, namely text boxes,
image boxes, graphs or progress bars. flaw provides many gadgets for common system information (like CPU or memory activity).
provider
flaw tries to minimise system access and data refresh. Since all information do not have the same expiration rate, all gadgets
refresh independently. And since some gadgets can share information, all data is provided by providers which can be shared among
gadgets. Providers maintain status data from the system and refreshes only when necessary (ie. when the gadget with the shortest
refresh rate demands it).
events Events are a way for the user to modify the gadget behaviour or properties when some conditions are met. An event is composed of a
trigger, which computes the condition, and an action. Event triggers are tested by the providers only when data changes. Both the
condition and the action are provided by the user.
USAGE
flaw depends on the lua-filesystem package which can be found http://luaforge.net/projects/luafilesystem. Once installed, the following
statement must be inserted in awesome configuration before any flaw gadget or mechanism is used.
require('flaw')
Using flaw consists in creating gadgets, passing them parameters to customize their display and events to add some behaviour to them, and
then adding them in a wibox like any other awesome widget. flaw and awful gadgets can live together. The complete flaw documentation is
available in Luadoc format. Enter the following command to generate it.
LUA_PATH="path_toflaw/doclet/html/?;;" luadoc -d html --nofiles *.lua
DIAGNOSTICS
flaw tries to recover upon bad invocations. When something wrong occurs, it outputs warning or error messages to stderr (for example, if
awesome was started with xsession, output will be found in ~/.xsession-errors ).
BUGS
Certainly a lot.
AUTHOR
David Soulayrol <david.soulayrol at gmail dot net>
SEE ALSO
awesome(1), awesome-client(1), awesomerc(5)
FEBRUARY 2009 flaw(7)