2. You don't have proper reverse DNS: adsl-66-143-181-9.dsl.austtx.swbell.net
Where's the RFC stating that this is invalid? AFAIK it is perfectly acceptable for forward and reverse DNS to mismatch if there are multiple names associated with a given IP.. in fact, this is very common in web-server farms were 200+ domains all live on the same server.
3. Your domain does not exist; DNS lookup of "cynistar.net" gives "Non-existent host/domain"
I believe that's only because you were attempting to look up an A record, instead of an MX record, like you should.
try dig mx cynistar.net instead. I get 3 valid mail exchangers.
It should be noted that as per RFC standards, it is preferred that mailing domains have MX records, and that using an A record is acceptable, but not the "true proper way". All mail exchangers MUST attempt MX resolution before trying A record resolution, and MUST only try to use the A record if no MX is found.
Associating an A record with the root of a domain with no host name specified is common practice, but is not a requirement of RFCs.
4. DNS exist for your subdomain "soyokaze.cynistar.net", but we cannot see how you are introducing yourself, because those lines from the log are missing.
That's not a subdomain, its a single host... It has an A record, and no MX record. It is also the authoritative nameserver for the cynistar.net domain, thus it cannot be a subdomain.
------------------------------------------------------- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
