Forum: Ruby on Rails action mailer settings and dkim signing

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
Stephen Burke (Guest)
on 2015-02-15 09:08
(Received via mailing list)
I am trying to figure out why this block of code in my
environments/production.rb file is causing the dkim signing to break.  I
have email being sent from a rake task with my UserMailer class.  It is
derived from Devise::Mailer.  If I have the action_mailer configuration
block within the "config.after_initialize" the dkim signature does not
through.  If I don't have that line "after_initialize" the signature
through.  Can someone shed some light on this for me?

Here's the code for my UserMailer class and the production.rb file.


require "#{Rails.root}/app/helpers/user_helper"
include UserHelper

class UserMailer < Devise::Mailer
  helper :application # gives access to all helpers defined within
  include Devise::Controllers::UrlHelpers # Optional. eg.
  default from: "Save The Sparkles <>",
  reply_to: ""


config.action_mailer.asset_host     = ''

config.action_mailer.default_url_options = { host: ''
config.after_initialize do
  config.action_mailer.perform_deliveries = true
  config.action_mailer.raise_delivery_errors = true
  config.action_mailer.delivery_method = :smtp
  config.action_mailer.smtp_settings = {
    address:              '',
    port:                 587,
    domain:               '',
    user_name:            ENV['AWS_SES_USER'],
    password:             ENV['AWS_SES_PASS'],
    authentication:       :login,
    enable_starttls_auto: true
Matt Jones (Guest)
on 2015-02-19 03:20
(Received via mailing list)
On Saturday, 14 February 2015 21:17:21 UTC-5, Stephen Burke wrote:
>   default from: "Save The Sparkles <
> config.action_mailer.default_url_options = { host: '' }
>     authentication:       :login,
>     enable_starttls_auto: true
>   }
> end
The documentation for Rails::Railtie::Configuration describes
after_initialize as the "last configurable block to run, called after
frameworks initialize". ActionMailer's own initialization routine copies
the values from config.action_mailer *before* the code above sets them.
the behavior you've described makes sense.

A better question is, why is having after_initialize here important?
the intent?

--Matt Jones
This topic is locked and can not be replied to.