Can't send mail

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
Wed Jun 09 09:14:46 CDT 2004

In article <BCEC8E46.464%tmccat@worldnet.att.net>,
Tom McCatherine <tmccat@worldnet.att.net> wrote:

> 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?

--
Adam Bailey | Chicago, Illinois
adamb@lull.org | Finger/Web for PGP & S/MIME
adamkb@aol.com | http://www.lull.org/adam/

chris
Wed Jun 09 09:15:07 CDT 2004

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

I really need help!=20
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=20
from PC's...
If you find any solution please post it immediately!!!
I'll do the same!
Thanks a lot
chris

>-----Original Message-----
>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=20
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
>
>
>.
>

anonymous
Wed Jun 09 09:21:17 CDT 2004

All the configurations are correct, I have also checked them more than =
10=20
times with my internet provider, and I have also tried to set up a new=20
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!


>-----Original Message-----
>In article <BCEC8E46.464%tmccat@worldnet.att.net>,
> Tom McCatherine <tmccat@worldnet.att.net> wrote:
>
>> I have just upgraded to Office 2004 from Office V.X and now I'm =
unable=20
to
>> send mail.
>
>What happens when you try? What error are you encountering?
>
>How /do/ you have your SMTP server information configured?
>
>--=20
>Adam Bailey | Chicago, Illinois
>adamb@lull.org | Finger/Web for PGP & S/MIME
>adamkb@aol.com | http://www.lull.org/adam/
>.
>

Barry
Wed Jun 09 10:30:02 CDT 2004

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.

--
Barry Wainwright
Microsoft MVP (see http://mvp.support.microsoft.com for details)
Seen the All-New Entourage Help Pages? - Check them out:
<http://www.entourage.mvps.org/>


> From: <anonymous@discussions.microsoft.com>
> Newsgroups: microsoft.public.mac.office.entourage
> Date: Wed, 9 Jun 2004 07:21:17 -0700
> Subject: Re: Can't send mail
>
> 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!
>
>
>> -----Original Message-----
>> In article <BCEC8E46.464%tmccat@worldnet.att.net>,
>> Tom McCatherine <tmccat@worldnet.att.net> wrote:
>>
>>> 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?
>>
>> --
>> Adam Bailey | Chicago, Illinois
>> adamb@lull.org | Finger/Web for PGP & S/MIME
>> adamkb@aol.com | http://www.lull.org/adam/
>> .
>>

Jeff
Wed Jun 09 10:37:10 CDT 2004

On 9/6/04 10:21 AM, in article 19eea01c44e2d$0771f460$a601280a@phx.gbl,
"anonymous@discussions.microsoft.com" <anonymous@discussions.microsoft.com>
wrote:

> 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!
>
>
>> -----Original Message-----
>> In article <BCEC8E46.464%tmccat@worldnet.att.net>,
>> Tom McCatherine <tmccat@worldnet.att.net> wrote:
>>
>>> 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?
>>
>> --
>> Adam Bailey | Chicago, Illinois
>> adamb@lull.org | Finger/Web for PGP & S/MIME
>> adamkb@aol.com | http://www.lull.org/adam/
>> .
>>

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

chris
Wed Jun 09 10:48:16 CDT 2004

I have the same settings for send and receive as I had in my previous=20
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=20
that it can't connect to the outgoing server.
What settings have you made for the send and receive schedule?


>-----Original Message-----
>On 9/6/04 10:21 AM, in article=20
19eea01c44e2d$0771f460$a601280a@phx.gbl,
>"anonymous@discussions.microsoft.com"=20
<anonymous@discussions.microsoft.com>
>wrote:
>
>> All the configurations are correct, I have also checked them more =
than=20
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!
>>=20
>>=20
>>> -----Original Message-----
>>> In article <BCEC8E46.464%tmccat@worldnet.att.net>,
>>> Tom McCatherine <tmccat@worldnet.att.net> wrote:
>>>=20
>>>> I have just upgraded to Office 2004 from Office V.X and now I'm=20
unable
>> to
>>>> send mail.
>>>=20
>>> What happens when you try? What error are you encountering?
>>>=20
>>> How /do/ you have your SMTP server information configured?
>>>=20
>>> --=20
>>> Adam Bailey | Chicago, Illinois
>>> adamb@lull.org | Finger/Web for PGP & S/MIME
>>> adamkb@aol.com | http://www.lull.org/adam/
>>> .
>>>=20
>
>Have you tried checking the "Send and Receive" schedule to see if both=20
send
>and receive actions are set? Mine weren't.
>
>.
>

ruggier3
Wed Jun 09 14:49:04 CDT 2004

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.


"chris" <anonymous@discussions.microsoft.com> wrote in message news:<19edd01c44e2c$2a80d3f0$a601280a@phx.gbl>...
> 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
>
> >-----Original Message-----
> >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
> >
> >
> >.
> >

Tom
Wed Jun 09 16:22:58 CDT 2004

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


On 6/9/04 10:14 AM, in article
adamb-344CDA.09144609062004@msnews.microsoft.com, "Adam Bailey"
<adamb@lull.org> wrote:

> In article <BCEC8E46.464%tmccat@worldnet.att.net>,
> Tom McCatherine <tmccat@worldnet.att.net> wrote:
>
>> 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?

pete
Wed Jun 09 23:02:03 CDT 2004

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.



On 10/6/04 5:49, in article dcb4e197.0406091149.2d2cccea@posting.google.com,
"Charlie" <ruggier3@msu.edu> wrote:

> 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.
>
>
> "chris" <anonymous@discussions.microsoft.com> wrote in message
> news:<19edd01c44e2c$2a80d3f0$a601280a@phx.gbl>...
>> 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
>>
>>> -----Original Message-----
>>> 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
>>>
>>>
>>> .
>>>

adamb
Thu Jun 10 13:22:37 CDT 2004

Tom McCatherine <tmccat@worldnet.att.net> wrote:
> 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

--
Adam Bailey | Chicago, Illinois
adamb@lull.org | Finger/Web for PGP & S/MIME
adamkb@aol.com | http://www.lull.org/adam/

Tom
Thu Jun 10 19:40:08 CDT 2004

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.

On 6/10/04 2:22 PM, in article slrncch9nd.s1g.adamb@typhoon.xnet.com, "Adam
Bailey" <adamb@lull.org> wrote:

> Tom McCatherine <tmccat@worldnet.att.net> wrote:
>> 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


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.

ruggier3
Fri Jun 11 08:17:00 CDT 2004

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).

