Re: Rule to detect same address in sender and receiver

2009-05-21 Thread Benny Pedersen
On Thu, May 21, 2009 07:10, LuKreme wrote: > On 8-May-2009, at 19:20, Benny Pedersen wrote: >> meta __SPF_NOT_PASS (!SPF_PASS) >> meta __NOT_LOCAL_TRUSTED (!NO_RELAYS || !ALL_TRUSTED) >> meta BLACKLIST_SPF (__SPF_NOT_PASS && __NOT_LOCAL_TRUSTED) >> describe BLACKLIST_SPF Meta: Blacklisted spf send

Re: Rule to detect same address in sender and receiver

2009-05-20 Thread LuKreme
On 8-May-2009, at 19:20, Benny Pedersen wrote: meta __SPF_NOT_PASS (!SPF_PASS) meta __NOT_LOCAL_TRUSTED (!NO_RELAYS || !ALL_TRUSTED) meta BLACKLIST_SPF (__SPF_NOT_PASS && __NOT_LOCAL_TRUSTED) describe BLACKLIST_SPF Meta: Blacklisted spf senders score BLACKLIST_SPF 5.0 meta WHITELIST_SPF (!BLACKL

Re: Rule to detect same address in sender and receiver

2009-05-08 Thread Karsten Bräckelmann
Quite late here, so my logic might be a little bit fuzzy or blurred... On Sat, 2009-05-09 at 03:20 +0200, Benny Pedersen wrote: > meta __SPF_NOT_PASS (!SPF_PASS) > meta __NOT_LOCAL_TRUSTED (!NO_RELAYS || !ALL_TRUSTED) Equivalent to ! ( NO_RELAYS && ALL_TRUSTED ) Probably not what you intended.

Re: Rule to detect same address in sender and receiver

2009-05-08 Thread Benny Pedersen
On Fri, May 8, 2009 14:47, McDonald, Dan wrote: > I would rather have: > blacklist_unless_auth @gmail.com > blacklist_unless_auth @yahoo.* meta __SPF_NOT_PASS (!SPF_PASS) meta __NOT_LOCAL_TRUSTED (!NO_RELAYS || !ALL_TRUSTED) meta BLACKLIST_SPF (__SPF_NOT_PASS && __NOT_LOCAL_TRUSTED) describe BLAC

Re: Rule to detect same address in sender and receiver

2009-05-08 Thread McDonald, Dan
On Fri, 2009-05-08 at 12:05 +0200, Benny Pedersen wrote: > On Thu, May 7, 2009 14:11, Matus UHLAR - fantomas wrote: > > On 07.05.09 03:59, jida...@jidanni.org wrote: > >> Ah ha, you can use something like > > > >> header FROM_SAME_AS_TO ALL=~/\nFrom: ([^\n]+)\n.*To: \1/sm > >> > add spf to your dom

Re: Rule to detect same address in sender and receiver

2009-05-08 Thread Benny Pedersen
On Thu, May 7, 2009 14:11, Matus UHLAR - fantomas wrote: > On 07.05.09 03:59, jida...@jidanni.org wrote: >> Ah ha, you can use something like > >> header FROM_SAME_AS_TO ALL=~/\nFrom: ([^\n]+)\n.*To: \1/sm >> > add spf to your domain >> But see e.g., http://david.woodhou.se/why-not-spf.html > > di

Re: Rule to detect same address in sender and receiver

2009-05-08 Thread Benny Pedersen
On Wed, May 6, 2009 21:59, jida...@jidanni.org wrote: > Ah ha, you can use something like > header FROM_SAME_AS_TO ALL=~/\nFrom: ([^\n]+)\n.*To: \1/sm nice rule, but its not the envelope >> add spf to your domain > But see e.g., http://david.woodhou.se/why-not-spf.html why-spf.html -- http:/

Re: Rule to detect same address in sender and receiver

2009-05-07 Thread Matus UHLAR - fantomas
On 07.05.09 03:59, jida...@jidanni.org wrote: > Ah ha, you can use something like > header FROM_SAME_AS_TO ALL=~/\nFrom: ([^\n]+)\n.*To: \1/sm > > add spf to your domain > But see e.g., http://david.woodhou.se/why-not-spf.html did I misread ot does the person blame SRS first and then reports he u

Re: Rule to detect same address in sender and receiver

2009-05-06 Thread jidanni
Ah ha, you can use something like header FROM_SAME_AS_TO ALL=~/\nFrom: ([^\n]+)\n.*To: \1/sm > add spf to your domain But see e.g., http://david.woodhou.se/why-not-spf.html

Re: Rule to detect same address in sender and receiver

2009-05-05 Thread Benny Pedersen
On Tue, May 5, 2009 16:30, vism...@email.it wrote: > I am in troubles with spam filtering via SpamAssassin; I have many many > many spam mails with the same sender and receiver, but I can't > understand which rule of SpamAssassin is right to block this mails. > > Someone has an idea? add spf to y

Rule to detect same address in sender and receiver

2009-05-05 Thread vismara
Hello, I am in troubles with spam filtering via SpamAssassin; I have many many many spam mails with the same sender and receiver, but I can't understand which rule of SpamAssassin is right to block this mails. Someone has an idea? Thank you in advance! Regards -- Caselle da 1GB, trasmetti al