On Thu, 8 Dec 2005 14:52:53 -0500, KMF-MIS <[EMAIL PROTECTED]> wrote:
>As I mentioned, RFC 1893 defines enhanced status codes, one of which indicates
>no such user
The DSN (Delivery Status Notification) codes in RFC 1893 do not apply during
the SMTP transaction, which is currently where the receiving mail server is
deciding to perform the rejection based on the spamcop (or other BL)
listing. DSN codes would only appear in a 'bounce' email generated by the
receiving site after first receiving the email and then deciding to reject
it for policy reasons. So they are not useful here. The recent trend in
anti-spam practices is to reject at the SMTP HELO level so the spam stays on
the spammer's server and never comes to yours. The problem is if you use a
BL like spamcop's that has a high false-positive rate you can (unknowingly)
reject a significant amount of wanted email.
>4 days gives plenty of time for the server to be white listed or the server to
>be removed from the BL, 50 bounces could happen in a couple of hours if the
>list is particularly active giving no chance for corrective action to be taken
OK, I'll increase it to 100.
>Is the list always sent via 209.119.0.21, or can it be sent via one of many
>servers? If multiple servers, can you supply a list of their addresses?
Our mail load is spread across multiple servers. Different types of
messages also go out by different servers. We are trying to keep List
Messages only going through one of 3 servers. Admin messages (confirms,
bounces, errors, etc) go via yet other servers. These messages are most
likely to include the spamtrap addresses so these servers are BL'd
frequently while the list message servers do not.
209.119.0.0/24 covers the range is you want to whitelist us.
--
----------------------------------------
To unsubscribe, mailto: [EMAIL PROTECTED]
Is your picture included in the Official Win-Home List Members Profiles Page?
http://www.besteffort.com/winhome/Profiles.html
If not, write to: [EMAIL PROTECTED]
