Large E-Mail not going through

[hmanningsmith]

I am currently running version 1.06 Standard.  I have an email that will not process, subsequently, the rest of the mail in this particular box will not go through.

The mail box has a message that is 183973895 bytes in size.  I restarted the PopGrabber service and received the error message:

Error forwarding message 1 from user@domain.com to localusername: Error sending message: An operation on a socket could not be performed becayse the system lacked sufficient buffer space or because a queue was full.

Sometimes,It will show this message instead:

Error downloading message 1: Exception of type System.OutOfMemoryException was thrown.

I looked for instructions on upgrading to the newer version (1.08), but could not find any.  If you request that I upgrade, please include instructions.  I don't want to lose the accounts that have been created (there are too many to redo).

[Eclarsys Support]

Hello,

We have not tested PopGrabber with such large messages, upgrading to the newest version will not help for this case, but we still recommend you to upgrade. Just uninstall the current version and install the new one, no settings are lost during the deinstallation. After installing the new version, you will need to reenter your registration code.

A 175MB email is a definitely too big for most email servers. Most administrators limit the maximum message size to 20 or 30MB, even the most generous mail providers do not exceed 50MB. If this is a one time event, we recommend you to download the message using a web client, if this is a requirement for your server let us know so that we make some tests and offer you another solution.

Also, please verify that your SMTP server is configured to receive such large messages.

In order to match our tests to you environment, please let us know your system configuration, specifically if you are using a 32 or 64 bit system and how much memory and paging space is allocated to the server.

Regards,

Eclarsys Support

[Eclarsys Support]

Another possible reason for this problem could be a bug in the initial .Net Framework 1.1, as described here http://support.microsoft.com/kb/825680/.

Please make sure you have the latest .Net Framework 1.1 updates installed, specially the Service Pack 1 available here: http://www.microsoft.com/downloads/details.aspx?FamilyID=a8f5654f-088e-40b2-bbdb-a83353618b38&displaylang=en.