Sponsored Content
Full Discussion: mail problem
Top Forums Shell Programming and Scripting mail problem Post 302306038 by TonyFullerMalv on Friday 10th of April 2009 03:49:11 PM
Old 04-10-2009
Add a line to the file:
/etc/mail/aliases
e.g.:
Code:
GROUP_ALERT: mailuser1@foo.com, mailuser2@foo.com

with one or more email addresses, comma separated.

Then run the command:
Code:
$ newaliases

to make sendmail to see the changes to the alias list.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Problem with mail

what I have to write in a shell that every time that it arrives a new e-mail has to perform a program taking some data from the e-mail. (2 Replies)
Discussion started by: mmistero
2 Replies

2. UNIX for Advanced & Expert Users

mail problem !!

Hi, Below a try to send an email to a local user can be seen. I can NOT send e-mail anywhere, but I receive email perfectly. <pre> isgsi01(root)10: mail aris < /home/aris/mail2send dbm map "Alias0": unsafe map file /etc/mail/aliases: No such file or directory </pre> ..... but the... (3 Replies)
Discussion started by: guest100
3 Replies

3. UNIX for Dummies Questions & Answers

mail problem (NOT Mail or Mail.app)

When I try to use the CLI mail, I get the following error. What's wrong? Welcome to Darwin! % mail root Subject: test test . EOT % /etc/mail/sendmail.cf: line 81: fileclass: cannot open /etc/mail/local-host-names: Group writable directory Do I just need to change the... (1 Reply)
Discussion started by: chenly
1 Replies

4. UNIX for Dummies Questions & Answers

Problem with mail.

Hello! I have two servers with Solaris 2.7 I send mail from first to second. The first is also dns. It's known as "ns.oldb.pkb", second is "dev.pkb". Ping works successful from 1 to 2 and vice verse. But when I am trying on first server : sendmail -v user@dev.pkb < /etc/motd it is... (3 Replies)
Discussion started by: Colf
3 Replies

5. OS X (Apple)

mail problem

i have mac os x 2.2 jaguar and Mail wont open any links? When i click on them it just does nothing. does anybody know why/how to fix it? please help me.. thanks, blip (4 Replies)
Discussion started by: Blip
4 Replies

6. UNIX for Dummies Questions & Answers

mail problem

if ping $1 3 then { sleep 1 echo "HELO domain.co.uk" sleep 1 echo "MAIL FROM: mark@domain.co.uk" sleep 1 echo "RCPT TO: markms@domain.co.uk" sleep 1 echo "DATA" echo "This is a test from a file." echo "." echo "quit" } | telnet $1 25 else echo problem fi The above is... (1 Reply)
Discussion started by: markms
1 Replies

7. Shell Programming and Scripting

problem with Mail !

I have a o/p file called a1.txt from a script. I m mailing this file but the problem is that in the mail the format is comming different. Contents of a1.txt ------------------------------------ Meter 090845086LG is now Made AMR Active Meter 090845088LG is now Made AMR Active Meter... (4 Replies)
Discussion started by: ali560045
4 Replies

8. Red Hat

Mail Problem. Maybe, it is a DNS Problem!

Hi, i've a redhat linux 9 upadated by redhat from 7 version to 9 version. A couple of days ago i was a problem with my mail, in other words i'm not able to get any email nor to send any email. I've a proxy configuration and i tried to set iptables in order to verify the port. The 110,255 and 995... (1 Reply)
Discussion started by: pintalgi
1 Replies

9. UNIX for Advanced & Expert Users

HP UX mail problem

I am uxing HP UX mailx, I want to send mail with: 1) to list 2) cc list 3) sender address 4) mail body 5) subject 6) attachment I am using : (cat cc_list; cat mail_body; ux2dos file_1 | uuencode attachment.txt)|mailx -m -s "subject" -r sender@abc.com recepient@abc.com cc_list... (2 Replies)
Discussion started by: gautamadak
2 Replies

10. UNIX for Dummies Questions & Answers

Mail Problem

Hi All, I am having a problem that is very similar to the one being discussed here. I am using OS X and am trying to send mail from the OS X Terminal to my GMail account. The mail seems to go through, but gets stuck at Google's servers. I have a log file from the /var/mail directory that... (0 Replies)
Discussion started by: danielsutton
0 Replies
NMUDIFF(1)						      General Commands Manual							NMUDIFF(1)

