Can't send mail

[Tom McCatherine]

I have just upgraded to Office 2004 from Office V.X and now I'm unable to
send mail. There is no problem, however, with receiving mail.

I have an iMac G4, running OS X, Version 10.3.4, and am using DSL service
through AT&T.

Entourage Version 11.0.0 is configured exactly as the older version of
Entourage had been, overriding the default SMTP port to 465. Reverting to
the default port fails to eliminate the problem.

It is obvious from reading the AT&T Mac newsgroups that many others are
experiencing this same problem. I'm wondering if others on this newsgroup
have encountered the same problem and, if so, were able to correct it. Is
this an issue that Microsoft is working on?

The older version of Entourage still works fine, so I am using it for my
mail.

Any help would be appreciated.

Tom

 

[Adam Bailey]

I have just upgraded to Office 2004 from Office V.X and now I'm unable to
send mail.

What happens when you try? What error are you encountering?

How /do/ you have your SMTP server information configured?

 

[chris]

I also have EXACTLY the same problem! And I am connecting through
forthnet (provider).
Tha funny thing is that when I tried to test it through panafonet (provider)
everthing worked perfectly!!!

I really need help!
And my problem is that I need to use Entourage 2004 because the previous
version is unable to recognise all of the encondings of some email I receive
from PC's...
If you find any solution please post it immediately!!!
I'll do the same!
Thanks a lot
chris

 

[Guest]

All the configurations are correct, I have also checked them more than 10
times with my internet provider, and I have also tried to set up a new
account, and tried to import the settings from my previous mail...
The outgoing mail server is not responding!
It gives me the message that it can't find the outgoing server.
BUT, whit the EXACT same settings for Entourage X it works!

 

[Barry Wainwright]

Double check the authentication.

In the account settings window, click on 'advanced sending option' and try
selecting/deselecting "This server requires authentication". This is the
most common cause of trouble with sending mail problems.

 

[Jeff Sumner]

All the configurations are correct, I have also checked them more than 10
times with my internet provider, and I have also tried to set up a new
account, and tried to import the settings from my previous mail...
The outgoing mail server is not responding!
It gives me the message that it can't find the outgoing server.
BUT, whit the EXACT same settings for Entourage X it works!

Have you tried checking the "Send and Receive" schedule to see if both send
and receive actions are set? Mine weren't.

 

[chris]

I have the same settings for send and receive as I had in my previous
programms.
Is there something particular that I have to fix?
I am trying to send a test message to myself and the message I get back is
that it can't connect to the outgoing server.
What settings have you made for the send and receive schedule?

 

[Charlie]

Michigan State University email users are not able to send messages
with Entourage 2004 either. Settings are all right (checked a million
times). Everything was fine in Entourage X and everyone I know who is
using POP with Entourage 2004 now cannot send messages (but they can
receive them). IMAP has problems sending messages to people outside
of the MSU network. I like Entourage 2004, but we are not going to
buy licenses until it works with the MSU email system.

Everyone asks so here are the errors:

While "Connecting securely to mail.msu.edu" (which is required in most
cases) I get an error -17895 "Connection to the server failed or was
dropped."

This problem is not just with my client. Everyone I know at MSU with
entourage 2004 cannot send mail.

 

[Tom McCatherine]

I have tried all the suggestions posted here, to no avail.

When I try to send mail, it remains in the outbox for an agonizingly long
time until I finally get an Error 111 message: "An operation on the server
timed out . . ." etc.

The settings are exactly as they were in v. X:

SMTP provider is imailhost.worldnet.att.net
Checked - SMTP service requires secure connection (SSL)
Checked - Override default SMTP port: 465
Checked - SMTP server requires authentication
Checked - Use same settings as receiving mail server

Toggling the authentication option does not solve the problem. Neither does
reverting to the default SMTP port.

At this point (he said in frustration), it seems that the Entourage upgrade
is useless to me.

Tom

 

[pete mac]

yep this is still happening to me too! I am at the university of sydney -
exchange X works fine, exchange 2004 won't function at all, neither send or
recieve for me.

 

