At 09:10 AM 02/21/2003, you wrote:
Well I sent a post while back on this and noone got it or at the time didn't
think of it as a of any use..
But as far as im concerned if they get blacklisted you should never see them
again.
That is the point of a blacklist...
I tried working something like this i
Maybe I missed it in the docs, but I would like to see an
include directive available to the user_prefs file.
This would help me (maybe others) put some more automation into
black/whitelist management.
e.g.
include "/home/bilbo/.spamassassin/badboys.lst"
--
Regards
Cliff Sarginson
The
Greg Cirino said:
> We do the same thing with a similar setup, increased
> the value of username to varchar(100)
> and it works just fine.
>
> I have the same username on 3 different domains and
> all have separate prefs.
Would it be worthwhile modifying the README appropriately? Sounds like
I would like to request a feature in the next development cycle, that feature being
support for multi-hosting in SQL prefs, ie [EMAIL PROTECTED] and [EMAIL PROTECTED] are
different users and need different prefs.
thanks
---
This SF.net email
Daniel Quinlan said:
> > I'd really like to see a blacklist_to option somewhere, or some other
> > way of automatically tagging a given destination as indicating 99.99%
> > probable spam.
>
> Here's what I do:
>
> header LOCAL_BAD_ADDRESSEnvelope-To =~ /foo\@bar\.com/i
> describe LOCAL_
"Rob MacGregor" <[EMAIL PROTECTED]> writes:
> I'd really like to see a blacklist_to option somewhere, or some other
> way of automatically tagging a given destination as indicating 99.99%
> probable spam.
>
> Basically, I've got an email address that I have to have to host some
> web pages on my
I'd really like to see a blacklist_to option somewhere, or some other way of
automatically tagging a given destination as indicating 99.99% probable
spam.
Basically, I've got an email address that I have to have to host some web
pages on my ISP. The email address is linked directly to the name
