Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Receive "The server had an internal error... always a problem of the server..." when trying to move inbox messages to folder

  • 6
  • 1 nwere nsogbu anwere nsogbu a
  • 1 view
  • Nzaghachi ikpeazụ nke James S.

more options

I manage multiple email accounts with Thunderbird and use message filters and subfolder extensively to keep my mail organized. I move messages to the subfolders with filters and manually. Until about 3 days ago, all worked well. However, one of my accounts - and Office 365 Exchange Server POP3 Account that I access with the OWL add-on - will no longer allow me to move message out of the inbox folder into subfolders. The message filters are not working either for this one account.

The full text of the message displayed is: "The server had an internal error. This is always a problem of the server and not of you or your application."

The other POP3 accounts allow for message transfer to subfolders and the filters work fine. Not sure where the problem lies here - whether it is OWL, Thunderbird, or the Exchange Server. I checked an I am running the latest version of Thunderbird and the latest version of OWL. I have reinstalled Thunderbird and restarted but no luck. Is it possible some configuration file has gotten corrupted?

Any thoughts or support would be much appreciated.

I manage multiple email accounts with Thunderbird and use message filters and subfolder extensively to keep my mail organized. I move messages to the subfolders with filters and manually. Until about 3 days ago, all worked well. However, one of my accounts - and Office 365 Exchange Server POP3 Account that I access with the OWL add-on - will no longer allow me to move message out of the inbox folder into subfolders. The message filters are not working either for this one account. The full text of the message displayed is: "The server had an internal error. This is always a problem of the server and not of you or your application." The other POP3 accounts allow for message transfer to subfolders and the filters work fine. Not sure where the problem lies here - whether it is OWL, Thunderbird, or the Exchange Server. I checked an I am running the latest version of Thunderbird and the latest version of OWL. I have reinstalled Thunderbird and restarted but no luck. Is it possible some configuration file has gotten corrupted? Any thoughts or support would be much appreciated.

All Replies (6)

more options

The error message says it's the exchange server, the message being "it's not you, it's us." I suggest you contact them for status on their server issue.

more options

I have the same problem. I'm also not able to open attachments. This started on Friday 1/6/23. The attachment is there at the bottom of the email window, but it says "Downloading" and there is a black line through the attachment name, and I am not able to open the attachment. Also, when I try to reply to messages that I have received after 4:42pm on Thursday 1/5/23, there is no address and the text from the original email is not there in the reply. I contacted my email provider and they had me login through a web browser to the webmail version and everything works like it should from there with attachments etc. With that they say the problem is not with the server.

more options
one of my accounts - and Office 365 Exchange Server POP3 Account that I access with the OWL add-on

If the Exchange server supports POP, then there is absolutely no need for using the Owl add-on. So what are you doing, and what are you trying to achieve in the first place?

more options

Hi Ryan,

I got a response from OWL developers today that shed some light on this issue. It turns out it is being caused by an update to the MS Exchange Server and they are getting reports of the problem. I have the same issue with reply and reply all as you indicate... In response to the OWL developer message, I did as they instructed, reproduced the error and sent them the resulting information. You might want to do the same and send to owl.support.beonex.com. It's good to know they are working on a solution.

Dear Owl customer,

thank you for your message to Owl support. If you have been asking about the "Internal Server Error" that appears when you try to open an attachment, reply to an email or similar actions, please note:

This is a bug caused by an update that Microsoft rolled out over the weekend to some (but not all) of their Office365 servers. This is a server problem. However, we are working on it. Not all users are affected, and our test accounts work fine, which makes fixing the problem harder.

If you wish to help with the solution, you can 1. go to Thunderbird | Tools | Developer tools | Developer Toolbox | tab Network. 2. Then after, trigger the problem again. 3. You will see lines appearing in the Developer Toolbox. Select the line with status "500" 4. then right-click on that line, and in the context menu, select Copy | Copy all as HAR 5. Finally, paste the "HAR" into an email and send it as reply to your support message that you just sent us.

If you have any other pertinent information that might help us to isolate, narrow down, or fix the problem, we'd be grateful for any information that helps to fix the bug. Given that we do not see the bug on our system, we are dependent on your help.

Thank you in advance for your help and your understanding!

Owl developer team

more options

Hey James, Thanks for the tip. I sent them the text they were asking for. Hopefully they find a solution.

Ryan

more options

Hey Ryan,

Just letting you know they seem to have fixed the issue this afternoon. My mail started working correctly - I can move messages to subfolders, see attachments and offload, and when I use reply the message and email address now populate correctly in the reply message. Thanks for sending in your error messages to them as well. I am sure it helped.

Hope your same problem was addressed by whatever they did to update the Exchange interface software. I sent them an email of appreciation for getting to it so quickly. What a relief.

Best, James