got better keeping the original version, only using de meta test... (without blacklist_fom .... )
header __FROM_DOMAIN From =~ /some\.com/i header __FROM_DOMAIN_TO To =~ /myuser\@mydomain\.com/i meta FROM_DOMAIN_IN_BLACKLIST (__FROM_DOMAIN && ! __FROM_DOMAIN_TO) score FROM_DOMAIN_IN_BLACKLIST 100 Em 08-02-2012 18:56, Rejaine Monteiro escreveu: > solved.. (maybe, I will do more tests ...) > > I made this way: > > blacklist_from @domain.com > > and then, i create a meta test , like this: > > header __FROM_BADDOMAIN From =~ /some\.com/i > header __FROM_BADDOMAIN_GOOD_TO To =~ /myser\@mydomain\.com/i > meta FROM_BADDOMAIN_UNBLACKLIST_TO (__FROM_BADDOMAIN && > __FROM_BADDOMAIN_GOOD_TO) > score FROM_BADDOMAIN_UNBLACKLIST_TO -100 > > (tips obtained in > http://markmail.org/message/7dz5ez2en442n6t5#query:+page:1+mid:ydrr57kl2msbprcc+state:results) > > > > > > > > > > Em 08-02-2012 18:38, Bowie Bailey escreveu: > >> On 2/8/2012 3:07 PM, Rejaine Monteiro wrote: >> >> >>> It's not exactly what I need ... I'll try to be clearer (sorry by poor >>> english) >>> >>> I need something like this: blacklist a entire @somedomain but accept >>> when the *recipient * (not the sender) is certain user of *my* domain >>> >>> Or ... blacklist_from *@somedomain.com except when destination is >>> myuser@mydomain >>> >>> i tried this: >>> >>> blacklist_from *@somedomain.com >>> whitelist_to [email protected] >>> >>> I tried this but it didn't work (for obvious reasons): >>> >>> content analysis details: (98 points, 5.0 required) >>> pts rule name description >>> ---- ---------------------- >>> -------------------------------------------------- >>> 100 USER_IN_BLACKLIST From: address is in the user's black-list >>> -6.0 USER_IN_WHITELIST_TO User is listed in 'whitelist_to' >>> >>> >> You could use blacklist_from in the main config and then in the >> user_prefs use unblacklist_from to override it for this particular user. >> >> >>
