The SitePoint Forums have moved.

You can now find them here.
This forum is now closed to new posts, but you can browse existing content.
You can find out more information about the move and how to open a new account (if necessary) here.
If you get stuck you can get support by emailing forums@sitepoint.com

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

AFAIK, there is no email sending restriction for the development or testing environments.

I don't know, but I imagine it's similar to PHP's mail() function. That is, ActionMailer sends the mail request to the email server, and if it sends it to the email server OK it considers it a "success". Whether or not the email server successfully sends the email to the client, and whether or not the email client successfully receives the email, is another story.

Check the configuration of your email server and the "junk" folder of the account you're sending it to.

By default ActiveMailer always tries to send an email. You can override this setting by adding something like this to your configuration (for example in config/environment.rb or in one of the environment files; for development config/environments/development.rb):

Code Ruby:

config.action_mailer.perform_deliveries = false

Possible reason why email isn't sent, but your app thinks it was might be because your server isn't properly configured to send email and by default ActionMailer is configured not to care about delivery errors in development. You can change this setting in config/environments/development.rb on this line:

Code Ruby:

config.action_mailer.raise_delivery_errors = false

Either way, if you see that an email would be sent (in your log file) that means properly configured server would have sent it.