Hi,
has Symantecs some problems? Currently the MX of securityfocus.com is
completly broken. Take care of restricted postfix installations which are
configured to block senders if MX is not resolvable:
Feb 24 07:59:23 **** postfix/smtpd[***]: ****: reject: RCPT from
unknown[205.206.231.26]: 550
<[EMAIL PROTECTED]>: Sender
address rejected: Domain not found;
from=<[EMAIL PROTECTED]>
to=<[EMAIL PROTECTED]> proto=ESMTP helo=<outgoing.securityfocus.com>
Note also that the mailhost has currently no PTR for it's IPv4 address -
not very professional....
$ host -t NS securityfocus.com
securityfocus.com name server ns1.symantec.com.
securityfocus.com name server ns1.securityfocus.com.
securityfocus.com name server ns2.securityfocus.com.
securityfocus.com name server ns3.symantec.com.
$ host -t MX securityfocus.com ns1.symantec.com.
Using domain server:
Name: ns1.symantec.com.
Address: 198.6.49.5#53
Aliases:
$ host -t MX securityfocus.com ns1.securityfocus.com.
host: Couldn't find server 'ns1.securityfocus.com.': Name or service not
known
$ host -t MX securityfocus.com ns2.securityfocus.com.
host: Couldn't find server 'ns2.securityfocus.com.': Name or service not
known
$ host -t MX securityfocus.com ns3.symantec.com.
Using domain server:
Name: ns3.symantec.com.
Address: 206.204.212.86#53
Aliases:
2 of 4 specified NS servers have currently no A records...
...ohoh...
Peter
--
Dr. Peter Bieringer http://www.bieringer.de/pb/
GPG/PGP Key 0x958F422D mailto: pb at bieringer dot de
Deep Space 6 Co-Founder and Core Member http://www.deepspace6.net/
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html
