m.vandun Posted January 4, 2017 Share Posted January 4, 2017 Hi, We have received an email with the following content: We have detected an error during the message decoding process for the attached inbound mail message. This could be due to the MIME decoding problem in Hornbill's software, a corrupt message from the message originator or a general communications problem. You will find the original raw RFC822 formatted message as well as other useful files attached to this message in order to help you identify the message originator and aid in debugging the problem. Please ask the originator of the message to send it to you again. If the problem persists and you are happy that this message or its attachments do not contain confidential personal or commercial information, please contact Hornbill support or your Hornbill partner if you have a valid support contract or post the problem on Hornbill's community support forum (https://forums.hornbill.com/) in order that we can investigate this problem further.Thank You.Hornbill Development TeamMessage tracking ID: imap4-Service-16eca59496eae72cThe error encountered was:No recipients found. Unable to process the message Any idea what this could be? Regards, Mark Link to comment Share on other sites More sharing options...
Gerry Posted January 4, 2017 Share Posted January 4, 2017 According to the error message... No recipients found. Unable to process the message Looks like the email message its self did not include any email recipients (from, to, cc, bcc)... so an invalid email message. The tracking ID will allow you to look in the logs and see the message processing Gerry Link to comment Share on other sites More sharing options...
m.vandun Posted January 9, 2017 Author Share Posted January 9, 2017 Hi @Gerry, I tried searching in the logs but cannot find anything on the tracking ID. How can I best search for this? Regards, Mark Link to comment Share on other sites More sharing options...
Gerry Posted January 9, 2017 Share Posted January 9, 2017 Hi Mark, Its probably in the archives now as we archive everything 24/7. If you have a support service you could log a call and the techs might be able to retrieve the log. Alternatively wait until it occurs again and then download the log for the same day. Gerry 1 Link to comment Share on other sites More sharing options...
m.vandun Posted January 10, 2017 Author Share Posted January 10, 2017 Hi Gerry, Thanks for the reply, will do that. Thanks for the help. Mark Link to comment Share on other sites More sharing options...
m.vandun Posted March 2, 2017 Author Share Posted March 2, 2017 Hi @Gerry, Today we got this message again. Tried searching the log but could not find anything. We have detected an error during the message decoding process for the attached inbound mail message. This could be due to the MIME decoding problem in Hornbill's software, a corrupt message from the message originator or a general communications problem. You will find the original raw RFC822 formatted message as well as other useful files attached to this message in order to help you identify the message originator and aid in debugging the problem. Please ask the originator of the message to send it to you again. If the problem persists and you are happy that this message or its attachments do not contain confidential personal or commercial information, please contact Hornbill support or your Hornbill partner if you have a valid support contract or post the problem on Hornbill's community support forum (https://forums.hornbill.com/) in order that we can investigate this problem further.Thank You.Hornbill Development TeamMessage tracking ID: imap4-Service-6c02a60734c7347cThe error encountered was: Failed to add message to the inbound queue. Operation[mail::addMessageToQueue] Unable to obtain [Service] mailbox How can I best troubleshoot this message? Regards, Mark Link to comment Share on other sites More sharing options...
Victor Posted March 2, 2017 Share Posted March 2, 2017 @m.vandun most likely occurred because of this underlying issue (link below). However this has now been sorted so you should not see the issue again, Please do let us know if this is not the case. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now