Problem with ssl context for smtp

[roxanneskelly]

The ruby 1.8.7 smtp provider takes an SSL context in enable_tls
/usr/lib/ruby/1.8/net/smtp.rb:307

in 2.5.4, smtp.rb was refactored to include an ssl_context call
which returns a context for ruby 1.9.0 +, and a string for verify_mode before that.
The result of this is passed down via enable_starttls/enable_starttls_auto to the 1.8.7 provider, which is expecting a context, not a string.

Results in failure:

FAILURE creating account: wrong argument (NilClass)! (Expected kind of OpenSSL::SSL::SSLContext)
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/net/smtp.rb:577:in `initialize'

(also on linux).

This was introduced in 2.5.4 (some oddness in 2.5.3 as well)

[korny]

Downgrading to 2.5.3 fixed the issue for us as well.

[nickhammond]

I'm also getting this issue, downgrading to 2.5.3 fixed the issue for me.

Can we yank 2.5.4 from rubygems? I just upgraded a few gems and it bumped the mail gem up to 2.5.4 triggering this behavior.

[ConradIrwin]

@nickhammond In the time before a new mail gem is released, feel free to put gem 'mail', '2.5.3' in your gemspec; this will prevent it from being upgraded when other gems are released.

[korny]

Great! Can you post here please when it's released? We haven't set up Gemnasium yet…

[nickhammond]

@ConradIrwin Thanks! Yah, I've specified 2.5.3 in there now so it won't do that. It got bumped when I upgraded Rails but I looked and they specify "~> 2.5.3" for the mail gem so Bundler must've just grabbed the latest.

[korny]

Rails 3.2.14 specifies ~> 2.5.4 now :/ Any chance for a new Gem release soon?

[corasaurus-hex]

Bump, any word on releasing a newer version?

[0xCCD]

Bump => Same problem, no downgrade possible with Rails 3.2.14

[ejzn]

Downgrading also did the trick for me. Glad I was able to find this thread.

[moty66]

Same here, downgrade to 2.5.3

Environment:
  Redmine version                2.3.3.stable.12137
  Ruby version                   1.8.7-p302 (2010-08-16) [i486-linux]
  Rails version                  3.2.13

[PowerKiKi]

Same here, had to workaround this by downgrading to 2.5.3.

This issue impact quite a few of Redmine users according to http://www.redmine.org/issues/13698

[tuupola]

Any change of 2.5.5 release?

[paulRbr]

We also had to downgrade to 2.5.3 in our team to make this work.

[jgm]

It would be great to have a 2.5.5 release. This problem is keeping me from doing rails security updates, since rails 2.3.16 requires mail 2.5.4.

[0xCCD]

+1

[paulRbr]

You can force the version in your lock file for the moment
Em 04/12/2013 19:29, "0xCCD" [email protected] escreveu:

+1

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/548#issuecomment-29831146
.

[PowerKiKi]

This bug was fixed 7 months ago, but it still affects users because it was never released. The last release is 9 months old.

Is there anything we could do to make mail 2.5.5 a reality ?

[simondeziel]

I'd really appreciate if the patch could make it into the next release as we are stuck with ruby 1.8.7 here.

[korny]

One solution: Use our fork.

gem 'mail', '= 2.5.4', :github => 'sofatutor/mail', :branch => '2.5.4-with-fix-548' # see https://github.com/mikel/mail/issues/548

[mikruhland]

@korny : Thanks a lot for you fork! I was searching along time to get this problem fixed!

[nburwell]

+1 for a 2.5.5 release that fixes the 1.8.7 bug

[alexparker]

+1 here too

[neohunter]

+1

[bf4]

Dear commenters: this issue is closed. Please create a new issue with the mail gem version and ruby version you are using (assuming you're using one that has the fix in it).