44 lines
1.7 KiB
HTML
44 lines
1.7 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
|
|
<!--Converted with LaTeX2HTML 96.1-c (Feb 29, 1996) by Nikos Drakos (nikos@cbl.leeds.ac.uk), CBLU, University of Leeds -->
|
|
<HTML>
|
|
<HEAD>
|
|
<TITLE>Dealing with Bounced Mail</TITLE>
|
|
</HEAD>
|
|
<BODY LANG="EN">
|
|
<A HREF="node1.html"><IMG WIDTH=65 HEIGHT=24 ALIGN=BOTTOM ALT="contents" SRC="contents_motif.gif"></A> <BR>
|
|
<B> Next:</B> <A HREF="node227.html">Domain Name Service Related </A>
|
|
<B>Up:</B> <A HREF="node223.html">Typically Used sendmail.m4 Parameters</A>
|
|
<B> Previous:</B> <A HREF="node225.html">Defining the Local Mailer</A>
|
|
<BR> <P>
|
|
<H3><A NAME="SECTION0017323000">Dealing with Bounced Mail</A></H3>
|
|
<P>
|
|
<A NAME="8406"></A>
|
|
<A NAME="7982"></A>
|
|
<P>
|
|
<P><P>
|
|
<P>
|
|
Many sites find that it is important to ensure that mail is sent and received
|
|
with close to a 100% success rate. While examining syslogd(8) logs
|
|
is helpful, the local mail administrator generally needs to see the headers
|
|
on bounced mail in order to determine if the mail was undeliverable because
|
|
of user error or a configuration error on one of the systems involved.
|
|
<P>
|
|
Defining POSTMASTERBOUNCE results in a copy of each bounced message
|
|
being set to the person defined as Postmaster for the system.
|
|
<P>
|
|
Unfortunately, setting this parameter also results in the <em>text</em> of the
|
|
message being sent to the Postmaster, which potentially has related privacy
|
|
concerns for people using mail on the system.
|
|
<P>
|
|
Site postmasters should in general attempt to discipline themselves (or do so
|
|
via technical means through shell scripts that delete the text of the bounce
|
|
messages they receive) from reading mail not addressed to them.
|
|
<P>
|
|
<BR> <HR>
|
|
<P><ADDRESS>
|
|
<I>Andrew Anderson <BR>
|
|
Thu Mar 7 23:22:06 EST 1996</I>
|
|
</ADDRESS>
|
|
</BODY>
|
|
</HTML>
|