[ww-bugs] Bug 3407: Failed to open the mailer: IO::Socket::SSL->start_SSL failed: SSL connect attempt failed with unknown error error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed

[bugzilla-daemon at webwork.maa.org]

http://bugs.webwork.maa.org/show_bug.cgi?id=3407





--- Comment #4 from Mike Gage <gage at math.rochester.edu>  2015-09-01 09:36:15 ---
Earlier reports of this problem (2013)

Hi Michael --

Something funny is going on with bugx.webwork.maa.org, so I'll send you this
bug instead of reporting it normally....

I figured out what the deal was with my error when trying to send email.  If
the CPAN module Mail::Sender is updated to a recent version, then email will no
longer work, and this error is generated.  I'm not sure if that will always
happen, or only if the mail server is using a self-signed certificate, like
here.

In order to fix the error, I rolled back Mail::Sender to version 0.8.16
(current version is 0.8.22).  You can roll back versions by temporarily
including backpan.perl.org as a repository and then installing with the version
number
 > o conf urllist push http://backpan.perl.org/ 
 > install J/JE/JENDA/Mail-Sender-0.8.16.tar.gz

I'm didn't spend enough time to figure out how to update webwork to be
compatible with the new Mail::Sender, so I cannot suggest a modification of
webwork code to fix this.

 Ben


On Thu, Feb 21, 2013 at 10:22 AM, Ben Walter <benwalt at gmail.com> wrote:
Hi Michael --

I've been trying to get a new webwork server up and running 2.5 for our
students this semester.  I've managed to get everything going well, except for
one thing.... the server can't send email.

When I try to send email using the "feedback to the instructor" button, I get
an error: 

Failed to open the mailer: IO::Socket::SSL->start_SSL failed: SSL connect
attempt failed with unknown error error:14090086:SSL
routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed

Sending email using the instructor function doesn't work either.  Though that
fails silently.

This may be related to METU using self-signed certificates for its systems (or
to the webwork server using a self-signed certificate).  Chrome also complains
about the certificate whenever I login to the METU system/webwork.  

Looking online it appears that I should be able to tell Socket to not check
certificates.... but I can't figure out where to modify the webwork code. 
Could you help out please?

(Incidentally, this problem never happened with the 2.4 installation.  I'm not
sure if it is due to a change in 2.5 code, or to me switching the server to
https in the new installation.)


 Ben

-- 
Configure bugmail: http://bugs.webwork.maa.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.