[quote user="malsmith"]

I double checked the ip's and names didn't find any typos.

I agree with your theory that the delivery is failing because the mx resolved to the inaccessible outside address and that the system should not get to the point of trying to deliver out since the postmaster@mail.momjunction.com is configured as a local address. 

It is equally strange that a test email - sent from the server 'send message' menu to postmaster does get delivered local to the admin user.  it seems like it is only the notification/failure notices that have the bad behavior.

(Thanks again for your help on this problem).

[/quote]

Is mail mail.momjunction.com entered into Configuration | Mercury core "Internet name for this system"?

I've got the server working generally - it delivers mail with the server and outbound and receives mail inbound from internet.

However, notifications to the postmaster are setting off some kind of mail loop storm.  They queue up and when processing starts the SMTP-Client resolves MX for mail.momjunction.com to 72.32.156.36 which is the public ip of this mail server.  Then the connections fail and process is restarted / re-queued.

 
My network config is:

 
Server name: 101931-APP1 (W2K3 server)

local ip: 192.168.1.36 / 2nd local ip  10.241.70.142

Firewall 192.168.1.1

public IP 72.32.156.36

 ** Key point (maybe) 72.32.156.36 is not accessible from the local side machines only from the public internet - so connection requests to this ip are failing from the 101932-APP1 server.

DNS

mail.momjunction.com => 72.32.156.36

record type=mx for momjunction.com => 72.32.156.36
 

Mercury Server name : mail.momjunction.com

Mercury.ini

[Domains]

101932-APP1: mail.momjunction.com
101932-APP1: momjunction.com
101932-APP1: [72.32.156.36]
101932-APP1: 72.32.156.36
101932-APP1: [192.168.1.36]
101932-APP1: [10.241.70.142]
101932-APP1: momjunction
101932-APP1: mx.momjunction.com
[72.32.156.36]: [72.32.156.36]
 

Any help would be greatly appreciated.  I suspect that the system is not detecting that postmaster@momjunction.com or postmaster@mail.momjunction.com is a local address -- but try as I might the domains section seems to have no effect.

Malcolm Smith

1.   What local username have you entered for the postmaster?

2.    What have you entered for the  "Internet name for this system"?

The postmaster@<internet name for this system> goes to the local users you have specified as the postmaster.  This address must NOT be forwarded.

The internet name for the system is "momjunction.com" the name used to identify myself as "mail.momjunction.com" in the SMTP-Client setup.  Postmaster local name is "Admin" .  There are no forwards or alias for Admin.

Also if I send mail from external addreses into this server to postmaster@momjunction.com -- they are delivered to the local "Admin" user mailbox and don't bounce around.  Just the notifications / failure notices seem to do this bouncing.

If the MX resolved to an outside IP address and it is not accessible then this is probably what is causing the problem of delivery.  The question is why is it even resolving the IP address, this should be going local only since the domain is in the domains lists and is the name of the system as well.  Are you sure there is no typo here?

I double checked the ip's and names didn't find any typos.

I agree with your theory that the delivery is failing because the mx resolved to the inaccessible outside address and that the system should not get to the point of trying to deliver out since the postmaster@mail.momjunction.com is configured as a local address. 

It is equally strange that a test email - sent from the server 'send message' menu to postmaster does get delivered local to the admin user.  it seems like it is only the notification/failure notices that have the bad behavior.

(Thanks again for your help on this problem).