NAME
nmudiff - email an NMU diff to the Debian BTS SYNOPSIS
nmudiff [options] DESCRIPTION
nmudiff should be run in the source tree of the package being NMUed, after the NMU is built. It assumes that the source packages (specifi- cally, the .dsc and any corresponding tar and diff files) for both the previous version of the package and the newly built NMU version are in the parent directory. It then uses debdiff to generate a diff between the previous version and the current NMU, and either runs mutt or an editor (using sensible-editor) so that the mail message (including the diff) can be examined and modified; once you exit the editor the diff will be mailed to the Debian BTS. The default behaviour is that if exactly one bug is closed by this NMU, then that bug will be mailed, otherwise a new bug will be submit- ted. This behaviour may be changed by command line options and configuration file options. OPTIONS
--new Instead of mailing the bug reports which are to be closed by this NMU, a new bug report is submitted directly to the BTS. --old Send the bug report to all of the bugs which are being closed by this NMU, rather than opening a new bug report. This option has no effect if no bugs are being closed by this NMU. --mutt Use mutt(1) for editing and sending the message to the BTS (default behaviour). This can be controlled using a configuration file option (see below). --no-mutt Use sensible-editor(1) to edit the message and then mail it directly using /usr/bin/sendmail. This can be controlled using a con- figuration file option (see below). --sendmail SENDMAILCMD Specify the sendmail command. The command will be split on white space and will be interpreted by the shell. Default is /usr/sbin/sendmail. The -t option will be automatically added if the command is /usr/sbin/sendmail or /usr/sbin/exim*. For other mailers, if they require a -t option, this must be included in the SENDMAILCMD, for example: --sendmail="/usr/sbin/mymailer -t". This can also be set using the devscripts configuration files; see below. --from EMAIL If using the sendmail (--no-mutt) option, then the email to the BTS will be sent using the name and address in the environment vari- ables DEBEMAIL and DEBFULLNAME. If these are not set, then the variables EMAIL and NAME will be used instead. These can be over- ridden using the --from option. The program will not work in this case if an email address cannot be determined. --delay DELAY Indicate in the generated mail that the NMU has been uploaded to the DELAYED queue, with a delay of DELAY days. The default value is XX which adds a placeholder to the e-mail. A value of 0 indicates that the upload has not been delayed. This can also be set using the devscripts configuration files; see below. --no-delay, --nodelay Equivalent to --delay 0. --no-conf, --noconf Do not read any configuration files. This can only be used as the first option given on the command-line. --help Display a help message and exit successfully. --version Display version and copyright information and exit successfully. CONFIGURATION VARIABLES
The two configuration files /etc/devscripts.conf and ~/.devscripts are sourced in that order to set configuration variables. Command line options can be used to override configuration file settings. Environment variable settings are ignored for this purpose. The currently recognised variables are: NMUDIFF_DELAY If this is set to a number, e-mails generated by nmudiff will by default mention an upload to the DELAYED queue, delayed for the specified number of days. The value 0 indicates that the DELAYED queue has not been used. NMUDIFF_MUTT Can be yes (default) or no, and specifies whether to use mutt to compose and send the message or not, as described above. NMUDIFF_NEWREPORT This option controls whether a new bug report is made, or whether the diff is sent to the bugs closed by this NMU. Can be maybe (default), which sends to the existing bug reports if exactly one bug is being closed; yes, which always creates a new report, or no, which always sends to the reports of the bugs being closed (unless no bugs are being closed, in which case a new report is always made). BTS_SENDMAIL_COMMAND If this is set, specifies a sendmail command to use instead of /usr/sbin/sendmail. Same as the --sendmail command line option. SEE ALSO
debdiff(1), sensible-editor(1) and devscripts.conf(5). AUTHOR
nmudiff was written and is copyright 2006 by Steinar H. Gunderson and modified by Julian Gilbey <jdg@debian.org>. The software may be freely redistributed under the terms and conditions of the GNU General Public License, version 2. DEBIAN
Debian Utilities NMUDIFF(1)
All times are GMT -4. The time now is 06:13 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy