On Thursday 20 January 2005 17:42, Nick Smith wrote: > > Let me see if I have this right: > > > > > > [SMTP_A] ---- [COMCAST GW] ---- [SMTP_B] > > > > And you are saying that SMTP_A can _receive_ email, but cannot _send_ > > email? > > that is correct, they are recieving mail on theirdomain.org and sending > on smtp.comcast.net which is now blocked.
Assuming SMTP_A is a client of comcast and SMTP_B is somewshere in the outside world, this is a rediculous setup. Blocking SMTP connections from SMTP_A to SMTP_B directly is reasonable. While it can't prevent intentional spamming from SMTP_A, it does prevent spamming viruses/worms/trojans from abusing SMTP_A. Preventing SMTP_A from using comcast's SMTP server as a smarthost and blocking direct SMTP connections from A to B leaves all comcast customers without email. Well, without outgoing email. There is technical solution to this but there is a social one: Threaten to shoot comcast's policy makers through their heads. ;-) Uwe -- Alternative phrasing of the First Law of Thermodynamics: If you eat it, and you don't burn it off, you'll sit on it. http://www.uwix.iway.na (last updated: 20.06.2004) -- gentoo-user@gentoo.org mailing list
