os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Update and clarify the freebsd-mail-bounces question (why mail to

Browse source 
freebsd.org bounces) to reflect reality.

Reviewed by:	postmaster (dhw)
Discussed on:	-doc
Approved by:	bcr (mentor)
This commit is contained in:
Eitan Adler 2013-02-07 13:52:41 +00:00
parent b1a9e0b408
commit 3629111746
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=40902
1 changed files with 35 additions and 51 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

88
en_US.ISO8859-1/books/faq/book.xml
View file

@ -7643,67 +7643,51 @@ hint.sio.7.irq="12"</programlisting>
<answer>
<para>The <hostid role="domainname">FreeBSD.org</hostid> mail
system implements some of the stricter
system implements some
<application>Postfix</application> checks on incoming mail
and rejects mail that is either misconfigured or is
potential spam. Your mail might bounce for one of the
following reasons:</para>
and rejects mail that is either from misconfigured relays or
otherwise appears likely to be spam. Some of the
specific requirements are: </para>
<itemizedlist>
<listitem>
<para>The email is being sent from a known spam domain or
IP block.</para>
<para>The &os; mail servers reject email from known spam
sources. If you have service through a company or
domain who generates or relays spam, please switch to a
service provider who does not.</para>
<para>The IP address of the SMTP client must
"reverse-resolve" to a forward
confirmed hostname.</para>
</listitem>
<listitem>
<para>The body of the email only contains HTML.</para>
<para>Mail should be sent in plain text only. Please
configure your mail user agent to send plain
text.</para>
</listitem>
<listitem>
<para>The mailer at <hostid
role="domainname">FreeBSD.org</hostid> cannot resolve
the IP address of the connecting host back to a
symbolic name.</para>
<para>Working reverse DNS is a standard requirement for
accepting mail from a host. Set up reverse DNS for your
mail server's IP address. Many home services (DSL,
cable, dialup, etc.) will not give you this option. In
this case, relay your email through your service
provider's mail server.</para>
</listitem>
<listitem>
<para>The hostname given in the EHLO/HELO part of the SMTP
exchange cannot be resolved to an IP address.</para>
<para>A fully qualified, resolvable host name is necessary
in this part of the SMTP dialogue before mail will be
accepted. If you do not have a host name that is
registered in the DNS, then you should use your service
provider's mail server to relay your mail.</para>
</listitem>
<listitem>
<para>Your message had a message ID ending with the string
<quote>localhost</quote>.</para>
<para>Some mail user agents generate bad message IDs which
will not be accepted. You will need to persuade your mail
user agent to generate a valid message ID or else
configure your mail transfer agent to rewrite
them.</para>
<para>The fully-qualified hostname given in the
SMTP conversation (either HELO or EHLO) must resolve
to the IP address of the client.</para>
</listitem>
</itemizedlist>
<para>Other advice to help your mail reach its destination
include:</para>
<itemizedlist>
<listitem>
<para>Mail should be sent in plain text, and messages
sent to mailing lists should generally be no more than
200KB in length.</para>
</listitem>
<listitem>
<para>Avoid excessive cross posting. Choose
<emphasis>one</emphasis> mailing list which seems most
relevant and send it there.</para>
</listitem>
</itemizedlist>
<para>If you still have trouble with email infrastructure at
<hostid role="domainname">FreeBSD.org</hostid> send a note
with the details to
<email>postmaster@freebsd.org</email>; Include a
date/time interval so that logs may be reviewed &mdash;
and note that we only keep one week's worth of mail logs.
(Be sure to specify the time zone or offset from
UTC.)</para>
</answer>
</qandaentry>