I have an exchange server configuration for a company with its on internal none routeable IP and internal domain. Occasionally when users send emails out they get #554 Transaction Failed. Spam Message not queued. The exchange server has an internal IP address like 192.168.5.5 and the internal domain name for the company is company.int. If I look at the message header of a rejected message it has the internal information like Received: from exchange.company.int (192.168.5.5) by exchange.company.int (192.168.5.5). The exchange server is behind a nated firewall so when it sends messages it sends from an internet IP address. The internet domain name is company.com and has an MX record that points to a service that receives the email for the company. Could I be getting these spam rejects because it is seeing the company.int domain name instead of company.com or the 192.168 IP address? If so how do I configure exchange so it is sending that information instead of internal info

Do you have SPF records set up?

On Thu, 22 Apr 2010 00:19:12 +0000, earl23 wrote:>I have an exchange server configuration for a company with its on internal none routeable IP and internal domain. Occasionally when users send emails out they get #554 Transaction Failed. Spam Message not queued. The exchange server has an internal IP address like 192.168.5.5 and the internal domain name for the company is company.int. If I look at the message header of a rejected message it has the internal information like Received: from exchange.company.int (192.168.5.5) by exchange.company.int (192.168.5.5). The exchange server is behind a nated firewall so when it sends messages it sends from an internet IP address. The internet domain name is company.com and has an MX record that points to a service that receives the email for the company. Could I be getting these spam rejects because it is seeing the company.int domain name instead of company.com or the 192.168 IP address? If so how do I configure exchange so it is sending that information instead of internal infoThe rejection text says the other machine thinks your e-mail is spam.That usually a content-based detection. Since you have no control overhow the other system deals with spam (or what criteria they user indeciding what's spam and what's not) you'll have to contact the adminsof the other system and work it out with them. They may white listyour IP addreses, or they decide that they've made a bad choice toinclude one test or another --or they may use the Exchange IMF andjust have the SCL values wrong. It's up to you to find out from themwhat's going on.Anyone the trusts the "Received:" headers in a message that areinserted by any server not under their control is just asking fortrouble. If that's what the other site is using then they'reoverly-paranoid and probably dumping a lot of "good" email. Youshouldn't have to worry about IP addresses in Received headers ifthey're in the private IP ranges.Your server shoulf be putting a FQDN into the HELO\EHLO that'sresolvable in a public DNS. That name should resolve to the IP addressthat was used to deliver the e-mail to the target system (i.e. theexternal IP address of your firewall, if that's what's doing the NAT).---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP

Hi, I agree with Rich. You may contact the administrator for thoes domains to solve the problem. Regards, Xiu