Re: [Declude.JunkMail] WHITELIST AUTH

2005-11-15 Thread Darrell \([EMAIL PROTECTED])
No you are absolutly correct - whitelist auth requires Imail version 8.x. Darrell Check out http://www.invariantsystems.com for utilities for Declude And Imail. IMail/Declude Overflow Queue Monitoring, SURBL/URI

[Declude.JunkMail] Blocking on resolved domain name

2005-11-15 Thread John Carter
I am getting a lot of spam for 64.192.25.* (which come in with constantly changing domains, but actually resolve back to outgoing.liverandcherrys.com). I am reluctant to block the whole class C, but will likely end up doing so. Is there a better way to handle this? Kind of a best practices?

Re: [Declude.JunkMail] Blocking on resolved domain name

2005-11-15 Thread Darin Cox
You could create a filter file to block REVDNS matching outgoing.liverandcherrys.com if you have Junkmail Pro, or create a simple external filter if you don't. Darin. - Original Message - From: John Carter [EMAIL PROTECTED] To: Declude.JunkMail@declude.com Sent: Tuesday, November 15,

RE: [Declude.JunkMail] Blocking on resolved domain name

2005-11-15 Thread John Carter
Ok. Haven't used REVDNS before, so didn't think of that one. Is there much CPU or network overhead in using REVDNS? Thanks, John -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darin Cox Sent: Tuesday, November 15, 2005 1:06 PM To:

Re: [Declude.JunkMail] Blocking on resolved domain name

2005-11-15 Thread Darin Cox
Nope. You're just testing the REVDNS value that has most likely already been retrieved by Declude. Darin. - Original Message - From: John Carter [EMAIL PROTECTED] To: Declude.JunkMail@declude.com Sent: Tuesday, November 15, 2005 2:11 PM Subject: RE: [Declude.JunkMail] Blocking on

Re: [Declude.JunkMail] Blocking on resolved domain name

2005-11-15 Thread Scott Fisher
I usually run the IP number through www.senderbase.org to get a feeling of the IP block. In this case: The netblock registered recently (a month ago) to a company named Direct Ventures with above average mail flowing coming from suspicious domain names. The 64.192.24.* is in the same netblock

Re: [Declude.JunkMail] Blocking on resolved domain name

2005-11-15 Thread Travis Sullivan
Sorry to chime in so late... this is what I do: I add that full class C to a weight of 80% of my hold weight... that weight, my content filters, body/subject, and combo filters take care of the rest. So, in the event a real person is sitting on that class C, their email still comes though,

Re: [Declude.JunkMail] Blocking on resolved domain name

2005-11-15 Thread Travis Sullivan
No, especially if you are using skipifweight directive for the filters. I use them for all my filters except the safe-mail filters. I use safe-mail filters to counter balance certain hosts. Travis - Original Message - From: John Carter [EMAIL PROTECTED] To:

Re: [Declude.JunkMail] Blocking on resolved domain name

2005-11-15 Thread John Carter
Thanks, Travis. Probably will use that method in the future with some other IPs. On this one as previously suggested I did set up a filter file using REVDNS 1 ENDSWITH liverandcherrys.com. Action is delete and seems to be doing a good job. Already has killed about 300 messages to some 2000

[Declude.JunkMail] CMDSPACE Failures

2005-11-15 Thread Christian Meenaghan
I love the CMDSPACE test, seems to catch a load of spammers. However, it also catches all of my clients that are using Microsoft Office Outlook. Build 11.0.5510 Is there a way i can retain the use of this test, and the weight (if possible), and not have Outlook fail the test? I mean, of

Re: [Declude.JunkMail] CMDSPACE Failures

2005-11-15 Thread Darin Cox
If MS were to fix it, we wouldn't be detecting a lot of the spam. So, while on one hand it would be nice if it were fixed... on the other hand the CMDSPACE test wouldn't be catching nearly as much. WHITELIST AUTH and custom filters to negate specific senders and servers that fail this test is