Hi Gerry, the problem is if you want to run a "public" smtpserver you need to use port 25 for smtp. Usually ISPs only block outgoing port 25, so if this is the case you need to specify the ISPS Mail gateway in RemoteDelivery.
Bye, Norman Ps: And yes changing smtp port has nothing todo with pop3 2010/6/1 Gerry Matte <gerry.ma...@shaw.ca>: > Hello. > A short while ago, I installed James 2.3.2 on a Windows 2003 Server. > The server is physically located two provinces away from my home and is not > part of my ISP's subnet. > > Configuration was minimal - I deliberately chose to make the least possible > change to the default config.xml file in order to ensure everything was > working satisfactorily. > The james server is supporting multiple domains but very few users. > > While testing the mail server from my shaw ISP in Victoria, I discovered that > I was not able to send emails with my Windows Live email client - the error > was 10061 which I quickly learned meant that my ISP was blocking connections > to port 25 on any mail server other than the shaw mail servers. Their > recommendation was to use an SMTP port other than 25 for sending email. > > So, I modified my config.xml (line 858 in the default file) to specify port > 587 instead of 25. I opened port 587 on my server's router and verified > that Windows Firewall was not running. I then restarted the mail service and > all seemed to be well (connections were made without error). > However I soon discovered that emails sent to my james server were being > delayed indefinitely - the error code in the "Message delayed" bounce back > email from mailer-dae...@shaw.ca is: > Delivery to the following recipients has been delayed. > <info at gerrymatte.com> > The reason for the problem: > 4.4.0 - Other network problem '[Errno 61] Connection refused' > > When I changed the SMTP port back to port 25, my test emails were delivered > within a short time period. > > I then re-tested by changing the SMTP port to 2525 (in case someone was > blocking 587), opened that port on the router, and bounced the james server. > The same results - POP3 incoming email was no longer accepted and the error > was again Error 61 Connection refused. Restoring the SMTP port to port 25 > causes emails to again be delivered. > > I have configured james to require SMTP Authorisation (with > authRequired=announce and also with true) neither setting seems to have an > effect on the "Connection Refused" error. > > I am now wondering if I have to take action to specifically authorise my shaw > email server using either "authorizedAddresses" or "RemoteAddrNotInNetwork > matcher in the transport processor". However, using either of these would > only enable incoming emails from the shaw network .... which is only a small > portion of my email traffic. > > In simple terms, I should be able to reconfigure my SMTP port with no effect > on my POP3 server (IMHO). > > Can anyone suggest an approach to resolving this ? > > Gerry Matte > 250-383-2466 http://www.gerrymatte.ca > mailto: gerry.matte at shaw.ca --------------------------------------------------------------------- To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org
