I'm getting nothing but timeouts at this point to any of att's mail servers. Nothing going through at all. -------------------------- Brian Bruns The Summit Open Source Development Group Open Solutions For A Closed World / Anti-Spam Resources http://www.sosdg.org ICQ: 8077511 ----- Original Message ----- From: "Marshall Eubanks" <tme@multicasttech.com> To: "Mike Tancsa" <mike@sentex.net> Cc: <nanog@nanog.org> Sent: Tuesday, October 21, 2003 5:57 PM Subject: Re: Heads-up: AT&T apparently going to whitelist-only inbound mail
Here is my experience (names are changed to protect...) :
Failed to deliver to 'AAA@att.com' SMTP module(domain att.com) reports: message text rejected by ckmsi2.att.com: 550 5.7.1 Your message was rejected as possible spam. Please call your AT&T contact. [3]
Failed to deliver to 'BBB@att.com' SMTP module(domain att.com) reports: message text rejected by ckmsi2.att.com: 550 5.7.1 Your message was rejected as possible spam. Please call your AT&T contact. [3]
Failed to deliver to 'CCC@att.com' SMTP module(domain att.com) reports: message text rejected by ckmsi2.att.com: 550 5.7.1 Your message was rejected as possible spam. Please call your AT&T contact. [3]
Failed to deliver to 'DDD@att.com' SMTP module(domain att.com) reports: message text rejected by ckmsi2.att.com: 550 5.7.1 Your message was rejected as possible spam. Please call your AT&T contact. [3]
Failed to deliver to 'EEE@att.com' SMTP module(domain att.com) reports: message text rejected by ckmsi2.att.com: 550 5.7.1 Your message was rejected as possible spam. Please call your AT&T contact. [3]
On Tuesday, October 21, 2003, at 05:46 PM, Mike Tancsa wrote:
Wow, this sounds like a pretty extreme shotgun approach. (or is it April 1st somewhere). Is AT&T going to make this whitelist publicly available ? Perhaps if there was some global white list that everyone could consult against, it might be a little more useable. Still, what do you do about multi-stage relays ?
---Mike