I can still both initiate and recieve SMTP traffic from both of my Comcast (Eagan, Minneapolis) hosts. I can't see this persisting too long. A lot of people don't have or use Comcast accounts and this would be a dealbreaker. They already monitor for email drones - I don't know why they would need this. -Dave On Tuesday 03 April 2007 22:31:07 Jon Schewe wrote: > Has anyone else run across this? As of today I'm no longer able to send > mail through my mailserver (mtu.net) port 25 as comcast is blocking all > outgoing connections on port 25 for "my protection". -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20070404/e6393e38/attachment.pgp