| Author |
Message |
Applebaum
Guest
|
 Posted:
Wed Sep 28, 2005 12:50 am Post subject:
Another Mx Problem |
|
|
Hi,
We recently switched our DNS services to Register.com. At first, I copied
the way our settings had been before. For Mx records, I put in:
Host Name Priority Mail Server
sa-intl.org High 64.115.124.115
it.sa-intl.org High mail.centroitalia.coop.org
After I set this up, it worked just fine, or so I thought.
Then I checked with Register.com's tech support to verify that I had set up
the subdomain's (it.) Mx record properly. They said that I had, but they
insisted that for our main record, it should say mail.sa-intl.org, and NOT
our mail server's IP address, and we should have an A record pointing
mail.sa-intl.org to our mail server's IP address.
I followed their advice, and we stopped receiving external email. So I
switched the Mx record back to our IP address, and we received external
email again.
But I'm getting reports that people from some domains are unable to email
us. They're getting NDRs like:
<SAI.sa-intl.org #5.5.0 smtp;550-Verification failed for...
And, when I go to DNSreport.com, we get:
FAIL: MX is host name, not IP
ERROR: You have one or more MX record(s) that contain an IP address. This
is not valid. A fully RFC-compliant mailserver will not be able to send you
mail (although some mail servers will, due to the TCP/IP functions that they
use). The problem MX records are: 64.115.124.115.
also I get:
WARN: Multiple MX records
WARNING: You only have 1 MX record. If your primary mail server is down or
unreachable, there is a chance that mail may have troubles reaching you.
But when I followed followed Register.com's advice, we stopped receiving
emails. I don't want to mess around with it again without knowing exactly
what to do.
Many thanks in advance!!!
Matthew |
|
| Back to top |
|
 |
