Mercury crashes when using SSL/Direct with mail.q.com

colorbars

posted Jun 18 '11 at 8:22 pm

My bad. I did but it didn't make sense.

Error -32 activating SSL session (locus 6014, type 4, code 0, 'Bad server key agreement parameter signature')

My bad. I did but it didn't make sense.&nbsp;Error -32 activating SSL session (locus 6014, type 4, code 0, 'Bad server key agreement parameter signature') &nbsp;

colorbars

posted Jun 18 '11 at 5:20 pm

I'm following the instructions that Qwest has for setting up POP3 mail. When trying to use the SSL with direct connection option to mail.q.com port 995, MercuryD responds with a D with a dash through the left side and "network error, delivering anyway" then crashes a few seconds later. I know the username/password is ok because switching to no encryption on port 110 works correctly. Also the direct SSL to GMail works correctly. Any ideas on what it is that Mercury doesn't like?

I'm following the instructions that Qwest has for setting up POP3 mail.&nbsp; When trying to use the SSL with direct connection option to mail.q.com port 995, MercuryD responds with a D with a dash through the left side and "network error, delivering anyway" then crashes a few seconds later.&nbsp; I know the username/password is ok because switching to no encryption on port 110 works correctly.&nbsp; Also the direct SSL to GMail works correctly.&nbsp; Any ideas on what it is that Mercury doesn't like?&nbsp;

Thomas R. Stephenson

posted Jun 18 '11 at 6:21 pm

> Any ideas on what it is that Mercury doesn't like?

No idea but turn on session logging in MercuryD to see what sort of failure you have.

&gt; Any ideas on what it is that Mercury doesn't like?No idea but turn on session logging in MercuryD to see what sort of failure you have.

Related Topics

Pending draft

Confirm move posts

Insufficient permissions

Select a different topic

Edit history