suddenly getting SMTP errors with Outlook -- cannot send out mail

A

albert

I use ATT Worldnet thru an outside DSL provider (Verizon). I can receive
mail just
fine (so no POP problem). But SMTP is screwy and I do not know why. This
began happening last night -- intermittently. Today -- nothing will go out.
(I have had this system, Worldnet + VZ DSL, for two-three years, and never
had this problem before. Using Outlook XP with WinXP. The Verizon mail
works perfectly)

here are the two errors I get (sometimes one, sometimes the other, sometimes
both):

1
Task 'albert - outlook - ipostoffice.worldnet.att.net - Sending and
Receiving' reported error (0x800CCC7D) : 'Your outgoing (SMTP) server does
not support SSL-secured connections. If SSL-secured connections have worked
in the past, contact your server administrator or Internet service provider
(ISP).'

2
Task 'albert - outlook - ipostoffice.worldnet.att.net - Sending and
Receiving' reported error (0x800CCC0F) : 'The connection to the server was
interrupted. If this problem continues, contact your server administrator
or Internet service provider (ISP).'

Here's what I have tried to remedy this problem:

I have done a "detect and repair" on MS Office -- no improvement in
Outlook's flaky behavior.

I have changed no settings. I have gone to the relevant ATT Worldnet Help
page and double checked all my settings -- and they appear just fine.

Further inscrutable weirdness -- I asked Outlook to verify that the
settings worked, several times -- and each time it said things are OK --
Outlook successfully sent a test message using the settings, and sure
enough, it came back to me when I did a send/receive with Outlook --
[mocking me no doubt, by informing me that all was well]). (So if the
error messages I placed above are accurate -- how in the world does it
successfully send its test messages??)

So, I then, I deleted my primary ATT account and totally rebuilt it
according to to ATT's specs.

After that, a test message I used out went fine. Hooray, I thought. Nope.
After that, back to the same behavior (i.e., everything I described above).

(A last detail. Not sure that this would be relevant, as my problems did
not begin until some 6+ hours after I did this --- Yesterday I upgraded my
router firmware [a Linksys BEFRS11] from 1.44 to 1.46. )

I am stumped (and annoyed, to say the least). Any suggestions, ideas, help
will be most appreciated.

TIA
albert
 
A

albert

And one more detail.........

If I use Outlook Express -- everything works perfectly. No SMTP problem, no
error messages. (and yes, all settings are identical, I promise)

I am stumped

again, TIA
albert
 
B

Billy

Corrected a very similar problem by setting my linksys befsr41
firmware back to 1.45.11 from 1.46

Cheers Bill D.
albert said:
And one more detail.........

If I use Outlook Express -- everything works perfectly. No SMTP problem, no
error messages. (and yes, all settings are identical, I promise)

I am stumped

again, TIA
albert


albert said:
I use ATT Worldnet thru an outside DSL provider (Verizon). I can receive
mail just
fine (so no POP problem). But SMTP is screwy and I do not know why. This
began happening last night -- intermittently. Today -- nothing will go out.
(I have had this system, Worldnet + VZ DSL, for two-three years, and never
had this problem before. Using Outlook XP with WinXP. The Verizon mail
works perfectly)

here are the two errors I get (sometimes one, sometimes the other, sometimes
both):

1
Task 'albert - outlook - ipostoffice.worldnet.att.net - Sending and
Receiving' reported error (0x800CCC7D) : 'Your outgoing (SMTP) server does
not support SSL-secured connections. If SSL-secured connections have worked
in the past, contact your server administrator or Internet service provider
(ISP).'

2
Task 'albert - outlook - ipostoffice.worldnet.att.net - Sending and
Receiving' reported error (0x800CCC0F) : 'The connection to the server was
interrupted. If this problem continues, contact your server administrator
or Internet service provider (ISP).'

Here's what I have tried to remedy this problem:

I have done a "detect and repair" on MS Office -- no improvement in
Outlook's flaky behavior.

I have changed no settings. I have gone to the relevant ATT Worldnet Help
page and double checked all my settings -- and they appear just fine.

Further inscrutable weirdness -- I asked Outlook to verify that the
settings worked, several times -- and each time it said things are OK --
Outlook successfully sent a test message using the settings, and sure
enough, it came back to me when I did a send/receive with Outlook --
[mocking me no doubt, by informing me that all was well]). (So if the
error messages I placed above are accurate -- how in the world does it
successfully send its test messages??)

So, I then, I deleted my primary ATT account and totally rebuilt it
according to to ATT's specs.

After that, a test message I used out went fine. Hooray, I thought. Nope.
After that, back to the same behavior (i.e., everything I described above).

(A last detail. Not sure that this would be relevant, as my problems did
not begin until some 6+ hours after I did this --- Yesterday I upgraded my
router firmware [a Linksys BEFRS11] from 1.44 to 1.46. )

I am stumped (and annoyed, to say the least). Any suggestions, ideas, help
will be most appreciated.

TIA
albert
 
A

adamp3

There is definitely a problem with outbound SMTP connections to some
ISPs after the 1.46 firmware upgrade. (I'm using Bell Canada's
business DSL and had the same problem.) Outgoing SMTP connections
over 1-2k time out. Rolling back the firmware to 1.45.11 fixes the
problem, but re-introduces the DHCP renewal bug on PPPoE connections.
If you roll back to 1.45.x and find your connection drops or your
router crashes, try v1.44.2. You can get it at:

ftp://ftp.linksys.com/pub/befsr41/befsr-fw-1442.zip


Corrected a very similar problem by setting my linksys befsr41
firmware back to 1.45.11 from 1.46

Cheers Bill D.
albert said:
And one more detail.........

