On 4/3/10 8:09 AM, "Alex" wrote:
> Hi,
>
>> I¹m building a new 3.3.1 SpamAssassin box from scratch, and ran into a small
>> problem when I ran lint:
>> $ spamassassin --lint
>> Apr 2 11:24:05.923 [22379] warn: plugin: failed to create instance of
>> plugin Mail::SpamAssassin::Plugin::EmailBL.p
On Monday April 5 2010 13:01:40 Daniel McDonald wrote:
> I'm building a new 3.3.1 SpamAssassin box from scratch, and ran into a
> small problem when I ran lint:
> $ spamassassin --lint
> Apr 2 11:24:05.923 [22379] warn: plugin: failed to create instance of
> plugin Mail::SpamAssassin::Plugin::Emai
On 4/5/10 6:53 AM, "Mark Martinec" wrote:
> On Monday April 5 2010 13:01:40 Daniel McDonald wrote:
>> I'm building a new 3.3.1 SpamAssassin box from scratch, and ran into a
>> small problem when I ran lint:
>> $ spamassassin --lint
>> Apr 2 11:24:05.923 [22379] warn: plugin: failed to create ins
Dear All,
I have Mail Filtration Gateway for our company. We have put filtration on 5
domain and 2 sub domains. So now, abc.com domain want mails from
@yahoo.comand another,
xyz.com do not want. So is there any facility to do domain level
blacklist/whitelist filtration via Spamassassin?
I am usin
Royce Williams wrote:
What is the optimal configuration (local.cf or other) for an ISP's
MSAs to prevent unauthenticated dynamic-IP customers from triggering
dynamic tests, but still benefiting from general filtering?
I was hoping for a magical 'mua_networks' option, which let me
enumerate the I
Hi John*
>> I have to ask, is your mail really so time-critical that you're not
willing to wait two minutes for spamd do to its job?
*
No reason really, initially it was set to the default (300secs) which I
thought was what was causing the errors in the logs.
I've set it to 60secs just as a test t
