08-21-2008
Hi deepa
If you need other way to coding in Unix to send mail , I can help you .
~Sakthifire
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
hi, Gurus,
I need some help with sending mail out from my UNIX server:
It is running Solaris 2.6 and the sendmail version is 8.8.
Output of :/usr/lib/sendmail -d0.1 -bt < /dev/null
Version 8.8.8+Sun
Compiled with: LOG MATCHGECOS MIME7TO8 MIME8TO7 NAMED_BIND NDBM NETINET
... (5 Replies)
Discussion started by: b5fnpct
5 Replies
2. UNIX for Dummies Questions & Answers
Using Mailx command i.e
mailx -s "subject" chinni@hotmail.com < \tmp\chin
this command executed sucessfully but not able to receive the mail in chinni@hotmail.com
please help. (1 Reply)
Discussion started by: chinnigd
1 Replies
3. Shell Programming and Scripting
Hi,
I need to write one unix script gor sending a mail notification.
I have to pass the followinf as arguments,from ,to,subject,messege body
Can i use mailx....Please provide the code
Thanks in advance. (1 Reply)
Discussion started by: sudhi
1 Replies
4. Shell Programming and Scripting
Hi,
I am able to generate the log file from my shell file. How can i send the content of the log file through mail to some one.
Raja (6 Replies)
Discussion started by: konankir
6 Replies
5. UNIX for Dummies Questions & Answers
Hi ,
I want to send mail in my script when i am not a super user.
Can some one help me on that ..
Regards,
Balamani (1 Reply)
Discussion started by: Balamani
1 Replies
6. UNIX for Dummies Questions & Answers
rshstatus=`rsh -n lilo /db/p2/oracle/names9208/restart_names.sh`
if $rshstatus <>0 then
errstatus=1
mailx -s "xirsol8dr" ordba@xxx.com >> $log_dr
else if errstatus=0
echo "status to xirsol8dr successful"
can anyone provide if this is t he correct way to do this or is there a better way? (1 Reply)
Discussion started by: bpm12
1 Replies
7. Shell Programming and Scripting
how to run a script using cron job and send the output as attachment via e-mail using unix. please help me.
how my cron job entry should be?
As of now my cron job entry is to run the script at specific time,
15 03 * * * /path/sample.sh | mail -s "Logs" email_id
In the above entry, what... (8 Replies)
Discussion started by: vidhyaS
8 Replies
8. Shell Programming and Scripting
Hi
Can any one please help me how to send mail through unix. (3 Replies)
Discussion started by: parthmittal2007
3 Replies
9. UNIX for Advanced & Expert Users
Hi all,
I want to send a mail for my business needs from outlook account to an unix server (HP-UX) but I don't send any mail. While I can send from the unix server to my outlook account, I can't send from outlook to unix.
How can I achieve this ? How can I send a mail from my outlook or other... (2 Replies)
Discussion started by: igelegin
2 Replies
10. UNIX for Beginners Questions & Answers
Hi Team,
I got a requirement to send a mail to the individual users of a unix server about their respective groups. can some one help me to provide the script as I am unable to write that.
I tried with below lines but I come out with errors.
cat /etc/passwd | awk -F':' '{ print $1}' |... (6 Replies)
Discussion started by: harshabag
6 Replies
LEARN ABOUT LINUX
git-mailinfo
GIT-MAILINFO(1) Git Manual GIT-MAILINFO(1)
NAME
git-mailinfo - Extracts patch and authorship from a single e-mail message
SYNOPSIS
git mailinfo [-k|-b] [-u | --encoding=<encoding> | -n] [--[no-]scissors] <msg> <patch>
DESCRIPTION
Reads a single e-mail message from the standard input, and writes the commit log message in <msg> file, and the patches in <patch> file.
The author name, e-mail and e-mail subject are written out to the standard output to be used by git am to create a commit. It is usually
not necessary to use this command directly. See git-am(1) instead.
OPTIONS
-k
Usually the program removes email cruft from the Subject: header line to extract the title line for the commit log message. This option
prevents this munging, and is most useful when used to read back git format-patch -k output.
Specifically, the following are removed until none of them remain:
o Leading and trailing whitespace.
o Leading Re:, re:, and :.
o Leading bracketed strings (between [ and ], usually [PATCH]).
Finally, runs of whitespace are normalized to a single ASCII space character.
-b
When -k is not in effect, all leading strings bracketed with [ and ] pairs are stripped. This option limits the stripping to only the
pairs whose bracketed string contains the word "PATCH".
-u
The commit log message, author name and author email are taken from the e-mail, and after minimally decoding MIME transfer encoding,
re-coded in the charset specified by i18n.commitencoding (defaulting to UTF-8) by transliterating them. This used to be optional but
now it is the default.
Note that the patch is always used as-is without charset conversion, even with this flag.
--encoding=<encoding>
Similar to -u. But when re-coding, the charset specified here is used instead of the one specified by i18n.commitencoding or UTF-8.
-n
Disable all charset re-coding of the metadata.
--scissors
Remove everything in body before a scissors line. A line that mainly consists of scissors (either ">8" or "8<") and perforation (dash
"-") marks is called a scissors line, and is used to request the reader to cut the message at that line. If such a line appears in the
body of the message before the patch, everything before it (including the scissors line itself) is ignored when this option is used.
This is useful if you want to begin your message in a discussion thread with comments and suggestions on the message you are responding
to, and to conclude it with a patch submission, separating the discussion and the beginning of the proposed commit log message with a
scissors line.
This can enabled by default with the configuration option mailinfo.scissors.
--no-scissors
Ignore scissors lines. Useful for overriding mailinfo.scissors settings.
<msg>
The commit log message extracted from e-mail, usually except the title line which comes from e-mail Subject.
<patch>
The patch extracted from e-mail.
GIT
Part of the git(1) suite
Git 1.8.5.3 01/14/2014 GIT-MAILINFO(1)