Check valid MX record on receive |
Post Reply 
|
Page <12 |
| Author | |
Clator 
Guest Group 
|
 Post Options
 Thanks(0)
 Quote Reply
 Posted: 03 March 2006 at 10:35am |
|
Just upgraded to .532 and have gotten a couple more false positives as described above. The cox.net address in particular.
|
|
 |
|
|
LogSat
Admin Group 
Joined: 25 January 2005 Location: United States Status: Offline Points: 4104 |
Post Options
Thanks(0)
Quote Reply
Posted: 03 March 2006 at 4:15pm |
|
Clator,
Can you post (or email us) the SpamFilter's logfile entries that show these false positives? We'll need to see the log to find out what is happening. |
|
|
|
|
dcook
Senior Member 
Joined: 31 January 2005 Location: United States Status: Offline Points: 174 |
Post Options
Thanks(0)
Quote Reply
Posted: 03 March 2006 at 6:03pm |
|
I am currently having success with the following maps setting:
sbl-xbl.spamhaus.org, true combined.njabl.org, true bl.spamcop.net, true block.rhs.mailpolice.com, true dul.dnsbl.sorbs.net, true tanks alot |
|
|
Dwight
www.vividmix.com |
|
|
|
|
WebGuyz
Senior Member
Joined: 09 May 2005 Location: United States Status: Offline Points: 348 |
Post Options
Thanks(0)
Quote Reply
Posted: 03 March 2006 at 6:24pm |
Same here. Did you delete your Bayes Corpus and let it grow again or just leave it be after you dropped SORB? The Bayes catch rate is great now but maybe a little too sensitive, still trying to figure out. |
|
|
http://www.webguyz.net
|
|
|
|
|
Clator
Guest Group
|
Post Options
Thanks(0)
Quote Reply
Posted: 07 March 2006 at 2:19pm |
|
Posted these in the wrong thread. They should go here. Per Dan's suggestion, Ive created a new corpus directory. Meanwhile some of the domains that are failing MX checks are elon.edu, aapa.org, and gci.net. Sorry I don't have the full headers at the moment. I went ahead and forced the messages through. Some more potential false positives ... Received: from 205.188.139.137 by clator.com (LogSat Software SMTP Server - Unlicensed Evaluation Copy) Tue, 7 Mar 2006 08:01:11 -0500
Joined: 25 January 2005 ------------------------------------------------------------ -------------------- and another ... personall details removed again to keep the bots from picking it up. Received: from 204.127.192.82 by clator.com (LogSat Software SMTP Server - Unlicensed Evaluation Copy) Mon, 6 Mar 2006 19:34:08 -0500
Received: from 207.171.160.42 by clator.com (LogSat Software SMTP Server - Unlicensed Evaluation Copy) Tue, 7 Mar 2006 13:33:57 -0500
Received: from 64.236.240.147 by clator.com (LogSat Software SMTP Server - Unlicensed Evaluation Copy) Tue, 7 Mar 2006 13:52:01 -0500
a legit one from turner.com ... Received: from 64.236.240.147 by clator.com (LogSat Software SMTP Server - Unlicensed Evaluation Copy) Tue, 7 Mar 2006 13:52:01 -0500
Hopefully these will point to some issues. In case it hasn't been said, thanks for any help you can provide. Received: from 68.230.240.34 by clator.com (LogSat Software SMTP Server - Unlicensed Evaluation Copy) Tue, 7 Mar 2006 13:56:40 -0500 |
|
|
|
|
LogSat
Admin Group
Joined: 25 January 2005 Location: United States Status: Offline Points: 4104 |
Post Options
Thanks(0)
Quote Reply
Posted: 07 March 2006 at 4:06pm |
|
Clator,
We'll need to see SpamFilter's activity logfiles showing those emails, as in the logs will be reported the reason for the failure, and we need to cross-reference with the emails themselves you just posted. |
|
|
|
|
Clator
Guest Group
|
Post Options
Thanks(0)
Quote Reply
Posted: 07 March 2006 at 5:10pm |
|
Sure thing. Is there an email address I should just send the logs to? I can send them unaltered that way. (No bots to pick up the various addresses and whatnot). Thanks. |
|
|
|
|
LogSat
Admin Group
Joined: 25 January 2005 Location: United States Status: Offline Points: 4104 |
Post Options
Thanks(0)
Quote Reply
Posted: 07 March 2006 at 8:10pm |
|
Clator,
Your logs still show the DNS disconnecting SpamFilter when queries are made: 03/07/06 08:01:11:368 -- (404) Resolving 205.188.139.137 - Error resolving IP address (Socket Error # 10054 Connection reset by peer.) 03/07/06 08:01:11:368 -- (404) - Invalid MX record - Socket Error # 10054 Connection reset by peer. We thought we had modified the MX filter so that forceful disconnects from the DNS server that would cause MX lookups to fail would not cause the filter to fail. Apparently your case is slightly different,and our workaround does not work. We'll try to replicate the problem and ignore the error you are receiving as well. In the meantime, you may want to check the connection to your DNS server to see if you can find out why it fails every now and then. |
|
|
|
|
LogSat
Admin Group
Joined: 25 January 2005 Location: United States Status: Offline Points: 4104 |
Post Options
Thanks(0)
Quote Reply
Posted: 07 March 2006 at 9:36pm |
|
We've uploaded build 2.7.1.535 in the registered user area. The release notes are as follows:
// New to VersionNumber = '2.7.1.535'; {TODO -cFix : Sometimes Socket Errors on MX test could cause rejects (catches more cases than in build 531)} {TODO -cNew : Changed the precedence for the :tag and :tagsubject modifiers for the Unfiltered Emails} {TODO -cFix : DoNotStartWithoutAV option in SpamFilter.ini file not working correctly} |
|
|
|
|
Clator
Guest Group
|
Post Options
Thanks(0)
Quote Reply
Posted: 10 March 2006 at 10:05am |
|
Thanks again. I've discovered an internal 10. address where my server is hosted that may prove more reliable for DNS than the current IP. Hopefully this'll do it.
|
|
|
|
Topic Options
Desperado wrote:|
Post Reply
|
Page <12 |
Tweet
|
| Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |
This page was generated in 0.295 seconds.