Action_mailer in windows -can't get to work

Rails
1

Newbie problem - I am on windows and can’t get action mailer to send
an email. There are no error messages, the command line says "Sent
mail to " and then lists the contents. I have done lots of seacrhing
on the web but I am missing something. Does Rails talk directly to
mail.aapt.net.au (in my case) or is there a mail client or something
that should be on windows? There is no activity on my modem when I try
to send the email. Tom.

2

thomasalbert wrote:

Newbie problem - I am on windows and can’t get action mailer to send
an email. There are no error messages, the command line says "Sent
mail to " and then lists the contents. I have done lots of seacrhing
on the web but I am missing something. Does Rails talk directly to
mail.aapt.net.au (in my case) or is there a mail client or something
that should be on windows? There is no activity on my modem when I try
to send the email. Tom.

Im having the same problem.
I have installed action_mailer_tls plugin but still the same.
Hard to solve for me because I have no idea what exactly is going on.
Any help very welcome.

Im using Rails 2.1.2, this is in my environment.rb:

ActionMailer::Base.delivery_method = :smtp
ActionMailer::Base.smtp_settings = {
:address => “smtp.gmail.com”,
:port => 587,
:domain => “gmail.com”,
:user_name => “blablabla”,
:password => “hackme”,
:authentication => :plain
}

3

David Kleman wrote:

I have installed action_mailer_tls plugin but still the same.
:user_name => “blablabla”,
:password => “hackme”,
:authentication => :plain
}

It’s difficult to debug this sort of problem (it would be nice if
there were a mechanism to trap and view errors returned by mail
servers talking to ActionMailer in a rails app).

A couple of things to look at:

Try using the full email address for the user_name:

:user_name => '[email protected]"

Also, look carefully at your development.log file for error messages
returned by the outgoing mail server in the interaction between the
mail server and your program. You can also try to run in production
mode (uncomment the line ENV[‘RAILS_ENV’] ||= ‘production’ in config/
environment.rb) - sometimes you can catch some error messages in
production mode that don’t appear when running in development mode.