README 4.4 KB
Newer Older
D
Initial  
David Heinemeier Hansson 已提交
1 2
= Action Mailer -- Easy email delivery and testing

D
David Heinemeier Hansson 已提交
3
Action Mailer is a framework for designing email-service layers. These layers
4
are used to consolidate code for sending out forgotten passwords, welcome
D
Initial  
David Heinemeier Hansson 已提交
5 6 7
wishes on signup, invoices for billing, and any other use case that requires
a written notification to either a person or another system.

8 9 10 11 12 13
Additionally, an Action Mailer class can be used to process incoming email,
such as allowing a weblog to accept new posts from an email (which could even
have been sent from a phone).

== Sending emails

D
Initial  
David Heinemeier Hansson 已提交
14 15 16 17 18
The framework works by setting up all the email details, except the body,
in methods on the service layer. Subject, recipients, sender, and timestamp
are all set up this way. An example of such a method:

  def signed_up(recipient)
19 20 21
    recipients recipient
    subject    "[Signed up] Welcome #{recipient}"
    from       "system@loudthinking.com"
D
Initial  
David Heinemeier Hansson 已提交
22

23
    body(:recipient => recipient)
D
Initial  
David Heinemeier Hansson 已提交
24 25 26
  end

The body of the email is created by using an Action View template (regular
27
ERb) that has the content of the body hash parameter available as instance variables. 
D
Initial  
David Heinemeier Hansson 已提交
28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54
So the corresponding body template for the method above could look like this:

  Hello there, 

  Mr. <%= @recipient %>
  
And if the recipient was given as "david@loudthinking.com", the email 
generated would look like this:

  Date: Sun, 12 Dec 2004 00:00:00 +0100
  From: system@loudthinking.com
  To: david@loudthinking.com
  Subject: [Signed up] Welcome david@loudthinking.com

  Hello there, 

  Mr. david@loudthinking.com

You never actually call the instance methods like signed_up directly. Instead,
you call class methods like deliver_* and create_* that are automatically
created for each instance method. So if the signed_up method sat on
ApplicationMailer, it would look like this:

  ApplicationMailer.create_signed_up("david@loudthinking.com")  # => tmail object for testing
  ApplicationMailer.deliver_signed_up("david@loudthinking.com") # sends the email
  ApplicationMailer.new.signed_up("david@loudthinking.com")     # won't work!

55 56 57 58 59 60 61 62 63 64 65 66 67
== Receiving emails

To receive emails, you need to implement a public instance method called receive that takes a
tmail object as its single parameter. The Action Mailer framework has a corresponding class method, 
which is also called receive, that accepts a raw, unprocessed email as a string, which it then turns
into the tmail object and calls the receive instance method.

Example:

  class Mailman < ActionMailer::Base
    def receive(email)
      page = Page.find_by_address(email.to.first)
      page.emails.create(
68
        :subject => email.subject, :body => email.body
69 70 71 72 73
      )

      if email.has_attachments?
        for attachment in email.attachments
          page.attachments.create({ 
74
            :file => attachment, :description => email.subject
75 76 77 78 79 80 81 82 83 84
          })
        end
      end
    end
  end

This Mailman can be the target for Postfix. In Rails, you would use the runner like this:

  ./script/runner 'Mailman.receive(STDIN.read)'

85 86 87 88
== Configuration

The Base class has the full list of configuration options. Here's an example:

89
ActionMailer::Base.smtp_settings = {
90 91 92 93 94 95
  :address=>'smtp.yourserver.com',    # default: localhost
  :port=>'25',                        # default: 25
  :user_name=>'user',
  :password=>'pass',
  :authentication=>:plain             # :plain, :login or :cram_md5
}
D
Initial  
David Heinemeier Hansson 已提交
96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138

== Dependencies

Action Mailer requires that the Action Pack is either available to be required immediately
or is accessible as a GEM.


== Bundled software

* tmail 0.10.8 by Minero Aoki released under LGPL
  Read more on http://i.loveruby.net/en/prog/tmail.html

* Text::Format 0.63 by Austin Ziegler released under OpenSource
  Read more on http://www.halostatue.ca/ruby/Text__Format.html


== Download

The latest version of Action Mailer can be found at

* http://rubyforge.org/project/showfiles.php?group_id=361

Documentation can be found at 

* http://actionmailer.rubyonrails.org


== Installation

You can install Action Mailer with the following command.

  % [sudo] ruby install.rb

from its distribution directory.


== License

Action Mailer is released under the MIT license.


== Support

139
The Action Mailer homepage is http://www.rubyonrails.org. You can find
D
Initial  
David Heinemeier Hansson 已提交
140 141 142 143 144
the Action Mailer RubyForge page at http://rubyforge.org/projects/actionmailer.
And as Jim from Rake says:

   Feel free to submit commits or feature requests.  If you send a patch,
   remember to update the corresponding unit tests.  If fact, I prefer
145
   new feature to be submitted in the form of new unit tests.