I am suddenly blocked from all comcast.net emails. . .

[enzosf]

Version: 2008
Operating System: Mac OS X 10.5 (Leopard)
Processor: Intel
Email Client: pop

I suspected everything but Entourage for this problem, thought it was their spam blocker, but I finally narrowed it down to Entourage. If I go to my provider (hostway) and use their webmail, or Mac Mail, I am fine, but from entourage only, starting 2 months ago, whenever I send to any comcast.net email address, I get

----- The following addresses had permanent fatal errors ----- then some variable text about spam blocker. They can send to me fine, but i cannot send to them. They've added me to their address book (I was already there) and as far as i know it is only the comcast domain.

Any suggestions? For now my workaround is to go outside of Entourage (which includes group emails) whenever I have a comcast.net recipient.

thanks
enzosf

 

[Adam Bailey]

I suspected everything but Entourage for this problem, thought it was
their spam blocker, but I finally narrowed it down to Entourage. If I go
to my provider (hostway) and use their webmail, or Mac Mail, I am fine,
but from entourage only, starting 2 months ago, whenever I send to any
comcast.net email address, I get

----- The following addresses had permanent fatal errors ----- then some
variable text about spam blocker. They can send to me fine, but i
cannot send to them. They've added me to their address book (I was
already there) and as far as i know it is only the comcast domain.

Talk to your provider. Comcast doesn't like the outgoing SMTP server you're
using.

 

[Ed Kimball]

Talk to your provider. Comcast doesn't like the outgoing SMTP server you're
using.

I would add that, since Mac Mail seems to work fine, Entourage must be using
a different SMTP server. Set Entourage up so that it uses the same SMTP
settings you're using in Mac Mail.

 

[hugh Jass]

Comcast has a particularly virulent spam filter. They're really bad about
blocking SMTP servers. In fact, I get annoyed when I see email from a
comcast address in my inbox because one out of three times there's some kind
of problem.

 

[William Smith [MVP]]

I suspected everything but Entourage for this problem, thought it was
their spam blocker, but I finally narrowed it down to Entourage. If I
go to my provider (hostway) and use their webmail, or Mac Mail, I am
fine, but from entourage only, starting 2 months ago, whenever I send
to any comcast.net email address, I get

----- The following addresses had permanent fatal errors ----- then
some variable text about spam blocker. They can send to me fine, but
i cannot send to them. They've added me to their address book (I was
already there) and as far as i know it is only the comcast domain.

Any suggestions? For now my workaround is to go outside of Entourage
(which includes group emails) whenever I have a comcast.net
recipient.

I have Comcast as well and something has indeed changed within the past
2-3 weeks with their mail servers. While at home on their network I use
to be able to send out mail with no special outgoing settings but now I
must authenticate. I think they've *stupidly* blocked port 25 to their
own outgoing mail servers.

Try this...

Edit your Comcast account under Tools --> Accounts...

Under the "Sending mail" section at the bottom of the Account Settings
tab click the "Click here for advanced sending options button".

Enable the "Override default SMTP port" and enter 587 for your port number.

Enable "SMTP server requires authentication" and select "Use same
settings as receiving mail server".

Hope this helps!

--

bill

Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>
YouTalk <http://nine.pairlist.net/mailman/listinfo/youtalk>
Twitter: follow <http://twitter.com/meck>

 

[Diane Ross]

Enable the "Override default SMTP port" and enter 587 for your port number.

Enable "SMTP server requires authentication" and select "Use same
settings as receiving mail server".

I had to do this for comcast account also. My change happened a while ago
because my account had been compromised.