I believe I had read the first.  I'm not sure about the second.  I have 
now read them again.  I'm see some applicability, but not really 
enough.  (I admit that the imperfection is mine.)

I suppose that I could go through the various senders of email that I 
receive and change them to tagged addresses, but it seems a hassle for 
me and others who I am managing.

What is really key do me here is that some application along the chain 
of email processing has verified that I received an email with a valid 
domain key signature.  I really want to believe that I haven't been 
spoofed if the email message has the valid signature.

*IF* I could get spamassisn to change from the prefered (default) 
behavior and munge the email by adding an extra header then I could 
simply do a header filter test on that.  This would be irrespective of 
the domain that the email came from.

If I started seeing a lot of domain key signed spam, I would then have 
to add a blacklist for them, BUT, I would worry about domain signed 
spam for domains that were VERY short lived.

This would then lead me back to wanting to perform more than one test - 
test for domain, then test for key.

Am I being particulaly unclear this morning?  Perhaps I should go eat.

On 2006-10-04 09:35:11 -0700, [EMAIL PROTECTED] (Jason R. Mastaler) said:

> Anthony Ercolano <[EMAIL PROTECTED]> writes:
> 
>> Suppose that I could get spamassassin to add a header that states that 
>> the email passed domain keys verification.
>> 
>> Is there any way that I could then have tmda somehow do:
>> 
>> Is the from address domain <SOME DOMAIN SPECIFICATION>?
>> No? Fall through to rest of incomng filters.
>> Yes, Is the header that spamassassin added present?
>> No? Drop the mail.
>> Yes? Deliver to maildir.
>> 
>> This would help block spoof of ebay, google, or paypal (which all seem 
>> to be sending with domain key signatures.)
>> 
>> I wondered if using the pipe source might be the way to go, but I would 
>> have to do a lot of the header processing myself.  Is there 
>> documentation on the tmda ABI?
> 
> Have you seen these?
> 
> http://wiki.tmda.net/SpamAssassin
> 
> http://wiki.tmda.net/TmdaFaq?highlight=%28Assassin%29#head-4e7eeaba7c360e034bbc37f5135d5035633fb6e2

 
> 


_____________________________________________
tmda-users mailing list (tmda-users@tmda.net)
http://tmda.net/lists/listinfo/tmda-users

Reply via email to