If I use Outlook Express -- everything works perfectly. No SMTP problem, no
error messages. (and yes, all settings are identical, I promise)

I am stumped

again, TIA
albert


albert said:
I use ATT Worldnet thru an outside DSL provider (Verizon). I can receive
mail just
fine (so no POP problem). But SMTP is screwy and I do not know why. This
began happening last night -- intermittently. Today -- nothing will go out.
(I have had this system, Worldnet + VZ DSL, for two-three years, and never
had this problem before. Using Outlook XP with WinXP. The Verizon mail
works perfectly)

here are the two errors I get (sometimes one, sometimes the other, sometimes
both):

1
Task 'albert - outlook - ipostoffice.worldnet.att.net - Sending and
Receiving' reported error (0x800CCC7D) : 'Your outgoing (SMTP) server does
not support SSL-secured connections. If SSL-secured connections have worked
in the past, contact your server administrator or Internet service provider
(ISP).'

2
Task 'albert - outlook - ipostoffice.worldnet.att.net - Sending and
Receiving' reported error (0x800CCC0F) : 'The connection to the server was
interrupted. If this problem continues, contact your server administrator
or Internet service provider (ISP).'

Here's what I have tried to remedy this problem:

I have done a "detect and repair" on MS Office -- no improvement in
Outlook's flaky behavior.

I have changed no settings. I have gone to the relevant ATT Worldnet Help
page and double checked all my settings -- and they appear just fine.

Further inscrutable weirdness -- I asked Outlook to verify that the
settings worked, several times -- and each time it said things are OK --
Outlook successfully sent a test message using the settings, and sure
enough, it came back to me when I did a send/receive with Outlook --
[mocking me no doubt, by informing me that all was well]). (So if the
error messages I placed above are accurate -- how in the world does it
successfully send its test messages??)

So, I then, I deleted my primary ATT account and totally rebuilt it
according to to ATT's specs.

After that, a test message I used out went fine. Hooray, I thought. Nope.
After that, back to the same behavior (i.e., everything I described above).

(A last detail. Not sure that this would be relevant, as my problems did
not begin until some 6+ hours after I did this --- Yesterday I upgraded my
router firmware [a Linksys BEFRS11] from 1.44 to 1.46. )

I am stumped (and annoyed, to say the least). Any suggestions, ideas, help
will be most appreciated.

TIA
albert
 
A

albert

In exasperation, I finally rolled back to firmware v.1.44 (which is what I
had installed previously) -- and that, indeed, licked the problem. Now it
all behaves. Thanks for the link, I will download that version, also.

Thanks Adam.

albert




adamp3 said:
There is definitely a problem with outbound SMTP connections to some
ISPs after the 1.46 firmware upgrade. (I'm using Bell Canada's
business DSL and had the same problem.) Outgoing SMTP connections
over 1-2k time out. Rolling back the firmware to 1.45.11 fixes the
problem, but re-introduces the DHCP renewal bug on PPPoE connections.
If you roll back to 1.45.x and find your connection drops or your
router crashes, try v1.44.2. You can get it at:

ftp://ftp.linksys.com/pub/befsr41/befsr-fw-1442.zip


(e-mail address removed) (Billy) wrote in message
Corrected a very similar problem by setting my linksys befsr41
firmware back to 1.45.11 from 1.46

Cheers Bill D.
"albert" <[email protected]> wrote in message
And one more detail.........

If I use Outlook Express -- everything works perfectly. No SMTP problem, no
error messages. (and yes, all settings are identical, I promise)

I am stumped

again, TIA
albert


I use ATT Worldnet thru an outside DSL provider (Verizon). I can receive
mail just
fine (so no POP problem). But SMTP is screwy and I do not know why. This
began happening last night -- intermittently. Today -- nothing will
go
out.
(I have had this system, Worldnet + VZ DSL, for two-three years, and never
had this problem before. Using Outlook XP with WinXP. The Verizon mail
works perfectly)

here are the two errors I get (sometimes one, sometimes the other, sometimes
both):

1
Task 'albert - outlook - ipostoffice.worldnet.att.net - Sending and
Receiving' reported error (0x800CCC7D) : 'Your outgoing (SMTP) server does
not support SSL-secured connections. If SSL-secured connections have worked
in the past, contact your server administrator or Internet service provider
(ISP).'

2
Task 'albert - outlook - ipostoffice.worldnet.att.net - Sending and
Receiving' reported error (0x800CCC0F) : 'The connection to the server was
interrupted. If this problem continues, contact your server administrator
or Internet service provider (ISP).'

Here's what I have tried to remedy this problem:

I have done a "detect and repair" on MS Office -- no improvement in
Outlook's flaky behavior.

I have changed no settings. I have gone to the relevant ATT Worldnet Help
page and double checked all my settings -- and they appear just fine.

Further inscrutable weirdness -- I asked Outlook to verify that the
settings worked, several times -- and each time it said things are OK --
Outlook successfully sent a test message using the settings, and sure
enough, it came back to me when I did a send/receive with Outlook --
[mocking me no doubt, by informing me that all was well]). (So if the
error messages I placed above are accurate -- how in the world does it
successfully send its test messages??)

So, I then, I deleted my primary ATT account and totally rebuilt it
according to to ATT's specs.

After that, a test message I used out went fine. Hooray, I thought. Nope.
After that, back to the same behavior (i.e., everything I described above).

(A last detail. Not sure that this would be relevant, as my problems did
not begin until some 6+ hours after I did this --- Yesterday I upgraded my
router firmware [a Linksys BEFRS11] from 1.44 to 1.46. )

I am stumped (and annoyed, to say the least). Any suggestions,
ideas,
help
will be most appreciated.

TIA
albert
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top