Exchange Server Forums

RDNS causes some companies not to accept my mails

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2007] >> Message Routing >> RDNS causes some companies not to accept my mails

Page: [1]

Message

<< Older Topic Newer Topic >>

RDNS causes some companies not to accept my mails - 9.Feb.2009 10:40:38 AM

Zulan

Posts: 16
Joined: 13.Mar.2003
From: Sweden
Status: offline

Hello!

I have exchange 2007 SP1, when trying to mails to a few compaines they bounce beacuse of RDNS. I've setup RDNS and everything seems fine. But if I telnet to my server port 25 and typ ehlo I get

250-exchange.companyname.local

No wonders it doesnt work, it's supposed to say owa.companyname.com as I've stated in my Send connector. The receive connectors cannot be changed, I get an error message. Can this be fixed?

Post #: 1

Featured Links*

RE: RDNS causes some companies not to accept my mails - 9.Feb.2009 12:41:18 PM

John Weber

Posts: 1236
Joined: 20.Apr.2005
From: Portland, Oregon
Status: offline

did you restart the transport service?

_____________________________

John Weber [Lync MVP] http://tsoorad.blogspot.com

(in reply to Zulan)

Post #: 2

RE: RDNS causes some companies not to accept my mails - 9.Feb.2009 1:26:11 PM

tmacdaddy

Posts: 98
Joined: 3.May2007
From: Washington DC. Georgetown
Status: offline

Your ISP needs to put that in place for you. Trust me on this one. Just did this. I put my own in with our DNS registrar, no luck. The folks who own the block of IPs assigned to you need to do it.

(in reply to Zulan)

Post #: 3

RE: RDNS causes some companies not to accept my mails - 10.Feb.2009 9:35:58 AM

Zulan

Posts: 16
Joined: 13.Mar.2003
From: Sweden
Status: offline

Yes, I restarted the transport server.

You are right about the ISP. I have asked them to to that about a week ago and it's in place already.

I might have found the issue, after fooling around the with the receive cnnectors for a while I found that removing "exchange servers" in the permission groups of the receive connectors it actually allowed me to change the FQDN. Now I'm just waiting for confirmation that it actually works.

(in reply to tmacdaddy)

Post #: 4