[sf-lug] For those COMCAST customers having trouble mailing -- time to switch ports

[Rick Moen]

Quoting Ken Shaffer (kenshaffer80 at gmail.com):

> Well, Comcast finally got around to killing access to their  simple mail
> transport protocol (smtp) server's use of port 25 (for unencrypted mail).
> The usual error you see is a failure to authenticate, and your mail is not
> sent.  Switch to port 465  from 25 for your outgoing mail (just selecting
> the SSL option works in some mail clients).  If you have devices not
> capable of encryption, (can't use 465), switch from 25 to 587, and things
> should work again.  See the Comcast internet forums for their reasoning --
> security of course. Apologies in advance for any inexact terminology.

You covered it commendably!

Some recent SVLUG posts on the same matter:
http://lists.svlug.org/archives/svlug/2013-March/057950.html
   Florin Andrei asks help
http://lists.svlug.org/archives/svlug/2013-March/057951.html
  Robert Lanning says it's Comcast Residential, but not Business
http://lists.svlug.org/archives/svlug/2013-March/057956.html
  Steve Litt suggests alternatives to running an MTA
http://lists.svlug.org/archives/svlug/2013-March/057957.html
  Yrs. truly describes 587/tcp and 465/tcp setup
http://lists.svlug.org/archives/svlug/2013-March/057959.html
  Yrs. truly agrees that Raw Bandwidth Communications rules.