message says send failed due to smtp timeout message though email does get sent

[pete...@ntlworld.com]

I keep getting problems sending emails, especially if there is an
attachment though it fail with just a couple of paragraphs of text.
For example today I tried to send an important business email with a
23.6kb attachment, I got the progress bar which stuck at 86% and then
I got a message saying the send failed due to smtp timeout. The email
stayed in the draft folder and wasn't copied to the sent folder. After
trying many times to send the email over 90 minutes while trying
closing down other applications, turning off virus scanning, adjusting
the network.tcp.sendbuffer size, but getting the same response each
time I then got an email from the recipient saying he had received the
email 9 times! I sent a brief two line apology which also apparently
failed but did in fact get through.

This makes using Thunderbird very difficult as I can't trust the
messages or rely on mail getting through.

I am running Thunderbird version 6.0.2 and Windows 7 64 bit on a four
core processor with maximum RAM. It's LAN connected to a D-Link
router. When this problem has happened bfore I got around it by cut
and pasting the email into my hotmail account and sending it from
there.

After looking at some forums I tried changing the
network.tcp.sendbuffer from 131072 to 65536, it didn't make any
difference so I put it back to the default setting.

[g]

On 09/26/2011 10:39 AM, pete...@ntlworld.com wrote:
> I keep getting problems sending emails, especially if there is an
> attachment though it fail with just a couple of paragraphs of text.
<>
>

> After looking at some forums I tried changing the
> network.tcp.sendbuffer from 131072 to 65536, it didn't make any
> difference so I put it back to the default setting.

you got close by using 'about:config', but i believe you changed
wrong preference name.

open 'about:config' again, this time with 'Filter: tcptimeout'.

you should see a 'default' value of '60' or '100'. change to '400'
or even '600' to see if that will be long enough. if not, kick it
up '700'.

see these pages;

http://kb.mozillazine.org/Mail_and_news_settings
http://kb.mozillazine.org/Thunderbird_3.0_-_New_Features_and_Changes

search for 'timeout'.


hth.
--

peace out.

tc.hago,

g
.

****
in a free world without fences, who needs gates.
**
help microsoft stamp out piracy - give linux to a friend today.
**
to mess up a linux box, you need to work at it.
to mess up an ms windows box, you just need to *look* at it.
**
The installation instructions stated to install Windows 2000 or better.
So I installed Linux.
**
learn linux:
'Rute User's Tutorial and Exposition' http://rute.2038bug.com/index.html
'The Linux Documentation Project' http://www.tldp.org/
'LDP HOWTO-index' http://www.tldp.org/HOWTO/HOWTO-INDEX/index.html
'HowtoForge' http://howtoforge.com/
****

[pete...@ntlworld.com]

Thanks for the response. tcptimeout was set to 100 so I am trying 400
first. A quick test seems Ok but the problem isn't there all the time
so I'll give it a while and if necessary push the timeout up further
as you suggest.


On Sep 28, 5:07 am, g <gel...@bellsouth.net> wrote:

>  signature.asc
> < 1KViewDownload

[g]

On 09/28/2011 08:04 AM, pete...@ntlworld.com wrote:
> Thanks for the response.

you are welcome.

> tcptimeout was set to 100 so I am trying 400 first. A quick test seems Ok
> but the problem isn't there all the time so I'll give it a while and if
> necessary push the timeout up further as you suggest.

ok.

you may wish to consider contacting your isp to see if they have
some sort of time limiting set that would cause delay.

also, time of day may be a factor if they do. a slim possibility, but
possibility.


i ran a google advanced search

http://www.google.com/advanced_search?hl=en&num=100

using;

this exact wording or phrase: network.tcp
Search within a site or domain: mozilla.org

link to results;

http://www.google.com/search?q=%22network.tcp%22+site%3Amozilla.org&hl=en&num=100&lr=&ft=i&cr=&safe=images&tbs=

shows 23 results.

among results are bugs, sending attachment, and send mail failure. so it
would be a good idea to have a look. several appear to relate to your
problems.