Tom McCatherine <tmccat@worldnet.att.net> wrote in message news:<BCEE77A8.54E%tmccat@worldnet.att.net>...
> 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.
>
> On 6/10/04 2:22 PM, in article slrncch9nd.s1g.adamb@typhoon.xnet.com, "Adam
> Bailey" <adamb@lull.org> wrote:
>
> > Tom McCatherine <tmccat@worldnet.att.net> wrote:
> >> 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
>
>
> 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.

lorichapman
Fri Jun 11 11:24:57 CDT 2004

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?

Tom McCatherine <tmccat@worldnet.att.net> wrote in message news:<BCEE77A8.54E%tmccat@worldnet.att.net>...
> 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.
>
> On 6/10/04 2:22 PM, in article slrncch9nd.s1g.adamb@typhoon.xnet.com, "Adam
> Bailey" <adamb@lull.org> wrote:
>
> > Tom McCatherine <tmccat@worldnet.att.net> wrote:
> >> 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
>
>
> 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.

lorichapman
Fri Jun 11 12:21:22 CDT 2004

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?

Tom McCatherine <tmccat@worldnet.att.net> wrote in message news:<BCEE77A8.54E%tmccat@worldnet.att.net>...
> 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.
>
> On 6/10/04 2:22 PM, in article slrncch9nd.s1g.adamb@typhoon.xnet.com, "Adam
> Bailey" <adamb@lull.org> wrote:
>
> > Tom McCatherine <tmccat@worldnet.att.net> wrote:
> >> 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
>
>
> 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.

Adam
Fri Jun 11 17:43:06 CDT 2004

In article <BCEE77A8.54E%tmccat@worldnet.att.net>,
Tom McCatherine <tmccat@worldnet.att.net> wrote:

> 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).

--
Adam Bailey | Chicago, Illinois
adamb@lull.org | Finger/Web for PGP & S/MIME
adamkb@aol.com | http://www.lull.org/adam/

Tom
Sat Jun 12 11:57:39 CDT 2004

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

On 6/11/04 6:43 PM, in article
adamb-1069EE.17430611062004@msnews.microsoft.com, "Adam Bailey"
<adamb@lull.org> wrote:

> In article <BCEE77A8.54E%tmccat@worldnet.att.net>,
> Tom McCatherine <tmccat@worldnet.att.net> wrote:
>
>> 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).

elmastero
Thu Jun 17 01:48:59 CDT 2004

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


Tom McCatherine <tmccat@worldnet.att.net> wrote in message news:<BCF0AE43.4D81%tmccat@worldnet.att.net>...
> Thanks for the update, Adam. It appears, then, that this is a problem AT&T
> needs to work on.
>
> On 6/11/04 6:43 PM, in article
> adamb-1069EE.17430611062004@msnews.microsoft.com, "Adam Bailey"
> <adamb@lull.org> wrote:
>
> > In article <BCEE77A8.54E%tmccat@worldnet.att.net>,
> > Tom McCatherine <tmccat@worldnet.att.net> wrote:
> >
> >> 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).

snortman
Mon Jun 21 12:25:44 CDT 2004

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?



>-----Original Message-----
>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).
>
>Tom McCatherine <tmccat@worldnet.att.net> wrote in message
news:<BCEE77A8.54E%tmccat@worldnet.att.net>...
>> 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.
>>
>> On 6/10/04 2:22 PM, in article
slrncch9nd.s1g.adamb@typhoon.xnet.com, "Adam
>> Bailey" <adamb@lull.org> wrote:
>>
>> > Tom McCatherine <tmccat@worldnet.att.net> wrote:
>> >> 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
>>
>>
>> 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.
>.
>

Barry
Mon Jun 21 14:19:57 CDT 2004

On 11/6/04 2:17 pm, in article
dcb4e197.0406110517.12a4d89b@posting.google.com, "Charlie"
<ruggier3@msu.edu> wrote:

> 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.

--
Barry Wainwright
Microsoft MVP (see http://mvp.support.microsoft.com for details)
Seen the All-New Entourage Help Pages? - Check them out:
<http://www.entourage.mvps.org/>

ruggier3
Tue Jun 22 10:17:46 CDT 2004

Barry Wainwright <barry@mvps.org.INVALID> wrote in message news:
> 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.

So what you are saying is Entourage 2004 doesn't work because they use
the "correct" specifications for POP? And therefore Entourage X,
Eudora, Apple's Mail Client, Outlook Express 5 and 6, Outlook 98 -
2003, Netscape Messenger 7 6.2 and 4.8, Kmail, Pegasus, and ximian are
all wrong? That is ridiculous. Even if they are following
specifications they should do something to allow you to use either
specification considering most of the rest of the email world works
with no problems.