HRLAdmin
asked on
When user mailbox is on member server, user can send emails but cannot receive emails.
When user mailbox is on member server, user can send emails but cannot receive emails. Account works with no issues when mailbox on master server mailstore. NDR reciept listed master exchange server with action delayed, then failed because of to many hops.
1. Reporting-MTA: dns;MASTER.hrl.net.au
Final-Recipient: rfc822;xxxnorm@xxx.com.au
Action: delayed
Status: 4.4.7
Will-Retry-Until: Sat, 29 Sep 2007 20:47:39 +1000
X-Display-Name: Norm, XXX
2. Reporting-MTA: dns;MASTER.xxx.net.au
Received-From-MTA: dns;mailmarshal.xxx.net.au
Arrival-Date: Thu, 27 Sep 2007 22:48:20 +1000
Final-Recipient: rfc822;xxxnorm@xxx.com.au
Action: failed
Status: 5.5.0
Diagnostic-Code: smtp;554 Too many hops 27 (25 max)
X-Display-Name: Norm, XXX
1. Reporting-MTA: dns;MASTER.hrl.net.au
Final-Recipient: rfc822;xxxnorm@xxx.com.au
Action: delayed
Status: 4.4.7
Will-Retry-Until: Sat, 29 Sep 2007 20:47:39 +1000
X-Display-Name: Norm, XXX
2. Reporting-MTA: dns;MASTER.xxx.net.au
Received-From-MTA: dns;mailmarshal.xxx.net.au
Arrival-Date: Thu, 27 Sep 2007 22:48:20 +1000
Final-Recipient: rfc822;xxxnorm@xxx.com.au
Action: failed
Status: 5.5.0
Diagnostic-Code: smtp;554 Too many hops 27 (25 max)
X-Display-Name: Norm, XXX
I would wager that it is the second option of Bob's config above, and that you have a smart host listed on the default SMTP server.
View this recent question for a similar scenario;
http:/Q_22855291.html
-red
View this recent question for a similar scenario;
http:/Q_22855291.html
-red
ASKER
Bob, you are correct the setup is Internet --> Mail Marshall ---> Master Server ---> Member Server
Will download ExBPA and advise of report. Have added member server to SMTP connector as suggested by redseatechnologies as this was not configured correctly, but this still has not resolved the recieve issue, Mailmarshal has also been setup with member server as alternative delivery but this will not make any effect unless master is not available, but needed to be done for later migration.
Will download ExBPA and advise of report. Have added member server to SMTP connector as suggested by redseatechnologies as this was not configured correctly, but this still has not resolved the recieve issue, Mailmarshal has also been setup with member server as alternative delivery but this will not make any effect unless master is not available, but needed to be done for later migration.
So do you have a Smarthost listed on the SMTP server? (not the connector?)
Is the "master" server and the member server in the same routing group?
My assumption is that you are using a single SMTP namespace, correct? If so then the "master" server should deliver to the member server.
See if Mail Marshall is trying to deliver to the member server for whatever reason (ldap lookup).
If you know how to send a test message using telnet server 25 or telnet server smtp see what you get back as a response and see if you can submit a message.
My assumption is that you are using a single SMTP namespace, correct? If so then the "master" server should deliver to the member server.
See if Mail Marshall is trying to deliver to the member server for whatever reason (ldap lookup).
If you know how to send a test message using telnet server 25 or telnet server smtp see what you get back as a response and see if you can submit a message.
ASKER
Yes the Master and Member servers are both in the same routing group. (first routing group). Mail Marshal delivers to the Master server not member server and the master handles the routing of emails, so no issue with mailmarshal. Have performed telnet to both master and member, when telnet to member server, user can send and recieve if mailbox located on member server. If telnet to master server, user can send but not recieve if mailbox is located on member server. Have performed EHLO from telnet and all SMTP functions are correct. Will be recreating connectors and or routing group in case these are in some way corrupt.
What did the ExBPA report happen to say? Can you also run the other too, the Exchange Troubleshooting Asssistant? It's at the same link.
Have you or your team possibly tried to secure the Default Virtual SMTP server and prevented the master server from sending to the member server?
Are there any event log errors on the bridgehead/master server? Can you turn up SMTP transport logging?
If the servers are in the same routing group then they should not need a connector (SMTP or RGC) to talk to each other. They should talk to each other via SMTP automatically.
Have you or your team possibly tried to secure the Default Virtual SMTP server and prevented the master server from sending to the member server?
Are there any event log errors on the bridgehead/master server? Can you turn up SMTP transport logging?
If the servers are in the same routing group then they should not need a connector (SMTP or RGC) to talk to each other. They should talk to each other via SMTP automatically.
ASKER
Found the issue finally to be related to the combination of two areas.
1. Protocols - SMTP - default SMTP Virtual Server properties - Delivery Tab - Advanced - had the IP address of the smart host.
2. Routing Groups - First Routing Group - Connectors - (did not have an "Internet Mail Connector" with an SMTP address space *
This wasn't a problem until we added another server as the server did not know how to route between servers for an unknown address. Originally the SMTP Virtual Server did this.
Since resolving this, have removed the first built exchange server after following information found under KB 822931 - http://support.microsoft.com/kb/822931
System is now operational.
1. Protocols - SMTP - default SMTP Virtual Server properties - Delivery Tab - Advanced - had the IP address of the smart host.
2. Routing Groups - First Routing Group - Connectors - (did not have an "Internet Mail Connector" with an SMTP address space *
This wasn't a problem until we added another server as the server did not know how to route between servers for an unknown address. Originally the SMTP Virtual Server did this.
Since resolving this, have removed the first built exchange server after following information found under KB 822931 - http://support.microsoft.com/kb/822931
System is now operational.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Can you give some more information regarding your routing topology? I am assuming that your primary MX record for inbound mail is the Mail Marshall server, correct?
Is it
-----> Master Server
Internet --> Mail Marshall
------> Member server
or
Internet --> Mail Marshall ---> Master Server ---> Member Server
Are there any significant events in the Application or System Event Logs on either Exchange server.
Would you mind running Exchange Best Practices Analyzer (ExBPA) and seeing if it reports any major errors?
http://technet.microsoft.com/en-us/exchange/bb288481.aspx