Unable to send using IMAP settings in Entourage

[skentfr]

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

Have previously had no problem but now can no longer send using the mobile.me IMAP server.

Recently was forced to change my ISP/FAI from Club-Internet to Neuf/SFR (because they bought Club-Internet) and I suspect the problem lies there (have other unrelated problems with this ISP too!).

I set up the account using the inbound server mail.me.com and outbound as smtp.mac.com. I've tried smtp.me.com but that makes no difference, and I've tried secure connection using receiving mail settings and overriding port 25 with 587.

Nothing works. All I get is "Entourage cannot find the server. Verify the server information is entered correctly in the Account Settings, and that your DNS settings in the Network pane of System Preferences are correct."

All my other accounts that I set up for POP work fine. Of course not when I'm on the road with my Macbook but that's another issue.

Anyone any ideas? Anyone else experienced the joys of dealing with Neuf/SFR and won?

 

[Ed Kimball]

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

Have previously had no problem but now can no longer send using the mobile.me
IMAP server.

Recently was forced to change my ISP/FAI from Club-Internet to Neuf/SFR
(because they bought Club-Internet) and I suspect the problem lies there (have
other unrelated problems with this ISP too!).

I set up the account using the inbound server mail.me.com and outbound as
smtp.mac.com. I've tried smtp.me.com but that makes no difference, and I've
tried secure connection using receiving mail settings and overriding port 25
with 587.

Nothing works. All I get is "Entourage cannot find the server. Verify the
server information is entered correctly in the Account Settings, and that your
DNS settings in the Network pane of System Preferences are correct."

All my other accounts that I set up for POP work fine. Of course not when I'm
on the road with my Macbook but that's another issue.

Anyone any ideas? Anyone else experienced the joys of dealing with Neuf/SFR
and won?

FWIW, I use MobileMe using smtp.me.com. Under Advanced sending options, I
have set "Server requires authorization" with the same info as the incoming
mail, no port override, no SSL. I am having no problems.

You might to contact your "new" ISP.

 

[skentfr]

Thanks Ed. I had no problems too until recently. I'll contact the ISP as you suggest.

 

[skentfr]

Ed, it occured to me to see if Mac's Mail worked, and it did. Therefore I figured it wasn't an ISP issue per se but was, if not unique, then particular to the Entourage email client.

I checked the Preference/Account/Edit server list/Advanced settings in Mail and the only difference I saw was that in Mail the default was SSL and the default ports were 25, 465 & 587. I therefore checked 'SSL' & 'overide default SMTP port'. First I input 465 to no avail and then 587 and lo & behold it worked!

Would therefore be nice to see Entourage have the same flexibility of automatically overiding the same 3 ports. All in the name of Spam fighting I guess?

Thought I'd share this in case anyone else has/is encountering the problem with changes wrought by their ISP/FAI.

Stuart

 

[Ed Kimball]

Ed, it occured to me to see if Mac's Mail worked, and it did. Therefore I
figured it wasn't an ISP issue per se but was, if not unique, then particular
to the Entourage email client.

I checked the Preference/Account/Edit server list/Advanced settings in Mail
and the only difference I saw was that in Mail the default was SSL and the
default ports were 25, 465 & 587. I therefore checked 'SSL' & 'overide default
SMTP port'. First I input 465 to no avail and then 587 and lo & behold it
worked!

Would therefore be nice to see Entourage have the same flexibility of
automatically overiding the same 3 ports. All in the name of Spam fighting I
guess?

Thought I'd share this in case anyone else has/is encountering the problem
with changes wrought by their ISP/FAI.

Stuart

Thanks for the feedback. I'm glad you got it working.