Michael Jenkin [SBS-MVP]
Guest
|
| Posted:
Wed Sep 28, 2005 12:50 am Post subject:
Re: Another Mx Problem |
|
|
Hello,
I am unfamilier with Register.com however one of your issues looks like
you do not have a valid reverse DNS lookup in their tables. Antispam etc
tools/email servers with reverse DNS lookup will have trouble
communicating with your exchange box.
Normally, at the SBS end, I run the CEICW wizard, tell it the domain
name and certificate name. This will give all users on the box the
correct email extension and allow exchange to accept emails for the
domain. It also set's up DNS, the forwarders etc.
Then I contact the ISP handling DNS and tell them, here is my IP, give
it this reverse lookup name and that would be that. And it normally
always works. It would be on their server and beyond my control.
Are you trying to modify DNS at your end on the SBS box or do you need
to add the information manually to register.com's DNS servers using some
form of web interface ?
I am unsure why you are trying to edit the DNS tables.
Thanks
Applebaum wrote:
| Quote: | Hi,
We recently switched our DNS services to Register.com. At first, I copied
the way our settings had been before. For Mx records, I put in:
Host Name Priority Mail Server
sa-intl.org High 64.115.124.115
it.sa-intl.org High mail.centroitalia.coop.org
After I set this up, it worked just fine, or so I thought.
Then I checked with Register.com's tech support to verify that I had set up
the subdomain's (it.) Mx record properly. They said that I had, but they
insisted that for our main record, it should say mail.sa-intl.org, and NOT
our mail server's IP address, and we should have an A record pointing
mail.sa-intl.org to our mail server's IP address.
I followed their advice, and we stopped receiving external email. So I
switched the Mx record back to our IP address, and we received external
email again.
But I'm getting reports that people from some domains are unable to email
us. They're getting NDRs like:
SAI.sa-intl.org #5.5.0 smtp;550-Verification failed for...
And, when I go to DNSreport.com, we get:
FAIL: MX is host name, not IP
ERROR: You have one or more MX record(s) that contain an IP address. This
is not valid. A fully RFC-compliant mailserver will not be able to send you
mail (although some mail servers will, due to the TCP/IP functions that they
use). The problem MX records are: 64.115.124.115.
also I get:
WARN: Multiple MX records
WARNING: You only have 1 MX record. If your primary mail server is down or
unreachable, there is a chance that mail may have troubles reaching you.
But when I followed followed Register.com's advice, we stopped receiving
emails. I don't want to mess around with it again without knowing exactly
what to do.
Many thanks in advance!!!
Matthew
|
--
Michael J. Jenkin MVP - SBS, Senior Systems Engineer
Visit http://www.mickyj.com
Microsoft Most Valued Professional, Microsoft's Windows Server Systems -
Small Business Server
MVP's do not work for Microsoft. If this email was generated in a
newsgroup, please reply only to the newsgroup.
Note: The contents of my postings and responses here represent my
personal opinions and do not necessarily reflect the views, thoughts or
feelings of Microsoft or any of its employees.
http://mvp.support.microsoft.com |
|
| Back to top |
|
|
Applebaum
Guest
|
| Posted:
Wed Sep 28, 2005 7:40 am Post subject:
Re: Another Mx Problem |
|
|
| Quote: | Are you trying to modify DNS at your end on the SBS box or do you need
to add the information manually to register.com's DNS servers using some
form of web interface ?
|
Yes, I'm trying to manually add the information to register.com's DNS
server. When I added an Mx record pointing to mail.sa-intl.org, as they
recommended, we didn't get any mail.
Thanks!
Matthew
"Michael Jenkin [SBS-MVP]" <michael.jenkin@mvps.org> wrote in message
news:evUY8s7wFHA.2516@TK2MSFTNGP12.phx.gbl...
| Quote: | Hello,
I am unfamilier with Register.com however one of your issues looks like
you do not have a valid reverse DNS lookup in their tables. Antispam etc
tools/email servers with reverse DNS lookup will have trouble
communicating with your exchange box.
Normally, at the SBS end, I run the CEICW wizard, tell it the domain
name and certificate name. This will give all users on the box the
correct email extension and allow exchange to accept emails for the
domain. It also set's up DNS, the forwarders etc.
Then I contact the ISP handling DNS and tell them, here is my IP, give
it this reverse lookup name and that would be that. And it normally
always works. It would be on their server and beyond my control.
Are you trying to modify DNS at your end on the SBS box or do you need
to add the information manually to register.com's DNS servers using some
form of web interface ?
I am unsure why you are trying to edit the DNS tables.
Thanks
Applebaum wrote:
Hi,
We recently switched our DNS services to Register.com. At first, I
copied
the way our settings had been before. For Mx records, I put in:
Host Name Priority Mail Server
sa-intl.org High 64.115.124.115
it.sa-intl.org High mail.centroitalia.coop.org
After I set this up, it worked just fine, or so I thought.
Then I checked with Register.com's tech support to verify that I had set
up
the subdomain's (it.) Mx record properly. They said that I had, but
they
insisted that for our main record, it should say mail.sa-intl.org, and
NOT
our mail server's IP address, and we should have an A record pointing
mail.sa-intl.org to our mail server's IP address.
I followed their advice, and we stopped receiving external email. So I
switched the Mx record back to our IP address, and we received external
email again.
But I'm getting reports that people from some domains are unable to
email
us. They're getting NDRs like:
SAI.sa-intl.org #5.5.0 smtp;550-Verification failed for...
And, when I go to DNSreport.com, we get:
FAIL: MX is host name, not IP
ERROR: You have one or more MX record(s) that contain an IP address.
This
is not valid. A fully RFC-compliant mailserver will not be able to send
you
mail (although some mail servers will, due to the TCP/IP functions that
they
use). The problem MX records are: 64.115.124.115.
also I get:
WARN: Multiple MX records
WARNING: You only have 1 MX record. If your primary mail server is down
or
unreachable, there is a chance that mail may have troubles reaching you.
But when I followed followed Register.com's advice, we stopped receiving
emails. I don't want to mess around with it again without knowing
exactly
what to do.
Many thanks in advance!!!
Matthew
--
Michael J. Jenkin MVP - SBS, Senior Systems Engineer
Visit http://www.mickyj.com
Microsoft Most Valued Professional, Microsoft's Windows Server Systems -
Small Business Server
MVP's do not work for Microsoft. If this email was generated in a
newsgroup, please reply only to the newsgroup.
Note: The contents of my postings and responses here represent my
personal opinions and do not necessarily reflect the views, thoughts or
feelings of Microsoft or any of its employees.
http://mvp.support.microsoft.com
|
|
|
| Back to top |
|
|
Kathy
Guest
|
| Posted:
Wed Sep 28, 2005 8:51 am Post subject:
Re: Another Mx Problem |
|
|
An MX record should be a host name, not an IP address. There should be an A
record for that hostname , so they are basically correct. 64.115.124.115 is
mail.sa-intl.org, (although it says sai.sa-intl.org in the greeting) so
that is the hostname you should use, so that the reverse lookup also works
correctly. Priority should be a number, I think, eg 10 for the primary
and 20 for the secondary.
Have a look at what DNS report says about your MX records
http://www.dnsreport.com/tools/dnsreport.ch?domain=sa-intl.org
Kathy
"Applebaum" <mappleNOSPAM@inchNOSPAM.com> wrote in message
news:uExFBa6wFHA.2348@TK2MSFTNGP15.phx.gbl...
| Quote: | Hi,
We recently switched our DNS services to Register.com. At first, I copied
the way our settings had been before. For Mx records, I put in:
Host Name Priority Mail Server
sa-intl.org High 64.115.124.115
it.sa-intl.org High mail.centroitalia.coop.org
After I set this up, it worked just fine, or so I thought.
Then I checked with Register.com's tech support to verify that I had set
up
the subdomain's (it.) Mx record properly. They said that I had, but they
insisted that for our main record, it should say mail.sa-intl.org, and NOT
our mail server's IP address, and we should have an A record pointing
mail.sa-intl.org to our mail server's IP address.
I followed their advice, and we stopped receiving external email. So I
switched the Mx record back to our IP address, and we received external
email again.
But I'm getting reports that people from some domains are unable to email
us. They're getting NDRs like:
SAI.sa-intl.org #5.5.0 smtp;550-Verification failed for...
And, when I go to DNSreport.com, we get:
FAIL: MX is host name, not IP
ERROR: You have one or more MX record(s) that contain an IP address. This
is not valid. A fully RFC-compliant mailserver will not be able to send
you
mail (although some mail servers will, due to the TCP/IP functions that
they
use). The problem MX records are: 64.115.124.115.
also I get:
WARN: Multiple MX records
WARNING: You only have 1 MX record. If your primary mail server is down or
unreachable, there is a chance that mail may have troubles reaching you.
But when I followed followed Register.com's advice, we stopped receiving
emails. I don't want to mess around with it again without knowing exactly
what to do.
Many thanks in advance!!!
Matthew
|
|
|
| Back to top |
|
|
Kathy
Guest
|
| Posted:
Wed Sep 28, 2005 8:51 am Post subject:
Re: Another Mx Problem |
|
|
mail.sa-intl.org does not accept connections on port 25 (from telnet), so
that may be why you don't get mail. Is it the external NIC of your router
and is port 25 open/forwarded to the SBS server on your router (and ISA)?
Kathy
"Applebaum" <mappleNOSPAM@inch.com> wrote in message
news:%23jmaHX9wFHA.3256@TK2MSFTNGP09.phx.gbl...
| Quote: | Are you trying to modify DNS at your end on the SBS box or do you need
to add the information manually to register.com's DNS servers using some
form of web interface ?
Yes, I'm trying to manually add the information to register.com's DNS
server. When I added an Mx record pointing to mail.sa-intl.org, as they
recommended, we didn't get any mail.
Thanks!
Matthew
"Michael Jenkin [SBS-MVP]" <michael.jenkin@mvps.org> wrote in message
news:evUY8s7wFHA.2516@TK2MSFTNGP12.phx.gbl...
Hello,
I am unfamilier with Register.com however one of your issues looks like
you do not have a valid reverse DNS lookup in their tables. Antispam etc
tools/email servers with reverse DNS lookup will have trouble
communicating with your exchange box.
Normally, at the SBS end, I run the CEICW wizard, tell it the domain
name and certificate name. This will give all users on the box the
correct email extension and allow exchange to accept emails for the
domain. It also set's up DNS, the forwarders etc.
Then I contact the ISP handling DNS and tell them, here is my IP, give
it this reverse lookup name and that would be that. And it normally
always works. It would be on their server and beyond my control.
Are you trying to modify DNS at your end on the SBS box or do you need
to add the information manually to register.com's DNS servers using some
form of web interface ?
I am unsure why you are trying to edit the DNS tables.
Thanks
Applebaum wrote:
Hi,
We recently switched our DNS services to Register.com. At first, I
copied
the way our settings had been before. For Mx records, I put in:
Host Name Priority Mail Server
sa-intl.org High 64.115.124.115
it.sa-intl.org High mail.centroitalia.coop.org
After I set this up, it worked just fine, or so I thought.
Then I checked with Register.com's tech support to verify that I had
set
up
the subdomain's (it.) Mx record properly. They said that I had, but
they
insisted that for our main record, it should say mail.sa-intl.org, and
NOT
our mail server's IP address, and we should have an A record pointing
mail.sa-intl.org to our mail server's IP address.
I followed their advice, and we stopped receiving external email. So
I
switched the Mx record back to our IP address, and we received
external
email again.
But I'm getting reports that people from some domains are unable to
email
us. They're getting NDRs like:
SAI.sa-intl.org #5.5.0 smtp;550-Verification failed for...
And, when I go to DNSreport.com, we get:
FAIL: MX is host name, not IP
ERROR: You have one or more MX record(s) that contain an IP address.
This
is not valid. A fully RFC-compliant mailserver will not be able to
send
you
mail (although some mail servers will, due to the TCP/IP functions
that
they
use). The problem MX records are: 64.115.124.115.
also I get:
WARN: Multiple MX records
WARNING: You only have 1 MX record. If your primary mail server is
down
or
unreachable, there is a chance that mail may have troubles reaching
you.
But when I followed followed Register.com's advice, we stopped
receiving
emails. I don't want to mess around with it again without knowing
exactly
what to do.
Many thanks in advance!!!
Matthew
--
Michael J. Jenkin MVP - SBS, Senior Systems Engineer
Visit http://www.mickyj.com
Microsoft Most Valued Professional, Microsoft's Windows Server Systems -
Small Business Server
MVP's do not work for Microsoft. If this email was generated in a
newsgroup, please reply only to the newsgroup.
Note: The contents of my postings and responses here represent my
personal opinions and do not necessarily reflect the views, thoughts or
feelings of Microsoft or any of its employees.
http://mvp.support.microsoft.com
|
|
|
| Back to top |
|
|
Applebaum
Guest
|
| Posted:
Wed Sep 28, 2005 8:52 pm Post subject:
Re: Another Mx Problem |
|
|
Right, because I reverted our Mx record so that *.sa-intl.org is pointing
directly to our server's IP address (the external NIC on our router), not to
mail.sa-intl.org.
I'm not sure about port 25.
"Kathy" <vbtskje@nospam.postalias> wrote in message
news:uoJLpY$wFHA.3436@TK2MSFTNGP10.phx.gbl...
| Quote: | mail.sa-intl.org does not accept connections on port 25 (from telnet), so
that may be why you don't get mail. Is it the external NIC of your router
and is port 25 open/forwarded to the SBS server on your router (and ISA)?
Kathy
"Applebaum" <mappleNOSPAM@inch.com> wrote in message
news:%23jmaHX9wFHA.3256@TK2MSFTNGP09.phx.gbl...
Are you trying to modify DNS at your end on the SBS box or do you need
to add the information manually to register.com's DNS servers using
some
form of web interface ?
Yes, I'm trying to manually add the information to register.com's DNS
server. When I added an Mx record pointing to mail.sa-intl.org, as they
recommended, we didn't get any mail.
Thanks!
Matthew
"Michael Jenkin [SBS-MVP]" <michael.jenkin@mvps.org> wrote in message
news:evUY8s7wFHA.2516@TK2MSFTNGP12.phx.gbl...
Hello,
I am unfamilier with Register.com however one of your issues looks
like
you do not have a valid reverse DNS lookup in their tables. Antispam
etc
tools/email servers with reverse DNS lookup will have trouble
communicating with your exchange box.
Normally, at the SBS end, I run the CEICW wizard, tell it the domain
name and certificate name. This will give all users on the box the
correct email extension and allow exchange to accept emails for the
domain. It also set's up DNS, the forwarders etc.
Then I contact the ISP handling DNS and tell them, here is my IP, give
it this reverse lookup name and that would be that. And it normally
always works. It would be on their server and beyond my control.
Are you trying to modify DNS at your end on the SBS box or do you need
to add the information manually to register.com's DNS servers using
some
form of web interface ?
I am unsure why you are trying to edit the DNS tables.
Thanks
Applebaum wrote:
Hi,
We recently switched our DNS services to Register.com. At first, I
copied
the way our settings had been before. For Mx records, I put in:
Host Name Priority Mail Server
sa-intl.org High 64.115.124.115
it.sa-intl.org High mail.centroitalia.coop.org
After I set this up, it worked just fine, or so I thought.
Then I checked with Register.com's tech support to verify that I had
set
up
the subdomain's (it.) Mx record properly. They said that I had, but
they
insisted that for our main record, it should say mail.sa-intl.org,
and
NOT
our mail server's IP address, and we should have an A record
pointing
mail.sa-intl.org to our mail server's IP address.
I followed their advice, and we stopped receiving external email.
So
I
switched the Mx record back to our IP address, and we received
external
email again.
But I'm getting reports that people from some domains are unable to
email
us. They're getting NDRs like:
SAI.sa-intl.org #5.5.0 smtp;550-Verification failed for...
And, when I go to DNSreport.com, we get:
FAIL: MX is host name, not IP
ERROR: You have one or more MX record(s) that contain an IP
address.
This
is not valid. A fully RFC-compliant mailserver will not be able to
send
you
mail (although some mail servers will, due to the TCP/IP functions
that
they
use). The problem MX records are: 64.115.124.115.
also I get:
WARN: Multiple MX records
WARNING: You only have 1 MX record. If your primary mail server is
down
or
unreachable, there is a chance that mail may have troubles reaching
you.
But when I followed followed Register.com's advice, we stopped
receiving
emails. I don't want to mess around with it again without knowing
exactly
what to do.
Many thanks in advance!!!
Matthew
--
Michael J. Jenkin MVP - SBS, Senior Systems Engineer
Visit http://www.mickyj.com
Microsoft Most Valued Professional, Microsoft's Windows Server
Systems -
Small Business Server
MVP's do not work for Microsoft. If this email was generated in a
newsgroup, please reply only to the newsgroup.
Note: The contents of my postings and responses here represent my
personal opinions and do not necessarily reflect the views, thoughts
or
feelings of Microsoft or any of its employees.
http://mvp.support.microsoft.com
|
|
|
| Back to top |
|
|
Applebaum
Guest
|
| Posted:
Wed Sep 28, 2005 8:52 pm Post subject:
Re: Another Mx Problem |
|
|
That's what register.com told me, but when I did that, we stopped receiving
mail. So they were right? If that's the way it's supposed to be configured,
then I wonder why it didn't work for us until we went back to the MX record
being the IP address? How to troubleshoot it when it's not working?
"Kathy" <vbtskje@nospam.postalias> wrote in message
news:O04D0V$wFHA.3860@TK2MSFTNGP09.phx.gbl...
| Quote: | An MX record should be a host name, not an IP address. There should be an
A
record for that hostname , so they are basically correct. 64.115.124.115
is
mail.sa-intl.org, (although it says sai.sa-intl.org in the greeting) so
that is the hostname you should use, so that the reverse lookup also works
correctly. Priority should be a number, I think, eg 10 for the primary
and 20 for the secondary.
Have a look at what DNS report says about your MX records
http://www.dnsreport.com/tools/dnsreport.ch?domain=sa-intl.org
Kathy
"Applebaum" <mappleNOSPAM@inchNOSPAM.com> wrote in message
news:uExFBa6wFHA.2348@TK2MSFTNGP15.phx.gbl...
Hi,
We recently switched our DNS services to Register.com. At first, I
copied
the way our settings had been before. For Mx records, I put in:
Host Name Priority Mail Server
sa-intl.org High 64.115.124.115
it.sa-intl.org High mail.centroitalia.coop.org
After I set this up, it worked just fine, or so I thought.
Then I checked with Register.com's tech support to verify that I had set
up
the subdomain's (it.) Mx record properly. They said that I had, but
they
insisted that for our main record, it should say mail.sa-intl.org, and
NOT
our mail server's IP address, and we should have an A record pointing
mail.sa-intl.org to our mail server's IP address.
I followed their advice, and we stopped receiving external email. So I
switched the Mx record back to our IP address, and we received external
email again.
But I'm getting reports that people from some domains are unable to
email
us. They're getting NDRs like:
SAI.sa-intl.org #5.5.0 smtp;550-Verification failed for...
And, when I go to DNSreport.com, we get:
FAIL: MX is host name, not IP
ERROR: You have one or more MX record(s) that contain an IP address.
This
is not valid. A fully RFC-compliant mailserver will not be able to send
you
mail (although some mail servers will, due to the TCP/IP functions that
they
use). The problem MX records are: 64.115.124.115.
also I get:
WARN: Multiple MX records
WARNING: You only have 1 MX record. If your primary mail server is down
or
unreachable, there is a chance that mail may have troubles reaching you.
But when I followed followed Register.com's advice, we stopped receiving
emails. I don't want to mess around with it again without knowing
exactly
what to do.
Many thanks in advance!!!
Matthew
|
|
|
| Back to top |
|
|
Kathy
Guest
|
| Posted:
Thu Sep 29, 2005 8:51 am Post subject:
Re: Another Mx Problem |
|
|
So, are you receiving all mail now?
You don't seem to have a host (A) record for mail.sa-intl.org or for
sai.sa-intl.org.
So you need to set up an A record for sai.sa-intl.org 64.115.124.115 (the
external address of the router)
An mx record sai.sa-intl.org priority 10 and a backup MX record if you have
an arrangement with someone to act as a secondary mail server. You may also
need a cname of mail for sai.sa-intl.org (I'm assuming it still announces
itself as sai.sa-intl.org as DNS report suggests). Otherwise substitute mail
for sai throughout. You could also ask about an SPF record,which allows you
to specify what hosts are allowed to send mail for your domain.
A 5.5.0 error suggests a missing PTR record - reverse lookup address - for
the external ip of the router (64.115.124.115) - ie sai-sa-intl.org does not
resolve to 64.115.124.115 and vice versa. That would affect others receiving
mail from you if you send using DNS, not incoming mail to you. The reverse
lookup zone is probably controlled by your ISP not register.com.
Also make sure that the SMTP Virtual server has sa-intl.org as its domain
name not sa-intl.local.
Sender verification failure also happens when the receiving server refuses
messages with a blank sender as that is against the RFC. So if you are
refusing these as an anti-spam measure, you'll have problems.
Sorry, I'm not an SMTP expert.
HTH
Kathy
You need to make sure that port 25 on the router is forwarded to the SBS
server
"Applebaum" <mappleNOSPAM@inch.com> wrote in message
news:usPjc7ExFHA.2848@TK2MSFTNGP15.phx.gbl...
| Quote: | That's what register.com told me, but when I did that, we stopped
receiving
mail. So they were right? If that's the way it's supposed to be
configured,
then I wonder why it didn't work for us until we went back to the MX
record
being the IP address? How to troubleshoot it when it's not working?
"Kathy" <vbtskje@nospam.postalias> wrote in message
news:O04D0V$wFHA.3860@TK2MSFTNGP09.phx.gbl...
An MX record should be a host name, not an IP address. There should be
an
A
record for that hostname , so they are basically correct. 64.115.124.115
is
mail.sa-intl.org, (although it says sai.sa-intl.org in the greeting) so
that is the hostname you should use, so that the reverse lookup also
works
correctly. Priority should be a number, I think, eg 10 for the
primary
and 20 for the secondary.
Have a look at what DNS report says about your MX records
http://www.dnsreport.com/tools/dnsreport.ch?domain=sa-intl.org
Kathy
"Applebaum" <mappleNOSPAM@inchNOSPAM.com> wrote in message
news:uExFBa6wFHA.2348@TK2MSFTNGP15.phx.gbl...
Hi,
We recently switched our DNS services to Register.com. At first, I
copied
the way our settings had been before. For Mx records, I put in:
Host Name Priority Mail Server
sa-intl.org High 64.115.124.115
it.sa-intl.org High mail.centroitalia.coop.org
After I set this up, it worked just fine, or so I thought.
Then I checked with Register.com's tech support to verify that I had
set
up
the subdomain's (it.) Mx record properly. They said that I had, but
they
insisted that for our main record, it should say mail.sa-intl.org, and
NOT
our mail server's IP address, and we should have an A record pointing
mail.sa-intl.org to our mail server's IP address.
I followed their advice, and we stopped receiving external email. So
I
switched the Mx record back to our IP address, and we received
external
email again.
But I'm getting reports that people from some domains are unable to
email
us. They're getting NDRs like:
SAI.sa-intl.org #5.5.0 smtp;550-Verification failed for...
And, when I go to DNSreport.com, we get:
FAIL: MX is host name, not IP
ERROR: You have one or more MX record(s) that contain an IP address.
This
is not valid. A fully RFC-compliant mailserver will not be able to
send
you
mail (although some mail servers will, due to the TCP/IP functions
that
they
use). The problem MX records are: 64.115.124.115.
also I get:
WARN: Multiple MX records
WARNING: You only have 1 MX record. If your primary mail server is
down
or
unreachable, there is a chance that mail may have troubles reaching
you.
But when I followed followed Register.com's advice, we stopped
receiving
emails. I don't want to mess around with it again without knowing
exactly
what to do.
Many thanks in advance!!!
Matthew
|
|
|
| Back to top |
|
|
Kathy
Guest
|
| Posted:
Thu Sep 29, 2005 4:51 pm Post subject:
Re: Another Mx Problem |
|
|
BTW Connecting to 64.115.124.115 on port 25 gets sai.sa-intl.org in the
greeting. But sai.sa-intl.org resolves to 204.9.42.20, so ignore what I
said about names etc - you may just need to change the fqdn of the virtual
smtp server to mail.sa-intl.org .
Sorry
"Kathy" <vbtskje@nospam.postalias> wrote in message
news:e5SahjMxFHA.3000@TK2MSFTNGP12.phx.gbl...
| Quote: | So, are you receiving all mail now?
You don't seem to have a host (A) record for mail.sa-intl.org or for
sai.sa-intl.org.
So you need to set up an A record for sai.sa-intl.org 64.115.124.115 (the
external address of the router)
An mx record sai.sa-intl.org priority 10 and a backup MX record if you
have
an arrangement with someone to act as a secondary mail server. You may
also
need a cname of mail for sai.sa-intl.org (I'm assuming it still announces
itself as sai.sa-intl.org as DNS report suggests). Otherwise substitute
mail
for sai throughout. You could also ask about an SPF record,which allows
you
to specify what hosts are allowed to send mail for your domain.
A 5.5.0 error suggests a missing PTR record - reverse lookup address - for
the external ip of the router (64.115.124.115) - ie sai-sa-intl.org does
not
resolve to 64.115.124.115 and vice versa. That would affect others
receiving
mail from you if you send using DNS, not incoming mail to you. The reverse
lookup zone is probably controlled by your ISP not register.com.
Also make sure that the SMTP Virtual server has sa-intl.org as its domain
name not sa-intl.local.
Sender verification failure also happens when the receiving server refuses
messages with a blank sender as that is against the RFC. So if you are
refusing these as an anti-spam measure, you'll have problems.
Sorry, I'm not an SMTP expert.
HTH
Kathy
You need to make sure that port 25 on the router is forwarded to the SBS
server
"Applebaum" <mappleNOSPAM@inch.com> wrote in message
news:usPjc7ExFHA.2848@TK2MSFTNGP15.phx.gbl...
That's what register.com told me, but when I did that, we stopped
receiving
mail. So they were right? If that's the way it's supposed to be
configured,
then I wonder why it didn't work for us until we went back to the MX
record
being the IP address? How to troubleshoot it when it's not working?
"Kathy" <vbtskje@nospam.postalias> wrote in message
news:O04D0V$wFHA.3860@TK2MSFTNGP09.phx.gbl...
An MX record should be a host name, not an IP address. There should
be
an
A
record for that hostname , so they are basically correct.
64.115.124.115
is
mail.sa-intl.org, (although it says sai.sa-intl.org in the greeting)
so
that is the hostname you should use, so that the reverse lookup also
works
correctly. Priority should be a number, I think, eg 10 for the
primary
and 20 for the secondary.
Have a look at what DNS report says about your MX records
http://www.dnsreport.com/tools/dnsreport.ch?domain=sa-intl.org
Kathy
"Applebaum" <mappleNOSPAM@inchNOSPAM.com> wrote in message
news:uExFBa6wFHA.2348@TK2MSFTNGP15.phx.gbl...
Hi,
We recently switched our DNS services to Register.com. At first, I
copied
the way our settings had been before. For Mx records, I put in:
Host Name Priority Mail Server
sa-intl.org High 64.115.124.115
it.sa-intl.org High mail.centroitalia.coop.org
After I set this up, it worked just fine, or so I thought.
Then I checked with Register.com's tech support to verify that I had
set
up
the subdomain's (it.) Mx record properly. They said that I had, but
they
insisted that for our main record, it should say mail.sa-intl.org,
and
NOT
our mail server's IP address, and we should have an A record
pointing
mail.sa-intl.org to our mail server's IP address.
I followed their advice, and we stopped receiving external email.
So
I
switched the Mx record back to our IP address, and we received
external
email again.
But I'm getting reports that people from some domains are unable to
email
us. They're getting NDRs like:
SAI.sa-intl.org #5.5.0 smtp;550-Verification failed for...
And, when I go to DNSreport.com, we get:
FAIL: MX is host name, not IP
ERROR: You have one or more MX record(s) that contain an IP
address.
This
is not valid. A fully RFC-compliant mailserver will not be able to
send
you
mail (although some mail servers will, due to the TCP/IP functions
that
they
use). The problem MX records are: 64.115.124.115.
also I get:
WARN: Multiple MX records
WARNING: You only have 1 MX record. If your primary mail server is
down
or
unreachable, there is a chance that mail may have troubles reaching
you.
But when I followed followed Register.com's advice, we stopped
receiving
emails. I don't want to mess around with it again without knowing
exactly
what to do.
Many thanks in advance!!!
Matthew
|
|
|
| Back to top |
|
|
Applebaum
Guest
|
| Posted:
Mon Oct 03, 2005 6:38 am Post subject:
Found the problem |
|
|
Thanks for your help, everyone.
On Friday, as I prepared to again accept the advice of register.com, as well
as the helpers on this thread, I found that the A record that I (I think it
was me) had set up connecting mail.sa-intl.org to our mail server's IP
address, was wrong. The IP address was off by one number. Tricky little
bugger.
Next tasks: Find a solution to our enourmous spam problem, and set up a
backup mail server.
Thanks again!!!
"Applebaum" <mappleNOSPAM@inchNOSPAM.com> wrote in message
news:uExFBa6wFHA.2348@TK2MSFTNGP15.phx.gbl...
| Quote: | Hi,
We recently switched our DNS services to Register.com. At first, I copied
the way our settings had been before. For Mx records, I put in:
Host Name Priority Mail Server
sa-intl.org High 64.115.124.115
it.sa-intl.org High mail.centroitalia.coop.org
After I set this up, it worked just fine, or so I thought.
Then I checked with Register.com's tech support to verify that I had set
up
the subdomain's (it.) Mx record properly. They said that I had, but they
insisted that for our main record, it should say mail.sa-intl.org, and NOT
our mail server's IP address, and we should have an A record pointing
mail.sa-intl.org to our mail server's IP address.
I followed their advice, and we stopped receiving external email. So I
switched the Mx record back to our IP address, and we received external
email again.
But I'm getting reports that people from some domains are unable to email
us. They're getting NDRs like:
SAI.sa-intl.org #5.5.0 smtp;550-Verification failed for...
And, when I go to DNSreport.com, we get:
FAIL: MX is host name, not IP
ERROR: You have one or more MX record(s) that contain an IP address. This
is not valid. A fully RFC-compliant mailserver will not be able to send
you
mail (although some mail servers will, due to the TCP/IP functions that
they
use). The problem MX records are: 64.115.124.115.
also I get:
WARN: Multiple MX records
WARNING: You only have 1 MX record. If your primary mail server is down or
unreachable, there is a chance that mail may have troubles reaching you.
But when I followed followed Register.com's advice, we stopped receiving
emails. I don't want to mess around with it again without knowing exactly
what to do.
Many thanks in advance!!!
Matthew
|
|
|
| Back to top |
|
|
Kevin Weilbacher [SBS-MVP
Guest
|
| Posted:
Tue Oct 04, 2005 12:50 am Post subject:
Re: Found the problem |
|
|
if you are on SBS 2003, Exchange has IMF for filtering out spam.
--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"
"Applebaum" <mappleNOSPAM@inch.com> wrote in message
news:OBbuyr7xFHA.1168@TK2MSFTNGP10.phx.gbl...
| Quote: | Thanks for your help, everyone.
On Friday, as I prepared to again accept the advice of register.com, as
well
as the helpers on this thread, I found that the A record that I (I think
it
was me) had set up connecting mail.sa-intl.org to our mail server's IP
address, was wrong. The IP address was off by one number. Tricky little
bugger.
Next tasks: Find a solution to our enourmous spam problem, and set up a
backup mail server.
Thanks again!!!
"Applebaum" <mappleNOSPAM@inchNOSPAM.com> wrote in message
news:uExFBa6wFHA.2348@TK2MSFTNGP15.phx.gbl...
Hi,
We recently switched our DNS services to Register.com. At first, I copied
the way our settings had been before. For Mx records, I put in:
Host Name Priority Mail Server
sa-intl.org High 64.115.124.115
it.sa-intl.org High mail.centroitalia.coop.org
After I set this up, it worked just fine, or so I thought.
Then I checked with Register.com's tech support to verify that I had set
up
the subdomain's (it.) Mx record properly. They said that I had, but they
insisted that for our main record, it should say mail.sa-intl.org, and
NOT
our mail server's IP address, and we should have an A record pointing
mail.sa-intl.org to our mail server's IP address.
I followed their advice, and we stopped receiving external email. So I
switched the Mx record back to our IP address, and we received external
email again.
But I'm getting reports that people from some domains are unable to email
us. They're getting NDRs like:
SAI.sa-intl.org #5.5.0 smtp;550-Verification failed for...
And, when I go to DNSreport.com, we get:
FAIL: MX is host name, not IP
ERROR: You have one or more MX record(s) that contain an IP address.
This
is not valid. A fully RFC-compliant mailserver will not be able to send
you
mail (although some mail servers will, due to the TCP/IP functions that
they
use). The problem MX records are: 64.115.124.115.
also I get:
WARN: Multiple MX records
WARNING: You only have 1 MX record. If your primary mail server is down
or
unreachable, there is a chance that mail may have troubles reaching you.
But when I followed followed Register.com's advice, we stopped receiving
emails. I don't want to mess around with it again without knowing
exactly
what to do.
Many thanks in advance!!!
Matthew
|
|
|
| Back to top |
|
|
Applebaum
Guest
|
| Posted:
Tue Oct 04, 2005 8:51 pm Post subject:
Re: Found the problem |
|
|
I'm still on SBS 2000.
We've had our server for more than four years. I'm hoping this organization
is going to pony up for a new server before this one turns five, at which
point we'll move to 2003.
Would it be dumb to migrate from SBS 2000 to SBS 2003 in the year 2006?
"Kevin Weilbacher [SBS-MVP]" <kweilbacMVP@gte.net> wrote in message
news:%230Po1THyFHA.1032@TK2MSFTNGP12.phx.gbl...
| Quote: | if you are on SBS 2003, Exchange has IMF for filtering out spam.
--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"
"Applebaum" <mappleNOSPAM@inch.com> wrote in message
news:OBbuyr7xFHA.1168@TK2MSFTNGP10.phx.gbl...
Thanks for your help, everyone.
On Friday, as I prepared to again accept the advice of register.com, as
well
as the helpers on this thread, I found that the A record that I (I think
it
was me) had set up connecting mail.sa-intl.org to our mail server's IP
address, was wrong. The IP address was off by one number. Tricky little
bugger.
Next tasks: Find a solution to our enourmous spam problem, and set up a
backup mail server.
Thanks again!!!
"Applebaum" <mappleNOSPAM@inchNOSPAM.com> wrote in message
news:uExFBa6wFHA.2348@TK2MSFTNGP15.phx.gbl...
Hi,
We recently switched our DNS services to Register.com. At first, I
copied
the way our settings had been before. For Mx records, I put in:
Host Name Priority Mail Server
sa-intl.org High 64.115.124.115
it.sa-intl.org High mail.centroitalia.coop.org
After I set this up, it worked just fine, or so I thought.
Then I checked with Register.com's tech support to verify that I had set
up
the subdomain's (it.) Mx record properly. They said that I had, but
they
insisted that for our main record, it should say mail.sa-intl.org, and
NOT
our mail server's IP address, and we should have an A record pointing
mail.sa-intl.org to our mail server's IP address.
I followed their advice, and we stopped receiving external email. So I
switched the Mx record back to our IP address, and we received external
email again.
But I'm getting reports that people from some domains are unable to
email
us. They're getting NDRs like:
SAI.sa-intl.org #5.5.0 smtp;550-Verification failed for...
And, when I go to DNSreport.com, we get:
FAIL: MX is host name, not IP
ERROR: You have one or more MX record(s) that contain an IP address.
This
is not valid. A fully RFC-compliant mailserver will not be able to send
you
mail (although some mail servers will, due to the TCP/IP functions that
they
use). The problem MX records are: 64.115.124.115.
also I get:
WARN: Multiple MX records
WARNING: You only have 1 MX record. If your primary mail server is down
or
unreachable, there is a chance that mail may have troubles reaching you.
But when I followed followed Register.com's advice, we stopped receiving
emails. I don't want to mess around with it again without knowing
exactly
what to do.
Many thanks in advance!!!
Matthew
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in