user_prefs won't work for me, because my server only filters messages
and then redirects them to an internal server (so I don't have mailboxes
here)
. one solution that I posted it seemed to work fine. may not the better
solution but this ok for what we need
Em 09-02-2012 19:12, Benny Pedersen e
Den 2012-02-09 17:59, Bowie Bailey skrev:
It may work, but it solves the wrong problem. The problem is to
blacklist the entire domain, but allow it through for one RECIPIENT.
in that case it needs to be solved with a plugin or outside of
spamassassin, if user_prefs is with more then one user
On 2/8/2012 6:53 PM, Benny Pedersen wrote:
> Den 2012-02-08 21:07, Rejaine Monteiro skrev:
>> blacklist_from *@somedomain.com
>> whitelist_to myu...@mydomain.com
> when you use blacklist_from you must use unblacklist_from not
> whitelist_to
>
> perldoc Mail::SpamAssassin::Conf
>
> everyone can wri
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
not solved it blocks usernames some.com
add :addr after From a
Den 2012-02-08 21:07, Rejaine Monteiro skrev:
blacklist_from *@somedomain.com
whitelist_to myu...@mydomain.com
when you use blacklist_from you must use unblacklist_from not
whitelist_to
perldoc Mail::SpamAssassin::Conf
everyone can write email to a to addr and thus the whitelist is not
wor
On 2/8/2012 3:56 PM, Rejaine Monteiro wrote:
> 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\@mydom
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
On Wed, 2012-02-08 at 18:07 -0200, 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
>
I
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_BADDOMA
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 ... blacklis
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
myuse
On Thu, 02 Feb 2012 16:51:51 -0200, Rejaine Monteiro wrote:
Example: blacklist_from @orig.com except when rcpt_to is
myb...@mydomain.com
freemail_domain example.org
freemail_whitelist non-spam-u...@example.org
untested, but its what i think is the nearest to what you asked
Am 02.02.2012 19:51, schrieb Rejaine Monteiro:
> Hi list,
>
> Is there any way to block an entire domain, except for a particular
> recipient?
> Example: blacklist_from @orig.com except when rcpt_to is
> myb...@mydomain.com
without read the faqs again
blacklist the domain, and whitelist one rec
Hi list,
Is there any way to block an entire domain, except for a particular
recipient?
Example: blacklist_from @orig.com except when rcpt_to is
myb...@mydomain.com
14 matches
Mail list logo