thanks for your help, i'm trying to get filters working now,  
and thanks for list subjects. 
bbxrider


Kris Deugau wrote:
> 
> bbxrider wrote:
>> yes, but..........................
>> i have a spam filter on my client, spambayes, and it works fine to sort
>> out
>> spam sent
>> to a 'real' account
>> the problem here is numbers, the spammer is spoofing my domain with a
>> constantly changing
>> name (but with a constant piece of it)  with dozens if not hundreds a
>> day,
>> are coming back to my domain pop3 with invalid address messages, i don't
>> want to deal with those and besides its further clogging the pipes with
>> messages being sent to me that are unnecessary, so my hunt continues to
>> determine a way
>> to have spam assassin handle it at my pop3, sitelutions.com, since they
>> don't seem to have
>> another way to handle it. 
>>  thanks bbxrider
> 
> You might want to lean on your provider a little to allow you to 
> *disable* the catchall email processing;  that's a big part of your
> problem.
> 
> That said, a quick and dirty method to brute-force SA into doing 
> something it's really not designed for could look like this:
> 
> header TO_VALID       ToCC =~ /(good1|good2|good3)[EMAIL PROTECTED]/
> describe TO_VALID     My valid accounts
> score TO_VALID        -5
> 
> header TO_INVALID     ToCC =~ /[EMAIL PROTECTED]/
> describe TO_INVALID   Everything is bad, unless it's good
> score TO_INVALID      5
> 
> Adjust efficiency, accuracy, score levels to taste.
> 
> This type of "identify the real valid accounts" processing belongs in 
> the MTA or at least whatever hands off processing to SA - if you've got 
> access to procmail, for instance, you can set up a fairly simple recipe 
> to only deliver mail addressed to a valid account at your domain.
> 
> Note that you'll have to create exceptions for things like, oh, say, 
> this list, because such messages are usually sent "to" the list, not 
> your account.  This applies to pretty much any method not working at the 
> MTA level.
> 
> -kgd
> 
> 

-- 
View this message in context: 
http://www.nabble.com/use-of-*-and---in-blacklist_from-tf3874156.html#a11017078
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.

Reply via email to