>From RFC2821 (http://www.faqs.org/rfcs/rfc2821.html)
6.1 Reliable Delivery and Replies by Email
When the receiver-SMTP accepts a piece of mail (by sending a "250 OK"
message in response to DATA), it is accepting responsibility for
delivering or relaying the message. It must take this responsibility
seriously. It MUST NOT lose the message for frivolous reasons, such
as because the host later crashes or because of a predictable
resource shortage.
If there is a delivery failure after acceptance of a message, the
receiver-SMTP MUST formulate and mail a notification message. This
notification MUST be sent using a null ("<>") reverse path in the
envelope. The recipient of this notification MUST be the address
from the envelope return path (or the Return-Path: line). However,
if this address is null ("<>"), the receiver-SMTP MUST NOT send a
notification. Obviously, nothing in this section can or should
prohibit local decisions (i.e., as part of the same system
environment as the receiver-SMTP) to log or otherwise transmit
information about null address events locally if that is desired. If
the address is an explicit source route, it MUST be stripped down to
its final hop.
Cheers,
Phil
----
Phil Randal
Network Engineer
Herefordshire Council
Hereford, UK
> -----Original Message-----
> From: Robert Fitzpatrick [mailto:[EMAIL PROTECTED]
> Sent: 12 May 2006 17:01
> To: SpamAssassin
> Subject: whitelisting without a from address
>
> I posted a whitelist_from_rcvd usage issue the other day and someone
> quickly opened my eyes to notice the message didn't have a
> from address,
> the log showed 'from=<>'. These people are asking that I
> whitelist their
> mail servers. I understand whitelist_from_rcvd uses two
> parameters, the
> first being the from address. Is there a way to whitelist the mail
> server found in the headers alone? Or should I stand to my
> last response
> to them, 'use a from address'.
>
> --
> Robert
>
