Thunderbird has stopped sending emails on our Server 2016. NS_ERROR_FILE_TOO_BIG
Hi Thunderbird has stopped sending emails on our Server 2016. Fully updating it has not solved the problem. My question is, if I uninstall and reinstall Thunderbird on the server, will this require a Server restart? We are hoping to avoid a restart because of the extended restart time due to Windows updates. The server is serving a call monitoring centre and downtime is critical.
Regards John Gilfillan
Ilungisiwe
All Replies (5)
Just to clarify: Thunderbird does not run on the server, so I'm not sure what the problem is. Maybe more information will help. Thank you.
Hi David
We have Thunderbird running on a Windows 2016 server - at least it was running on the server until it stopped working. It is set as the windows default email client.
Our call centre monitoring software (CAMS) runs on the same server and uses the windows MAPI driver to communicate with Thunderbird when sending emails to customers.
Regarding my original question, I did uninstall and reinstall Thunderbird on the server and it did not require a reboot of the server, but it did not solve the problem of Thunderbird not working.
I have since started on a work around which will remove the need to use Thunderbird.
Regards John
There is a dedicated enterprise mailing list. https://thunderbird.topicbox.com/groups/enterprise
But this topic is about not sending mail as far as I can see, and you have not even mentioned why it is reporting not sending or what the error messages are that are presented, either in Dialogs of the error console. So there is nothing here to even begin to work with.
Hi
When attempting to send an email from Thunderbird, we get this error message - see attached image
Do you know what this message means? Let me know if you need more information.
Regards John
I have updated the posting topic to something meaningful. (hint)
NS_ERROR_FILE_TOO_BIG leads to Bug 673703 - Thunderbird is limited to 10000 temp files, stops sending emails if nsmail-9999.tmp exists, and fails to open attachment if <attachment_filename>-9999.attachment_extension exists