MrC wrote:
Jim McIver wrote:
My header_checks file contains:
# Disallow sender-specified routing. This is a must if you relay mail
#for other domains.
/[EMAIL PROTECTED]@]/ 550 Sender-specified routing rejected
This seems prone to many false positives. Many headers have such
patterns. Eg:
X-Amavis-OS-Fingerprint: Linux 2.4-2.6 (NAT!) (firewall!) (up: 815 hrs),
From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
note that it also matches the message-id of the rejected message.
Message-Id: <[EMAIL PROTECTED]>
it looks like he copied Jim's cheat sheet but put the rules in
header_checks instead of smtpd restrictions.
now, I woul'nt even use these in smtpd restrictions. I'm not seeing any
spam with such patterns. so why reject valid characters if it doesn't
even reduce spam?
Perhaps you need to be more restrictive, matching only a particular
header, and allow for valid email addresses as above.
he needs to put the checks in a check_sender_access instead.
