M Z Rahman wrote:
this header doesn't have the "Return-path:" header at all.
There is no Return-Path header before the final delivery, and
so you can't expect it verbatim in a Non-Delivery message.
Your address (= the To of the bounce) would be the Return-Path.
Question: if AOL had SPF implemented (current SPF clients)
at their relay servers, would the SPF client be able to
detect this or it would simply quit 'cause there is no HELO
or EHLO in the headers?
If AOL would support SPF, then they'd check the sending IP
(= 80.59.43.4) against the sender policy of zort.org. In the
worst case that results in a "?all" and has no effect. That
is your sender policy, change it, if you don't like it.
BTW, there is a HELO 4.Red-80-59-43.pooles.rima-tde.net in
the Received header, and it's okay for 80.59.43.4
SPF will just terminate with "unknown" error when it can't
find any FQDN in the HELO argument.
But 4.Red-80-59-43.pooles.rima-tde.net _is_ a FQDN, and the
result "unknown" won't help you. You (= zort.org) need a
"-all" if you want AOL to reject this mail. But AFAIK they
don't do this at the moment, so the "-all" would only help in
discussions with postmaster@ and abuse(_at_)AOL (= why they bounce
mails to forged addresses, and why they are so ignorant).
is it wise to drop any email that does not have HELO or
EHLO argument?
It's wise to read STD 10 and RfC 2821 <gd&r> You don't find
it as header, but often it's logged in the time stamp lines
(= Received: header)
Bye, Frank