psandeen
asked on
Exchange 2003 Multiple Domains
Exchange 2003 Enterprise.
Some mail servers that perform extensive lookups (DNS, rDNS, mx, SPF, txt,) for our Exchange server will generate various
SMTP errors when accepting mail for delivery from our Exchange server when the recipients primary email address from our Exchange server is not our Exchange organizations default recieving domain.
(Our server recieves mail for 123.com and ABC.com, 123.com is the default policy email address domain, a user sho has ABC.com as the default email address may recieve email deliverability issues because of this..)
How should an Exchange 2003 server / organization be implemented or configured to alleviate this issue?
Is there a 3rd party solution or add on?
Thanks!
Some mail servers that perform extensive lookups (DNS, rDNS, mx, SPF, txt,) for our Exchange server will generate various
SMTP errors when accepting mail for delivery from our Exchange server when the recipients primary email address from our Exchange server is not our Exchange organizations default recieving domain.
(Our server recieves mail for 123.com and ABC.com, 123.com is the default policy email address domain, a user sho has ABC.com as the default email address may recieve email deliverability issues because of this..)
How should an Exchange 2003 server / organization be implemented or configured to alleviate this issue?
Is there a 3rd party solution or add on?
Thanks!
you mention the following in your post: (DNS, rDNS, mx, SPF, txt,)
the one from that list most likely to cause the issue you describe is an incorrect spf record for abc.com. if you only ever get issues when sending as abc.com then make sure the spf txt record for abc.com has your sending server ip address(es) listed. you can check by going to command prompt and typing
nslookup -q=txt abc.com
make sure the record has your domain. if no record exists then this is not the cause and I suspect there may be more to the problem.
also make sure the rdns matches the ehlo greeting of sending server.
shaun
the one from that list most likely to cause the issue you describe is an incorrect spf record for abc.com. if you only ever get issues when sending as abc.com then make sure the spf txt record for abc.com has your sending server ip address(es) listed. you can check by going to command prompt and typing
nslookup -q=txt abc.com
make sure the record has your domain. if no record exists then this is not the cause and I suspect there may be more to the problem.
also make sure the rdns matches the ehlo greeting of sending server.
shaun
ASKER
Exchange recieves for
123.com and abc.com
123.com is the default domain (policy)
mx for 123.com > mail.global.frontbridge.co m (Spam filter service)
mx for abc.com > mail.123.com
DNS for mail.123.com > xxx.xxx.xxx.242
rDNS for xxx.xxx.xxx.242 > mail.123.com
DNS for mail.ABC.com > xxx.xxx.xxx.242
rDNS for NONE > ABC.com
EHLO for Exchange > mail.123.com
SPF for 123.com > xxx.xxx.xxx.242
SPF for ABC.com > NONE
**Further, a mail server has returned the following
550 550 5.7.1 SPF unauthorized mail is prohibited. (state 15).
I see no SPF for ABC.com, I am thinking that is related to this error....?
123.com and abc.com
123.com is the default domain (policy)
mx for 123.com > mail.global.frontbridge.co
mx for abc.com > mail.123.com
DNS for mail.123.com > xxx.xxx.xxx.242
rDNS for xxx.xxx.xxx.242 > mail.123.com
DNS for mail.ABC.com > xxx.xxx.xxx.242
rDNS for NONE > ABC.com
EHLO for Exchange > mail.123.com
SPF for 123.com > xxx.xxx.xxx.242
SPF for ABC.com > NONE
**Further, a mail server has returned the following
550 550 5.7.1 SPF unauthorized mail is prohibited. (state 15).
I see no SPF for ABC.com, I am thinking that is related to this error....?
ASKER
i.e. would adding the mail server IP address of 123.com to a new SPF record for ABC.com work?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Default policy: add the extra domain names.
This will add the domain you are receiving emails for onto each user. If you do not want to have this domain on your users, unselect the box, or make a policy and attach it to only a selection.