07-09-2002
Here is something that might work, but I'm not gonna try it. So no money-back guarantees on this one...
Create a group called "nomail" or something and put titi in it.
Then do:
chgrp nomail /usr/lib/sendmail
chmod 4705 /usr/lib/sendmail
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
when sending the contents of a ascii file to the body of an email then sending it off. it seems sendmail is breaking up the lines with a "!" thus ruining the data. Has this ever happened to anyone?
i am guessing there is a line buffer limit in either the mail command or in sendmail itself.
... (3 Replies)
Discussion started by: Optimus_P
3 Replies
2. UNIX for Dummies Questions & Answers
Ok thats the Problem:
I'm logged in as user "cypher" on my FreeBSD 4.7 and sendmail worked fine but wenn i try to send an EMail as "tobi@provider.org" the mail arrive as "cypher@provider.org". I configured Sendmail with
genericstable "cypher tobi@provider.org"
virtusertable ... (3 Replies)
Discussion started by: Cyvver
3 Replies
3. Shell Programming and Scripting
Hai..I have one question in unix Shell script.Following is the script
System Configuration: lcpu=4 mem=8192MB
kthr memory page faults cpu
----- ----------- ------------------------ ------------ -----------
r b avm fre re pi po fr sr cy ... (1 Reply)
Discussion started by: sollin
1 Replies
4. UNIX for Advanced & Expert Users
gurus,
i need to know 2 things,
first: how can i send mail over the internet in case of system failures/crash?
second: how can i receive SMS alert on my phone in case of failures?
do i need to start any service on my box?
thanks & regards
abhijeet (1 Reply)
Discussion started by: abhijeetkul
1 Replies
5. Shell Programming and Scripting
I send an attachment 123.pdf using the below script:-
<< script content >>
#!/usr/bin/ksh
/usr/lib/sendmail -C sendmail.cf abc@gmail.com << END
Subject: HELLO
`uuencode 123.pdf 123.pdf`
END
However, the message I got in gmail look like:-
begin 644 123.pdf
... garbage ...
... many... (4 Replies)
Discussion started by: pok.fung
4 Replies
6. Solaris
Hi
I have two realtively identical Solaris zones. They both appear to have the same config in relation to sendmail. But, when I send a test email using mailx the first one sends via a mail relay and the other sends via localhost. I need them both to use the relay but can't figure out what is... (0 Replies)
Discussion started by: gregb
0 Replies
7. UNIX for Dummies Questions & Answers
Hi i am having a probleme with my sendmail server. using it as a mta to send out email.
keem on getting this error message back.
----- The following addresses had permanent fatal errors ----- <XXX@XXXX.co.za>
(reason: 554 Denied (Mode: normal))
----- Transcript of session... (1 Reply)
Discussion started by: sakie
1 Replies
8. Shell Programming and Scripting
Hello All,
I have been trying to execute a script to send me alerts using a log file of a job which can be success or failed. But when I try to send log as attachment using sendmail it does not not send any email but job runs fine. I am not able to debug it. Please help to get the correct code.... (1 Reply)
Discussion started by: Rossdba
1 Replies
9. Shell Programming and Scripting
Hi,
I am trying to send log file of a job run in unix machince through sendmail.Though I am able to send the text but it is not sending as attachment.
Could you please look into the code and let me know where I have gone wrong
fdate=`date %Y%j`... (2 Replies)
Discussion started by: Rossdba
2 Replies
LEARN ABOUT FREEBSD
mailwrapper
MAILWRAPPER(8) BSD System Manager's Manual MAILWRAPPER(8)
NAME
mailwrapper -- invoke appropriate MTA software based on configuration file
SYNOPSIS
Special. See below.
DESCRIPTION
At one time, the only Mail Transfer Agent (MTA) software easily available was sendmail(8). As a result of this, most Mail User Agents (MUAs)
such as mail(1) had the path and calling conventions expected by sendmail(8) compiled in.
Times have changed, however. On a modern UNIX system, the administrator may wish to use one of several available MTAs.
It would be difficult to modify all MUA software typically available on a system, so most of the authors of alternative MTAs have written
their front end message submission programs so that they use the same calling conventions as sendmail(8) and may be put into place instead of
sendmail(8) in /usr/sbin/sendmail.
sendmail(8) also typically has aliases named mailq(1) and newaliases(1) linked to it. The program knows to behave differently when its
argv[0] is ``mailq'' or ``newaliases'' and behaves appropriately. Typically, replacement MTAs provide similar functionality, either through
a program that also switches behavior based on calling name, or through a set of programs that provide similar functionality.
Although having drop-in replacements for sendmail(8) helps in installing alternative MTAs, it essentially makes the configuration of the sys-
tem depend on hand installing new programs in /usr. This leads to configuration problems for many administrators, since they may wish to
install a new MTA without altering the system provided /usr. (This may be, for example, to avoid having upgrade problems when a new version
of the system is installed over the old.) They may also have a shared /usr among several machines, and may wish to avoid placing implicit
configuration information in a read-only /usr.
The mailwrapper utility is designed to replace /usr/sbin/sendmail and to invoke an appropriate MTA instead of sendmail(8) based on configura-
tion information placed in ${LOCALBASE}/etc/mail/mailer.conf falling back on /etc/mail/mailer.conf. This permits the administrator to con-
figure which MTA is to be invoked on the system at run time.
Other configuration files may need to be altered when replacing sendmail(8). For example, if the replacement MTA does not support the -A
option with mailq(1), daily_status_include_submit_mailq should be turned off in /etc/periodic.conf.
FILES
Configuration for mailwrapper is kept in ${LOCALBASE}/etc/mail/mailer.conf or /etc/mail/mailer.conf. /usr/sbin/sendmail is typically set up
as a symbolic link to mailwrapper which is not usually invoked on its own.
EXIT STATUS
The mailwrapper utility exits 0 on success, and >0 if an error occurs.
DIAGNOSTICS
The mailwrapper will print a diagnostic if its configuration file is missing or malformed, or does not contain a mapping for the name under
which it was invoked.
SEE ALSO
mail(1), mailq(1), newaliases(1), mailer.conf(5), periodic.conf(5), sendmail(8)
HISTORY
The mailwrapper utility first appeared in NetBSD 1.4 and then FreeBSD 4.0.
AUTHORS
Perry E. Metzger <perry@piermont.com>
BUGS
The entire reason this program exists is a crock. Instead, a command for how to submit mail should be standardized, and all the "behave dif-
ferently if invoked with a different name" behavior of things like mailq(1) should go away.
BSD
August 27, 2014 BSD