Hi There,

I am getting the following bounce back when emailing people from my Exchange 2013 server:

Remote Server returned 550 5.7.1 <rene.fleisch@bitschnau.com<mailto:rene.fleisch@bitschnau.com>>: Recipient address rejected: Mail appeared to be SPAM or forged. Ask your Mail/DNS-Administrator to correct HELO and DNS MX settings or to get removed from DNSBLs; MTA helo: ttlcloudexch04.ttlcloud.local, MTA hostname: remote.ttlhosting.co.uk[131.117.188.187] (helo/hostname mismatch)

This is a reverse DNS error because the MTA host name of my Exchange system should be mail.ttlhosting.co.uk not remote.ttlhosting.co.uk 

How can I change this? 

Thanks

Dave

Hi ,

1.Please check the pointer record for your domain is getting resolved to the exact name mentioned on the mx records for your domain .

Use mxtoolbox to check  .

2.Same time please ensure you have a properly mentioned FQDN value on the send connector in exchange as same as the name on the MX record .

Please reply me if you have any queries.

Regards

S.Nithyanandham

Hi Dave,

Agree with S.Nithyanandham, you should make sure that the FQDN on the send connector matching the MX record.

Here is a same thread for your reference:

HELO and DNS MX Settings - Exchange

Best regards,

Hi,

What I understand that you want to change the  MTA host name in Exchange Server 2013.

The complete procedure to change the host name is mentioned below: -

Step1: - Sart ESM.

Step 2: - Go to Server protocols.

Step 3: - Select Default SMTP Virtual Server Properties.

Step4: - Go to the Delivery tab.

Step 5: - Click on Advanced button.

Step 6: - Fully Qualified Domain Name put what the outside DNS host name is here.

Step 7: - Restart SMTP service.

Thanks and regards

Ashish@S  

There is no requirement that the FQDN on the send connector must match the MX record. If that was the case, most mail flow would fail.

The important thing is that there is a PTR for the IP of the sending SMTP gateway and you it should have a FQDN n the send connector that matches that.

If you want to set the send connector to mail.ttlhosting.co.uk, do that following:

http://technet.microsoft.com/en-us/library/aa998294(v=exchg.150).aspx

The Fqdn parameter specifies the FQDN used as the source server for connected messaging servers that use the Send connector to receive outgoing messages. The value of this parameter is displayed to connected messaging servers whenever a source server name is required, as in the following examples:

• In the EHLO/HELO command when the Send connector communicates with the next hop messaging server

• In the most recent Received header field added to the message by the next hop messaging server after the message leaves the Transport service on a Mailbox server or an Edge server

• During TLS authentication

The default value of the Fqdn parameter is $null. This means the default FQDN value is the FQDN of the Mailbox server or Edge server that contains the Send connector.

There is no requirement that the FQDN on the send connector must match the MX record. If that was the case, most mail flow would fail

Your not totaly rights here.. Go read :

https://tools.ietf.org/html/rfc5321#section-2.3.5

with states :

Only resolvable, fully-qualified domain names (FQDNs) are permitted
   when domain names are used in SMTP.  In other words, names that can
   be resolved to MX RRs or address (i.e., A or AAAA) RRs (as discussed
   in Section 5) are permitted, as are CNAME RRs whose targets can be
   resolved, in turn, to MX or address RRs.  Local nicknames or
   unqualified names MUST NOT be used.  There are two exceptions to the
   rule requiring FQDNs:

The domain name given in the EHLO command MUST be either a primary
      host name (a domain name that resolves to an address RR) or, if
      the host has no name, an address literal, as described in
      Section 4.1.3 and discussed further in the EHLO discussion of
      Section 4.1.4.

If a HELO comes with:  myserver.mydomain.local    then its not RFC compliant and mail wil be rejected.

Lots of exchange servers report .local   and mainwhile...

.local and .lan are reserved domainnames by mDNS.

I block everybody without correct dns settings for mail.. why save for about more than 90% of spam...