pgaliardo
MIS
- Nov 30, 2004
- 887
I have a feeling our MX records are not totally set up correctly and I wanted some input from the experts. Here is our setup:
Exchange Server 2000 - name is EX2
Symantec Mail Security Appliance - Name: Mail8240
Cisco Router NATS public ip address used for mail to the Mail8240 appliance.
So when we receive mail, it first hits the appliance and if the mail is spam free, it is forwarded to our Exchange Server. However, outgoing mail goes directly from Exchange to the outside world. I changed this at one point on the advice of Symantec because a version upgrade had a problem sending outgoing mail.
First question: When I registered the MX record with our ISP, I gave the the name of the Exchange Server - EX2. This is associated with the public IP address. Is this correct, or should the DNS name be Mail8240? When I do a test with DNSStuff, I get the following warning:
WARNING: One or more of your mailservers is claiming to be a host other than what it really is (the SMTP greeting should be a 3-digit code, followed by a space or a dash, then the host name). If your mailserver sends out E-mail using this domain in its EHLO or HELO, your E-mail might get blocked by anti-spam software. This is also a technical violation of RFC821 4.3 (and RFC2821 4.3.1). Note that the hostname given in the SMTP greeting should have an A record pointing back to the same server. Note that this one test may use a cached DNS record.
ex2.corp.<domain_name>.com claims to be non-existent host mail8240.corp.<domain_name>.com:
220 mail8240.corp.<domain_name>.com ESMTP Symantec Mail Security
This concerns me. Also note that the server name is being resolved to the internal domain name with the CORP prefix. I have a feeling this is not correct. If it isn't, how do I correct that?
We are not really having problems sending or receiving e-mail, but lately we are getting 4.4.7 messages back from one particular domain. That error seems to be a server timeout on the receiving end, but I'm wondering if any of the above concerns have anything to do with it.
If anyone has advice or can point to a really in depth document on the correct configurations on an Exchange Server, I would really appreciate it.
Thanks.
Exchange Server 2000 - name is EX2
Symantec Mail Security Appliance - Name: Mail8240
Cisco Router NATS public ip address used for mail to the Mail8240 appliance.
So when we receive mail, it first hits the appliance and if the mail is spam free, it is forwarded to our Exchange Server. However, outgoing mail goes directly from Exchange to the outside world. I changed this at one point on the advice of Symantec because a version upgrade had a problem sending outgoing mail.
First question: When I registered the MX record with our ISP, I gave the the name of the Exchange Server - EX2. This is associated with the public IP address. Is this correct, or should the DNS name be Mail8240? When I do a test with DNSStuff, I get the following warning:
WARNING: One or more of your mailservers is claiming to be a host other than what it really is (the SMTP greeting should be a 3-digit code, followed by a space or a dash, then the host name). If your mailserver sends out E-mail using this domain in its EHLO or HELO, your E-mail might get blocked by anti-spam software. This is also a technical violation of RFC821 4.3 (and RFC2821 4.3.1). Note that the hostname given in the SMTP greeting should have an A record pointing back to the same server. Note that this one test may use a cached DNS record.
ex2.corp.<domain_name>.com claims to be non-existent host mail8240.corp.<domain_name>.com:
220 mail8240.corp.<domain_name>.com ESMTP Symantec Mail Security
This concerns me. Also note that the server name is being resolved to the internal domain name with the CORP prefix. I have a feeling this is not correct. If it isn't, how do I correct that?
We are not really having problems sending or receiving e-mail, but lately we are getting 4.4.7 messages back from one particular domain. That error seems to be a server timeout on the receiving end, but I'm wondering if any of the above concerns have anything to do with it.
If anyone has advice or can point to a really in depth document on the correct configurations on an Exchange Server, I would really appreciate it.
Thanks.