After install of Traveler 851 on SMTP server, I setup a support person who is helping me test. He is using the Traveler settings document and is in the access group. He successfully downloaded and synched his Palm device. He is able to send internal and SMTP mail from his device. He can receive replies to his sent mail BUT new if I sent him a new mail from my gmail account it is rejected. I get the following error message: Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 550 550 #5.1.0 Address rejected username@maildomain.com (state 14). I don’t see any error messages on the SMTP server log, mail.box is empty, the intended recipient just doesn’t receive it. But the same address as a reply goes through just fine. Anyone with an idea of how to fix this?
Subject: RE: Traveler 8.5.1 on SMTP server
I would not suspect Traveler would have any effect on the server’s ability to process SMTP trafic. In general traveler communicates over TCP 8642 and HTTP 80 or 443 and does not interfere with other channels.
The only thing I can think of from a Traveler point of view, is if you are using Internet Site Documents, verify the settings for the Internet Site Document for SMTP.
Subject: SMTP Inbound Controls
Sounds like an settings issue with the SMTP Inbound Controls configuration of your Traveler Server, assuming that it-is the Server that Google is attempting to send to.
Subject: Problem bigger
I’m now finding all SMTP incoming mail is intermittent. Outside senders are receiving 550 Address rejected notices. FYI Ironport is outside the SMTP server and using LDAP to identify the recipients and route the mail. I’ve have them check their external DNS servers and they say all in synch - any ideas?
Could directory assistance result in this type of activity?
Thanks for your help…
Subject: Source of 550s
The source of the 550s needs to be determined. It-is not clear whether the Traveler or IronPort device is generating these:Review the Traveler Server’s Console/Log.nsf.
Review the IronPort device/service’s Logging.
If necessary, implement SMTPDebugIO=3 (carries performance-overhead) on the Traveler’s Server & then reproduce the problem (then review the output).