>> >> reading at the spamhaus site abt PBL i note, >> >> "WARNING! Some post-delivery filters use "full Received line >> traversal" or "deep parsing", where the filter reads all the IPs in >> the Received lines. Legitimate users, correctly sending good mail out >> through their ISP's smarthost, will have PBL-listed IPs show up in the >> first (lowest) Received header where their ISP picks it up. Such mail >> should not be blocked! So, you should tell your filters to stop >> comparing IPs against PBL at the IP which hands off to your mail >> server! That last hand-off IP is the one which PBL is designed to >> check. If you cannot configure your filters that way, then do not use >> PBL to filter your mail." >> >> with the ever-smarter filters available with SA & SARE etc, what -- if >> anything -- should 'we' do/configure differently in SA's confs/ops to >> avoid this issue? >> >> thanks. >> Hi,
unfortunately we cannot do much about it. If the sending mailserver does its job right (says that the connection from the sending end user to itself was authenticated), and SA understands the format of the auth line, SA will do the right thing Now, if the sending server does not include auth token, its customers should complain Wolfgang Hamann
