actionmailer 3.2.13 requires "mail ~> 2.5.3" breaking compatibility

[semmons99]

we just upgraded to 3.2.13 from 3.2.12. actionmailer now appears to require mail ~> 2.5.3 which is causing us to receive OpenSSL::SSL::SSLError: SSL_connect returned=1 errno=0 state=unknown state: unknown protocol even though we explictly set openssl_verify_mode to none.

help!

[j-w]

+1

On Mon, Mar 18, 2013 at 1:58 PM, Shane Emmons notifications@github.comwrote:

we just upgraded to 3.2.13 from 3.2.12. actionmailer now appears to
require mail ~> 2.5.3 which is causing us to receive OpenSSL::SSL::SSLError:
SSL_connect returned=1 errno=0 state=unknown state: unknown protocol even
though we explictly set openssl_verify_mode to none.

help!

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/9780
.

[rafaelfranca]

@jeremy thoughts?

[rafaelfranca]

Guys, please, help us and try the release candidates, after the release we can't rush to fix your issues.

[masterkain]

I just got bitten by this, started investigating

[take]

Hmm looks like this is breaking the backward compatibility of ActionMailer::Base.mail method too.

If we dont pass any recipient (To, Cc or Bcc) like belows code, we'll now get an error in action_mail 3.2.13

mail(from: "noreply <noreply@foo.com>",
  to: nil, subject: "hello, this is a mail")

ArgumentError:
  At least one recipient (To, Cc or Bcc) is required to send a message

[joelr]

👍

[arunagw]

@tkhr I think previously it was silently failing if there are no TO in mail. But now it's giving an error.

[take]

@arunagw

@tkhr I think previously it was silently failing if there are no TO in mail. But now it's giving an error.

Yea exactly, doesn't that mean the backwards compatibility is broken?
Now we'll have to check all of the recipient variables before executing the mail method right?

like

mail(from: "noreply <noreply@foo.com>",
  to: @user.email, subject: "hello, this is a mail")

to

unless @user.email.blank?
  mail(from: "noreply <noreply@foo.com>",
    to: @user.email, subject: "hello, this is a mail")
end

[ledermann]

Regarding the SSL issue: Maybe caused by this?
mikel/mail@9890b19

[semmons99]

@ledermann: looks like a leading candidate

[djhopper01]

@tkhr We're seeing this as well (although we found it was a bad test that was not supplying To:)

@rafaelfranca Thanks for the tip. We'll try to test release candidates against our app in the future.

[semmons99]

I've worked around this by manually setting mail = 2.4.4 in the Gemfile.lock. It's not pretty, but it works for now.

[markysharky70]

I ran into this problem upgrading from rails 3.2.11 to 3.2.13. Oddly enough my work around was to remove the "openssl_verify_mode => 'none'" from my configuration. After doing this the error went away and the emails deliver. One smtp server is using a self-signed certificate and the other a wildcard certificate...once upon a time this parameter was required in these scenarios.

[mvlwn]

The "openssl_verify_mode => 'none'" is the problem for me too. I will try to remove it, and deploy again.

[robertcigan]

Having the same error for 3.2.13 but not for 3.2.12