James SMTP server while redirecting mail sends it to itself rather than to the 
destination
------------------------------------------------------------------------------------------

                 Key: JAMES-1018
                 URL: https://issues.apache.org/jira/browse/JAMES-1018
             Project: JAMES Server
          Issue Type: Bug
          Components: SMTPServer
    Affects Versions: 2.3.1
         Environment: Windows XP
            Reporter: Anastasia Tugaenko
            Priority: Minor


Under certain network and DNS configuration James SMTP server version 2.3.1 
sends mail to itself rather than to the next hop. As a result, the mail loops 
until resending limit is exceeded. It never gets to the destination.

 
Configuration 

The configuration file - http://www.ispras.ru/ru/james/config.xml. 

The issue was reproduced in a virtual network with three nodes and two domains 
(see http://www.ispras.ru/ru/james/virtualNet.png): 
1.      network vbox1.test with nodes XP11 and XP12, 
2.      network vbox2.test with nodes XP21 and XP22;
3.      nodes XP11 and XP21 are physically on the same virtual machine where 
James SMTP server runs. DNS runs on the same server.

DNS configuration used to reproduces the issue is available here - 
http://www.ispras.ru/ru/james/etc.zip. 

The issue occurs when MX record for XP21 has higher priority than that of XP22.
XP22               IN MX 15        XP21
XP22               IN MX 25        XP22 


Steps to reproduce the issue:

1. Turn on the virtual machines for nodes XP11/XP21, XP12, XP22. Launch DNS and 
James SMTP on the XP11/XP21 virtual machine. Launch mail agents on XP12 and 
XP22.
2. Send a mail from XP12 to XP22 (e.g. to [email protected]).
 

Issue:

Mail agent on XP12 sends the mail to the James SMTP server on XP11. The James 
SMTP server re-sends the mail to itself  (the MX record priority is higher than 
that of XP22). As a result the mail never arrives to XP22. 

James SMTP log is available here - 
http://www.ispras.ru/ru/james/smtpserver.log. 
Here is an extract from it:

09/06/10 16:54:51 INFO  smtpserver: Connection from XP12 (192.168.56.22)
09/06/10 16:54:52 INFO  smtpserver: Successfully spooled mail 
Mail1276088091716-0 from [email protected] on 192.168.56.22 for 
[[email protected]]
09/06/10 16:55:32 INFO  smtpserver: Connection from XP1 (192.168.209.21)
09/06/10 16:55:32 INFO  smtpserver: Successfully spooled mail 
Mail1276088132675-1 from [email protected] on 192.168.209.21 for 
[[email protected]]
09/06/10 16:56:12 INFO  smtpserver: Connection from XP1 (192.168.209.21)
09/06/10 16:56:12 INFO  smtpserver: Successfully spooled mail 
Mail1276088172782-2 from [email protected] on 192.168.209.21 for 
[[email protected]]
09/06/10 16:56:52 INFO  smtpserver: Connection from XP1 (192.168.209.21)
09/06/10 16:56:52 INFO  smtpserver: Successfully spooled mail 
Mail1276088212910-3 from [email protected] on 192.168.209.21 for 
[[email protected]]

The log shows that the mail gets constantly re-sent from XP11 to XP12 (the same 
physical machine) and never arrives to the destination. We tried other 
open-source SMTP servers in the same configuration - they do not loop and 
deliver the mail to the next hop.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to