Author |
|
japollock Newbie
Joined: 13 December 2007 Location: United States
Online Status: Offline Posts: 2
|
Posted: 13 December 2007 at 1:54pm | IP Logged
|
|
|
Stacktrace is included below -
I've been using the MailBee.Net IMAP component for some time now, and have been very happy with it. Recently however, we encountered a problem while testing a component that relies on the MailBee IMAP component. When a user sends a somewhat large email (say an email with 40+MB of attachments, or a single 90+MB attachment), the MailBee.Mime.MailMessage.Parser appears to blow up from parsing too large of an email. Has any else had this problem? Is it a known issue? Is there a config setting that I can set to avoid such exceptions?
---
System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
at System.String.CreateStringFromEncoding(Byte* bytes, Int32 byteLength, Encoding encoding)
at System.Text.EncodingNLS.GetString(Byte[] bytes, Int32 index, Int32 count)
at System.Text.Encoding.GetString(Byte[] bytes)
at cs.a(String A_0, MailTransferEncoding A_1, Byte[] A_2)
at MailBee.Mime.MimePart.a(Byte[] A_0, MailMessage A_1)
at MailBee.Mime.MimePart.a(Byte[] A_0, MailMessage A_1)
at MailBee.Mime.MailMessage.m()
at MailBee.Mime.MessageParserConfig.Apply()
at MailBee.Mime.MailMessage.get_To()
<code that, after setting a parser option, calls Parser.Apply()>
|
Back to Top |
|
|
Andrew AfterLogic Support
Joined: 28 April 2006 Location: United States
Online Status: Offline Posts: 1189
|
Posted: 14 December 2007 at 1:30am | IP Logged
|
|
|
Do you use the latest version of MailBee.NET Objects? If not, please upgrade to the latest version and try again. You can learn how to download the latest version and upgrade your installation from this topic of MailBee FAQ.
Please let us know the outcome.
Best regards,
Andrew
|
Back to Top |
|
|
japollock Newbie
Joined: 13 December 2007 Location: United States
Online Status: Offline Posts: 2
|
Posted: 14 December 2007 at 10:10am | IP Logged
|
|
|
That was exactly the fix. We were still using v2.0.0.6. Upgrading to v3.0.2.78 fixed our problem. Thanks!
|
Back to Top |
|
|