Good catch.  Thanks, John

---------- Original Message ----------------------------------
From: "Darin Cox" <[EMAIL PROTECTED]>
Reply-To: Declude.JunkMail@declude.com
Date:  Tue, 15 Nov 2005 21:20:04 -0500

>You might want to amend that to
>
>REVDNS 1 ENDSWITH .liverandcherrys.com
>
>(note the period before liverandcherrys)
>
>That way you won't be taking erroneous action against oliverandcherrys.com
>or deliverandcherrys.com.
>
>Darin.
>
>
>----- Original Message ----- 
>From: "John Carter" <[EMAIL PROTECTED]>
>To: <Declude.JunkMail@declude.com>
>Sent: Tuesday, November 15, 2005 8:59 PM
>Subject: Re: [Declude.JunkMail] Blocking on resolved domain name
>
>
>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 users.
>
>John
>
>
>---------- Original Message ----------------------------------
>From: "Travis Sullivan" <[EMAIL PROTECTED]>
>Reply-To: Declude.JunkMail@declude.com
>Date:  Tue, 15 Nov 2005 19:24:08 -0600
>
>>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, unless they are selling Viagra :)
>>
>>Travis
>>
>>----- Original Message ----- 
>>From: "John Carter" <[EMAIL PROTECTED]>
>>To: <Declude.JunkMail@declude.com>
>>Sent: Tuesday, November 15, 2005 12:51 PM
>>Subject: [Declude.JunkMail] Blocking on resolved domain name
>>
>>
>>>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"?
>>>
>>> John
>>>
>>> ---
>>> This E-mail came from the Declude.JunkMail mailing list.  To
>>> unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
>>> type "unsubscribe Declude.JunkMail".  The archives can be found
>>> at http://www.mail-archive.com.
>>>
>>>
>>
>>
>>---
>>This E-mail came from the Declude.JunkMail mailing list.  To
>>unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
>>type "unsubscribe Declude.JunkMail".  The archives can be found
>>at http://www.mail-archive.com.
>>
>
>
>---
>This E-mail came from the Declude.JunkMail mailing list.  To
>unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
>type "unsubscribe Declude.JunkMail".  The archives can be found
>at http://www.mail-archive.com.
>
>---
>This E-mail came from the Declude.JunkMail mailing list.  To
>unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
>type "unsubscribe Declude.JunkMail".  The archives can be found
>at http://www.mail-archive.com.
>
 
             
---
This E-mail came from the Declude.JunkMail mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail".  The archives can be found
at http://www.mail-archive.com.

Reply via email to