Technically it lies about it's dependencies as if it's working with
Rails 3 which does have mail gem as a dependency.  Anyway the
problematic line is
which passes in a few options that aren't required anymore,  the
current method for mail gem is to flatten and turn them into mail
fields.  I've never  really worked with the older mail gem but it
looks the way you are doing it is passing configs, fields and a
mailer.  This is no longer the preferred method.

Firing up my trusty Pry console: (cheatery inc, it's also cut)
[2] pry(main)> show-doc

@ line 49:
Number of lines: 45
Owner: #<Class:Mail>
Visibility: public
Signature: new(*args, &block)

 message ={
  :to => '',
  'from' => '',
  :subject => 'This is an email',
  :body => 'This is the body'

Tracing it back to here you
notice that now with the latest gem you are doing it all wrong.
Shouldn't be too hard to fix, I'll see what I can later tonight and
send up a pull request to fix it once I look at the full source of the
mailer extension and see what exactly it's doing and why it's doing

On Tue, Apr 24, 2012 at 5:03 PM, john <> wrote:
> i don't think the mailer extension has any external dependencies. do you
> mean something in the mailer extension conflicts with your using the mail
> gem for some other purpose?
> On Tuesday, April 24, 2012 10:49:49 AM UTC-5, AJ Siegel wrote:
>> It seems like the Mailer extension is only compatible with versions of
>> the Mail gem <2.0. Specifically, I think after 2.0 Mail gem removed
>> the valid_config? method and there are a few other issues.
>> This is preventing me from successfully implementing AWS-SES gem
>> because it is only compatible with Mail > 2.0
>> Is anyone working on the mailer extension to make it compatible with
>> 2.0 and greater?

Reply via email to