Re: Outlook Express will not send mail.
From: Shannon Jacobs (shanen_at_my-deja.com)
Date: 05/23/04
- Next message: Jerry Queen: "Re: problems with muti-identities in OE"
- Previous message: KiwiBrian: "Re: Received attachments not available"
- In reply to: PA Bear: "Re: Outlook Express will not send mail."
- Next in thread: PA Bear: "Re: Outlook Express will not send mail."
- Reply: PA Bear: "Re: Outlook Express will not send mail."
- Reply: Mark F: "Re: Outlook Express will not send mail."
- Reply: Shannon Jacobs: "Re: Outlook Express will not send mail."
- Reply: Shannon Jacobs: "Re: Outlook Express will not send mail."
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 23 May 2004 13:31:54 +0900
Typically useless response from the now typically useless MVPs. Microsoft
has destroyed yet another resource for free support. Sad, since the MVPs
used to be very helpful and knowledgeable.
Oh, yes. The obligatory substantive technical comment: I (and many other
people) have very similar problems and I have studied all of the below
referenced documents (and many others) and I have tried all of the
Microsoft-recommended solutions. Those solutions do not work.
My own conclusion after some months of struggle is that the root cause is
actually flaws in the IP implementation under Windows 2000 (and probably
W9x, too), but I have not been able to find any public discussions of this
part of the situation. I strongly suspect that Microsoft is aware of it
internally. The situation is somewhat complicated and runs backwards, and I
am saying this on the basis of taking the original UNIX-based
implementations as the definition of "correct network behavior". During the
long period when W2K was an important client system (probably extending back
into the W9x period), the servers (my own research has mostly involved NNTP
servers) were developed and tested against those W9x clients. Testing and
debugging continued until they worked, because that was a crucial de facto
client standard. Networks were also tested and configured accordingly.
When Microsoft redid the TCP stacks for Windows XP, they "fixed" things. The
result was actually that many server and network configurations that worked
under W2K became broken. However, my testing has shown that the new WXP
networking behavior actually corresponds to the correct-by-prior-definition
behavior on UNIX boxes, so they can't "fix" it, because now WXP is actually
doing the correct thing--it is the servers and networks that have become
"broken" (because they were configured to work with a broken "standard"
implementation). (And by the way, this explains why Microsoft's own (NNTP)
servers work properly--they have been fixed. As I noted earlier, I do
believe that Microsoft is internally well aware of the real problems. If you
pay Microsoft some money for the "premium" support, they will reveal some
small but sufficient part of the solution unto you. Probably yet another
secret backwards "compatibility" mode.)
As the OP noted, the variations of the problems are widespread and
frequently reported, and almost never solved. I haven't totaled up the
numbers, but my belief is that many, or perhaps most, of the people with
these problems simply give up and switch to Web-based alternatives. In fact,
XP practically requires Web connectivity, so in that sense this is a problem
that include its own workaround. This masks the scope of the problem rather
effectively. The problem remains unsolved, but the victims work around it.
However, in the old days of competent MVPs, one of them would have escalated
the problem and found a real fix long ago.
PA Bear wrote:
> Yeah, it's a known problem:
>
> 250663 - MaxMTU - TCP-IP Registry Entries in the NetTrans Subkey
> http://support.microsoft.com/?kbid=250663
>
> 315008 - OE Hangs sending.message.Attachment - MTU values
> http://support.microsoft.com/?kbid=315008
>
> Cannot Send Outgoing Mail (Linksys and Word)
> http://support.microsoft.com/?kbid=329918
>
> Error Message 421 and Linksys router
> http://www.linksys.com/support/support.asp?spid=87
>
> But I wouldn't make a lotta changes just for Hotmail-in-OE. Most such
> problems are on MSN/Hotmail's end. Of course YMMV.
>
> Lester Hinton wrote:
>> This problem is widespread,I been several forums,and did a
>> search to find them. I called my ISP several times,and
>> they said everything at their servers was alright.
>> Netgear wants $28 dollars to help me. I uninstalled Zone
>> Alarm, and Norton System Works still not good. I found
>> that my problem was the MTU setting in my Netgear router.
>> It was set to 1500. Now the weird thing is if I lower
>> this to 1499 my Outlook Express mail will send. But
>> Hotmail will stall opening up mail. Now if its
>> 1500 Hotmail will work, Outlook Express will get this
>> error. Now why is one digit making this much of a
>> difference? That what I too know.
>>
>>
>> Your server has unexpectedly terminated the connection.
>> Possible causes for this include server problems,
>> network problems, or a long period of inactivity.
>> Subject 'Hello How everyone doing!!!!!!',
>> Account: 'pop3.cebridge.net',
>> Server: 'smtp.cebridge.net', Protocol: SMTP, Port: 25,
>> Secure(SSL): No, Socket Error: 10053, Error Number:
>> 0x800CCC0Fet on 1500 Hotmail works but Outlook will get
>> this error
- Next message: Jerry Queen: "Re: problems with muti-identities in OE"
- Previous message: KiwiBrian: "Re: Received attachments not available"
- In reply to: PA Bear: "Re: Outlook Express will not send mail."
- Next in thread: PA Bear: "Re: Outlook Express will not send mail."
- Reply: PA Bear: "Re: Outlook Express will not send mail."
- Reply: Mark F: "Re: Outlook Express will not send mail."
- Reply: Shannon Jacobs: "Re: Outlook Express will not send mail."
- Reply: Shannon Jacobs: "Re: Outlook Express will not send mail."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
