class ActionMailer::Base

delivery_method :test. Most useful for unit and functional testing.
* deliveries - Keeps an array of all the emails sent out through the Action Mailer with
be turned off to aid in functional testing.
call .deliver on an email message or on an Action Mailer method. This is on by default but can
* perform_deliveries - Determines whether emails are actually sent from Action Mailer when you
implement for a custom delivery agent.
object e.g. MyOwnDeliveryMethodClass. See the Mail gem documentation on the interface you need to
:sendmail, :test, and :file. Or you may provide a custom delivery method
* delivery_method - Defines a delivery method. Possible values are :smtp (default),
* raise_delivery_errors - Whether or not errors should be raised if the email fails to be delivered.
tmp/mails.
* :location - The directory into which emails will be written. Defaults to the application
* file_settings - Allows you to override options for the :file delivery method.
added automatically before the message is sent.
* :arguments - The command line arguments. Defaults to -i -t with -f sender@address
* :location - The location of the sendmail executable. Defaults to /usr/sbin/sendmail.
* sendmail_settings - Allows you to override options for the :sendmail delivery method.
OpenSSL::SSL::VERIFY_PEER, …).
'fail_if_no_peer_cert') or directly the constant (OpenSSL::SSL::VERIFY_NONE,
of an OpenSSL verify constant ('none', 'peer', 'client_once',
really useful if you need to validate a self-signed and/or a wildcard certificate. You can use the name
* :openssl_verify_mode - When using TLS, you can set how OpenSSL checks the certificate. This is
to use it. Defaults to true.
* :enable_starttls_auto - Detects if STARTTLS is enabled in your SMTP server and starts
information and a cryptographic Message Digest 5 algorithm to hash important information)
send password Base64 encoded) or :cram_md5 (combines a Challenge/Response mechanism to exchange
This is a symbol and one of :plain (will send the password in the clear), :login (will
authentication type here.
* :authentication - If your mail server requires authentication, you need to specify the
* :password - If your mail server requires authentication, set the password in this setting.
* :user_name - If your mail server requires authentication, set the username in this setting.
* :domain - If you need to specify a HELO domain, you can do it here.
* :port - On the off chance that your mail server doesn’t run on port 25, you can change it.
“localhost” setting.
* :address - Allows you to use a remote mail server. Just change it from its default
* smtp_settings - Allows detailed configuration for :smtp delivery method:
Can be set to nil for no logging. Compatible with both Ruby’s own Logger and Log4r loggers.
* logger - the logger is used for generating information on the mailing run if available.
per the above section.
* default_options - You can pass this in at a class level as well as within the class itself as
ActionMailer::Base.raise_delivery_errors = true
These options are specified on the class level, like
= Configuration options
previewing emails.
and register_preview_interceptor if they should operate on both sending and
Note that interceptors need to be registered both with register_interceptor
config.action_mailer.preview_interceptors :css_inline_styler
end
end
# inline CSS styles
def self.previewing_email(message)
class CssInlineStyler
a preview interceptor that has a previewing_email method:
Previews can also be intercepted in a similar manner as deliveries can be by registering
on a running development server instance.
An overview of all previews is accessible at http://localhost:3000/rails/mailers
config.action_mailer.preview_path = “#{Rails.root}/lib/mailer_previews”
of test/mailers/previews:
mailer previews directory can be configured using the preview_path option which has a default
method without the additional deliver_now / deliver_later. The location of the
Methods must return a Mail::Message object which can be generated by calling the mailer
end
end
Notifier.welcome(User.first)
def welcome
class NotifierPreview < ActionMailer::Preview
with database data, you’ll need to write some scenarios to load messages with fake data:
ActionMailer::Base.preview_path. Since most emails do something interesting
You can preview your email templates visually by adding a mailer preview file to the
= Previewing emails
rather than after_action in your Action Mailer classes so that headers are parsed properly.
Note that unless you have a specific reason to do so, you should prefer using before_action
inherit from ActionController::Base.
callbacks in the same manner that you would use callbacks in classes that
AbstractController::Callbacks, so you can define and configure
Callbacks in Action Mailer are implemented using<br><br>end<br>end<br>attachments.inline = File.read(‘/path/to/filename.jpg’)
def add_inline_attachment!
private
end
mail
def welcome
before_action :add_inline_attachment!
class Notifier < ApplicationMailer
messages sent out by a certain mailer class:
This may be useful, for example, when you want to add default inline attachments for all
You can specify callbacks using before_action and after_action for configuring your messages.
= Callbacks
config.action_mailer.default_options = { from: “no-reply@example.org” }
the default_options= configuration in config/application.rb:
It is also possible to set these default options that will be used in all mailers through
mailer method, it will get over written by the mailer method.
set something in the defaults using a proc, and then set the same thing inside of your
Note that the proc is evaluated right at the start of the mail message generation, so if you
end
end
’some complex call’
def my_method
private
default ‘X-Special-Header’ => Proc.new { my_method }
class Notifier < ApplicationMailer
can define methods that evaluate as the message is being generated:
Finally, Action Mailer also supports passing Proc objects into the default hash, so you
end
content_description: ‘This is a description’
default ‘Content-Transfer-Encoding’ => ‘7bit’,
class Notifier < ApplicationMailer
an underscored symbol, so the following will work:
As you can pass in any header, you need to either quote the header as a string, or pass it in as
but Action Mailer translates them appropriately and sets the correct values.
parts_order and charset are not actually valid Mail::Message header fields,
* parts_order: [ "text/plain", "text/enriched", "text/html" ]
* content_type: "text/plain",
* charset: "UTF-8",
* mime_version: "1.0"
ActionMailer::Base sets the following:
You can pass in any header value that a Mail::Message accepts. Out of the box,
end
default sender: ‘system@example.com’
class Notifier < ApplicationMailer
default method inside the class definition:
Action Mailer provides some intelligent defaults for your emails, these are usually specified in a
= Default Hash
in Mail::Message instance.
the delivery agents. Your class should make any needed modifications directly to the passed
called before the email is sent, allowing you to make modifications to the email before it hits
An interceptor class must implement the :delivering_email(message) method which will be
called once for every email sent after the email has been sent.
An observer class must implement the :delivered_email(message) method which will be
register classes that are called during the mail delivery life cycle.
Action Mailer provides hooks into the Mail observer and interceptor methods. These allow you to
= Observing and Intercepting Mails
<%= image_tag attachments.url, alt: ‘Our Photo’, class: ‘photo’ -%>
<h1>Please Don’t Cringe</h1>
As we are using Action View’s image_tag method, you can pass in any other options you want:
<%= image_tag attachments.url -%>
<h1>Please Don’t Cringe</h1>
url on the attachment to get the relative content id path for the image source:
make a call to image_tag passing in the attachment you want to display and then call
And then to reference the image in the view, you create a welcome.html.erb file and
end
end
mail(to: recipient, subject: “Here is what we look like”)<br>attachments.inline = File.read(‘path/to/photo.png’)
def welcome(recipient)
class Notifier < ApplicationMailer
if you want to display a corporate logo or a photo.
You can also specify that a file should be displayed inline with other HTML. This is useful
= Inline Attachments
end
end
mail(to: recipient, subject: “New account information”, body: “”)
= File.read(‘path/to/file.pdf’)
def welcome(recipient)
class Notifier < ApplicationMailer
or add an empty body parameter like this:
If you need to send attachments with no content, you need to create an empty view for it,
with the filename free_book.pdf.
and the second being a application/pdf with a Base64 encoded copy of the file.pdf book
the first part being a multipart/alternative with the text and HTML email parts inside,
template in the view directory), send a complete multipart/mixed email with two parts,
Which will (if it had both a welcome.text.erb and welcome.html.erb
end
end
mail(to: recipient, subject: “New account information”)<br>attachments = File.read(‘path/to/file.pdf’)
def welcome(recipient)
class Notifier < ApplicationMailer
Sending attachment in emails is easy:
= Attachments
to multipart/alternative.
This means that you’ll have to manually add each part to the email and set the content type of the email
Implicit template rendering is not performed if any attachments or parts have been added to the email.
body. The same instance variables defined in the action are passed to all email templates.
which indicates that the email contains multiple different representations of the same email
type. The content type for the entire message is automatically set to multipart/alternative,
Each would be rendered and added as a separate part to the message, with the corresponding content
* signup_notification.yml.erb
* signup_notification.xml.builder
* signup_notification.html.erb
* signup_notification.text.erb
For example, if the following templates exist:
type. Each such detected template will be added as a separate part to the message.
multipart templates, where each template is named after the name of the action, followed by the content
Multipart messages can also be used implicitly because Action Mailer will automatically detect and use
= Multipart Emails
You never instantiate your mailer class. Rather, you just call the method you defined on the class itself.
Notifier.welcome(User.first).deliver_later # enqueue the email sending to Active Job
of the request-response cycle, so the user doesn’t have to wait on it):
Action Mailer is nicely integrated with Active Job so you can send emails in the background (example: outside
Notifier.welcome(User.first).message # => a Mail::Message object
the ActionMailer::MessageDelivery object.
you want direct access to the Mail::Message object you can call the message method on
The ActionMailer::MessageDelivery class is a wrapper around a Mail::Message object. If
mail.deliver_now # sends the email
mail = Notifier.welcome(User.first) # => an ActionMailer::MessageDelivery object
Notifier.welcome(User.first).deliver_now # sends the email
for delivery later:
Once a mailer action and template are defined, you can deliver your message or create it and save it
= Sending mail
only_path: false will ensure that absolute URLs are generated.
will generate relative URLs by default when a :host option isn’t explicitly provided, passing
only_path: false option when using url_for. Since the url_for view helper
When you decide to set a default :host for your mailers, then you need to make sure to use the
config.action_mailer.default_url_options = { host: “example.com” }
option as a configuration option in config/application.rb:
It is also possible to set a default host that will be used in all mailers by setting the :host
have no concept of a current URL from which to determine a relative path.
named_route_path style (which generates relative URLs), since clients reading the mail will
You should use the named_route_url style (which generates absolute URLs) and avoid using the
<%= users_url(host: “example.com”) %>
When using named routes you only need to supply the :host:
<%= url_for(host: “example.com”, controller: “welcome”, action: “greeting”) %>
When using url_for you’ll need to provide the :host, :controller, and :action:
to provide all of the details needed to generate a URL.
Action Pack, the mailer instance doesn’t have any context about the incoming request, so you’ll need
URLs can be generated in mailer views using url_for or named routes. Unlike controllers from
= Generating URLs
<%= truncate(@note.body, length: 25) %>
You got a new note from <%= message.from %>!
If you need to access the subject, from or the recipients in the view, you can do that through message object:
<%= truncate(@note.body, length: 25) %>
You got a new note!
You can even use Action View helpers in these views. For example:
Thanks for joining our service! Please check back often.
Hi <%= @account.name %>,
Emails by default are sent in plain text, so a sample view for our model example might look like this:
corresponding view.
Variables defined in the methods of your mailer model are accessible as instance variables in their
app/views/notifier/welcome.text.erb would be used to generate the email.
name as the method in your mailer model. For example, in the mailer defined above, the template at
To define a template to be used with a mailing, create an .erb file with the same
method of the class looks for a template with its name.
Like Action Controller, each mailer class has a corresponding view directory in which each
= Mailer views
end
format.html { render “some_other_template” }
format.text
mail(to: user.email) do |format|
Or even to render a special view:
end
format.html
format.text(content_transfer_encoding: “base64”)
mail(to: user.email) do |format|
The block syntax is also useful in providing information specific to a part:
end
format.html
format.text
mail(to: user.email) do |format|
If you want to explicitly render only certain templates, pass a block:
file as well as the welcome.html.erb view file in a multipart/alternative email.
the same name as the method, so the above action would send the welcome.text.erb view
The mail method, if not passed a block, will inspect your views and send all the views with
will accept (any valid email header including optional fields).
The hash passed to the mail method allows you to specify any header that a Mail::Message
* mail - Allows you to specify email to be sent.
as headers({'X-No-Spam' => 'True', 'In-Reply-To' => '1234@message.id'})
* headers(hash) - Allows you to specify multiple headers in your email such
will add many fields of the same name. Read #headers doc for more information.
as headers['X-No-Spam'] = 'True'. Note that declaring a header multiple times
* headers[]= - Allows you to specify any header field in your email such
in the same manner as attachments[]=
* attachments.inline[]= - Allows you to add an inline attachment to your email
manner; attachments['filename.png'] = File.read('path/to/filename.png')
* attachments[]= - Allows you to add attachments to your email in an intuitive
Within the mailer method, you have access to the following methods:
end
end
bcc: [“bcc@example.com”, “Order Watcher <watcher@example.com>”])
mail(to: recipient.email_address_with_name,
@account = recipient
def welcome(recipient)
return_path: ‘system@example.com’
default from: ‘no-reply@example.com’,
class Notifier < ApplicationMailer
end
layout ‘mailer’
default from: ‘from@exmaple.com’
class ApplicationMailer < ActionMailer::Base
the mailer views, options on the mail itself such as the :from address, and attachments.
used to generate an email message. In these methods, you can setup variables to be used in
inherits from ActionMailer::Base. A mailer model defines methods
The generated model inherits from ApplicationMailer which in turn
$ rails generate mailer Notifier
To use Action Mailer, you need to create a mailer model.
= Mailer Models
Action Mailer allows you to send email from your application using a mailer model and views.

def self.supports_path?

Emails do not support relative path links.

def self.supports_path?
  false
end

def _protected_ivars # :nodoc:

:nodoc:

def _protected_ivars # :nodoc:
  PROTECTED_IVARS
end

def attachments

mail.attachments[0] # => Mail::Part (first attachment)
# or by index

mail.attachments['filename.jpg'] # => Mail::Part object or nil
# By Filename

You can also search for specific attachments:

content: file_content }
encoding: 'SpecialEncoding',
mail.attachments['filename.jpg'] = {mime_type: 'application/x-gzip',
file_content = SpecialEncode(File.read('/path/to/filename.jpg'))

Mail to know how to decode this data:
but then it is up to you to pass in the content pre-encoded, and don't expect
If you want to use a different encoding than Base64, you can pass an encoding in,

content: File.read('/path/to/filename.jpg')}
mail.attachments['filename.jpg'] = {mime_type: 'application/x-gzip',

You can also specify overrides if you want by passing a hash instead of a string:

base64 encode the contents of the attachment all for you.
set the Content-Type, Content-Disposition, Content-Transfer-Encoding and
If you do this, then Mail will take the file name and work out the mime type

mail.attachments['filename.jpg'] = File.read('/path/to/filename.jpg')

Allows you to add attachments to an email, like so:

def attachments
  if @_mail_was_called
    LateAttachmentsProxy.new(@_message.attachments)
  else
    @_message.attachments
  end
end

def collect_responses(headers) #:nodoc:

:nodoc:

def collect_responses(headers) #:nodoc:
  responses = []
  if block_given?
    collector = ActionMailer::Collector.new(lookup_context) { render(action_name) }
    yield(collector)
    responses = collector.responses
  elsif headers[:body]
    responses << {
      body: headers.delete(:body),
      content_type: self.class.default[:content_type] || "text/plain"
    }
  else
    templates_path = headers.delete(:template_path) || self.class.mailer_name
    templates_name = headers.delete(:template_name) || action_name
    each_template(Array(templates_path), templates_name) do |template|
      self.formats = template.formats
      responses << {
        body: render(template: template),
        content_type: template.type.to_s
      }
    end
  end
  responses
end

def create_parts_from_responses(m, responses) #:nodoc:

:nodoc:

def create_parts_from_responses(m, responses) #:nodoc:
  if responses.size == 1 && !m.has_attachments?
    responses[0].each { |k,v| m[k] = v }
  elsif responses.size > 1 && m.has_attachments?
    container = Mail::Part.new
    container.content_type = "multipart/alternative"
    responses.each { |r| insert_part(container, r, m.charset) }
    m.add_part(container)
  else
    responses.each { |r| insert_part(m, r, m.charset) }
  end
end

def default(value = nil)

Aliased by ::default_options=

config.action_mailer.default(from: "no-reply@example.org")

Sets the defaults through app configuration:

def default(value = nil)
  self.default_params = default_params.merge(value).freeze if value
  default_params
end

def default_i18n_subject(interpolations = {})

If the subject has interpolations, you can pass them through the +interpolations+ parameter.
humanized version of the action_name.
If it does not find a translation for the +subject+ under the specified scope it will default to a
Translates the +subject+ using Rails I18n class under [mailer_scope, action_name] scope.

def default_i18n_subject(interpolations = {})
  mailer_scope = self.class.mailer_name.tr('/', '.')
  I18n.t(:subject, interpolations.merge(scope: [mailer_scope, action_name], default: action_name.humanize))
end

def deliver_mail(mail) #:nodoc:

:nodoc:
nothing except tell the logger you sent the email.
calling +deliver_mail+ directly and passing a Mail::Message will do
through a callback when you call :deliver on the Mail::Message,
This method is actually called by the Mail::Message object itself

Wraps an email delivery inside of ActiveSupport::Notifications instrumentation.

def deliver_mail(mail) #:nodoc:
  ActiveSupport::Notifications.instrument("deliver.action_mailer") do |payload|
    set_payload_for_mail(payload, mail)
    yield # Let Mail do the delivery actions
  end
end

def each_template(paths, name, &block) #:nodoc:

:nodoc:

def each_template(paths, name, &block) #:nodoc:
  templates = lookup_context.find_all(name, paths)
  if templates.empty?
    raise ActionView::MissingTemplate.new(paths, name, paths, false, 'mailer')
  else
    templates.uniq { |t| t.formats }.each(&block)
  end
end

def headers(args = nil)

for the same header.
+nil+ in order to reset the value otherwise another field will be added
If you want to replace any header which already exists, first set it to

X-Anything can appear multiple times.
Fields can only appear once in email headers while other fields such as

* +references+
* +message-id+
* +orig-date+
* +reply-to+
* +bcc+
* +cc+
* +to+
* +from+
* +sender+
* +subject+

Note about replacing already defined headers:

X-Special-Domain-Specific-Header: SecretValue

The resulting Mail::Message will have the following in its header:

'In-Reply-To' => incoming.message_id
headers 'X-Special-Domain-Specific-Header' => "SecretValue",

which will then be set on the Mail::Message object:
You can also pass a hash into headers of header field names and values,

headers['X-Special-Domain-Specific-Header'] = "SecretValue"

object which will add them to itself.
Allows you to pass random and unusual headers to the new Mail::Message

def headers(args = nil)
  if args
    @_message.headers(args)
  else
    @_message
  end
end

def initialize(method_name=nil, *args)

method, for instance).
remain uninitialized (useful when you only need to invoke the "receive"
will be initialized according to the named method. If not, the mailer will
Instantiate a new mailer object. If +method_name+ is not +nil+, the mailer

def initialize(method_name=nil, *args)
  super()
  @_mail_was_called = false
  @_message = Mail.new
  process(method_name, *args) if method_name
end

def insert_part(container, response, charset) #:nodoc:

:nodoc:

def insert_part(container, response, charset) #:nodoc:
  response[:charset] ||= charset
  part = Mail::Part.new(response)
  container.add_part(part)
end

def mail(headers = {}, &block)

end
format.html
format.text(content_transfer_encoding: "base64")
mail(to: 'mikel@test.lindsaar.net') do |format|

The block syntax also allows you to customize the part headers if desired:

+text/html+ parts.
Which will render a +multipart/alternative+ email with +text/plain+ and

end
format.html { render html: "

Hello Mikel!

".html_safe }
format.text { render plain: "Hello Mikel!" }
mail(to: 'mikel@test.lindsaar.net') do |format|

You can even render plain text directly without using a template:

end
format.html
format.text
mail(to: 'mikel@test.lindsaar.net') do |format|

If you do pass a block, you can render specific templates of your choice:

And now it will look for all templates at "app/views/notifications" with name "another".

mail(template_path: 'notifications', template_name: 'another')

However, those can be customized:

If no welcome template exists, it will raise an ActionView::MissingTemplate error.
Will look for all templates at "app/views/notifier" with name "welcome".

end
end
mail(to: 'mikel@test.lindsaar.net')
def welcome

default from: 'no-reply@test.lindsaar.net'
class Notifier < ActionMailer::Base

For example:

ready to call :deliver on to send.
content type and sequence, and return a fully prepared Mail::Message
each of these templates intelligently, making educated guesses on correct
method name that it is being called from, it will then create parts for
templates in the view paths using by default the mailer name and the
If you do not pass a block to the +mail+ method, it will find all

from' value.
to the +:sender+ in preference to the +:from+ field for the 'envelope
one in +:from+. Mail will actually use the +:return_path+ in preference
when you want delivery notifications sent to a different address than the
the 'envelope from' address for the Mail message. Setting this is useful
When a +:return_path+ is specified as header, that value will be used as

method.
as part of the headers hash or use the headers['name'] = value
If you need other headers not listed above, you can either pass them in

end
reply_to: 'bounces@test.lindsaar.net'
bcc: 'email_logger@test.lindsaar.net',
default from: 'no-reply@test.lindsaar.net',
class Notifier < ActionMailer::Base

by using the ::default class method:
You can set default values for any of the above headers (except +:date+)

* +:date+ - The date to say the email was sent on.
* +:reply_to+ - Who to set the Reply-To header of the email to.
addresses, or an array of addresses.
* +:bcc+ - Who you would like to Blind-Carbon-Copy on this email, can be a string of
or an array of addresses.
* +:cc+ - Who you would like to Carbon-Copy on this email, can be a string of addresses,
* +:from+ - Who the message is from
of addresses.
* +:to+ - Who the message is destined for, can be a string of addresses, or an array
humanized version of the +action_name+
[mailer_scope, action_name] or if this is missing, will translate the
ask the Rails I18n class for a translated +:subject+ in the scope of
* +:subject+ - The subject of the message, if this is omitted, Action Mailer will

the most used headers in an email message, these are:
It accepts a headers hash. This hash allows you to specify

two ways to call this method, with a block, or without a block.
The main method that creates the message and renders the email templates. There are

def mail(headers = {}, &block)
  return @_message if @_mail_was_called && headers.blank? && !block
  m = @_message
  # At the beginning, do not consider class default for content_type
  content_type = headers[:content_type]
  # Call all the procs (if any)
  default_values = {}
  self.class.default.each do |k,v|
    default_values[k] = v.is_a?(Proc) ? instance_eval(&v) : v
  end
  # Handle defaults
  headers = headers.reverse_merge(default_values)
  headers[:subject] ||= default_i18n_subject
  # Apply charset at the beginning so all fields are properly quoted
  m.charset = charset = headers[:charset]
  # Set configure delivery behavior
  wrap_delivery_behavior!(headers.delete(:delivery_method), headers.delete(:delivery_method_options))
  # Assign all headers except parts_order, content_type and body
  assignable = headers.except(:parts_order, :content_type, :body, :template_name, :template_path)
  assignable.each { |k, v| m[k] = v }
  # Render the templates and blocks
  responses = collect_responses(headers, &block)
  @_mail_was_called = true
  create_parts_from_responses(m, responses)
  # Setup content type, reapply charset and handle parts order
  m.content_type = set_content_type(m, content_type, headers[:content_type])
  m.charset      = charset
  if m.multipart?
    m.body.set_sort_order(headers[:parts_order])
    m.body.sort_parts!
  end
  m
end

def mailer_name

If this is an anonymous mailer, this method will return +anonymous+ instead.
Returns the name of current mailer. This method is also being used as a path for a view lookup.

def mailer_name
  @mailer_name ||= anonymous? ? "anonymous" : name.underscore
end

def mailer_name

Returns the name of the mailer object.

def mailer_name
  self.class.mailer_name
end

def method_missing(method_name, *args) # :nodoc:

:nodoc:

def method_missing(method_name, *args) # :nodoc:
  if action_methods.include?(method_name.to_s)
    MessageDelivery.new(self, method_name, *args)
  else
    super
  end
end

def process(method_name, *args) #:nodoc:

:nodoc:

def process(method_name, *args) #:nodoc:
  payload = {
    mailer: self.class.name,
    action: method_name
  }
  ActiveSupport::Notifications.instrument("process.action_mailer", payload) do
    lookup_context.skip_default_locale!
    super
    @_message = NullMail.new unless @_mail_was_called
  end
end

def receive(raw_mail)

end
end
# ...
def receive(mail)
class MyMailer < ActionMailer::Base

as a parameter:
need to implement a +receive+ method that accepts the raw email string
If you want your mailer to be able to process incoming messages, you'll

object's +receive+ method.
instantiates a new mailer, and passes the email object to the mailer
Receives a raw email, parses it into an email object, decodes it,

def receive(raw_mail)
  ActiveSupport::Notifications.instrument("receive.action_mailer") do |payload|
    mail = Mail.new(raw_mail)
    set_payload_for_mail(payload, mail)
    new.receive(mail)
  end
end

def register_interceptor(interceptor)

If a string or symbol is passed in it will be camelized and constantized.
Either a class, string or symbol can be passed in as the Interceptor.
Register an Interceptor which will be called before mail is sent.

def register_interceptor(interceptor)
  delivery_interceptor = case interceptor
    when String, Symbol
      interceptor.to_s.camelize.constantize
    else
      interceptor
    end
  Mail.register_interceptor(delivery_interceptor)
end

def register_interceptors(*interceptors)

def register_interceptors(*interceptors)
  interceptors.flatten.compact.each { |interceptor| register_interceptor(interceptor) }
end

def register_observer(observer)

If a string or symbol is passed in it will be camelized and constantized.
Either a class, string or symbol can be passed in as the Observer.
Register an Observer which will be notified when mail is delivered.

def register_observer(observer)
  delivery_observer = case observer
    when String, Symbol
      observer.to_s.camelize.constantize
    else
      observer
    end
  Mail.register_observer(delivery_observer)
end

def register_observers(*observers)

def register_observers(*observers)
  observers.flatten.compact.each { |observer| register_observer(observer) }
end

def respond_to?(method, include_private = false) #:nodoc:

:nodoc:

def respond_to?(method, include_private = false) #:nodoc:
  super || action_methods.include?(method.to_s)
end

def set_content_type(m, user_content_type, class_default)

used.
attachments, or the message is multipart, then the default content type is
If there is no content type passed in via headers, and there are no

type will be "multipart/related", otherwise "multipart/mixed".
message has any attachments. If the attachments are inline, the content
It will use the given +user_content_type+, or multipart if the mail

Used by #mail to set the content type of the message.

def set_content_type(m, user_content_type, class_default)
  params = m.content_type_parameters || {}
  case
  when user_content_type.present?
    user_content_type
  when m.has_attachments?
    if m.attachments.detect { |a| a.inline? }
      ["multipart", "related", params]
    else
      ["multipart", "mixed", params]
    end
  when m.multipart?
    ["multipart", "alternative", params]
  else
    m.content_type || class_default
  end
end

def set_payload_for_mail(payload, mail) #:nodoc:

:nodoc:

def set_payload_for_mail(payload, mail) #:nodoc:
  payload[:mailer]     = name
  payload[:message_id] = mail.message_id
  payload[:subject]    = mail.subject
  payload[:to]         = mail.to
  payload[:from]       = mail.from
  payload[:bcc]        = mail.bcc if mail.bcc.present?
  payload[:cc]         = mail.cc  if mail.cc.present?
  payload[:date]       = mail.date
  payload[:mail]       = mail.encoded
end

Modules

Classes

class ActionMailer::Base

def self.supports_path?

def _protected_ivars # :nodoc:

def attachments

def collect_responses(headers) #:nodoc:

def create_parts_from_responses(m, responses) #:nodoc:

def default(value = nil)

def default_i18n_subject(interpolations = {})

def deliver_mail(mail) #:nodoc:

def each_template(paths, name, &block) #:nodoc:

def headers(args = nil)

def initialize(method_name=nil, *args)

def insert_part(container, response, charset) #:nodoc:

def mail(headers = {}, &block)

Hello Mikel!

def mailer_name

def mailer_name

def method_missing(method_name, *args) # :nodoc:

def process(method_name, *args) #:nodoc:

def receive(raw_mail)

def register_interceptor(interceptor)

def register_interceptors(*interceptors)

def register_observer(observer)

def register_observers(*observers)

def respond_to?(method, include_private = false) #:nodoc:

def set_content_type(m, user_content_type, class_default)

def set_payload_for_mail(payload, mail) #:nodoc:

Namespace

Classes in this namespace

Parent class

Included Modules

Class Methods

Instance Methods

Defined in