Community Discussions and Support
"SSL improperly closed by remote host" entries in session logs

I turned on session logging to try to determine why two iDevice users could not connect after I upgraded to v4.80.  One got his working after a reboot of the phone but the subsequent session logs contain an "SSL improperly closed by remote host" at the end of each session.  Is there anything I should be concerned with on my end?

I turned on session logging to try to determine why two iDevice users could not connect after I upgraded to v4.80.  One got his working after a reboot of the phone but the subsequent session logs contain an "SSL improperly closed by remote host" at the end of each session.  Is there anything I should be concerned with on my end?

It's just the way that client behaves, nothing to do about it server-side and nothing to be concerned about as the session was being closed anyway.

 

<p>It's just the way that client behaves, nothing to do about it server-side and nothing to be concerned about as the session was being closed anyway.</p><p> </p>

I have seen this happening a lot.

When an email of particular isze with a bunch of attachments get sent to my server, i often see the message failing, resulting in the message being sent again. But, I see the 'SSL improperly closed". Yes, if I use another email server, the message is received fine.

So somhow MERCURY is thinking the data is finished being sent, even though it has been sent correctly, then discarded, and it never makes it so its delivered, and a proper response is never passed on to the client or mercury is somehow terminating the connection (its not the client)

I have run into this problem 10 times now.

<p>I have seen this happening a lot.</p><p>When an email of particular isze with a bunch of attachments get sent to my server, i often see the message failing, resulting in the message being sent again. But, I see the 'SSL improperly closed". Yes, if I use another email server, the message is received fine.</p><p>So somhow MERCURY is thinking the data is finished being sent, even though it has been sent correctly, then discarded, and it never makes it so its delivered, and a proper response is never passed on to the client or mercury is somehow terminating the connection (its not the client)</p><p>I have run into this problem 10 times now.</p>

The sad thing about this problem. is that the client will keep re-trying to defective server over and over again, and not retry another server. (each time trying to send the big email wasting resources)

The sad thing about this problem. is that the client will keep re-trying to defective server over and over again, and not retry another server. (each time trying to send the big email wasting resources)

[quote user="sheldows"]The sad thing about this problem. is that the client will keep re-trying to defective server over and over again, and not retry another server. (each time trying to send the big email wasting resources)[/quote]

Are you using the latest Mercury version? A session log would be useful as this message is for information only.

<P>[quote user="sheldows"]The sad thing about this problem. is that the client will keep re-trying to defective server over and over again, and not retry another server. (each time trying to send the big email wasting resources)[/quote]</P> <P>Are you using the latest Mercury version? A session log would be useful as this message is for information only.</P>

Yes using latest version.

I had to change my dns to point to my secondary server, just so the email would go threw from remote server trying to send it. (they tried 5+ times last night).

When mercury receives large emails, it uses up a lot of cpu cycles.

<p>Yes using latest version.</p><p>I had to change my dns to point to my secondary server, just so the email would go threw from remote server trying to send it. (they tried 5+ times last night).</p><p>When mercury receives large emails, it uses up a lot of cpu cycles.</p>

Mercury will typically use tiny system resources when receiving a message by SMTP, even if there are big attachments. Do you have any realtime antivirus software running that might interfere with Mercury's network or disk access?

 

<p>Mercury will typically use tiny system resources when receiving a message by SMTP, even if there are big attachments. Do you have any realtime antivirus software running that might interfere with Mercury's network or disk access?</p><p> </p>
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft