Avatar for Username

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Tuta nitka je so archiwowała. Prošu stajće nowe prašenje, jeli pomoc trjebaće.

TB sent email OK but cannot save in remote sent directory on ISP server

  • 1 wotmołwa
  • 1 ma tutón problem
  • 12 napohladow
  • Poslednja wotmołwa wot Kinetix

Kinetix
Kinetix
more options

This happens intermittently on Thunderbird 68 in both 32 bit & 64 bit PCs. Happens for both email with and without attachment. The error message is: "Your message was sent but a copy was not placed in your sent folder (Sent Mail) due to network or file access errors. You can retry or save the message locally to Local Folders/Sent Mail-xxxxxxx@aussiebroadband.com.au"

This happened when I upgraded to TB 68 so I have gone back to TB 60 and the problem has not reoccurred so far. I had a similar problem before that was caused by the antivirus software email scanning. Since that time, I have the antivirus email scanning switched off for both sending and receiving. So this problem is not caused by the antivirus software.

This happens intermittently on Thunderbird 68 in both 32 bit & 64 bit PCs. Happens for both email with and without attachment. The error message is: "Your message was sent but a copy was not placed in your sent folder (Sent Mail) due to network or file access errors. You can retry or save the message locally to Local Folders/Sent Mail-xxxxxxx@aussiebroadband.com.au" This happened when I upgraded to TB 68 so I have gone back to TB 60 and the problem has not reoccurred so far. I had a similar problem before that was caused by the antivirus software email scanning. Since that time, I have the antivirus email scanning switched off for both sending and receiving. So this problem is not caused by the antivirus software.

Wšě wotmołwy (1)

Kinetix
Kinetix Prašer
more options

Update to the problem, just encountered the same problem on Thunderbird 60 as well. So not unique to version 68.