Email Problem: An error occurred while sending mail (No connection could be made because the target machine actively refused it. - connect(2))

Added by Jean-Pierre Fouche over 12 years ago

Hello,

I receive the following error: An error occurred while sending mail (No connection could be made because the target machine actively refused it. - connect(2))

My email.yml looks like this:

  1. Outgoing email settings

production:
delivery_method: :smtp
smtp_settings:
address: 10.19.16.3
port: 25
domain: banana.com
authentication: :none

development:
delivery_method: :smtp
smtp_settings:
address: 10.19.16.3
port: 25
domain: banana.com
authentication: :none

I cannot see anything in production.log

Replies (3)

RE: Email Problem: An error occurred while sending mail (No connection could be made because the target machine actively refused it. - connect(2)) - Added by Jean-Pierre Fouche over 12 years ago

btw, I am using Exchange server, and I am able to send emails using Outlook Express from the server. I am also able to send emails using telnet, and a C# Console application.
What's up with the Redmine app?

Answering my own question... Thanks for the help out there, people :) - Added by Jean-Pierre Fouche over 12 years ago

The problem was fixed by setting up the email.yml below, and then RESARTING the mongrel services.

1. Set up email.yml as follows:

  1. Outgoing email settings

production:
delivery_method: :smtp
smtp_settings:
address: 110.65.22.22
port: 25
domain: banana.com
authentication: :none

development:
delivery_method: :smtp
smtp_settings:
address: 10.65.22.22
port: 25
domain: banana.com
authentication: :none

2. Redmine runs some ‘hidden’ services which need to be restarted (3 services in total – Redmine Apache, RedmineMongrel1 and RedmineMongrel2). Note that ALL of these need to be restarted, not just RedmineApache.

RE: Email Problem: An error occurred while sending mail (No connection could be made because the target machine actively refused it. - connect(2)) - Added by Nanda P over 12 years ago

I had the same issue. Restarting the server solved the problem.

  • Environment: Windows XP, Exchange server & MySQL

(1-3/3)