It appears that I may be, at least on occasion, having the following
problem that Eric discovered here:

http://comments.gmane.org/gmane.mail.spam.spamdyke.user/3106

Today it is affecting google's gmail servers:

2011-04-28 12:23:13.290273500 spamdyke[11358]: ERROR: DNS response for
adaxa.com: expected type MX, A, CNAME but received type (unknown)
2011-04-28 12:23:13.290860500 spamdyke[11358]: FILTER_SENDER_NO_MX domain:
adaxa.com
2011-04-28 12:23:13.826486500 spamdyke[11358]: DENIED_SENDER_NO_MX from:
[email protected] to: [email protected] origin_ip:
209.85.212.43 origin_rdns: mail-vw0-f43.google.com auth: (unknown)
encryption: TLS
2011-04-28 12:24:15.335562500 spamdyke[11358]: TIMEOUT from:
[email protected] to: [email protected] origin_ip:
209.85.212.43 origin_rdns: mail-vw0-f43.google.com auth: (unknown)
encryption: TLS reason: TIMEOUT


On the particular server that's having this trouble, I'm running spamdyke
4.1.0.

It appears from the above that this trouble was discovered after the
release of the current 4.2.0 version (release Feb 11) of spamdyke.

Does anyone know if this also affects version 4.1.0, and if so, how to
bypass this without compromising security until a corrective update is
released?

It's definitely not affecting the 4.0.10 version of spamdyke that I have
running on another qmailtoaster server as the mx lookups for the above
domain are having no trouble there.

Thanks,
-- 
Tim Pleiman
Bravo Systems Technologies
"Advanced Open Source Solutions for Business"
Chicago, IL USA


---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
    Vickers Consulting Group offers Qmailtoaster support and installations.
      If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
     Please visit qmailtoaster.com for the latest news, updates, and packages.
     
      To unsubscribe, e-mail: [email protected]
     For additional commands, e-mail: [email protected]


Reply via email to