SMTP issues all of a sudden

[david toub]

Today, it would seem that Comcast started blocking port 25, making it
impossible to send e-mail from .Mac using port 25 to smtp.mac.com. I
can send using smtp.comcast.net, without authentication, however. This
is fine, except that I also need to send mail from my .mac account at
work and other places, and must now change the smtp server settings in
Entourage each time I change location (which I have never had to do!).
Using smtp.mac.com and other ports do not work since these apparently
are not supported (like SSL) at comcast.

Any suggestions, other than changing my SMTP settings each time I'm
using my iBook at a different location? Is there any way to get
SMTP.mac.com to be accepted via a different port (I tried 587 and 110
but Comcast seems not to accept these). Thanks!

 

[Adam Bailey]

Today, it would seem that Comcast started blocking port 25, making it
impossible to send e-mail from .Mac using port 25 to smtp.mac.com. I
can send using smtp.comcast.net, without authentication, however. This
is fine, except that I also need to send mail from my .mac account at
work and other places, and must now change the smtp server settings in
Entourage each time I change location (which I have never had to do!).

Use the SMTP Location AppleScript, located at

Using smtp.mac.com and other ports do not work since these apparently
are not supported (like SSL) at comcast.

Any suggestions, other than changing my SMTP settings each time I'm
using my iBook at a different location? Is there any way to get
SMTP.mac.com to be accepted via a different port (I tried 587 and 110
but Comcast seems not to accept these). Thanks!

smtp.mac.com does appear to be listening on port 587. Complain to
Comcast -- I can't think of any valid reason to restrict that port.

 

[Bailey, Adam K]

smtp.mac.com does appear to be listening on port 587. Complain to
Comcast -- I can't think of any valid reason to restrict that port.

Are you sure they are? I'm connected via Comcast right now and they don't
seem to be monkeying with port 25, although at least one SMTP server I tried
kicked me out because of a bad PTR record. I don't have a Mac.com account to
try, but I successfully sent a message through AOL's SMTP server on port 25.

Perhaps they're still rolling out the blocking and haven't hit me yet.

 

[Adam Bailey]

smtp.mac.com does appear to be listening on port 587. Complain to
Comcast -- I can't think of any valid reason to restrict that port.

Are you sure they are? I'm connected via Comcast right now and they don't
seem to be monkeying with port 25, although at least one SMTP server I tried
kicked me out because of a bad PTR record. I don't have a Mac.com account to
try, but I successfully sent a message through AOL's SMTP server on port 25.

Perhaps they're still rolling out the blocking and haven't hit me yet.

 

[Paul Berkowitz]

Use the SMTP Location AppleScript, located at
<http://homepage.mac.com/berkowit28/FileSharing.html>.

That should be

SMTP Location X

script in the Entourage X scripts directory. It also works in 2004 (and is
also the version needed for 2001 when used in Classic in OS X).

Also you're usually better off downloading my scripts from
<http://macscripter.net/scriptbuilders/> , which is why I put that URL in my
signature here. Since that excellent repository took over from the previous
(and now defunct) AppleScript Central over a year ago, there has never, ever
been a single download problem. It always "just works". Whereas my homepage
(iDisk) URL Adam gives above is subject to all the usual .Mac vagaries (site
unobtainable, .sit files downloading with strange extensions, etc.) They'll
both work, but Macscripter.net is better.

--
Paul Berkowitz
MVP MacOffice
Entourage FAQ Page: <http://www.entourage.mvps.org/faq/index.html>
AppleScripts for Entourage: <http://macscripter.net/scriptbuilders/>

Please "Reply To Newsgroup" to reply to this message. Emails will be
ignored.

PLEASE always state which version of Microsoft Office you are using -
**2004**, X or 2001. It's often impossible to answer your questions
otherwise.

 

[Page Hayes]

i'm having the same issue, I think it's related to having different
outgoing/incoming mail servers. worked for me up until monday. works fine if
incoming and outgoing are the same. I thought it was a comcast issue at
first too, but outlook express handles this fine.

I saw other posts re: apple scripts. but it just seems strange that it was
working and then abruptly stopped!