[Adam Bailey]

I have just upgraded to Office 2004 from Office V.X and now I'm unable to
send mail. There is no problem, however, with receiving mail.

I have an iMac G4, running OS X, Version 10.3.4, and am using DSL service
through AT&T.

This just in:
http://wurd.com/cl_ssl_osx_enabler.php

 

[Tom McCatherine]

Thanks for the response, Adam. I have already downloaded SSL Enabler but
have not installed it, preferring to use this only as a last resort if no
other remedy is available.

The WURD page points out that, with SSL Enabler, you can use "programs that
are not capable of making secure connections to AT&T Worldnet." I'm left
wondering how Entourage lost this capability from v.X (where there was no
problem) to Entourage 2004.

I can install and try to use SSL Enabler if I must, but it seems to be a
roundabout way of dealing with an issue that apparently is inherent in the
Microsoft application.

Again, thanks for the reponse.

This just in:
http://wurd.com/cl_ssl_osx_enabler.php

And here's a further description from a subsequent post of mine:

When I try to send mail, it remains in the outbox for an agonizingly long
time until I finally get an Error 111 message: "An operation on the server
timed out . . ." etc.

The settings are exactly as they were in v. X:

SMTP provider is imailhost.worldnet.att.net
Checked - SMTP service requires secure connection (SSL)
Checked - Override default SMTP port: 465
Checked - SMTP server requires authentication
Checked - Use same settings as receiving mail server

Toggling the authentication option does not solve the problem. Neither does
reverting to the default SMTP port.

At this point (he said in frustration), it seems that the Entourage upgrade
is useless to me.

 

[Charlie]

The SSL Enabler made Entourage 2004 worked for me, but I agree that it
is not a great solution. Entourage should work without the SSL
enabler, especially considering people are paying for the software.
Eudora and Apple's Mail work and are free (if you use Eudora in
sponsor mode).

 

[Chap]

I am having the same problem, but only since hooking up to an airport
base station. Before that I had no problem sending mail in Entourage.
Somewhere i recently read that sending mail over a network won't work
until some change was made. know anything about that?

 

[Chap]

I am having the same problem, but only since hooking up to an airport
base station. Before that I had no problem sending mail in Entourage.
Somewhere i recently read that sending mail over a network won't work
until some change was made. know anything about that?

 

[Adam Bailey]

The WURD page points out that, with SSL Enabler, you can use "programs that
are not capable of making secure connections to AT&T Worldnet." I'm left
wondering how Entourage lost this capability from v.X (where there was no
problem) to Entourage 2004.

The current explanation, per Barry Wainwright and Paul Berkowitz:

Entourage 2004 has changed the way it negotiates a secure
connection in order to comply with internet protocol RFC 3207.
This provides a better connection as well as complying with the
RFC. It seems that AT & T uses a method not compatible with this
protocol (with respect to the order in which certain items are
negotiated).

 

[Tom McCatherine]

Thanks for the update, Adam. It appears, then, that this is a problem AT&T
needs to work on.

 

[AL]

Well, it's June 16th and I'm up at midnight trying to configure this
)&&%* thing.

I'm glad to see that I'm not crazy. The sad thing is that I
downloaded that SSL thing, installed and activated it and I STILL
can't send anything.

If anyone's figured this out, please post something. This is
ridiculous.
-a

 

[snortman]

Thanks for the workaround this does work. I can now send
mail with 2004. Has anyone tried installing the root
certificate to see if this also solves the problem?

 

[Barry Wainwright]

Entourage should work without the SSL
enabler, especially considering people are paying for the software.

You would rather have Entourage deviate from the specifications to 'work
round' a mis-configured server? I certainly wouldn't.

MS comes in for a lot of criticism for implementing 'proprietary protocols'.
Entourage is one of the most standards compliant mail clients around. It
hardly seems fair to criticise it for sticking to the rules. Better you
contact the server controllers and complain to them to get the problem
fixed, instead of complaining to the entourage team to work round it.