|
here is my mx and mail info
| INFO |
MX Record |
Your 3 MX records are:
1 mail.dirxion.com. [TTL=1200]
IP=209.50.107.88 [TTL=1200] [US]
10 smtp.easydns.com. [TTL=1200]
IP=205.210.42.52 [TTL=3600] [CA]
100 smtp2.easydns.com. [TTL=1200]
IP=205.210.42.53 [TTL=3600] [CA]
|
| PASS |
Invalid characters |
OK. All of your MX records appear to use valid hostnames, without any
invalid characters. |
| PASS |
All MX IPs public |
OK. All of your MX records appear to use public IPs. If there were any
private IPs, they would not be reachable, causing slight mail delays,
extra resource usage, and possibly bounced mail. |
| PASS |
MX records are not CNAMEs |
OK. Looking up your MX record did not just return a CNAME. If an MX
record query returns a CNAME, extra processing is required, and some mail
servers may not be able to handle it. |
| PASS |
MX A lookups have no CNAMEs |
OK. There appear to be no CNAMEs returned for A records lookups from
your MX records (CNAMEs are prohibited in MX records, according to RFC974,
RFC1034 3.6.2, RFC1912 2.4, and RFC2181 10.3). |
| PASS |
MX is host name, not IP |
OK. All of your MX records are host names (as opposed to IP addresses,
which are not allowed in MX records). |
| PASS |
Multiple MX records |
OK. You have multiple MX records. This means that if one is down or
unreachable, the other(s) will be able to accept mail for you. |
| PASS |
Duplicate MX records |
OK. You do not have any duplicate MX records (pointing to the same
IP). Although technically valid, duplicate MX records can cause a lot of
confusion, and waste resources. |
| PASS |
Reverse DNS entries for MX records |
OK. The IPs of all of your mail server(s) have reverse DNS (PTR)
entries. RFC1912 2.1 says you should have a reverse DNS for all your mail
servers. It is strongly urged that you have them, as many mailservers will
not accept mail from mailservers with no reverse DNS entry. Note that this
information is cached, so if you changed it recently, it will not
be reflected here (see the www.DNSstuff.com Reverse DNS Tool for
the current data). The reverse DNS entries are:
88.107.50.209.in-addr.arpa mail.dirxion.com. [TTL=3600]
52.42.210.205.in-addr.arpa smtp.easydns.com. [TTL=1200]
53.42.210.205.in-addr.arpa smtp2.easydns.com. [TTL=1200]
|
| Mail |
PASS |
Connect to mail servers |
OK: I was able to connect to all of your mailservers. |
| WARN |
Mail server host name in greeting |
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). This probably won't
cause any harm, but is 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.
smtp2.easydns.com claims to be host carnage.easydns.com [but that
host is at 205.210.42.52, not 205.210.42.53].
|
| PASS |
Acceptance of NULL <> sender |
OK: All of your mailservers accept mail from "<>". You are
required (RFC1123 5.2.9) to receive this type of mail (which includes
reject/bounce messages and return receipts). |
| PASS |
Acceptance of postmaster address |
OK: All of your mailservers accept mail to [EMAIL PROTECTED] (as
required by RFC822 6.3, RFC1123 5.2.7, and RFC2821 4.5.1). |
| PASS |
Acceptance of abuse address |
OK: All of your mailservers accept mail to [EMAIL PROTECTED] |
| INFO |
Acceptance of domain literals |
WARNING: One or more of your mailservers does not accept mail in the
domain literal format ([EMAIL PROTECTED]). Mailservers are technically
required RFC1123 5.2.17 to accept mail to domain literals for any of its
IP addresses. Not accepting domain literals can make it more difficult to
test your mailserver, and can prevent you from receiving E-mail from
people reporting problems with your mailserver. However, it is unlikely
that any problems will occur if the domain literals are not accepted
(mailservers at many common large domains have this problem).
smtp2.easydns.com's [EMAIL PROTECTED] response:
>>> RCPT TO:<[EMAIL PROTECTED]>
<<< 554 : Relay access denied
smtp.easydns.com's [EMAIL PROTECTED] response:
>>> RCPT TO:<[EMAIL PROTECTED]>
<<< 554 : Relay access denied
|
| PASS |
Open relay test |
OK: All of your mailservers appear to be closed to relaying. This is
not a thorough check, you can get a thorough one here.
mail.dirxion.com OK:
550 not local host DNSreport.com, not a gateway
smtp2.easydns.com OK:
554 :
Relay access denied
smtp.easydns.com OK: 554
: Relay
access denied
|
| WARN |
SPF record |
Your domain does not have an SPF record. This means that spammers can
easily send out E-mail that looks like it came from your domain, which can
make your domain look bad (if the recipient thinks you really sent it),
and can cost you money (when people complain to you, rather than the
spammer). You may want to add an SPF
record ASAP, as 01 Oct 2004 was the target date for domains to have
SPF records in place (Hotmail, for example, started checking SPF records
on 01 Oct 2004). |
Chris Moreland
Dirxion, LLC
636.717.2395
I seem to be bouncing email when my client sends an email
they receive an immediate response back (below) I checked the domains through
dnsstuff/report and also had my client send them an email through Yahoo! which
worked fine
Any ideas???
> RCPT TO generated following response:
> 550 Rule imposed mailbox access for xxxxxxxx@sportime.com
refused
|
