Dumb.  Ok, the "fix" I did was to create new self-signed certs, but when I did that, the file permissions were only for my login, it didn't inherit the folder permissions of the Mercury program folder.  Very strange.  Ok, so I fixed that.  I guess that is my punishment, better to just live with the periodic SSL errors I guess than to hose myself completely! [8-)]

I don't recall ever getting these before when running Mercury 4.01b for over 3 years, but since I upgraded to version 4.51 in early May, every few days, I'll get a failure trying to send a message through.  I go under queued Mail in Pegasus and re-send and it always re-sends fine.  The last time it happened, two days ago, I went into Mercury and enabled session logging and tonight when it just happened again, the error in the session log is:

19:10:26.359: << 220 OK, begin SSL/TLS negotiation now.<cr><lf>
19:10:26.375: 22: Error -32 activating SSL session (locus 0, type 0, code 0, '')

 Now, when I re-sent it from the Pegasus queue, it went through...

19:10:38.625: << 220 OK, begin SSL/TLS negotiation now.<cr><lf>
19:10:38.640: [*] SSL/TLS session established: 3DES, CBC mode, keysize 192 bits

Given that my two computers I do almost all of my e-mailing on haven't changed and the only change to Mercury was updating from 4.01c to 4.51, any idea why this periodic SSL error would suddenly appear?

 Regards,

Tom T.

Actually, in trying "fix" it, I apparently now broke it to the point where Mercury now refuses all SSL connections, now with
Error -41.   [:'(]