We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

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

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

  • 1 wótegrono
  • 1 ma toś ten problem
  • 12 naglědow
  • Slědne wótegrono wót 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 [email protected]"

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 [email protected]" 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šykne wótegrona (1)

more options

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