mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
46f30f902f
commit0fc3381aa5
Author: Xavier Noria <fxn@hashref.com> Date: Fri May 16 23:44:51 2008 +0200 Conventions. Formatting. Revising docs all over the rails. This revision encourages the modern resource-oriented form_for usage. In addition corrects some markup and other details. commit70e4bcf5cb
Author: Chris Kampmeier <chris@kampers.net> Date: Fri May 16 12:09:46 2008 -0700 Fix a couple spelling errors in docs commit6ea5e4208f
Author: Chris O'Sullivan <thechrisoshow@gmail.com> Date: Fri May 16 16:09:11 2008 +0100 Added docs about source_type for has_one association commita01a0178be
Author: miloops <miloops@gmail.com> Date: Wed May 14 09:22:39 2008 +0000 Change migration generator USAGE to explain the timestamped migrations behaviour commit4e2bc02163
Author: Xavier Noria <fxn@hashref.com> Date: Fri May 16 00:43:03 2008 +0200 minor revision in url_for docs Made explicit that RESTful and controller/action styles are not interchangeable, and revised some markup. commitd6ecce66f4
Author: Michael Hartl <michael@michaelhartl.com> Date: Thu May 15 10:46:40 2008 -0700 Expanded and updated the link_to documentation commitb8c46c86f0
Author: Cody Fauser <cody@jadedpixel.com> Date: Wed May 14 09:10:02 2008 -0400 Improve and cleanup ActionMailer documentation commit9546ee2999
Author: Yehuda Katz <wycats@gmail.com> Date: Mon May 12 23:41:43 2008 -0700 Add documentation for Inflector.inflections commitcbd5db8f51
Author: Manik Juneja <mjuneja@manik-junejas-computer.local> Date: Mon May 12 23:43:31 2008 +0530 minor changes in railties/README. Added dbconsole introduction commit130a280dde
Author: Gaurav Sharma <gaurav@norbauer.com> Date: Mon May 12 18:00:19 2008 +0530 adding documentation for cached_attributes commit164c958648
Author: TomK32 <tomk32@tomk32.de> Date: Mon May 12 10:59:33 2008 +0200 proper heading for "Example:" commit35634feb47
Author: Matt Boehlig <thetamind@gmail.com> Date: Sun May 11 16:46:07 2008 -0500 Cleanup whitespace and change_table documentation commit80bba28a1a
Author: Xavier Noria <fxn@hashref.com> Date: Sun May 11 02:54:02 2008 +0200 documented the source annotation extractor commite6823bb165
Author: Mike Mondragon <mikemondragon@gmail.com> Date: Fri May 9 13:49:56 2008 -0700 Added additional information about processing email with ActionMailer and the strategy one might want to employ to do so. commite6afd8b273
Author: Xavier Noria <fxn@hashref.com> Date: Thu May 8 23:49:36 2008 +0200 corrected and completed docs of increment/decrement/toggle in AR::Base commit2fead68b31
Author: Austin Putman <austin@emmanuel.local> Date: Wed May 7 19:35:46 2008 -0700 Documented class methods on ActionController::Routing. These are dangerous, and mostly used for testing. commitf5b84182db
Author: Teflon Ted <github@rudiment.net> Date: Wed May 7 16:08:49 2008 -0400 Added explanation about errant inflections not being patched in the future in order to avoid breaking legacy applications. commit370f4f5172
Author: Sunny Ripert <negatif@gmail.com> Date: Wed May 7 14:00:59 2008 +0200 Applied list conventions in AR::Base commit5bd18429f0
Author: Sunny Ripert <negatif@gmail.com> Date: Wed May 7 13:53:35 2008 +0200 Renamed Options list to Attributes list whenever they weren't option hashes in AR::Base commit2fa628e34b
Author: Xavier Noria <fxn@hashref.com> Date: Wed May 7 11:52:33 2008 +0200 revised details in Exceptions section of AR::Base docs commitd912bd5672
Author: Yaroslav Markin <yaroslav@markin.net> Date: Wed May 7 13:50:28 2008 +0400 Add a filter_parameter_logging usage hint to generated ApplicationController. This may help to remind the developer to filter sensitive information from application logs. Closes #11578 commitf81d771f06
Author: Jack Danger Canty <git@6brand.com> Date: Tue May 6 23:35:05 2008 -0700 doc: ActiveRecord::Reflection::AssociationReflection#through_reflection Added documentation demonstrating the use of #through_reflection for finding intervening reflection objects for HasManyThrough and HasOneThrough. commitae6b46f00b
Author: Cheah Chu Yeow <chuyeow@gmail.com> Date: Wed May 7 13:47:41 2008 +0800 Document AttributeAssignmentError and MultiparameterAssignmentErrors. commit8f463550b5
Author: John Barnette <jbarnette@gmail.com> Date: Tue May 6 22:46:44 2008 -0700 Killing/fixing a bunch of outdated language in the AR README. commit284a930a93
Author: Jonathan Dance <jd@wuputah.com> Date: Tue May 6 14:58:26 2008 -0400 improvements to the page caching docs commit9482da6213
Author: Sunny Ripert <negatif@gmail.com> Date: Mon May 5 18:13:40 2008 +0200 validates_numericality_of() "integer" option really is "only_integer" commite9afd6790a
Author: Sunny Ripert <negatif@gmail.com> Date: Mon May 5 12:11:59 2008 +0200 Harmonized hash notation in AR::Base commit67ebf14a91
Author: Sunny Ripert <negatif@gmail.com> Date: Mon May 5 12:06:19 2008 +0200 Turned options into rdoc-lists in AR::Base commit0ec7c0a41d
Author: Marshall Huss <mwhuss@Macbook.local> Date: Sun May 4 23:21:33 2008 -0400 Added information of how to set element_name in the case the user has a name confliction with an existing model Signed-off-by: Pratik Naik <pratiknaik@gmail.com>
149 lines
4.8 KiB
Text
Executable file
149 lines
4.8 KiB
Text
Executable file
= Action Mailer -- Easy email delivery and testing
|
|
|
|
Action Mailer is a framework for designing email-service layers. These layers
|
|
are used to consolidate code for sending out forgotten passwords, welcome
|
|
wishes on signup, invoices for billing, and any other use case that requires
|
|
a written notification to either a person or another system.
|
|
|
|
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
|
|
|
|
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)
|
|
recipients recipient
|
|
subject "[Signed up] Welcome #{recipient}"
|
|
from "system@loudthinking.com"
|
|
body :recipient => recipient
|
|
end
|
|
|
|
The body of the email is created by using an Action View template (regular
|
|
ERb) that has the content of the body hash parameter available as instance variables.
|
|
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!
|
|
|
|
== 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(
|
|
:subject => email.subject, :body => email.body
|
|
)
|
|
|
|
if email.has_attachments?
|
|
for attachment in email.attachments
|
|
page.attachments.create({
|
|
:file => attachment, :description => email.subject
|
|
})
|
|
end
|
|
end
|
|
end
|
|
end
|
|
|
|
This Mailman can be the target for Postfix or other MTAs. In Rails, you would use the runner in the
|
|
trivial case like this:
|
|
|
|
./script/runner 'Mailman.receive(STDIN.read)'
|
|
|
|
However, invoking Rails in the runner for each mail to be received is very resource intensive. A single
|
|
instance of Rails should be run within a daemon if it is going to be utilized to process more than just
|
|
a limited number of email.
|
|
|
|
== Configuration
|
|
|
|
The Base class has the full list of configuration options. Here's an example:
|
|
|
|
ActionMailer::Base.smtp_settings = {
|
|
:address => 'smtp.yourserver.com', # default: localhost
|
|
:port => '25', # default: 25
|
|
:user_name => 'user',
|
|
:password => 'pass',
|
|
:authentication => :plain # :plain, :login or :cram_md5
|
|
}
|
|
|
|
== 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
|
|
|
|
The Action Mailer homepage is http://www.rubyonrails.org. You can find
|
|
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
|
|
new feature to be submitted in the form of new unit tests.
|