Question Locked

Exchange 2003 internal and external mail issues

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Dear all,

I have some serious issues with our email. I would be very happy to have a bit of help because I don't really know where to start. This is the configuration:

MS Win 2000 Server SP4 and update roll up 1, with Exchange 2003 SP2 version 6.5.7650.28, one server in backend, one in frontend configured.

Installed software: Symantec Information Foundation Mail security 6.0 with premium anti spam.

Maybe this is also important info: My inbound and outbound WAN IP address are different. Although both addresses are fully reversible to their host names, some mail servers complain about this configuration. Some examples of NDR's:

here was a SMTP communication problem with the recipient's email server. Please contact your system administrator.

Action: failed
Status: 5.5.0
X-Supplementary-Info:
X-Display-Name: name@emailaddress.com

name@hotmail.com on 22/08/2007 2:30
There was a SMTP communication problem with the recipient's email server. Please contact your system administrator.

You do not have permission to send to this recipient. For assistance, contact your system administrator.
... Relaying denied. IP name possibly forged [123.123.123.123]>

This is an automatically generated Delivery Status Notification

Delivery to the following recipient failed permanently: name@emailaddress.com
Technical details of permanent failure:
PERM_FAILURE: SMTP Error (state 13): 554 : Relay access denied

For some non-delivered email no NDR is received at all. Does this mean that the anti spam of the recipient's SMTP server deleted the message? Would it be a good idea for solving the external mail issues to have both inbound and outbound server on the same IP address?

The last week I had also internal mail problems. One user could send an email with attachment to one particular user, the other recipients within our company have no problems receiving her mail. The particular recipient receives the mail, but without the attachment. No user-specific exchange options were changed, all settings are default... Another user reported that she did not receive internal messages at all.

Symantec's software has configuration which excludes email, spam and content filtering for internal mail.

I know it's a lot but I would be very happy if already a tiny bit of my issues would be resolved.

Kind regards,

G?nther a

3 replies

by tg2

First resolve the helo issue.

get a hotmail or other free email account, test sending to yourself.

If you get the message, look at the email headers and try to identify your mail servers in them.

Sample header with bad helo:

Received: from source ([64.124.114.100]) (using SSLv3) by exprod8mx66.postini.com ([64.18.7.10]) with SMTP;
Mon, 24 Sep 2007 06:58:56 EDT

the ip address in block and parenthesis after the word "source" shows that the receiving server did not see a reverse for the ip. the word "source" is potentially the name the server called itself.

you want to make sure your server says "helo" with the correct forward name, and that the forward name reverses properly.

Does the internal server have a smarthost setup as the external server? And does the external server then allow relay coming from the internal server?

If the external server is the smarthost for your internal server, make sure IT has a proper helo and forward / reverse match.

Your "outgoing" and "incoming" ip's do not have to match, and your domain can have MX entries that don't mention anything about these two machines, say if you were using Postini to pre-filter spam and virus mail etc..

Also, do you have an SPF record set up for your domain? None of the methods out have 100% acceptance, but it doesn't cause denial if you do have it.. and if the receiving mail server does pay attention to the SPF then you could short circuit some of the "is the connecting server really for XYZ domain" logic.

Once you have your outbound paths correct, see what issues are left, as the authentication issues may be from servers not seeing each other, or you may not need the external server to authenticate your internal just knowing that its allowed to relay for your internal server may be enough.. etc..

So start with the outbound ... fix that.. and then continue to the next problem...

by gunther.imbrechts

Hey TG2,

Thanks a lot for your info. You really got me on track. First of all, this BAD HELO message was a one-time error only, didn't have it since then.
There is no SPF record set up for our domain. Since our DNS servers are hosted by our ISP, I asked them to add this SPF record. (they were aware of our relaying issues, but never proposed this...)
About smarthost setup: there is a lot which is not properly configured on our Exchange FE and BE configuration so I will need to revise this configuration before I can outnumber the other causes of the problems.

Kind regards,

G?nther

This discussion is closed to new replies.