Getting a random error in production with downloading a mail message. Everything works most of the time. At random intervals I get this in the pop server's log:
-ERR The specified message is out of range.,
After the error occurs, that same message can be downloaded with a second attempt. Server is 2007 exchange.
Hi Brian,
Thank you for writing to Aspose support team.
Could you please provide us with the detailed exception report for our investigation and does this always happen with a particular message or is it random? Also, if it is possible please arrange a test account for us on your server so that we can test this issue at our end and assist you further in this regard.
There are no errors other than what we see in the POP log. The failure is on FetchMessage. When I call FetchMessage on a particular message, it just hangs.
I am able to call getmessagesize, and getmessageheaders successfully. The fetchmessage call continues to fail.
I seem to be seeing exactly what is described here:
Hi Brian,
I have tested this issue at my end using the latest version of Aspose.Email for .NET 4.2.0 but I’m afraid to share that I could not face any such exception. Could you please:
1. Share with us a sample message which fails the test each time?
2. Provide us with the credentials of a test account that we can use to carry out the tests at our end as it is otherwise impossible for us to reproduce the issue at our end.
We appreciate your cooperation in this regard.
I can get you a message that triggers this issue, but I don’t expect it’s going to provide any value. We can take that same message, resend it to the mailbox and it will work. The failure happens randomly, and reposting the same message does not trigger the error. If you leave the “trigger” message in the mailbox however, it will fail every time.
The customer does not have the ability to expose external access to the mail account. I can get you controlled access to the system if you want to run through the issue with me, or I can implement whatever logging to troubleshooting steps you think are appropriate.
Hi Brian,
Thank you for writing back.
I’m not sure if the controlled access will help us in this case specifically when the issue is random and can’t be reproduced once the file is re-posted. Also, the Pop3 Client logging may not be of much help in this case as well. Anyways, please share the controlled access information with us where we can reproduce this issue at our end. We’ll look into it for our analysis and see if something can be suggested in this regard.