This happens on a regular basis every few days, with no known cause, and has been occurring for over 1 year since upgrading from XP to Win7. Does the WIn crash report indicate the problem?
Problem signature:
Problem Event Name: APPCRASH
Application Name: mercury.exe
Application Version: 4.7.4.0
Application Timestamp: 00000000
Fault Module Name: MERCURYD.DLL
Fault Module Version: 4.7.4.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 00008a1b
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 7177
Additional Information 1: 4bd9
Additional Information 2: 4bd9b05052f87040d21802f26402028b
Additional Information 3: 57ba
Additional Information 4: 57ba5094906127bcb802018e1de52d03
The report indicates that the problem originated in the MercuryD POP3 client module, so that's probably a good place to start investigating the cause. Check MercuryD settings and try switching off encryption if activated. Make sure there is no antivirus software running that might interfere with Mercury's disk or network access. All Mercury directories should preferably be excluded from realtime AV checking. If the problem persists, try temporarily switching on session logging in MercuryD to see if that reveals something.
Thank you for this tip, Rolf. Now that you mention it, I think the problem may have started when we switched from "Normal (no encryption)" to "SSL encryption using direct connection". It would be difficult to switch back to Normal for a period of time long enough to definitely prove this. The antivirus software is AVG free, but we've used this longer than the problem has been occurring, so I would think it unlikely to cause this.
So my question would be: is there a history of problems with SSL encryption and Mercury? Will switch on session logging anyway.
There has been various issues with SSL encryption for some time, mainly because the external encryption library used in version 4.74 and earlier is somewhat outdated. For that reason v. 4.80 will use current OpenSSL instead, which has performed very satisfactory in beta testing.
The thing about beta testing is that there can always be another bug that unexpectedly pops up just when you think everything is OK. That said, the current beta build has been running without flaws on 2 servers here since Monday, and I feel very optimistic about it! As for MercuryD David has written in another thread (http://community.pmail.com/forums/2/39043/ShowThread.aspx) that the 4.80 module actually can be used together with 4.74. Please let me know if you want a download link.
[quote user="Rolf Lindby"]The thing about beta testing is that there can always be another bug that unexpectedly pops up just when you think everything is OK. That said, the current beta build has been running without flaws on 2 servers here since Monday, and I feel very optimistic about it! As for MercuryD David has written in another thread (http://community.pmail.com/forums/2/39043/ShowThread.aspx) that the 4.80 module actually can be used together with 4.74. Please let me know if you want a download link.[/quote]
Hi!
Today our uplink was switched over to SSL... And my 4.74 POP3 cannot handle that. Please provide access to the 4.80 MercuryD (or any other possible fix or solution). I do not want to use stunnel or spamihilator or anything additionally, if possible...
Thanks in advance!
