Funkcionalnosć toś togo sedła se pśez wótwardowańske źěła wobgranicujo, kótarež maju wašo dožywjenje pólěpšyś. Jolic nastawk waš problem njerozwězujo a cośo pšašanje stajiś, wobrośćo se na našo zgromoźeństwo pomocy, kótarež na to caka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomagaś.

Avatar for Username

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Toś ta nitka jo se archiwěrowała. Pšosym stajśo nowe pšašanje, joli trjebaśo pomoc.

Can I limit concurrent smtp connections?

  • 4 wótegrona
  • 2 matej toś ten problem
  • 8 naglědow
  • Slědne wótegrono wót dmallinson

dmallinson
dmallinson
more options

I have an accounts system (Sage/Pastel) that is sending out PDF statements via Thunderbird 3.0.11. Thuderbird is giving an error from the remote smtp server : too many concurrent connections.

Checking sent items I see that the first 5 mails send. I spoke to the smtp servers' admins who say that 5 concurrent smtp connections are allowed. This leads me to beleive that Sage dumps the mails onto Thunderbird to send - and THunderbird doesn't queue them up one by one - it tries to push them put simultaneously - leading to the concurrent connections error.

Could I be right? Is there a way to force Thunderbird to only create one smtp connection at a time?

I am not sure if this is relevant, but the software is running in Windows Remote Desktop via a Server 2008 Foundation terminal server.

Thanks, David

I have an accounts system (Sage/Pastel) that is sending out PDF statements via Thunderbird 3.0.11. Thuderbird is giving an error from the remote smtp server : too many concurrent connections. Checking sent items I see that the first 5 mails send. I spoke to the smtp servers' admins who say that 5 concurrent smtp connections are allowed. This leads me to beleive that Sage dumps the mails onto Thunderbird to send - and THunderbird doesn't queue them up one by one - it tries to push them put simultaneously - leading to the concurrent connections error. Could I be right? Is there a way to force Thunderbird to only create one smtp connection at a time? I am not sure if this is relevant, but the software is running in Windows Remote Desktop via a Server 2008 Foundation terminal server. Thanks, David

Wubrane rozwězanje

Thanks - I got the following errors:

aDocumentNode.cardDetails.cardDetails is undefined

Exception ... "componenet returned failure code:0x8004011 (NS_error_Not_avaialable)

BUT - then found a bug related to the top one on bugfix - it is for a older version. So I updated TB to current version and - boom - all working.

Thanks for you input Matt

Toś to wótegrono w konteksće cytaś 👍 0

Wšykne wótegrona (4)

Matt
Matt
  • Moderator
  • Top 10 Contributor
more options

Short answer is place Thunderbird into offline mode before generating mail (click the two blue monitors in the bottom left of the screen) That will cause all mail to be placed in the outbox folder and force a send later mode

Once mail is generated, go back online by clicking the monitors again and sending will not fall over itself. Should you forget to go online, Thunderbird will prompt you to send all unsent mail when you close it.

dmallinson
dmallinson Pšašaŕ
more options

Thanks for the reply Matt, have tried that now - but it seems that with MT offline the mail doesn't make it into the outbox at all.

What could be that cause of that do you think?

Matt
Matt
  • Moderator
  • Top 10 Contributor
more options

Have you found the outbox folder? It will be under local folders.

Is there anything in the error console? Tools menu (alt+T) > error console Clear it then try the send as it always contains loads of rubbish

dmallinson
dmallinson Pšašaŕ
more options

Wubrane rozwězanje

Thanks - I got the following errors:

aDocumentNode.cardDetails.cardDetails is undefined

Exception ... "componenet returned failure code:0x8004011 (NS_error_Not_avaialable)

BUT - then found a bug related to the top one on bugfix - it is for a older version. So I updated TB to current version and - boom - all working.

Thanks for you input Matt