Re: Spamassassin not working after update of Perl

[Jos Chrispijn]

So true. I have processed as you suggested and will follow that + the 
UPDATING suggestion as well in future.
Just got on wrong track that this scenario should be used with 5.14 to 
5.14.x as well.


FYI:
After running

sa-update -D
sa-update --nogpg
spamassassin --lint -D
freshclam

I got at the end a warning, saying:
warn: Use of uninitialized value $opt{"syslog-socket"} in lc at 
/usr/local/bin/spamd line 44


Found out that this is a minor thing and fixed *in* 3.3.2 and *in* trunk.

BR,
Jos Chrispijn

Damien Fleuriot:

Normally, any special care to be taken while upgrading your port should
be noted in UPDATING.

However, it's always prudent to rebuild dependencies when upgrading a
port, because you never know what changed (unless you take the time to
check the changelog + source code).


On 6/24/11 12:33 PM, Jos Chrispijn wrote:

Hi Damien,

What I don't understand is that if I already are on 15.4 and there is an
update to 15.4.1 I have to perform always a 'portupgrade -fr perl' to
have this work?
Normally this only goes for 15.3 to 15.4 (full version upgrade) or do I
miss something here?

Thanks for your help
Jos Chrispijn

Damien Fleuriot:

On 6/23/11 3:51 PM, Jos Chrispijn wrote:

I have updated my Perl version yesterday but now my Spamd doesn't work
anymore.
Can someone hint me how to solve this?

thanks,
Jos Chrispijn

Pls see output:

Can't locate Net/DNS.pm in @INC (@INC contains:
/usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
/usr/local/lib/perl5/site_perl/5.14.1/mach
/usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
/usr/local/lib/perl5/5.14.1) at /usr/local/bin/sa-update line 80.
BEGIN failed--compilation aborted at /usr/local/bin/sa-update line 80.

Can't locate Net/DNS.pm in @INC (@INC contains:
/usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
/usr/local/lib/perl5/site_perl/5.14.1/mach
/usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
/usr/local/lib/perl5/5.14.1) at /usr/local/bin/sa-update line 80.
BEGIN failed--compilation aborted at /usr/local/bin/sa-update line 80.

Can't locate NetAddr/IP.pm in @INC (@INC contains:
/usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
/usr/local/lib/perl5/site_perl/5.14.1/mach
/usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
/usr/local/lib/perl5/5.14.1) at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm
line 25.

BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm
line 25.
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86.
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71.
Compilation failed in require at /usr/local/bin/spamassassin line 80.
BEGIN failed--compilation aborted at /usr/local/bin/spamassassin line
80.
ClamAV update process started at Thu Jun 23 15:43:00 2011
main.cld is up to date (version: 53, sigs: 846214, f-level: 53, builder:
sven)
daily.cld is up to date (version: 13231, sigs: 130699, f-level: 60,
builder: arnaud)
bytecode.cld is up to date (version: 143, sigs: 40, f-level: 60,
builder: edwin)
spamd not running? (check /var/run/spamd/spamd.pid).
Starting spamd.

Can't locate NetAddr/IP.pm in @INC (@INC contains:
/usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
/usr/local/lib/perl5/site_perl/5.14.1/mach
/usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
/usr/local/lib/perl5/5.14.1) at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm
line 25.

BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm
line 25.
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86.
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71.
Compilation failed in require at /usr/local/bin/spamd line 85.
BEGIN failed--compilation aborted at /usr/local/bin/spamd line 85.

Can't locate NetAddr/IP.pm in @INC (@INC contains:
/usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
/usr/local/lib/perl5/site_perl/5.14.1/mach
/usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
/usr/local/lib/perl5/5.14.1) at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm
line 25.

BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm
line 25.
Compilation failed i

Re: Spamassassin not working after update of Perl

[Jos Chrispijn]

So true. I have processed as you suggested and will follow that + the 
UPDATING suggestion as well in future.
Just got on wrong track that this scenario should be used with 5.14 to 
5.14.x as well.


FYI:
After running

sa-update -D
sa-update --nogpg
spamassassin --lint -D
freshclam

I got at the end a warning, saying:
warn: Use of uninitialized value $opt{"syslog-socket"} in lc at 
/usr/local/bin/spamd line 44


Found out that this is a minor thing and fixed *in* 3.3.2 and *in* trunk.

BR,
Jos Chrispijn

Damien Fleuriot:

Normally, any special care to be taken while upgrading your port should
be noted in UPDATING.

However, it's always prudent to rebuild dependencies when upgrading a
port, because you never know what changed (unless you take the time to
check the changelog + source code).


On 6/24/11 12:33 PM, Jos Chrispijn wrote:

Hi Damien,

What I don't understand is that if I already are on 15.4 and there is an
update to 15.4.1 I have to perform always a 'portupgrade -fr perl' to
have this work?
Normally this only goes for 15.3 to 15.4 (full version upgrade) or do I
miss something here?

Thanks for your help
Jos Chrispijn

Damien Fleuriot:

On 6/23/11 3:51 PM, Jos Chrispijn wrote:

I have updated my Perl version yesterday but now my Spamd doesn't work
anymore.
Can someone hint me how to solve this?

thanks,
Jos Chrispijn

Pls see output:

Can't locate Net/DNS.pm in @INC (@INC contains:
/usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
/usr/local/lib/perl5/site_perl/5.14.1/mach
/usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
/usr/local/lib/perl5/5.14.1) at /usr/local/bin/sa-update line 80.
BEGIN failed--compilation aborted at /usr/local/bin/sa-update line 80.

Can't locate Net/DNS.pm in @INC (@INC contains:
/usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
/usr/local/lib/perl5/site_perl/5.14.1/mach
/usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
/usr/local/lib/perl5/5.14.1) at /usr/local/bin/sa-update line 80.
BEGIN failed--compilation aborted at /usr/local/bin/sa-update line 80.

Can't locate NetAddr/IP.pm in @INC (@INC contains:
/usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
/usr/local/lib/perl5/site_perl/5.14.1/mach
/usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
/usr/local/lib/perl5/5.14.1) at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm
line 25.

BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm
line 25.
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86.
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71.
Compilation failed in require at /usr/local/bin/spamassassin line 80.
BEGIN failed--compilation aborted at /usr/local/bin/spamassassin line
80.
ClamAV update process started at Thu Jun 23 15:43:00 2011
main.cld is up to date (version: 53, sigs: 846214, f-level: 53, builder:
sven)
daily.cld is up to date (version: 13231, sigs: 130699, f-level: 60,
builder: arnaud)
bytecode.cld is up to date (version: 143, sigs: 40, f-level: 60,
builder: edwin)
spamd not running? (check /var/run/spamd/spamd.pid).
Starting spamd.

Can't locate NetAddr/IP.pm in @INC (@INC contains:
/usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
/usr/local/lib/perl5/site_perl/5.14.1/mach
/usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
/usr/local/lib/perl5/5.14.1) at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm
line 25.

BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm
line 25.
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86.
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71.
Compilation failed in require at /usr/local/bin/spamd line 85.
BEGIN failed--compilation aborted at /usr/local/bin/spamd line 85.

Can't locate NetAddr/IP.pm in @INC (@INC contains:
/usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
/usr/local/lib/perl5/site_perl/5.14.1/mach
/usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
/usr/local/lib/perl5/5.14.1) at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm
line 25.

BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm
line 25.
Compilation failed i

Re: Spamassassin not working after update of Perl

[Damien Fleuriot]

Normally, any special care to be taken while upgrading your port should
be noted in UPDATING.

However, it's always prudent to rebuild dependencies when upgrading a
port, because you never know what changed (unless you take the time to
check the changelog + source code).


On 6/24/11 12:33 PM, Jos Chrispijn wrote:
> Hi Damien,
> 
> What I don't understand is that if I already are on 15.4 and there is an
> update to 15.4.1 I have to perform always a 'portupgrade -fr perl' to
> have this work?
> Normally this only goes for 15.3 to 15.4 (full version upgrade) or do I
> miss something here?
> 
> Thanks for your help
> Jos Chrispijn
> 
> Damien Fleuriot:
>> On 6/23/11 3:51 PM, Jos Chrispijn wrote:
>>> I have updated my Perl version yesterday but now my Spamd doesn't work
>>> anymore.
>>> Can someone hint me how to solve this?
>>>
>>> thanks,
>>> Jos Chrispijn
>>>
>>> Pls see output:
>>>
>>> Can't locate Net/DNS.pm in @INC (@INC contains:
>>> /usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
>>> /usr/local/lib/perl5/site_perl/5.14.1/mach
>>> /usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
>>> /usr/local/lib/perl5/5.14.1) at /usr/local/bin/sa-update line 80.
>>> BEGIN failed--compilation aborted at /usr/local/bin/sa-update line 80.
>>>
>>> Can't locate Net/DNS.pm in @INC (@INC contains:
>>> /usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
>>> /usr/local/lib/perl5/site_perl/5.14.1/mach
>>> /usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
>>> /usr/local/lib/perl5/5.14.1) at /usr/local/bin/sa-update line 80.
>>> BEGIN failed--compilation aborted at /usr/local/bin/sa-update line 80.
>>>
>>> Can't locate NetAddr/IP.pm in @INC (@INC contains:
>>> /usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
>>> /usr/local/lib/perl5/site_perl/5.14.1/mach
>>> /usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
>>> /usr/local/lib/perl5/5.14.1) at
>>> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm
>>> line 25.
>>>
>>> BEGIN failed--compilation aborted at
>>> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm
>>> line 25.
>>> Compilation failed in require at
>>> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86.
>>> BEGIN failed--compilation aborted at
>>> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86.
>>> Compilation failed in require at
>>> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71.
>>> BEGIN failed--compilation aborted at
>>> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71.
>>> Compilation failed in require at /usr/local/bin/spamassassin line 80.
>>> BEGIN failed--compilation aborted at /usr/local/bin/spamassassin line
>>> 80.
>>> ClamAV update process started at Thu Jun 23 15:43:00 2011
>>> main.cld is up to date (version: 53, sigs: 846214, f-level: 53, builder:
>>> sven)
>>> daily.cld is up to date (version: 13231, sigs: 130699, f-level: 60,
>>> builder: arnaud)
>>> bytecode.cld is up to date (version: 143, sigs: 40, f-level: 60,
>>> builder: edwin)
>>> spamd not running? (check /var/run/spamd/spamd.pid).
>>> Starting spamd.
>>>
>>> Can't locate NetAddr/IP.pm in @INC (@INC contains:
>>> /usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
>>> /usr/local/lib/perl5/site_perl/5.14.1/mach
>>> /usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
>>> /usr/local/lib/perl5/5.14.1) at
>>> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm
>>> line 25.
>>>
>>> BEGIN failed--compilation aborted at
>>> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm
>>> line 25.
>>> Compilation failed in require at
>>> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86.
>>> BEGIN failed--compilation aborted at
>>> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86.
>>> Compilation failed in require at
>>> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71.
>>> BEGIN failed--compilation aborted at
>>> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71.
>>> Compilation failed in require at /usr/local/bin/spamd line 85.
>>> BEGIN failed--compilation aborted at /usr/local/bin/spamd line 85.
>>>
>>> Can't locate NetAddr/IP.pm in @INC (@INC contains:
>>> /usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
>>> /usr/local/lib/perl5/site_perl/5.14.1/mach
>>> /usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
>>> /usr/local/lib/perl5/5.14.1) at
>>> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm
>>> line 25.
>>>
>>> BEGIN failed--compilation aborted at
>>> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm
>>> line 25.
>>> Compilation failed in require at
>>> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86.
>>> BEGIN failed--compilation aborted at
>>> /usr/local/lib/perl5/sit

Re: Spamassassin not working after update of Perl

[Jos Chrispijn]

Hi Damien,

What I don't understand is that if I already are on 15.4 and there is an 
update to 15.4.1 I have to perform always a 'portupgrade -fr perl' to 
have this work?
Normally this only goes for 15.3 to 15.4 (full version upgrade) or do I 
miss something here?


Thanks for your help
Jos Chrispijn

Damien Fleuriot:

On 6/23/11 3:51 PM, Jos Chrispijn wrote:

I have updated my Perl version yesterday but now my Spamd doesn't work
anymore.
Can someone hint me how to solve this?

thanks,
Jos Chrispijn

Pls see output:

Can't locate Net/DNS.pm in @INC (@INC contains:
/usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
/usr/local/lib/perl5/site_perl/5.14.1/mach
/usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
/usr/local/lib/perl5/5.14.1) at /usr/local/bin/sa-update line 80.
BEGIN failed--compilation aborted at /usr/local/bin/sa-update line 80.

Can't locate Net/DNS.pm in @INC (@INC contains:
/usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
/usr/local/lib/perl5/site_perl/5.14.1/mach
/usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
/usr/local/lib/perl5/5.14.1) at /usr/local/bin/sa-update line 80.
BEGIN failed--compilation aborted at /usr/local/bin/sa-update line 80.

Can't locate NetAddr/IP.pm in @INC (@INC contains:
/usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
/usr/local/lib/perl5/site_perl/5.14.1/mach
/usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
/usr/local/lib/perl5/5.14.1) at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm line 25.

BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm line 25.
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86.
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71.
Compilation failed in require at /usr/local/bin/spamassassin line 80.
BEGIN failed--compilation aborted at /usr/local/bin/spamassassin line 80.
ClamAV update process started at Thu Jun 23 15:43:00 2011
main.cld is up to date (version: 53, sigs: 846214, f-level: 53, builder:
sven)
daily.cld is up to date (version: 13231, sigs: 130699, f-level: 60,
builder: arnaud)
bytecode.cld is up to date (version: 143, sigs: 40, f-level: 60,
builder: edwin)
spamd not running? (check /var/run/spamd/spamd.pid).
Starting spamd.

Can't locate NetAddr/IP.pm in @INC (@INC contains:
/usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
/usr/local/lib/perl5/site_perl/5.14.1/mach
/usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
/usr/local/lib/perl5/5.14.1) at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm line 25.

BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm line 25.
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86.
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71.
Compilation failed in require at /usr/local/bin/spamd line 85.
BEGIN failed--compilation aborted at /usr/local/bin/spamd line 85.

Can't locate NetAddr/IP.pm in @INC (@INC contains:
/usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
/usr/local/lib/perl5/site_perl/5.14.1/mach
/usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
/usr/local/lib/perl5/5.14.1) at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm line 25.

BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm line 25.
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86.
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71.
Compilation failed in require at /usr/local/bin/spamassassin line 80.
BEGIN failed--compilation aborted at /usr/local/bin/spamassassin line 80.

--- cut ---
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
"freebsd-questions-unsubscr...@freebsd.org"





Just to make really sure, did you check for any n

Re: Spamassassin not working after update of Perl

[Damien Fleuriot]

On 23 Jun 2011, at 21:37, Matthew Seaman  
wrote:

> On 23/06/2011 14:55, Damien Fleuriot wrote:
>> I have updated my Perl version yesterday but now my Spamd doesn't work
>>> anymore.
>>> Can someone hint me how to solve this?
> 
> You need to reinstall all perl modules if you upgrade perl from 5.10.x
> or 5.12.x to 5.14.1.  This is explained in UPDATING.
> 
> If you do it right, there should be pretty much nothing left in
> /usr/local/lib/perl5/5.X.Y where 5.X.Y is the version you're upgrading
> from.  Specifically reinstall p5-NetAddr-IP and p5-Net-DNS
> 
>Cheers,
> 
>Matthew
> 
> -- 
> Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
>  Flat 3
> PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
> JID: matt...@infracaninophile.co.uk   Kent, CT11 9PW
> 


You're totally misquoting me as I'm not the OP but I'll live 
;)___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Spamassassin not working after update of Perl

[Matthew Seaman]

On 23/06/2011 14:55, Damien Fleuriot wrote:
> I have updated my Perl version yesterday but now my Spamd doesn't work
>> anymore.
>> Can someone hint me how to solve this?

You need to reinstall all perl modules if you upgrade perl from 5.10.x
or 5.12.x to 5.14.1.  This is explained in UPDATING.

If you do it right, there should be pretty much nothing left in
/usr/local/lib/perl5/5.X.Y where 5.X.Y is the version you're upgrading
from.  Specifically reinstall p5-NetAddr-IP and p5-Net-DNS

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matt...@infracaninophile.co.uk   Kent, CT11 9PW



signature.asc
Description: OpenPGP digital signature

Re: Spamassassin not working after update of Perl

[Damien Fleuriot]

On 6/23/11 3:51 PM, Jos Chrispijn wrote:
> I have updated my Perl version yesterday but now my Spamd doesn't work
> anymore.
> Can someone hint me how to solve this?
> 
> thanks,
> Jos Chrispijn
> 
> Pls see output:
> 
> Can't locate Net/DNS.pm in @INC (@INC contains:
> /usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
> /usr/local/lib/perl5/site_perl/5.14.1/mach
> /usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
> /usr/local/lib/perl5/5.14.1) at /usr/local/bin/sa-update line 80.
> BEGIN failed--compilation aborted at /usr/local/bin/sa-update line 80.
> 
> Can't locate Net/DNS.pm in @INC (@INC contains:
> /usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
> /usr/local/lib/perl5/site_perl/5.14.1/mach
> /usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
> /usr/local/lib/perl5/5.14.1) at /usr/local/bin/sa-update line 80.
> BEGIN failed--compilation aborted at /usr/local/bin/sa-update line 80.
> 
> Can't locate NetAddr/IP.pm in @INC (@INC contains:
> /usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
> /usr/local/lib/perl5/site_perl/5.14.1/mach
> /usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
> /usr/local/lib/perl5/5.14.1) at
> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm line 25.
> 
> BEGIN failed--compilation aborted at
> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm line 25.
> Compilation failed in require at
> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86.
> BEGIN failed--compilation aborted at
> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86.
> Compilation failed in require at
> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71.
> BEGIN failed--compilation aborted at
> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71.
> Compilation failed in require at /usr/local/bin/spamassassin line 80.
> BEGIN failed--compilation aborted at /usr/local/bin/spamassassin line 80.
> ClamAV update process started at Thu Jun 23 15:43:00 2011
> main.cld is up to date (version: 53, sigs: 846214, f-level: 53, builder:
> sven)
> daily.cld is up to date (version: 13231, sigs: 130699, f-level: 60,
> builder: arnaud)
> bytecode.cld is up to date (version: 143, sigs: 40, f-level: 60,
> builder: edwin)
> spamd not running? (check /var/run/spamd/spamd.pid).
> Starting spamd.
> 
> Can't locate NetAddr/IP.pm in @INC (@INC contains:
> /usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
> /usr/local/lib/perl5/site_perl/5.14.1/mach
> /usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
> /usr/local/lib/perl5/5.14.1) at
> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm line 25.
> 
> BEGIN failed--compilation aborted at
> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm line 25.
> Compilation failed in require at
> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86.
> BEGIN failed--compilation aborted at
> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86.
> Compilation failed in require at
> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71.
> BEGIN failed--compilation aborted at
> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71.
> Compilation failed in require at /usr/local/bin/spamd line 85.
> BEGIN failed--compilation aborted at /usr/local/bin/spamd line 85.
> 
> Can't locate NetAddr/IP.pm in @INC (@INC contains:
> /usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
> /usr/local/lib/perl5/site_perl/5.14.1/mach
> /usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
> /usr/local/lib/perl5/5.14.1) at
> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm line 25.
> 
> BEGIN failed--compilation aborted at
> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm line 25.
> Compilation failed in require at
> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86.
> BEGIN failed--compilation aborted at
> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86.
> Compilation failed in require at
> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71.
> BEGIN failed--compilation aborted at
> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71.
> Compilation failed in require at /usr/local/bin/spamassassin line 80.
> BEGIN failed--compilation aborted at /usr/local/bin/spamassassin line 80.
> 
> --- cut ---
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "freebsd-questions-unsubscr...@freebsd.org"





Just to make really sure, did you check for any notes in UPDATING
regarding perl ?

Also, have you run perl-after-update ?
___
freebsd

Re: spamassassin config help

[matteo filippetto]

2010/11/17 AN :
> I just setup a new mailserver on 8-stable using sendmail with Spamassassin
> and ClamAv.  Spam is being identified correctly, but it is being delivered
> to users inbox.  Would someone please suggest some good documentation to
> configure mail marked as spam to a different directory. Are there any
> scripts or tools to configure Spamassassin?  Where is the spamassassin
> config file?  Thanks in advance for any help.
>

Hi,

MailScanner.conf has a section called

#
# What to do with spam
# 
#

that is well documented. You can find there what you need.

Best regards

-- 
Matteo Filippetto
http://op83.blogspot.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: spamassassin config help

[Bruce Cran]

On Wed, 17 Nov 2010 15:42:51 + (UTC)
AN  wrote:

> I just setup a new mailserver on 8-stable using sendmail with
> Spamassassin and ClamAv.  Spam is being identified correctly, but it
> is being delivered to users inbox.  Would someone please suggest some
> good documentation to configure mail marked as spam to a different
> directory. Are there any scripts or tools to configure Spamassassin?
> Where is the spamassassin config file?  Thanks in advance for any
> help.

SpamAssassin just tags spam - you'd need to use procmail or something
like it to move mail into different directories depending on the
X-Spam-Level and/or X-Spam-Status headers.

The spamassassin config lives in /usr/local/etc/mail/spamassassin, and
the spamassassin site has lots of documentation.

See http://wiki.apache.org/spamassassin/DeletingAllMailsMarkedSpam for
more information about filtering spam into different directories.

-- 
Bruce Cran
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

[Solved] Re: SpamAssassin 3.3.0/sa-update problem

[Marco Beishuizen]

On Sat, 13 Feb 2010, Marco Beishuizen wrote:


Hi,

Since the update of SpamAssassin to 3.3.0, spamd doesn't start anymore and 
exits with an error:


child process [x] exited or timed out without signaling production of a 
PID file: exit 25 at /usr/local/bin/spamd line 2544.


It seems that after the upgrade, sa-update has to be run first. But in my 
case this results in an error also:


sa-update -D
Feb 13 15:32:07.852 [31554] dbg: dns: query failed: 
0.3.3.updates.spamassassin.org => NOERROR
Feb 13 15:32:07.855 [31554] dbg: dns: query failed: 
mirrors.updates.spamassassin.org => NOERROR

channel: no 'mirrors.updates.spamassassin.org' record found, channel failed
Feb 13 15:32:07.855 [31554] dbg: diag: updates complete, exiting with code 4

I've tried to reinstall SpamAssassin by portupgrade -Rrf 
p5-Mail-SpamAssassin, but this doesn't make any difference. Hope that anyone 
has an idea how to solve this.


I've upgraded the firmware of my DSL modem and the problem has 
disappeared.


Regards,
Marco

--
You can only live once, but if you do it right, once is enough.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: spamassassin Y2010 bug

[Matthew Seaman]

Matthew Seaman wrote:


I'll add your patches and post an updated shar later on.


Done.

Matthew


--
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
 Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
 Kent, CT11 9PW



signature.asc
Description: OpenPGP digital signature

Re: spamassassin Y2010 bug

[Matthew Seaman]

Matt Emmerton wrote:

On Sun, 03 Jan 2010 20:10:19 +
Matthew Seaman  wrote:


Comments, critique are welcome.  Unless there are any killer bugs,
I'll send-pr(1) in a week or so.


You have:

: ${daily_sa_compile="YES"}

sa-compile is installed by the SA port, but it requires devel/re2c,
which is an optional dependency. With a standard install your script
will update the rules, the compile will unconditionally fail, and so
spamd won't get restarted.

You could detect the re2c port, but I think it would be better to turn
it off by default


Hmmm... good point.  


I'd also suggest running sa-compile with nice  by default.


I've put up a set of diffs (patches) in shar format that address some of 
these issues:


1) re2c is listed as a run dependency.  No two ways around it - if you 
do plan on running sa-compile at some time, you'll need re2c, and 
chances are that the machine that is running sa-update is also going to 
be running sa-compile.


Yes.  Agreed.  

2) sa-compile is nice(1)'d by default, and you can provide other flags 
to nice(1) as well.


This is a good idea too.


See http://www.gsicomp.on.ca/~matt/sa-utils-patches.shar


I'll add your patches and post an updated shar later on.

Thank you all very much for your comments.

Cheers,

Matthew

--
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
 Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
 Kent, CT11 9PW



signature.asc
Description: OpenPGP digital signature

Re: spamassassin Y2010 bug

[Matthew Seaman]

Jeffrey Goldberg wrote:

On Jan 3, 2010, at 2:10 PM, Matthew Seaman wrote:


There's a .shar of the new port at:

 http://www.infracaninophile.co.uk/sa-utils.shar

Comments, critique are welcome.  Unless there are any killer bugs, I'll
send-pr(1) in a week or so.


Thanks for doing that. It looks great to me. I just wonder about it
being enabled by default. I don't know what official policy is (if
such a thing exists), but my experience with FreeBSD ports is that
while they install things, the user must still explicitly enable
them.


Yes.  I considered that myself.  There's no clear standard followed by other
ports installing periodic scripts -- some are enabled by default, others
aren't.  In the end I went for having it on by default as installing it
does indicate a desire to run it.  It's no big deal to switch it around
though.


So if might be a good idea to set the defaults to "NO" and include a
pkg-message that instructs people to add the enabling lines in
/etc/periodic.conf.local


Sure.  That's no problem.


I'm also wondering about the name of the port. This really is only
one utility.


That's just future proofing...


Anyway, those are trivial concerns. The substance of your port all
looks very good to me.


Excellent. Thank you very much.  I've a small cosmetic change -- it needs to
print a blank line before anything else -- and apart from the enabled by
default or not question, I need to force it to do a rules update somehow,
so that code path gets tested properly.

Cheers,

Matthew

--
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
 Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
 Kent, CT11 9PW



signature.asc
Description: OpenPGP digital signature

Re: spamassassin Y2010 bug

[Matt Emmerton]

On Sun, 03 Jan 2010 20:10:19 +
Matthew Seaman  wrote:


Comments, critique are welcome.  Unless there are any killer bugs,
I'll send-pr(1) in a week or so.


You have:

: ${daily_sa_compile="YES"}

sa-compile is installed by the SA port, but it requires devel/re2c,
which is an optional dependency. With a standard install your script
will update the rules, the compile will unconditionally fail, and so
spamd won't get restarted.

You could detect the re2c port, but I think it would be better to turn
it off by default

I'd also suggest running sa-compile with nice  by default.


I've put up a set of diffs (patches) in shar format that address some of 
these issues:


1) re2c is listed as a run dependency.  No two ways around it - if you do 
plan on running sa-compile at some time, you'll need re2c, and chances are 
that the machine that is running sa-update is also going to be running 
sa-compile.


2) sa-compile is nice(1)'d by default, and you can provide other flags to 
nice(1) as well.


See http://www.gsicomp.on.ca/~matt/sa-utils-patches.shar

Regards,
--
Matt Emmerton 


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: spamassassin Y2010 bug

[RW]

On Sun, 03 Jan 2010 20:10:19 +
Matthew Seaman  wrote:

> Comments, critique are welcome.  Unless there are any killer bugs,
> I'll send-pr(1) in a week or so.


You have:

: ${daily_sa_compile="YES"}

sa-compile is installed by the SA port, but it requires devel/re2c,
which is an optional dependency. With a standard install your script
will update the rules, the compile will unconditionally fail, and so
spamd won't get restarted.

You could detect the re2c port, but I think it would be better to turn
it off by default

I'd also suggest running sa-compile with nice  by default.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: spamassassin Y2010 bug

[Jeffrey Goldberg]

On Jan 3, 2010, at 2:10 PM, Matthew Seaman wrote:

> There's a .shar of the new port at:
> 
>  http://www.infracaninophile.co.uk/sa-utils.shar
> 
> Comments, critique are welcome.  Unless there are any killer bugs, I'll
> send-pr(1) in a week or so.

Thanks for doing that.  It looks great to me.  I just wonder about it being 
enabled by default.  I don't know what official policy is (if such a thing 
exists), but my experience with FreeBSD ports is that while they install 
things, the user must still explicitly enable them.

So if might be a good idea to set the defaults to "NO" and include a 
pkg-message that instructs people to add the enabling lines in 
/etc/periodic.conf.local

I'm also wondering about the name of the port.  This really is only one utility.

Anyway, those are trivial concerns.  The substance of your port all looks very 
good to me.

Cheers,

-j



-- 
Jeffrey Goldberghttp://www.goldmark.org/jeff/

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: spamassassin Y2010 bug

[Matthew Seaman]

Matthew Seaman wrote:

Jeffrey Goldberg wrote:


Alternatively, if someone were sufficiently motived they could put
together an SA utilities port that installs a number of maintenance
scripts which a user can enable.


This sounds like a very good idea to me.  As far as I can see, there's only
one script required, which can be based on Jeremy's one in ports/127242
but extended so that:

  * allow various flags to be passed to sa-update
- alternative update channels
- extra GPG keys
- gpghomedir setting
  * sa-compile can optionally be run if any updates are downloaded

This should be installed as a daily periodic script -- which should be
appropriate for most users: anyone wanting more frequent updates can just
run it stand-alone as a cron job.

Anything else?  Jeremy -- any objections to my stealing your script as the
basis of this?


There's a .shar of the new port at:

  http://www.infracaninophile.co.uk/sa-utils.shar

MD5 (sa-utils.shar) = aa1f75d840e97c4759119bf653d292bf
SHA256 (sa-utils.shar) = 
701d366035a6ff8dedfd33dfe9057bf33f94efd5f8263445561db1e9e98bcfd1

Comments, critique are welcome.  Unless there are any killer bugs, I'll
send-pr(1) in a week or so.

Cheers,

Matthew

--
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
 Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
 Kent, CT11 9PW



signature.asc
Description: OpenPGP digital signature

Re: spamassassin - Y2K10 bug

[RW]

On Sun, 3 Jan 2010 06:19:55 -0500
Jerry  wrote:

> There is an apparent bug in 'spamassassin' regarding 2010 e-mails. The
> full story is available here:
> 
> http://spamassassin.apache.org/.
> 
> There is also a discussion of it on SlashDot:
> 
> http://it.slashdot.org/story/10/01/02/0027207/SpamAssassin-2010-Bug

And it was discussed on this list a few threads back.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: spamassassin Y2010 bug

[Matthew Seaman]

Jeffrey Goldberg wrote:


Alternatively, if someone were sufficiently motived they could put
together an SA utilities port that installs a number of maintenance
scripts which a user can enable.


This sounds like a very good idea to me.  As far as I can see, there's only
one script required, which can be based on Jeremy's one in ports/127242
but extended so that:

  * allow various flags to be passed to sa-update
- alternative update channels
- extra GPG keys
- gpghomedir setting
  * sa-compile can optionally be run if any updates are downloaded

This should be installed as a daily periodic script -- which should be
appropriate for most users: anyone wanting more frequent updates can just
run it stand-alone as a cron job.

Anything else?  Jeremy -- any objections to my stealing your script as the
basis of this?

Cheers,

Matthew

--
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
 Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
 Kent, CT11 9PW



signature.asc
Description: OpenPGP digital signature

Re: spamassassin Y2010 bug

[Jeffrey Goldberg]

On Jan 2, 2010, at 8:45 AM, RW wrote:

> On Sat, 02 Jan 2010 13:15:25 +
> Matthew Seaman  wrote:
> 
>> However, neither of these have been accepted by the
>> p5-Mail-SpamAssassin port maintainer.
> 
> It's not really a one-size fits all problem - it depends on which
> channels you use and  whether you want sa-compile (which isn't
> supported by either script quoted).

Of course both of these scripts could be easily modified to meet local needs.  
The second script already had some customization hooks built in.

> sa-update is very cheap to run - if there's no update it's just a dns
> lookup. If you're using the auto-generated "sought" rules you may wish
> to update several times a day. OTOH sa-compile is very cpu intensive,
> and once a day may be too much.

That is all true.  If you are maintaining a high traffic site (for which 
sa-compile would be useful) then you will probably be rolling your own 
maintenance scripts anyway.  But none of this is not a reason to not include 
something like these in the SA port.

Alternatively, if someone were sufficiently motived they could put together an 
SA utilities port that installs a number of maintenance scripts which a user 
can enable.

> One other thing is that just I always use sa-update with
> --gpghomedir. If you use the default you loose any third-party public
> keys each time the SA port is reinstalled.

That is useful to know.

Thank you both for your help on getting me to maintain my system better.

Cheers,

-j


-- 
Jeffrey Goldberghttp://www.goldmark.org/jeff/

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: spamassassin Y2010 bug

[RW]

On Sat, 02 Jan 2010 13:15:25 +
Matthew Seaman  wrote:

> However, neither of these have been accepted by the
> p5-Mail-SpamAssassin port maintainer.

It's not really a one-size fits all problem - it depends on which
channels you use and  whether you want sa-compile (which isn't
supported by either script quoted).

sa-update is very cheap to run - if there's no update it's just a dns
lookup. If you're using the auto-generated "sought" rules you may wish
to update several times a day. OTOH sa-compile is very cpu intensive,
and once a day may be too much.

One other thing is that just I always use sa-update with
--gpghomedir. If you use the default you loose any third-party public
keys each time the SA port is reinstalled.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: spamassassin Y2010 bug

[Matthew Seaman]

Jeffrey Goldberg wrote:


How do I know if I am running sa-update? When installing SpamAssassin
from ports I was prompted as to whether I wanted to do this (I said
"yes"), but I don't see anything about it in any crontab I can find
nor in /etc/periodic or /usr/local/etc/periodic.


You need some sort of cron job.  Personally, I have been using a script
posted on the freebsd-p...@... list by Gordon Tetlow -- see

http://www.mavetju.org/mail/view_message.php?list=freebsd-perl&id=2335740

The attachment was scrubbed from the FreeBSD list archives, so the official archive copy of the message is a bit empty: 


http://lists.freebsd.org/pipermail/freebsd-perl/2006-August/001135.html

Jeremy Chadwick also submitted a pretty similar script in 


http://www.freebsd.org/cgi/query-pr.cgi?pr=127242

However, neither of these have been accepted by the p5-Mail-SpamAssassin 
port maintainer.


Cheers,

Matthew

--
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
 Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
 Kent, CT11 9PW



signature.asc
Description: OpenPGP digital signature

Re: spamassassin Y2010 bug

[RW]

On Fri, 1 Jan 2010 18:05:59 -0600
Jeffrey Goldberg  wrote:

> How do I know if I am running sa-update?  When installing
> SpamAssassin from ports I was prompted as to whether I wanted to do
> this (I said "yes"), but I don't see anything about it in any crontab
> I can find nor in /etc/periodic or /usr/local/etc/periodic.

You have to do it yourself.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: spamassassin Y2010 bug

[Jeffrey Goldberg]

On Jan 1, 2010, at 5:19 PM, RW wrote:

> On Fri, 1 Jan 2010 15:05:54 -0600
> Jeffrey Goldberg  wrote:
> 
> 
>> it is likely that
>> some fix will be in with the next batch of rule updates for those who
>> use sa-update.
> 
> It's already available in sa-update.

Great.

How do I know if I am running sa-update?  When installing SpamAssassin from 
ports I was prompted as to whether I wanted to do this (I said "yes"), but I 
don't see anything about it in any crontab I can find nor in /etc/periodic or 
/usr/local/etc/periodic.

I'm on 8-STABLE.

Cheers,

-j


-- 
Jeffrey Goldberghttp://www.goldmark.org/jeff/

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: spamassassin Y2010 bug

[RW]

On Fri, 1 Jan 2010 15:05:54 -0600
Jeffrey Goldberg  wrote:


> There is discussion on the SA mailing list, and it is likely that
> some fix will be in with the next batch of rule updates for those who
> use sa-update.

It's already available in sa-update.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: spamassassin question

[RW]

On Mon, 23 Nov 2009 02:30:47 +
Marwan Sultan  wrote:

> 
> Gary,
> 
>  
> 
>  Its an old problem with /root/.spamassassin
> 
>  I dunt know why spamassassin still have it by default :(
> 
>  I spent a day or so to figure it out.. however,
> 
>  


If you run spamd as root it will setuid to the user running spamc and
use  ~/.spamassassin for user configuration - this is the normal way to
set it up if you wish to use traditional unix mail accounts with per
user conf (including bayes). Presumably this is why it
used /root/.spamassassin, assuming that you ran spamc as root.

Alternately you can use an unprivileged user either by letting it drop
privileges, like this

spamd_flags=" -u "

or by starting it directly, with spamd_user=, since spamd will
no longer be able to bind to the default port, you need to specify a
high port in this case. And for some odd reason spamd still expects the
-u option to be used.

You can also add virtual users like this:

spamd_flags=" -c -x -u 
--virtual-config-dir=/var/db/spamassassin/conf/%u"

and then using:

spamc -u 

in the above  is the unprivileged user and   is the
virtual user which is substituted for %u in the above path. 

There are also numerous sql alternatives, but that's a bit more
complicated.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: spamassassin question

[Ruben de Groot]

On Mon, Nov 23, 2009 at 06:40:37AM +, Marwan Sultan typed:
> 
> > lastly, what format is used in the whitelist? is it similar
> > to what i have in /etc/mail/access?
> 
>  Well, I never change the whitelist, my openwebmail generates the data 
> Automaticaly.
>  You will not need to touch the file, as your webmail client will do it.
> 
>  However to answer your question its as
>  whitelist_from  u...@xxx.xxx
>  whitelist_from  *...@xxx.xxx

This may be confusing, as this thread started about spamassassins 
auto_whitelist feature.
Sure you can have your webmail or other client generate seperate whitelists as 
you 
describe here, but the auto_whitelist file really is maintained by SA only, and 
it's
in Berkeley DB format.

Here's how it works:

http://wiki.apache.org/spamassassin/AutoWhitelist

Ruben

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

RE: spamassassin question

[Marwan Sultan]

 

Hi Gary,


> just to be complete++, :-), you mean
> /usr/local/etc/mail/spamassassin/local.cf
> , is this correct??

 

 Yes, You are 100% Correct :)

> would you check my tying to see if i've made any mistakes?


 Again, Correct :)

 
> another question: are these the same perms, 0755, as before [in /root]?
> i want to document and save these data in a local spamd howto
> file for the next time i need to go thru this morass... 

 

 Gary, Its a sensitive part! if I give you the wrong permission you will be 
exposed to

 attackers! I my self dunt have the right permission, because I didnot have 
enough

 time to look for it, however

 If you set the wrong permission and you run spamd you will see error in you

 log files as "cannot create ..etc.. permission denied"

 You will have to go back and change the permission..

 and start spamd again..and check your log again..755 might be very good.

 after you set 0755 check your log..all errors should disappear.



> lastly, what format is used in the whitelist? is it similar
> to what i have in /etc/mail/access?


 Well, I never change the whitelist, my openwebmail generates the data 
Automaticaly.

 You will not need to touch the file, as your webmail client will do it.

 

 However to answer your question its as

 whitelist_from  u...@xxx.xxx

 whitelist_from  *...@xxx.xxx

 

 donot forget to change /usr/local/etc/rc.d/spamass-milter

 where it says owner and group to "spamd"

 So it run as spamd user instead of root.

 

 and this is in your /etc/rc.conf

 

spamd_enable="YES"
spamass_milter_enable="YES"
spamd_flags="-u spamd -H /var/spool/spamd"

 

 note that after -u there is spamd (which is the user)

 

 Good luck.

 

 Marwan.
  
_
Hotmail: Trusted email with Microsoft's powerful SPAM protection.
http://clk.atdmt.com/GBL/go/177141664/direct/01/
http://clk.atdmt.com/GBL/go/177141664/direct/01/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: spamassassin question

[Gary Kline]

On Mon, Nov 23, 2009 at 02:30:47AM +, Marwan Sultan wrote:
> 
> Gary,
> 
>  
> 
>  Its an old problem with /root/.spamassassin
> 
>  I dunt know why spamassassin still have it by default :(
> 
>  I spent a day or so to figure it out.. however,
> 


i think everyone uwho uses spamassassim would be very
grateful; i am, certain.  thanks!


>  
> 
>  in your local.cf
> 
>  add the lines
> 
>  
> 
> auto_whitelist_path /var/spool/spamd/.spamassassin/auto-whitelist
> bayes_path /var/spool/spamd/.spamassassin/bayes
> 

just to be complete++, :-), you mean

/usr/local/etc/mail/spamassassin/local.cf

, is this correct??


>  
> 
>  Save and Exit,
> 

done!

>  Then:
> 
>  
> 
>  mkdir /var/spool/spamd/.spamassassin
> 
>  touch /var/spool/spamd/.spamassassin/auto-whitelist
> 
>  chown spamd /var/spool/spamd/.spamassassin
> 
>  chown spamd /var/spool/spamd/.spamassassin/auto-whitelist


would you check my tying to see if i've made any mistakes?


> 
>  
> 
>  You will need to set the right permissions then.
> 
>  


another question: are these the same perms, 0755, as before [in /root]?
i want to document and save these data in a local spamd howto
file for the next time i need to go thru this morass... 


lastly, what format is used in the whitelist?  is it similar
to what i have in /etc/mail/access?

-


> 
>  And thats it.
> 
>  
> 
>  Marwan Sultan
> 
>  System Administrator
> 
 Gary Kline  kl...@thought.org  http://www.thought.org  Public Service Unix
http://jottings.thought.org   http://transfinite.thought.org
The 7.31a release of Jottings: http://jottings.thought.org/index.php

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

RE: spamassassin question

[Marwan Sultan]

Gary,

 

 Its an old problem with /root/.spamassassin

 I dunt know why spamassassin still have it by default :(

 I spent a day or so to figure it out.. however,

 

 in your local.cf

 add the lines

 

auto_whitelist_path /var/spool/spamd/.spamassassin/auto-whitelist
bayes_path /var/spool/spamd/.spamassassin/bayes

 

 Save and Exit,

 Then:

 

 mkdir /var/spool/spamd/.spamassassin

 touch /var/spool/spamd/.spamassassin/auto-whitelist

 chown spamd .spamassassin

 chown spamd auto-whitelist

 

 You will need to set the right permissions then.

 

 And thats it.

 

 Marwan Sultan

 System Administrator

 

 
 
> Date: Sun, 22 Nov 2009 17:22:10 -0800
> From: kl...@thought.org
> To: freebsd-questions@FreeBSD.ORG
> CC: 
> Subject: spamassassin question
> 
> 
> Guys,
> 
> my network guy suggests this is ONE way of creating a
> .spamassassin file. Is there a better way than this:
> 
> mkdir /root/.spamassassin
> chmod 775 /root/.spamassassin
> chown root:spamd /root/.spamassassin
> 
> what's the consensus, mail gurus?
> 
> gary
> 
> PS: Is there any other spam tool i can use in-concert-wirh
> spamassissim? I *despise* spam loathe it.
> 
> 
> 
> -- 
> Gary Kline kl...@thought.org http://www.thought.org Public Service Unix
> http://jottings.thought.org http://transfinite.thought.org
> The 7.31a release of Jottings: http://jottings.thought.org/index.php
> 
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
  
_
Windows 7: I wanted simpler, now it's simpler. I'm a rock star.
http://www.microsoft.com/Windows/windows-7/default.aspx?h=myidea?ocid=PID24727::T:WLMTAGL:ON:WL:en-US:WWL_WIN_myidea:112009___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: SpamAssassin/Perl eating enormous amounts of memory?

[Karl Vogel]

>> On Mon, 02 Mar 2009 17:21:53 -0800, 
>> Andrew Moran  said:

A> Thank you for your suggestion.  I'll try compiling Perl and it's
A> dependencies without using PERL_MALLOC.

   I've had similar memory problems using Hyperestraier to index
   collections exceeding 1,000,000 documents.  The indexer would run
   without complaint under Solaris, but die periodically on FreeBSD with
   "out of memory" errors.  Since I had around 6 Gb of RAM, I was pretty
   sure memory wasn't the problem, so I recompiled using a version of
   Doug Lea's malloc and the problem went away.

   The most recent malloc sources are here:

 ftp://gee.cs.oswego.edu/pub/misc/malloc-2.8.3.c
 ftp://gee.cs.oswego.edu/pub/misc/malloc-2.8.3.h

   Here's a Makefile suitable for building and installing the library
   with GCC.  I'm sure the tabs have been mangled:

 CC= gcc
 CPLUS = g++
 LIBS  = libmalloc.a libcppmalloc.a
 DEST  = /usr/local/lib
 INC   = /usr/local/include

 all: $(LIBS)

 clean:
 rm -f $(LIBS) *.o

 cppmalloc.o: malloc.c
 $(CPLUS) -O -c -I. malloc.c -o cppmalloc.o

 install: $(LIBS)
 cp $(LIBS) $(DEST)
 cp -p malloc.h $(INC)
 ranlib $(DEST)/libcppmalloc.a
 ranlib $(DEST)/libmalloc.a

 libcppmalloc.a: cppmalloc.o
 rm -f libcppmalloc.a
 ar q libcppmalloc.a cppmalloc.o

 libmalloc.a: malloc.o
 rm -f libmalloc.a
 ar q libmalloc.a malloc.o

 malloc.o: malloc.c
 $(CC) -O -c -I. malloc.c

   To build something using configure and this library, change the configure
   commands to include these environment variables:

 LDFLAGS="-L/usr/local/lib -lmalloc" CPPFLAGS="-I/usr/local/include"

-- 
Karl Vogel  I don't speak for the USAF or my company
Why are they called apartments, when they're all stuck together?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: SpamAssassin/Perl eating enormous amounts of memory?

[Andrew Moran]

On Mar 3, 2009, at 12:31 PM, Mel wrote:


On Tuesday 03 March 2009 07:26:02 Andrew Moran wrote:





Ok sadly that didn't seem to do much:

celebrian# cat /boot/loader.conf
kern.maxdsiz="8G"
kern.defdsiz="4G"
celebrian#


Can you show limits -H -d?



[r...@celebrian ~]# limits -H -d
Resource limits (current):
  datasize  8388608 kB
[r...@celebrian ~]#


I rebooted, but still see my memory being chewed up.   Almost
immediately after booting, one of my spamassassin processes spun out
of control.  Here's the top with it eating 16 gigs of memory:

  PIDUIDTHR PRI NICE   SIZERES STATE  C   TIME   WCPU
COMMAND
 1611   1030  1  680 15062M   818M CPU2   2   0:44 20.65%
perl5.8.9


At this point, have your cd to a partition large enough to hold a  
few 100

megs, and type:
ktrace -p 1611

where 1611 is the PID of the perl process. You may want to be a bit  
earlier
then this point. After a few seconds, type ktrace -C. Then kdump| 
less. There

should be plenty of allocations there (*alloc* functions).



I'll try to do this if I can catch it in the act. I've  
mitigated the problem by turning off swap completely, which means my  
system doesn't get bogged down but then it's less obvious when it's  
happening.  I do seem to be seeing a lot of other processes dying as  
well:


pid 53393 (perl5.8.9), uid 1030, was killed: out of swap space
pid 53415 (sendmail), uid 0, was killed: out of swap space
pid 53401 (imap-login), uid 143, was killed: out of swap space
pid 53400 (imap-login), uid 143, was killed: out of swap space
pid 53399 (imap-login), uid 143, was killed: out of swap space
pid 53417 (procmail), uid 1030, was killed: out of swap space
pid 47702 (sendmail), uid 0, was killed: out of swap space
pid 53418 (perl5.8.9), uid 1030, was killed: out of swap space
pid 53416 (procmail), uid 1030, was killed: out of swap space
pid 971 (dovecot), uid 0: exited on signal 11 (core dumped)

This morning i had to restart many of my services.  The mystery  
continues.


--Andy
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: SpamAssassin/Perl eating enormous amounts of memory?

[Mel]

On Tuesday 03 March 2009 07:26:02 Andrew Moran wrote:
> On Mar 3, 2009, at 8:01 AM, Andrew Moran wrote:
> > In Mar 3, 2009, at 7:40 AM, Mel wrote:
> >> On Monday 02 March 2009 16:21:53 Andrew Moran wrote:
>  What's even weirder is that the process gets that far. Did you play
>  with
>  kern.maxdsiz loader tuneable?
>  If so, set it lower, so you can at least have the machine in a
>  usable state at
>  all times. 4G should be enough for any process and should give
>  enough time
>  for you to spot the leak and get a ktrace.
> >>>
> >>> Nope, I haven't tweaked any kernel settings, just using the generic
> >>> DEFAULT amd64 kernel.   I've been way about tweaking settings
> >>> because
> >>> I don't fully understand what the 'correct' values for my setup are.
> >>
> >> Could you show kenv kern.maxdsiz and if unset limits -H -d? Looks
> >> like it's
> >> 32G on my 6.x amd64, in which case setting it is a good idea.
> >> echo 'kern.maxdsiz="8G"' >> /boot/loader.conf
> >> echo 'kern.defdsiz="4G"' >> /boot/loader.conf
> >
> > Thank you for helping me. The earlier suggestion of toggling
> > Perl Malloc didn't work, nor did syncing sources and installing new
> > kernel and new world which is what I did lsat night.
> >
> > As for kernel settings, I don't have anything in my loader.conf,
> > and I'm not entirely sure how to show things that aren't sysctls, as
> > this one doesn't seem to be:
> >
> > celebrian# sysctl -a | grep kern.maxdsiz
> > celebrian# sysctl -a | grep kern.defdsiz
> > celebrian#
>
> Ok sadly that didn't seem to do much:
>
> celebrian# cat /boot/loader.conf
> kern.maxdsiz="8G"
> kern.defdsiz="4G"
> celebrian#

Can you show limits -H -d?

> I rebooted, but still see my memory being chewed up.   Almost
> immediately after booting, one of my spamassassin processes spun out
> of control.  Here's the top with it eating 16 gigs of memory:
>
>PIDUIDTHR PRI NICE   SIZERES STATE  C   TIME   WCPU
> COMMAND
>   1611   1030  1  680 15062M   818M CPU2   2   0:44 20.65%
> perl5.8.9

At this point, have your cd to a partition large enough to hold a few 100 
megs, and type:
ktrace -p 1611

where 1611 is the PID of the perl process. You may want to be a bit earlier 
then this point. After a few seconds, type ktrace -C. Then kdump|less. There 
should be plenty of allocations there (*alloc* functions).

>
> and from dmesg:
>
> 
> swap_pager_getswapspace(16): failed
> swap_pager_getswapspace(16): failed
> swap_pager_getswapspace(16): failed
> swap_pager_getswapspace(16): failed
> swap_pager_getswapspace(3): failed
> swap_pager_getswapspace(16): failed
> pid 1611 (perl5.8.9), uid 1030, was killed: out of swap space
>
>
> The computer gets pretty unresponsive during this, unless swapoff my
> swap, then the process eats the memory faster and gets killed
> faster.   Did I type in the wrong variables?

Nope, I'm now reading up myself, I would think this works on amd64. You can 
see defaults in /boot/defaults/loader.conf.

Maybe it only works on what top shows as RES memory (truely used memory, so 
overallocation is possible). In that case, set kern.defdsiz to 512M, perl 
should bug out earlier and probably doesn't affect normal operations (busy 
MySQL server might).

I do hope this feature isn't obsolete on amd64, I kinda like knowing there's a 
guard against my programming errors ;)

-- 
Mel

Problem with today's modular software: they start with the modules
and never get to the software part.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: SpamAssassin/Perl eating enormous amounts of memory?

[Andrew Moran]

On Mar 3, 2009, at 8:01 AM, Andrew Moran wrote:



In Mar 3, 2009, at 7:40 AM, Mel wrote:


On Monday 02 March 2009 16:21:53 Andrew Moran wrote:


What's even weirder is that the process gets that far. Did you play
with
kern.maxdsiz loader tuneable?
If so, set it lower, so you can at least have the machine in a
usable state at
all times. 4G should be enough for any process and should give
enough time
for you to spot the leak and get a ktrace.


Nope, I haven't tweaked any kernel settings, just using the generic
DEFAULT amd64 kernel.   I've been way about tweaking settings  
because

I don't fully understand what the 'correct' values for my setup are.


Could you show kenv kern.maxdsiz and if unset limits -H -d? Looks  
like it's

32G on my 6.x amd64, in which case setting it is a good idea.
echo 'kern.maxdsiz="8G"' >> /boot/loader.conf
echo 'kern.defdsiz="4G"' >> /boot/loader.conf



Thank you for helping me. The earlier suggestion of toggling  
Perl Malloc didn't work, nor did syncing sources and installing new  
kernel and new world which is what I did lsat night.


As for kernel settings, I don't have anything in my loader.conf,   
and I'm not entirely sure how to show things that aren't sysctls, as  
this one doesn't seem to be:


celebrian# sysctl -a | grep kern.maxdsiz
celebrian# sysctl -a | grep kern.defdsiz
celebrian#



Ok sadly that didn't seem to do much:

celebrian# cat /boot/loader.conf
kern.maxdsiz="8G"
kern.defdsiz="4G"
celebrian#

I rebooted, but still see my memory being chewed up.   Almost  
immediately after booting, one of my spamassassin processes spun out  
of control.  Here's the top with it eating 16 gigs of memory:


  PIDUIDTHR PRI NICE   SIZERES STATE  C   TIME   WCPU  
COMMAND
 1611   1030  1  680 15062M   818M CPU2   2   0:44 20.65%  
perl5.8.9


and from dmesg:


swap_pager_getswapspace(16): failed
swap_pager_getswapspace(16): failed
swap_pager_getswapspace(16): failed
swap_pager_getswapspace(16): failed
swap_pager_getswapspace(3): failed
swap_pager_getswapspace(16): failed
pid 1611 (perl5.8.9), uid 1030, was killed: out of swap space


The computer gets pretty unresponsive during this, unless swapoff my  
swap, then the process eats the memory faster and gets killed  
faster.   Did I type in the wrong variables?


--Andy
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: SpamAssassin/Perl eating enormous amounts of memory?

[Andrew Moran]

In Mar 3, 2009, at 7:40 AM, Mel wrote:


On Monday 02 March 2009 16:21:53 Andrew Moran wrote:


What's even weirder is that the process gets that far. Did you play
with
kern.maxdsiz loader tuneable?
If so, set it lower, so you can at least have the machine in a
usable state at
all times. 4G should be enough for any process and should give
enough time
for you to spot the leak and get a ktrace.


Nope, I haven't tweaked any kernel settings, just using the generic
DEFAULT amd64 kernel.   I've been way about tweaking settings because
I don't fully understand what the 'correct' values for my setup are.


Could you show kenv kern.maxdsiz and if unset limits -H -d? Looks  
like it's

32G on my 6.x amd64, in which case setting it is a good idea.
echo 'kern.maxdsiz="8G"' >> /boot/loader.conf
echo 'kern.defdsiz="4G"' >> /boot/loader.conf



Thank you for helping me. The earlier suggestion of toggling Perl  
Malloc didn't work, nor did syncing sources and installing new kernel  
and new world which is what I did lsat night.


As for kernel settings, I don't have anything in my loader.conf,  and  
I'm not entirely sure how to show things that aren't sysctls, as this  
one doesn't seem to be:


celebrian# sysctl -a | grep kern.maxdsiz
celebrian# sysctl -a | grep kern.defdsiz
celebrian#


(Btw, using Perl Malloc didn't work, nor did syncing sources and  
installing new kernel and new world.)


I'm going to try your settings in loader.conf and see if they work for  
me.


--Andy
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: SpamAssassin/Perl eating enormous amounts of memory?

[Mel]

On Monday 02 March 2009 16:21:53 Andrew Moran wrote:

> > What's even weirder is that the process gets that far. Did you play
> > with
> > kern.maxdsiz loader tuneable?
> > If so, set it lower, so you can at least have the machine in a
> > usable state at
> > all times. 4G should be enough for any process and should give
> > enough time
> > for you to spot the leak and get a ktrace.
>
> Nope, I haven't tweaked any kernel settings, just using the generic
> DEFAULT amd64 kernel.   I've been way about tweaking settings because
> I don't fully understand what the 'correct' values for my setup are.

Could you show kenv kern.maxdsiz and if unset limits -H -d? Looks like it's 
32G on my 6.x amd64, in which case setting it is a good idea.
echo 'kern.maxdsiz="8G"' >> /boot/loader.conf
echo 'kern.defdsiz="4G"' >> /boot/loader.conf

would set it to 4G soft limit, 8G hard limit. The difference between soft and 
hard is, that the limits(1) program can be used to run a process with more 
then 4G allocatable memory and nothing can run with more then 8G, until 
loader tunable is changed and a reboot is done.

I really have no idea why on amd64 this default is so high, surely 32G for a 
process is an extreme circumstance, for which one would require 4 physical 
CPU's to begin with.
-- 
Mel

Problem with today's modular software: they start with the modules
and never get to the software part.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: SpamAssassin/Perl eating enormous amounts of memory?

[Andrew Moran]

On Mar 2, 2009, at 3:39 PM, Mel wrote:


This is hard to debug, but I'd first toggle the PERL_MALLOC option  
in the
configuration dialog for the perl port. If this doesn't solve the  
problem,
then you'd have to get a ktrace to get some indication of what is  
allocating

the memory.



Thank you for your suggestion.  I'll try compiling Perl and it's  
dependencies without using PERL_MALLOC.



What's even weirder is that the process gets that far. Did you play  
with

kern.maxdsiz loader tuneable?
If so, set it lower, so you can at least have the machine in a  
usable state at
all times. 4G should be enough for any process and should give  
enough time

for you to spot the leak and get a ktrace.




Nope, I haven't tweaked any kernel settings, just using the generic  
DEFAULT amd64 kernel.   I've been way about tweaking settings because  
I don't fully understand what the 'correct' values for my setup are.



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: SpamAssassin/Perl eating enormous amounts of memory?

[Mel]

On Sunday 01 March 2009 19:23:33 Andrew Moran wrote:
> Hey guys,
>
> After having lots of problems with memory and 7.1/ZFS, I first
> switched everything to 64-bit (amd64), and then I had a new problem,
> so I eventually gave up and switched back to UFS (saying on amd64
> distro/ports), but I'm still having memory issues.
>
> My current one is that SpamAssassin seems to be periodically  eating
> up all my memory, causing the server to slow to a crawl until the
> kernel kills the process and then I have enormous amounts of free
> memory.  Rinse, repeat.   I thought maybe it had something to do with
> the fact that I was using multithreaded perl (which I wasn't before I
> jumped into 7.1/ZFS), but rebuilding perl (and all its' dependencies)
> without threads didn't help.
>
> I have 8GB of physical memory and 16GB of swap memory.   Here is a
> line from top showing perl taking 21 gigs of memory:
>
>   6035  0  1  760 21190M   791M pfault 0   1:20  4.69%
> perl5.8.9

This is hard to debug, but I'd first toggle the PERL_MALLOC option in the 
configuration dialog for the perl port. If this doesn't solve the problem, 
then you'd have to get a ktrace to get some indication of what is allocating 
the memory.

What's even weirder is that the process gets that far. Did you play with 
kern.maxdsiz loader tuneable?
If so, set it lower, so you can at least have the machine in a usable state at 
all times. 4G should be enough for any process and should give enough time 
for you to spot the leak and get a ktrace.

-- 
Mel

Problem with today's modular software: they start with the modules
and never get to the software part.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: SpamAssassin/Perl eating enormous amounts of memory?

[Mikhail Goriachev]

Andrew Moran wrote:

[...]

> Has anyone heard of this?   Or any pointers on what I can do to figure  
> out what is causing it?
> 
> Your advice is much appreciated.

As an alternative:

You could try mail/mimedefang. It calls spamassassin to evaluate an
e-mail but without having it running all the time. This can solve your
problem of running out of memory.

For instance, sendmail could be the first line of defence with its own
rules (rDNS, noMX, RBLs and what not). Then mimedefang with a set of
rules to further reject dodgy e-mails (helo/ehlo, spoofings, SPF and so
on). After that, spamassassin comes into play (controlled by
mimedefang), but only at the end as a last line of defence. By the time
it gets to the end, a lion's share has already been rejected and that
means less work for spamassassin.


I hope this helps.


Regards,
Mikhail.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Spamassassin very slow

[jdow]

That says you are driving spamd into swapping. The two canonical
reasons for SpamAssassin to be really slow are dead BL sites or
overrunning memory and going into heavy swapping. You made a
change to reduce the amount of swapping. Hence you probably have
too many children at any one time.

Modify your minimum and maximum number of children. For best results
you MAY want only one child per processor you can spare from other
work. Regardless, use "top" to see when you go into swapping with the
spamd load. When you do, back off the number of children running at
any given time.

Check rule sets you are using with RDJ. Some of them require incredible
amounts of memory to run. I run enough rules to pull down about 60
megabytes of memory. There are some rule sets that can go over 100
megabytes on the SARE site (SpamAssassin Rules Emporium). 40 children
at 100 megabytes each could use a "lot of machine". {^_-}

You might consider investigating the spamassassin users list at
apache.org. You can find it via the SpamAssassin home page,
http://www.spamassassin.org/

{^_^}   Joanne
- Original Message - 
From: "lyd mc" <[EMAIL PROTECTED]>

Sent: Tuesday, 2008, July 22 23:31



Hi James,

I remove spamc on .procmailrc and I can see lots of improvements!

Thanx,

alyd

--- On Wed, 7/23/08, James Tanis <[EMAIL PROTECTED]> wrote:
From: James Tanis <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]

"lyd mc" <[EMAIL PROTECTED]> wrote:


What causes spamassassin to slow?

Here is my config:

snippet from sendmail.mc
..  ..

I have .procmailrc in every home directory of my mail users and it goes

like

this:


So if I'm understanding you correctly.. your calling spamc from a sendmail
milter *and* .procmailrc. That's pretty redundant and would definately 
slow

you down. Choose one based on your needs.



I also have RulesDuJour installed and spammassassin --lint does complain

about

it.



Extra rules can slow you down regardless of syntax, but most computers
created this decade can handle RulesDuJour fine. Personally I think your
main problem is that your effectively spam checking every message twice. 
The

spamassassin queues most likely get filled followed by sendmail having to
wait and queue up the slack.

--
James Tanis
Technical Coordinator
Monsignor Donovan Catholic High School
e: [EMAIL PROTECTED]



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
"[EMAIL PROTECTED]" 


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Spamassassin very slow

[lyd mc]

Hi James,

I remove spamc on .procmailrc and I can see lots of improvements!

Thanx,

alyd

--- On Wed, 7/23/08, James Tanis <[EMAIL PROTECTED]> wrote:
From: James Tanis <[EMAIL PROTECTED]>
Subject: Re: Spamassassin very slow
To: [EMAIL PROTECTED]
Date: Wednesday, July 23, 2008, 11:07 AM

"lyd mc" <[EMAIL PROTECTED]> wrote:
> 
> What causes spamassassin to slow?
> 
> Here is my config:
> 
> snippet from sendmail.mc
> ..  ..
> 
> I have .procmailrc in every home directory of my mail users and it goes
like
> this:

So if I'm understanding you correctly.. your calling spamc from a sendmail
milter *and* .procmailrc. That's pretty redundant and would definately slow
you down. Choose one based on your needs.

> 
> I also have RulesDuJour installed and spammassassin --lint does complain
about
> it.
> 

Extra rules can slow you down regardless of syntax, but most computers
created this decade can handle RulesDuJour fine. Personally I think your
main problem is that your effectively spam checking every message twice. The
spamassassin queues most likely get filled followed by sendmail having to
wait and queue up the slack.

--
James Tanis
Technical Coordinator
Monsignor Donovan Catholic High School
e: [EMAIL PROTECTED]


  
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Spamassassin very slow

[lyd mc]

thnx Philip, your config will help in my current setup.



--- On Wed, 7/23/08, Philip M. Gollucci <[EMAIL PROTECTED]> wrote:
From: Philip M. Gollucci <[EMAIL PROTECTED]>
Subject: Re: Spamassassin very slow
To: "James Tanis" <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED], freebsd-questions@freebsd.org
Date: Wednesday, July 23, 2008, 11:53 AM

James Tanis wrote:
> "lyd mc" <[EMAIL PROTECTED]> wrote:
>> What causes spamassassin to slow?
>>
>> Here is my config:
>>
>> snippet from sendmail.mc
>> ..  ..
>>
>> I have .procmailrc in every home directory of my mail users and it
goes
> like
>> this:
The following setup by the front line mx's (2 of them) for apache.org 
can handle ~1million messages/day for a total of 2million without 
breaking a sweat.

No .procailrc involved.

/etc/rc.conf:
postfix_enable="YES"
sendmail_enable="NO"
sendmail_submit_enable="NO"
sendmail_outbound_enable="NO"
sendmail_msp_queue_enable="NO"

rbldnsd_enable="YES"
rbldnsd_flags="MASKED OUT"

svscan_enable="YES"

clamav_clamd_enable="YES"
clamav_freshclam_enable="YES"

spamd_enable="YES"
spamd_pidfile="/var/run/spamd/spamd.pid"
spamd_flags="--min-children=4 --max-children=40 --min-spare=2 
--max-spare=8 --max-conn-per-child=100 -c -d 
--socketpath=/var/run/spamd/socket --socketmode=0777 -r ${spamd_pidfile}"

Thats FreeBSD 6.x (soon to be 7.x when I update it)
httpd 2.2.9+worker mpm with qpsmtp using mod_perl

in my consulting buss, for sendmail I use the following sendmail.mc snippet:

INPUT_MAIL_FILTER(`clmilter',`S=local:/var/run/clamav/clmilter.sock, F=, 
T=S:4m;R:4m')
INPUT_MAIL_FILTER(`spamassassin', `S=local:/var/run/spamass-milter.sock, 
F=, T=C:15m;S:4m;R:4m;E:10m')
define(`confMILTER_MACROS_ENVRCPT',`r, v, Z')
define(`confMILTER_MACROS_CONNECT',`b, j, _, {daemon_name}, {if_name}, 
{if_addr}')


That said, all individual users do you ~/.procmailrc, with the following 
rule:
:0
* ^X-Spam-Status: Yes
spam




-- 

Philip M. Gollucci ([EMAIL PROTECTED])
o:703.549.2050x206
Senior System Admin - Riderway, Inc.
http://riderway.com / http://ridecharge.com
1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70  3F8C 75B8 8FFB DB9B 8C1C

Work like you don't need the money,
love like you'll never get hurt,
and dance like nobody's watching.


  
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Spamassassin very slow

[Philip M. Gollucci]

James Tanis wrote:

"lyd mc" <[EMAIL PROTECTED]> wrote:

What causes spamassassin to slow?

Here is my config:

snippet from sendmail.mc
..  ..

I have .procmailrc in every home directory of my mail users and it goes

like

this:
The following setup by the front line mx's (2 of them) for apache.org 
can handle ~1million messages/day for a total of 2million without 
breaking a sweat.


No .procailrc involved.

/etc/rc.conf:
postfix_enable="YES"
sendmail_enable="NO"
sendmail_submit_enable="NO"
sendmail_outbound_enable="NO"
sendmail_msp_queue_enable="NO"

rbldnsd_enable="YES"
rbldnsd_flags="MASKED OUT"

svscan_enable="YES"

clamav_clamd_enable="YES"
clamav_freshclam_enable="YES"

spamd_enable="YES"
spamd_pidfile="/var/run/spamd/spamd.pid"
spamd_flags="--min-children=4 --max-children=40 --min-spare=2 
--max-spare=8 --max-conn-per-child=100 -c -d 
--socketpath=/var/run/spamd/socket --socketmode=0777 -r ${spamd_pidfile}"


Thats FreeBSD 6.x (soon to be 7.x when I update it)
httpd 2.2.9+worker mpm with qpsmtp using mod_perl

in my consulting buss, for sendmail I use the following sendmail.mc snippet:

INPUT_MAIL_FILTER(`clmilter',`S=local:/var/run/clamav/clmilter.sock, F=, 
T=S:4m;R:4m')
INPUT_MAIL_FILTER(`spamassassin', `S=local:/var/run/spamass-milter.sock, 
F=, T=C:15m;S:4m;R:4m;E:10m')

define(`confMILTER_MACROS_ENVRCPT',`r, v, Z')
define(`confMILTER_MACROS_CONNECT',`b, j, _, {daemon_name}, {if_name}, 
{if_addr}')



That said, all individual users do you ~/.procmailrc, with the following 
rule:

:0
* ^X-Spam-Status: Yes
spam




--

Philip M. Gollucci ([EMAIL PROTECTED])
o:703.549.2050x206
Senior System Admin - Riderway, Inc.
http://riderway.com / http://ridecharge.com
1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70  3F8C 75B8 8FFB DB9B 8C1C

Work like you don't need the money,
love like you'll never get hurt,
and dance like nobody's watching.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Spamassassin very slow

[James Tanis]

"lyd mc" <[EMAIL PROTECTED]> wrote:
>
> What causes spamassassin to slow?
>
> Here is my config:
>
> snippet from sendmail.mc
> ..  ..
>
> I have .procmailrc in every home directory of my mail users and it goes
like
> this:

So if I'm understanding you correctly.. your calling spamc from a sendmail
milter *and* .procmailrc. That's pretty redundant and would definately slow
you down. Choose one based on your needs.

>
> I also have RulesDuJour installed and spammassassin --lint does complain
about
> it.
>

Extra rules can slow you down regardless of syntax, but most computers
created this decade can handle RulesDuJour fine. Personally I think your
main problem is that your effectively spam checking every message twice. The
spamassassin queues most likely get filled followed by sendmail having to
wait and queue up the slack.
--
James Tanis
Technical Coordinator
Monsignor Donovan Catholic High School
e: [EMAIL PROTECTED]


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Spamassassin very slow

[lyd mc]

Thanks james. I thought before that spamc on .procmailrc handle checking mail 
for outgoing (mail from local user) and milter in sendmail handle incoming mail 
checking.

Best  regards,

alyd 

--- On Wed, 7/23/08, James Tanis <[EMAIL PROTECTED]> wrote:
From: James Tanis <[EMAIL PROTECTED]>
Subject: Re: Spamassassin very slow
To: [EMAIL PROTECTED], freebsd-questions@freebsd.org
Date: Wednesday, July 23, 2008, 11:08 AM

"lyd mc" <[EMAIL PROTECTED]> wrote:
>
> What causes spamassassin to slow?
>
> Here is my config:
>
> snippet from sendmail.mc
> ..  ..
>
> I have .procmailrc in every home directory of my mail users and it goes
like
> this:

So if I'm understanding you correctly.. your calling spamc from a sendmail
milter *and* .procmailrc. That's pretty redundant and would definately slow
you down. Choose one based on your needs.

>
> I also have RulesDuJour installed and spammassassin --lint does complain
about
> it.
>

Extra rules can slow you down regardless of syntax, but most computers
created this decade can handle RulesDuJour fine. Personally I think your
main problem is that your effectively spam checking every message twice. The
spamassassin queues most likely get filled followed by sendmail having to
wait and queue up the slack.
--
James Tanis
Technical Coordinator
Monsignor Donovan Catholic High School
e: [EMAIL PROTECTED]



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Spamassassin very slow

[lyd mc]

Thanks edwin. I better watch those dns rbl feature..

Regards,

alyd

--- On Wed, 7/23/08, Edwin Groothuis <[EMAIL PROTECTED]> wrote:
From: Edwin Groothuis <[EMAIL PROTECTED]>
Subject: Spamassassin very slow
To: freebsd-questions@FreeBSD.org
Cc: "lyd mc" <[EMAIL PROTECTED]>
Date: Wednesday, July 23, 2008, 10:38 AM

> iLast day my mail server became very slow. I haven't found any
> mysterious errors/warnings in /var/log/message and maillog. When I
> disable spammilter in sendmail it became fast.

Normally this happens to me when I a DNS based RBL suddenly goes
out of action.

I know it won't solve your problem, but have a look on the wire if
all DNS queries are answered in time.

Edwin

-- 
Edwin Groothuis  |Personal website: http://www.mavetju.org
[EMAIL PROTECTED]|  Weblog: http://www.mavetju.org/weblog/


  
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: spamassassin and amavisd with stock sendmail

[Derek Ragona]

At 12:12 PM 4/11/2008, Eric Melville wrote:

I've got a very plain and standard sendmail configuration running on a
machine as a primary mail exchanger. After years of running without any
kind of automated spam filtering, it's just gotten too poor and I have
to turn to rejecting mail.

I installed the spamassassin and new-amavisd port, set the basic
configuration options, turned them on, and it doesn't seem to do anything.
My "test" has been to tell it to tag messages even with a threshold of
zero, and nothing is ever tagged.

Has anyone got a walk through or good document on getting these tools
running on FreeBSD with the system's base sendmail installation? I've
tried web searching and my usual FreeBSD documentation sites with no
luck so far.


I use sendmail with clam for av and spamassasin.  You should also have 
mailscanner installed as well.


You need to make setting changes in your MailScanner.conf  file located in 
/usr/local/etc/MailScanner/


In this file are setting for how spam is dealt with.
Look for the setting:
High Scoring Spam Actions =

You will probably want to set that to delete.

Also go through all the setting in this file.

Once you have mailscanner running you should see subjects changed and also 
a footer added to each email.


-Derek

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Spamassassin: Fill /var/log/maillog

[Ruben de Groot]

On Thu, Jan 31, 2008 at 09:45:10PM +0100, Martin Schweizer typed:
> Hello 
> 
> I get allways the following message in /var/log/maillog:
> 
> Jan 31 17:21:36 acsvfbsd02 spamd[53289]: spamd: connection from 
> localhost.sample.ch [127.0.0.1] at port 64026
> Jan 31 17:21:36 acsvfbsd02 spamd[53289]: spamd: setuid to root succeeded
> Jan 31 17:21:36 acsvfbsd02 spamd[53289]: spamd: still running as root: user 
> not specified with -u, not found, or set to root,falling back to nobody
> Jan 31 17:21:36 acsvfbsd02 spamd[53289]: spamd: processing message <[EMAIL 
> PROTECTED]> for root:65534
> Jan 31 17:21:42 acsvfbsd02 spamd[53289]: auto-whitelist: open of 
> auto-whitelist file failed: locker: safe_lock: cannot create tmp lockfile 
> /nonexistent/.spamassassin/auto-whitelist.lock.acsvfbsd02.acutronic.ch.53289 
> for /nonexistent//.spamassassin/auto-whitelist.lock: No such file or directory
> Jan 31 17:21:42 acsvfbsd02 spamd[53289]: spamd: clean message (0.0/7.0) for 
> root:65534 in 6.2 seconds, 19091 bytes.
> Jan 31 17:21:42 acsvfbsd02 spamd[53289]: spamd: result: . 0 - HTML_MESSAGE 
> scantime=6.2,size=19091,user=root,uid=65534,required_score=7.0,rhost=localhost.acutronic.ch,raddr=127.0.0.1,rport=64026,mid=<[EMAIL
>  PROTECTED]>,autolearn=failed
> 
> 
> There was a pr years ago: 
> http://lists.freebsd.org/pipermail/freebsd-ports-bugs/2005-March/054262.html
> 
> Is there an other solution today?

See the audit trail of this PR, it was allready implemented in 2005.
http://www.FreeBSD.org/cgi/query-pr.cgi?pr=78700&cat=ports

regards,
Ruben

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Spamassassin RBL's

[Warren Block]

On Tue, 12 Jun 2007, Reko Turja wrote:

IMHO mail gateway isn't the point of checking whether machines inside are 
virus free or not. There should be other practises used on workstations 
ensuring that the inside environment is virus free at any given moment.


It's impossible to guarantee that the LAN machines are virus-free at any 
given time, particularly if they run Windows or are portable and move in 
and out of the LAN.


The idea of virus-checking outgoing email isn't to tell whether LAN 
machines are infected, but to prevent abuse of other networks and 
possible loss of connectivity because a virus got through the first-line 
defenses.


-Warren Block * Rapid City, South Dakota USA
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Spamassassin RBL's

[Olivier Nicole]

> IMHO mail gateway isn't the point of checking whether machines inside 
> are virus free or not. There should be other practises used on 
> workstations ensuring that the inside environment is virus free at any 
> given moment.

There should be. But there are also users that decide to use their own
XYZ anti virus because their uncle told them it is better than the one
choosen by the professionals in charge of the system. That is why
outgoing mail gateway is a good place to check that inside machines
are not infected.

I once got my email outgoing gateway inform me that some user had his
machine infected, he had an antivirus, but was one week late for
update... At least my outgoing mail gateway, I have control on it and
the antiviruses are updated every 2 hours :)

Security is better design by adding several layer of checking. At
least IMHO too :)

Bests,

olivier
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Spamassassin RBL's

[Reko Turja]

The directive above tells  postfix to add information into
headers that tell Amavis the mail was sent by someone who was
authenticated by the system and thus trusted.


I expect that the above mentionned headers cannot be forged. Else 
that

would be a nice way for spam to avoid filtering.

Beside, I am not sure it is a good measure to disable Amavis for any
email. First goal of amavis is virus scanning, even a
trusted/authenticated sender could have his machine infected and 
could

be spreading viruses.


Using the header above of course implies that the machine running 
postfix will relay to amavis only on loopback, not via regular IP - or 
using other method that can be counted as secure. And of course for 
viruses authenticating via SASL using encrypted authentication and 
real user/password pair isn't usually successful :)


IMHO mail gateway isn't the point of checking whether machines inside 
are virus free or not. There should be other practises used on 
workstations ensuring that the inside environment is virus free at any 
given moment.


-Reko 


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Spamassassin RBL's

[Olivier Nicole]

> The directive above tells  postfix to add information into 
> headers that tell Amavis the mail was sent by someone who was 
> authenticated by the system and thus trusted.

I expect that the above mentionned headers cannot be forged. Else that
would be a nice way for spam to avoid filtering.

Beside, I am not sure it is a good measure to disable Amavis for any
email. First goal of amavis is virus scanning, even a
trusted/authenticated sender could have his machine infected and could
be spreading viruses.

My 2 cents.

Olivier
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Spamassassin RBL's

[Reko Turja]

I see, I disabled bayes and awl in spamassassin, and updated 
amavisd-new
from ports. I have a different problem. Mail I am sending out is 
being
thrown away because it's being flagged as spam. I'm stumped, it 
never did

this before.


From memory, you can tell amavis which are your networks, so it 
doesnt scan emails on the way out. (or maybe you tell postfix to 
>only send the email via amavis on the way out, not in... i cant 
remember nor check atm).


If you use SASL authentication and Postfix, you can use the following 
postfix directive:


smtpd_sasl_authenticated_header = yes

in main.cf in order to bypass the mail heading outside to be marked as 
spam. The directive above tells  postfix to add information into 
headers that tell Amavis the mail was sent by someone who was 
authenticated by the system and thus trusted. I needed the above as 
the system relays mail from authenticated users from outside the 
netblock the server resides.


In addition Amavis can read the relay_domains database created for 
Postfix in defining what domains are OK to send and receive mail, 
using for example something like:


read_hash(\%local_domains, '/usr/local/etc/postfix/relay_domains');

in amavisd.conf.

Hope these help you!

-Reko 


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Spamassassin RBL's

[Norberto Meijome]

On Sun, 10 Jun 2007 12:33:00 -0700 (PDT)
Peter Pluta <[EMAIL PROTECTED]> wrote:

> I see, I disabled bayes and awl in spamassassin, and updated amavisd-new
> from ports. I have a different problem. Mail I am sending out is being
> thrown away because it's being flagged as spam. I'm stumped, it never did
> this before. 

From memory, you can tell amavis which are your networks, so it doesnt scan 
emails on the way out. (or maybe you tell postfix to only send the email via 
amavis on the way out, not in... i cant remember nor check atm).

B

_
{Beto|Norberto|Numard} Meijome

Sysadmins can't be sued for malpractice, but surgeons don't have to
deal with patients who install new versions of their own innards.

I speak for myself, not my employer. Contents may be hot. Slippery when wet. 
Reading disclaimers makes you go blind. Writing them is worse. You have been 
Warned.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Spamassassin RBL's

[Olivier Nicole]

> How can I enable spamassasssin RBL's. I'm running FreeBSD 6.1, postfix,
> amavisd-new, and spamassassin with razor. I'm getting many spams that
> shouldn't be getting thru with RBL's. I havent been able to find anything
> useful on Google that can explain how to get RBL working with spamassassin.
> Any feedback would be greatly appreciated. 
 
RDL test are enabled in SA if you configure it in the local.cf
configuration. My config file is in /etc/mail/spamassassin.

I can find a lines saying:

skip_rbl_checks 0
rbl_timeout 30
dns_available yes

that means that I use RBL, and that I wait up to 30 seconds to get an
answer. I don't remember about the 3rd line, but it could be related.

Reason that your RBL rules are never triggered could be that the time
out is too low or that you have disabled RBL checks. Or that when you
received the spam, the sender was not yet listed. But was listed lated
when you did the dnsstuff.com check.

If I am not confused, the list of RBL configured in SA by default is
quite short, you may find it usefull to add more RBL to SA. But you
are faced with the risk of adding lists that are poorly managed and
have a lot of false positive.

Like mentionned bellow:

> Or you can out and out block servers in the RBL from your MTA. You
> probably want to be carefull with the latter technique since is
> transfers onus of the work of delivering the mail into the wrong
> hands.

If you do RBL at the MTA level, you better be sure that the RBL you
use are not polluted with false positives.

I'd try to run the ugly spam through SA by hand (spamassassin -t
) and see what the output is. You'll see if the RBL are
triggered or not.

If you are new to SA, I woudl warn you against modifying the scores
for RBL, unless you no what you are doing. SA scoring is a difficulte
and delicate task and modifying the scores may result in unwanted
situation.

Best regards,

Olivier
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Spamassassin RBL's

[Peter Pluta]

Christopher Hilton wrote:
> 
> Peter Pluta wrote:
>> 
>> Mikhail Goriachev-2 wrote:
>>> Peter Pluta wrote:
 How can I enable spamassasssin RBL's. I'm running FreeBSD 6.1, postfix,
 amavisd-new, and spamassassin with razor. I'm getting many spams that
 shouldn't be getting thru with RBL's. I havent been able to find
 anything
 useful on Google that can explain how to get RBL working with
 spamassassin.
 Any feedback would be greatly appreciated. 
>>>
>>> 
> 
> [snip]
> 
>>> /usr/local/share/spamassassin/20_dnsbl_tests.cf
>>>
>>>
> 
> You will also want to look at:
> 
>   /usr/local/share/spamassassin/5-_scores.cf
> 
> There are two ways to use the rbls. You can either raise the score for 
> being in the RBL above SA's threshold. Or you can out and out block 
> servers in the RBL from your MTA. You probably want to be carefull with 
> the latter technique since is transfers onus of the work of delivering 
> the mail into the wrong hands.
> 
> I just spent 3 hours diagnosing a problem for a client on Friday. It 
> turns out that people weren't able to deliver email to him and for the 
> past 6 months he's believed that there was some intermittent problem 
> with his ISP's mailserver. The actual problem is that his ISP is using 
> an overzealous RBL. I found out about this because my delivery server 
> was listed in his RBL due to some mistake that happened in 1999 before 
> my ISP got the IP address. The practical upshot for my client was that 
> until he could find someone who could both see and diagnose the problem 
> he just wasn't receiving mail and thus he was loosing business. Nota 
> Bene for all users of RBLs.
> 
> -- 
>__o  "All I was doing was trying to get home from work."
>  _`\<,_   -Rosa Parks
> ___(*)/_(*)___
> Christopher Sean Hilton
>  pgp key: D0957A2D/f5 30 0a e1 55 76 9b 1f 47 0b 07 e9 75 0e 14
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"
> 
> 

I see, I disabled bayes and awl in spamassassin, and updated amavisd-new
from ports. I have a different problem. Mail I am sending out is being
thrown away because it's being flagged as spam. I'm stumped, it never did
this before. 

Log entry:
Jun 10 14:23:59 mail amavis[541]: (00541-04) cached
f6255bb01c648fe967714d52a89e8e9c from <[EMAIL PROTECTED]> (1,0)
Jun 10 14:24:00 mail amavis[541]: (00541-04) Blocked SPAM, [67.175.92.171]
[67.175.92.171] <[EMAIL PROTECTED]> -> <[EMAIL PROTECTED]>,
Message-ID: <[EMAIL PROTECTED]   ublishing.net>, mail_id:
kj76mFHOu5uA, Hits: 5.651, size: 775, 638 ms
Jun 10 14:24:00 mail postfix/smtp[785]: 7A5215083F:
to=<[EMAIL PROTECTED]>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.84,
delays=0.18/0.01/0/0.64, dsn=2.7.0, status=sent (250 2.7.0Ok,
discarded, id=00541-04 - SPAM)

-- 
View this message in context: 
http://www.nabble.com/Spamassassin-RBL%27s-tf3896464.html#a11051531
Sent from the freebsd-questions mailing list archive at Nabble.com.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Spamassassin RBL's

[Christopher Hilton]

Peter Pluta wrote:


Mikhail Goriachev-2 wrote:

Peter Pluta wrote:

How can I enable spamassasssin RBL's. I'm running FreeBSD 6.1, postfix,
amavisd-new, and spamassassin with razor. I'm getting many spams that
shouldn't be getting thru with RBL's. I havent been able to find anything
useful on Google that can explain how to get RBL working with
spamassassin.
Any feedback would be greatly appreciated. 





[snip]


/usr/local/share/spamassassin/20_dnsbl_tests.cf




You will also want to look at:

 /usr/local/share/spamassassin/5-_scores.cf

There are two ways to use the rbls. You can either raise the score for 
being in the RBL above SA's threshold. Or you can out and out block 
servers in the RBL from your MTA. You probably want to be carefull with 
the latter technique since is transfers onus of the work of delivering 
the mail into the wrong hands.


I just spent 3 hours diagnosing a problem for a client on Friday. It 
turns out that people weren't able to deliver email to him and for the 
past 6 months he's believed that there was some intermittent problem 
with his ISP's mailserver. The actual problem is that his ISP is using 
an overzealous RBL. I found out about this because my delivery server 
was listed in his RBL due to some mistake that happened in 1999 before 
my ISP got the IP address. The practical upshot for my client was that 
until he could find someone who could both see and diagnose the problem 
he just wasn't receiving mail and thus he was loosing business. Nota 
Bene for all users of RBLs.


--
  __o  "All I was doing was trying to get home from work."
_`\<,_   -Rosa Parks
___(*)/_(*)___
Christopher Sean Hilton
pgp key: D0957A2D/f5 30 0a e1 55 76 9b 1f 47 0b 07 e9 75 0e 14
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Spamassassin RBL's

[Peter Pluta]

Mikhail Goriachev-2 wrote:
> 
> Peter Pluta wrote:
>> How can I enable spamassasssin RBL's. I'm running FreeBSD 6.1, postfix,
>> amavisd-new, and spamassassin with razor. I'm getting many spams that
>> shouldn't be getting thru with RBL's. I havent been able to find anything
>> useful on Google that can explain how to get RBL working with
>> spamassassin.
>> Any feedback would be greatly appreciated. 
> 
> 
> RBL is already enabled in SA. Probably you should increase the values SA 
> assigns to RBL checks. See:
> 
> http://www.spamhaus.org/effective_filtering.html
> 
> Skim through:
> 
> /usr/local/share/spamassassin/20_dnsbl_tests.cf
> 
> 
> Just a thought. You may consider implementing RBL at MTA level (postfix 
> in your case). It is a lot faster then processing through SA, which is a 
> resource hog.
> 
> 
> 
> Regards,
> Mikhail.
> 
> -- 
> Mikhail Goriachev
> Webanoide
> 
> Telephone: +61 (0)3 62252501
> Mobile Phone: +61 (0)4 38255158
> E-Mail: [EMAIL PROTECTED]
> Web: www.webanoide.org
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"
> 
> 

Thanks, I think postfix already does the basic RBl's. PTR records and stuff
like that, but i'm still getting some ugly spam. When I feed the spam ip's
into dnsstuff.com's spam database many of the databases show it as
blacklisted, so i'm guessing the RBL's are not functioning correctly. 
-- 
View this message in context: 
http://www.nabble.com/Spamassassin-RBL%27s-tf3896464.html#a11050907
Sent from the freebsd-questions mailing list archive at Nabble.com.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Spamassassin RBL's

[Mikhail Goriachev]

Peter Pluta wrote:

How can I enable spamassasssin RBL's. I'm running FreeBSD 6.1, postfix,
amavisd-new, and spamassassin with razor. I'm getting many spams that
shouldn't be getting thru with RBL's. I havent been able to find anything
useful on Google that can explain how to get RBL working with spamassassin.
Any feedback would be greatly appreciated. 



RBL is already enabled in SA. Probably you should increase the values SA 
assigns to RBL checks. See:


http://www.spamhaus.org/effective_filtering.html

Skim through:

/usr/local/share/spamassassin/20_dnsbl_tests.cf


Just a thought. You may consider implementing RBL at MTA level (postfix 
in your case). It is a lot faster then processing through SA, which is a 
resource hog.




Regards,
Mikhail.

--
Mikhail Goriachev
Webanoide

Telephone: +61 (0)3 62252501
Mobile Phone: +61 (0)4 38255158
E-Mail: [EMAIL PROTECTED]
Web: www.webanoide.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Spamassassin not working

[Olivier Nicole]

> I have installed Spamaassassin along with amavisd-new to filter spam, but
> I don't think it is working. I am getting a bunch of spam and spamassassin
> is not tagging it as spam. I have the score set at 3.0. It worked before
> on my old box but when I installed it on a new box using the same
> procedure I used on the old box it is not working. Anyone have any ideas?

I have about 1000 of ideas, so we need to narrow down the problem.

First thing would be to tell us if SpamAssassin is working at all or
not: are the messages tagged by SA but all are under 3.0 or they are
not tagged at all?

Did you try to run a message throught SA by hand, using the command
spamassassin? Are you running SA daemon, do you have spamd running?
Did you try to feed a message to spand?

Olivier
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Spamassassin not working

[betts]

What MTA are you using?
Postfix

What method are you using to forward messages
between the MTA and amavisd-new?
This is part of the main.cf

smtp-amavis unix -  -   y   -   2  smtp
-o smtp_data_done_timeout=1200
-o smtp_send_xforward_command=yes
-o disable_dns_lookups=yes
-o max_use=20

127.0.0.1:10025 inet n  -   n   -   -  smtpd
-o content_filter=
-o local_recipient_maps=
-o relay_recipient_maps=
-o smtpd_restriction_classes=
-o smtpd_delay_reject=no
-o smtpd_client_restrictions=permit_mynetworks,reject
-o smtpd_helo_restrictions=
-o smtpd_sender_restrictions=
-o smtpd_recipient_restrictions=permit_mynetworks,reject
-o smtpd_data_restrictions=reject_unauth_pipelining
-o smtpd_end_of_data_restrictions=
-o mynetworks=127.0.0.0/8
-o smtpd_error_sleep_time=0
-o smtpd_soft_error_limit=1001
-o smtpd_hard_error_limit=1000
-o smtpd_client_connection_count_limit=0
-o smtpd_client_connection_rate_limit=0

Have you copied the appropriate plug-in .cf files for SA into
`/usr/local/etc/mail/spamassassin`?  Are the plugins being loaded in
`/usr/local/etc/mail/spamassassin/init.pre`?

I don't see any plugins in that directory. Where would I find those
plugins or do I need to reinstall spamassassin with amavis-new?

Thanks



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Spamassassin not working

[Chris Slothouber]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 2007-05-22 06:45, [EMAIL PROTECTED] wrote:
> I have installed Spamaassassin along with amavisd-new to filter spam, but
> I don't think it is working. I am getting a bunch of spam and spamassassin
> is not tagging it as spam. I have the score set at 3.0. It worked before
> on my old box but when I installed it on a new box using the same
> procedure I used on the old box it is not working. Anyone have any ideas?

What MTA are you using?  What method are you using to forward messages
between the MTA and amavisd-new?

Have you copied the appropriate plug-in .cf files for SA into
`/usr/local/etc/mail/spamassassin`?  Are the plugins being loaded in
`/usr/local/etc/mail/spamassassin/init.pre`?

- --
Chris Slothouber ([EMAIL PROTECTED]) -=- Mercenary Sysadmin
BIZ: http://www.hier7.com -=- building.better.ideas
PGP: 7A83 F021 5AC3 4BD7 6738 21D8 B348 0B16 79C0 C27F
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGUtm3s0gLFnnAwn8RAhd1AJ4q3O9+soBroig7IIQX/JZcV1rjgwCgtIwQ
Q8xnkFNKMoxCoJAtEIwrBcU=
=jkdF
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: SpamAssassin and the nonexistent home directory.

[Steve Bernacki]

Start spamd with -D (debug) on both servers to see where and how
spamassassin is configuring itself.  Chances are there is some subtle
configuration variation that is causing this behavior.  It's easy for this
to happen given the fact that spamassassin reads through a number of
directories for configuration information when it starts up.

Steve
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: SpamAssassin and the nonexistent home directory.

[Derrick]

On Wed, 21 Feb 2007, Kevin Kinsey wrote:

> Derrick wrote:
> > I'm confused as to why on box #1 I have in /etc/rc.conf:
> >
> > spamd_enable="YES"
> > spamd_flags="-c -u spamd -H /var/spool/spamd -m 10"
> >
> > And spamd is writing to /var/spool/spamd/.spamassassin
> >
> > on box #2 and #3, I have the exact same settings yet I see:
> >
> > /nonexistent/.spamassassin/auto-whitelist.lock: No such file or directory
> > Feb 21 00:06:44 mail spamd[39002]: auto-whitelist: open of auto-whitelist
> > file failed: locker: safe_lock: cannot create tmp lockfile
> >
> > /nonexistent/.spamassassin/auto-whitelist.lock.xxx.xxx.xxx.39002 for
> > /nonexistent/.spamassassin/auto-whitelist.lock : No such file or directory
> > Feb 21 00:06:44 mail spamd[39002]: bayes: locker: safe_lock: cannot create
> > tmp lockfile /nonexistent/.spamassassin/bayes.lock.xxx.xxx.xxx.39002 for
> > /nonexistent/.spamassassin/bayes.lock: No such file or directory
>
> Well, first I'd check that /var/spool/spamd does exist on both boxes.
> Probably then I would try `id` and `finger` perhaps, on the spamd user,
> and hope that the output might give me a clue.


Ya they are all identical in those regards.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: SpamAssassin and the nonexistent home directory.

[Kevin Kinsey]

Derrick wrote:

I'm confused as to why on box #1 I have in /etc/rc.conf:

spamd_enable="YES"
spamd_flags="-c -u spamd -H /var/spool/spamd -m 10"

And spamd is writing to /var/spool/spamd/.spamassassin

on box #2 and #3, I have the exact same settings yet I see:

/nonexistent/.spamassassin/auto-whitelist.lock: No such file or directory
Feb 21 00:06:44 mail spamd[39002]: auto-whitelist: open of auto-whitelist
file failed: locker: safe_lock: cannot create tmp lockfile

/nonexistent/.spamassassin/auto-whitelist.lock.xxx.xxx.xxx.39002 for
/nonexistent/.spamassassin/auto-whitelist.lock : No such file or directory
Feb 21 00:06:44 mail spamd[39002]: bayes: locker: safe_lock: cannot create
tmp lockfile /nonexistent/.spamassassin/bayes.lock.xxx.xxx.xxx.39002 for
/nonexistent/.spamassassin/bayes.lock: No such file or directory


Well, first I'd check that /var/spool/spamd does exist on both boxes. 
Probably then I would try `id` and `finger` perhaps, on the spamd user, 
and hope that the output might give me a clue.


Grasping a straw,

Kevin Kinsey
--
If you can lead it to water and force it to drink, it isn't a horse.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Spamassassin error

[Andrew Pantyukhin]

On 12/22/06, Beech Rintoul <[EMAIL PROTECTED]> wrote:

I just set up spamassassin on one of my servers. Everything appears to be
working properly, except I'm seeing this error in the maillog:

Dec 22 08:49:57 pinnacle spamd[25077]: spamd: could not create INET socket on
127.0.0.1:783: Permission denied.

Anyone have an idea how to fix this?


Looks like you're trying to create a low-port (<=1024)
socket under a non-privileged account. Try a higher
port number.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: spamassassin

[jdow]

From: "justins" <[EMAIL PROTECTED]>


I`ve installed spamassassin rules on my sentmailserver and i am trying to 
filter my mail in order to pick out some spam.
The spamd process is running only it doesn`t add anything to my mail 
heather so procmail can`t forward it to the caughtspam folder.


How do i start spamassassin in order to filter my incomming mail.
Anyone.


You want spamd running as a daemon.

Then you want lines like this in your procmailrc
:0
* < 50
* !^List-Id: .*(spamassassin\.apache.\org)
| /usr/bin/spamc -t 150 -u $LOGNAME

The third line is my personal filter to prevent spamassassin triggering
on the SpamAssassin list. Any spam there is FOOD for the anti-spam rules
folks. {^_-}

This will add markups, probably the default markups.

http://www.spamassassin.org/ is a starting source for information.
The Wiki link points to the (admittedly pathetic) online documentation.
This also has a link to the users mailing list. You're certainly
welcome there.

http://www.rulesemporium.com/ is a nice place to get pre-canned sets
of effective rules to supplement the stock rules.

Other help is found with man spamassassin, etc. Also check out man
or perldoc for Mail::SpamAssassin::Conf for configuration help.

{^_^}


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: spamassassin

[Matthew Seaman]

justins wrote:
> 
> I`ve installed spamassassin rules on my sentmailserver and i am trying
> to filter my mail in order to pick out some spam.
> The spamd process is running only it doesn`t add anything to my mail
> heather so procmail can`t forward it to the caughtspam folder.
> 
> How do i start spamassassin in order to filter my incomming mail.
> Anyone.

That depends on what MTA software you are using.  If it's sendmail,
then there are several choices.  The mail/spamass-milter is probably
the least complicated to use, as it's purely about integrating
SpamAssassin and sendmail.  There's also several integrated Anti-Virus
and Anti-Spam setups that can use SpamAssassin internally, such as 
mail/mailscanner.

Another alternative is to invoke spamassassin from the delivery agent
-- in that case, I'd recommend installing mail/procmail and using that
as your default MDA -- in sendmail that's done by including
'FEATURE(local_procmail)' into the .mc file -- and then write yourself
a .procmailrc file that feeds messages into spamc for spam checking.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
  Kent, CT11 9PW



signature.asc
Description: OpenPGP digital signature

Re: spamassassin

[Bob Johnson]

On 9/18/06, justins <[EMAIL PROTECTED]> wrote:


I`ve installed spamassassin rules on my sentmailserver and i am trying to
filter my mail in order to pick out some spam.
The spamd process is running only it doesn`t add anything to my mail
heather so procmail can`t forward it to the caughtspam folder.



spamd is the daemon version of spamassassin.  It doesn't do anything
unless something hands mail to it via its companion program, spamc
(unless you want to roll your own interface program). It is intended
to be used on high-volume servers that can't stand the overhead of
starting a new spamassassin process for each email message.


How do i start spamassassin in order to filter my incomming mail.
Anyone.


That depends on your server. If it knows how to use spamd/spamc, then
configure it according to its documentation.  Otherwise, to filter an
individual message in a file, use the spamassassin program (rather
than spamd), e.g. "spamassassin /path/to/message/file".  Or more
likely you will want to pipe the message to spamassassin on stdin and
get the marked-up message from stdout.

If you need more detail than that, you probably should be looking at
the documentation for your mail server or for spamassassin. Every
server package seems to have a different way to do it.

- Bob
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: spamassassin

[Paul Lathrop]

I'd suggest asking the Spamassassin mailing lists...

justins wrote:
>
> I`ve installed spamassassin rules on my sentmailserver and i am trying
> to filter my mail in order to pick out some spam.
> The spamd process is running only it doesn`t add anything to my mail
> heather so procmail can`t forward it to the caughtspam folder.
>
> How do i start spamassassin in order to filter my incomming mail.
> Anyone.
>
> Thanks in advance,
> Justin.
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"


signature.asc
Description: OpenPGP digital signature

Re: spamassassin build failure

[Michael P. Soulier]

On 27/03/06 Lowell Gilbert said:

> Even among scripting languages, perl is unique in its pathological
> lack of backward compatibility.  The FreeBSD maintainers do a nice job
> of limiting the pain, but you *do* have to follow their directions.

Python's worse. :(

Mike

-- 
Michael P. Soulier <[EMAIL PROTECTED]>
"Any intelligent fool can make things bigger and more complex... It
takes a touch of genius - and a lot of courage to move in the opposite
direction." --Albert Einstein


pgpyWwe1Ic16O.pgp
Description: PGP signature

Re: spamassassin build failure

[Lowell Gilbert]

"Michael P. Soulier" <[EMAIL PROTECTED]> writes:

> As I think I only went from perl 5.6 to 5.8, I'm surprised that so much would
> be out of date. Good to know though. Do the other scripting languages have
> this kind of support? Python?

Even among scripting languages, perl is unique in its pathological
lack of backward compatibility.  The FreeBSD maintainers do a nice job
of limiting the pain, but you *do* have to follow their directions.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: spamassassin build failure

[Riemer Palstra]

On Sun, Mar 26, 2006 at 08:30:04AM -0500, Michael P. Soulier wrote:
> As I think I only went from perl 5.6 to 5.8, I'm surprised that so
> much would be out of date.

That's actually quite a change, as Perl 5.6.2 dates from, I think,
November 2003, while Perl 5.8.8 was released February 2006.

-- 
Riemer PalstraAmsterdam, The Netherlands
[EMAIL PROTECTED]http://www.palstra.com/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: spamassassin build failure

[Matthias Fechner]

Hello Michael,

* Michael P. Soulier <[EMAIL PROTECTED]> [26-03-06 08:19]:
> Nope, I didn't do that. How would I know to do that? :)

reading /usr/ports/UPDATING :)


Best regards,
Matthias


pgpOvxufzBn0e.pgp
Description: PGP signature

Re: spamassassin build failure

[Michael P. Soulier]

On 26/03/06 Matthew Seaman said:

> Did you run the perl-after-upgrade script with the '-f' flag so it
> actually does anything?  This symptom occurs when the pkg system
> thinks a package is installed (because there's an entry in
> /var/db/pkgs) but perl can't find the corresponding module, because
> it's in /usr/local/lib/perl5/site_perl/5.8.X with X != 8.

perl-after-upgrade -f seems to have fixed the problem. 

As I think I only went from perl 5.6 to 5.8, I'm surprised that so much would
be out of date. Good to know though. Do the other scripting languages have
this kind of support? Python?

Mike

-- 
Michael P. Soulier <[EMAIL PROTECTED]>
"Any intelligent fool can make things bigger and more complex... It
takes a touch of genius - and a lot of courage to move in the opposite
direction." --Albert Einstein


pgpGmhwH9GgMn.pgp
Description: PGP signature

Re: spamassassin build failure

[Michael P. Soulier]

On 26/03/06 Matthew Seaman said:

> Did you run the perl-after-upgrade script with the '-f' flag so it
> actually does anything?  This symptom occurs when the pkg system
> thinks a package is installed (because there's an entry in
> /var/db/pkgs) but perl can't find the corresponding module, because
> it's in /usr/local/lib/perl5/site_perl/5.8.X with X != 8.

Nope, I didn't do that. How would I know to do that? :)

> Forcing a reinstall of p5-Test-Harness would also work.

Ok, great. Thanks. 

Mike

-- 
Michael P. Soulier <[EMAIL PROTECTED]>
"Any intelligent fool can make things bigger and more complex... It
takes a touch of genius - and a lot of courage to move in the opposite
direction." --Albert Einstein


pgpBK6bdcDKIN.pgp
Description: PGP signature

Re: spamassassin build failure

[Matthew Seaman]

On Sat, Mar 25, 2006 at 10:18:41PM -0500, Michael P. Soulier wrote:
> Hi there,
> 
> I'm trying to build spamassassin from ports. 
> 
> So, I go to /usr/ports/mail/p5-Mail-SpamAssassin and make. 
> 
> ===>  Checking if devel/p5-Test-Harness already installed
> ===>   p5-Test-Harness-2.56 is already installed
>   You may wish to ``make deinstall'' and install this port again
>   by ``make reinstall'' to upgrade it properly.
>   If you really wish to overwrite the old port of devel/p5-Test-Harness
>   without deleting it first, set the variable "FORCE_PKG_REGISTER"
>   in your environment or the "make install" command line.
> *** Error code 1
> 
> Whoops. Well, lets upgrade with portupgrade then, since it wants to upgrade. 
> 
> [EMAIL PROTECTED] p5-Mail-SpamAssassin]$ sudo portupgrade -vR p5-Test-Harness
> --->  Session started at: Sat, 25 Mar 2006 22:16:12 -0500
> ** No need to upgrade 'perl-5.8.8' (>= perl-5.8.8). (specify -f to force)
> ** No need to upgrade 'p5-Test-Harness-2.56' (>= p5-Test-Harness-2.56).
> (specify -f to force)
> --->  Listing the results (+:done / -:ignored / *:skipped / !:failed)
> - lang/perl5.8 (perl-5.8.8)
> - devel/p5-Test-Harness (p5-Test-Harness-2.56)
> --->  Packages processed: 0 done, 2 ignored, 0 skipped and 0 failed
> --->  Session ended at: Sat, 25 Mar 2006 22:16:15 -0500 (consumed 00:00:02)
> 
> Whoops. Apparently it doesn't need to upgrade. 
> 
> Should I make deinstall? And if so, why, since it doesn't need to upgrade?

Did you run the perl-after-upgrade script with the '-f' flag so it
actually does anything?  This symptom occurs when the pkg system
thinks a package is installed (because there's an entry in
/var/db/pkgs) but perl can't find the corresponding module, because
it's in /usr/local/lib/perl5/site_perl/5.8.X with X != 8.

Forcing a reinstall of p5-Test-Harness would also work.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
  Kent, CT11 9PW


pgptFuxe6a463.pgp
Description: PGP signature

Re: SpamAssassin and country-specific blocking

[jdow]

From: "Dave" <[EMAIL PROTECTED]>


Hello,
   I just installed the latest SpamAssassin port and noticed it had 
country-specific spam filtering as well as spf and ssl support. Does anyone 
have a howto on getting all this going with an mta in a production 
environment? I'm not looking for anything like a manual, but practical 
experiences.

Thanks.
Dave.


mailto:[EMAIL PROTECTED]

That list is quite handy for solving SPF problems if you have any. (It
should work "outa the box.") It can also help you setup the "trusted_network"
concept. It's not quite what you might think it is. It simply means that
"this network is one I trust not to falsify header information." Usually
SA can figure this out for itself. But if you see ALL_TRUSTED as a spam
rule that got listed for all or most messages then it needs to be setup.

The ssl support is something I've not looked at. (I am still running a
tweaked 3.04 brought up to 3.05 for bug fixes. I have some special
debugging crammed into my spamassassin install.)

Interesting places to look for "ideas" is the /usr/share/spamassassin
(in Linux speak - my install's on linux for now) for the common rules.
You can search for "score" for scores and look at the rules to get some
idea of what's going on with them.

The users's list, though, is generally the best help. Folks with LARGE
ISPs are there as well as my "ISP For Two" setup.

{^_^}
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: spamassassin problem and question

[Ken Stevenson]

David Banning wrote:
Having said that, I don't think that's what you want to do. It sounds like you 
upgraded Spamassassin without upgrading Razor2. I don't think Razor2 gets 
upgraded automatically when you upgrade Spamassassin because it's optional. I 
would try upgrading the Razor2 port to the latest version. 


It is already upgraded. I did put the file that Spamassassin was looking 
for in one of the directories that is was searching and the error message

disappeared. Perhaps not a by-the-book way, but it seemed to work.
Thanks for your response.


Whatever works. FYI, on my system, Razor2.pm is at.

/usr/local/lib/perl5/site_perl/5.8.7/Mail/SpamAssassin/Plugin/Razor2.pm

Also what I said previously about having to upgrade it separately 
apparently isn't true, because I never explicitly installed Razor. I 
guess it was installed when I installed SpamAssassin.


--
Ken Stevenson
Allen-Myland Inc.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: spamassassin problem and question

[David Banning]

> Having said that, I don't think that's what you want to do. It sounds like 
> you 
> upgraded Spamassassin without upgrading Razor2. I don't think Razor2 gets 
> upgraded automatically when you upgrade Spamassassin because it's optional. I 
> would try upgrading the Razor2 port to the latest version. 

It is already upgraded. I did put the file that Spamassassin was looking 
for in one of the directories that is was searching and the error message
disappeared. Perhaps not a by-the-book way, but it seemed to work.
Thanks for your response.

-- 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: spamassassin problem and question

[Ken Stevenson]

On Friday 27 January 2006 02:00 am, David Banning wrote:
> While spamassassin is executing I am getting this error;
>
> Can't locate Razor2/Client/Agent.pm in @INC (@INC contains:
> /usr/local/lib/perl5/site_perl/5.8.7 ../lib
> /usr/local/lib/perl5/5.8.7/BSDPAN /usr/local/lib/perl5/site_perl/5.8.7/mach
> /usr/local/lib/perl5/site_perl/5.8.6 /usr/local/lib/perl5/site_perl/5.005
> /usr/local/lib/perl5/site_perl /usr/local/lib/perl5/5.8.7/mach
> /usr/local/lib/perl5/5.8.7) at
> /usr/local/lib/perl5/site_perl/5.8.7/Mail/SpamAssassin/Plugin/Razor2.pm
> line 70.
>
> So I look for the file;
>
> # locate Agent.pm
> /usr/local/lib/perl5/site_perl/5.005/Sitescooper/UserAgent.pm
> /usr/local/lib/perl5/site_perl/5.005/i386-freebsd/Razor2/Client/Agent.pm
> /usr/local/lib/perl5/site_perl/5.8.7/LWP/UserAgent.pm
>
> In my simplistic way of attempting resolution, I am thinking
> of just adding /usr/local/lib/perl5/site_perl/5.005/i386-freebsd
> to @INC - but here is where my knowledge runs out. Where are the
> references to directories referred to as @INC stored?
> @INC does not appear to be a file.
>
I believe @INC is created when perl is compiled, so you can't change it 
directly. To use a module in a directory that's not in the compiled list, you 
add the following line before the "use" statement that references Razor2:

use lib "/usr/local.../location of the perl module

> I may even be attempting to solve this incorrectly. Any pointers
> would be useful -

Having said that, I don't think that's what you want to do. It sounds like you 
upgraded Spamassassin without upgrading Razor2. I don't think Razor2 gets 
upgraded automatically when you upgrade Spamassassin because it's optional. I 
would try upgrading the Razor2 port to the latest version. 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: SpamAssassin help...

[Vincent Bachelier]

You can't run spamassassin as root (see your
configuration).
Well, it fall back to nobody user, because you don't
specify anything.
The problem is that the working directory is in root
dir (/root)
Well, spamassassin running in nobody try to write in
root directory ! It's forbidden
Edit you conf and find nobody
replace it by a spamc user, you have created before
... (don't put root, it's dangerous)

ok see if it's work
see ya
 --- Eric F Crist <[EMAIL PROTECTED]> a
écrit : 
> Can anyone tell me how to fix the following two
> errors?
> 
> Feb 15 17:43:13 grog spamd[594]: Still running as
> root: user not 
> specified with -u, not found, or set to root.  Fall
> back to nobody.
> Feb 15 17:43:13 grog spamd[594]: processing message 
> <[EMAIL PROTECTED]>
> for root:65534.
> Feb 15 17:43:13 grog spamd[594]: Cannot open bayes
> databases 
> /root/.spamassassin/bayes_* R/W: tie failed:
> Permission denied
> Feb 15 17:43:15 grog last message repeated 2 times
> 
> I'm getting all sorts of bayes database errors.  Is
> there something I 
> didn't update when I installed the system?  Also, I
> tried a -u nobody 
> to spamd, but it just seemed to hang.
> 
> TIA
> 
>
___
> Eric F Crist  "I am so smart,
> S.M.R.T!"
> Secure Computing Networks  -Homer J
> Simpson
> 

> ATTACHMENT part 2 application/pgp-signature
x-mac-type=70674453; name=PGP.sig
 

=
Vincent Bachelier
System: FreeBSD-5.3-RELEASE - AMD64






Découvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos mails ! 
Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: spamassassin

[Olivier Nicole]

> "pass out quick on rl0 proto tcp from any to any port = 2703 flags S
> keep state"

Yes, here I have:

pass in log first quick proto tcp from x.x.x.x to any port = 2703 flags S keep 
state group 200

Olivier
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: SpamAssassin-Milter accuracy...

[Louis LeBlanc]

On 01/04/05 08:59 PM, Ted Mittelstaedt sat at the `puter and typed:
> 
> > 
> 
> The only problem with doing this is that you have to completely
> receive the e-mail message before SA can check it against the
> blacklists.
> 
> We do the blacklist checks at the MTA level and turn them off in SA.
> As a result the e-mail is never accepted by the server if it's in a
> blacklist.  As a result of that if the spam is coming from a
> compromised mailserver then that mailserver will just requeue the
> message.  And with everyone on the Internet doing this, it will make
> the compromised mailserver melt down immediately, which will punish
> the admin of it for running an open mailserver in the first place.

Whether this is the "Right Thing To Do" may be debatable, but I think
you leave yourself open to rejecting legitimate email on the word of
an overzealous blacklister.  I read somewhere recently that some lists
had been known to blacklist servers simply because their admin was
critical of their listing criteria.  This is third hand, of course,
but you have to accept that blacklists have been compiled with very
objective criteria, and usually by overzealous anti-spammers.  Even
those that have automated criteria often rely on unconfirmed reports
to blacklist an IP.

Believe me, I'm all for thumping the spammers - and I mean hard.  I
was giddy when I read the story on the little ISP that was awarded $1
Billion from a spammer that kept their network on its knees for
months.  Still, it's probably not a good thing to run over innocent
pedestrians to get them.  I know an open relay isn't necessarily an
innocent pedestrian - more like a careless admin, but they're still
being victimized by the spammer too.

Not to say you shouldn't reject spam, but there are more reliable
ways, like amavis-new, which will check the message through
SpamAssassin, and reject at the MTA it if the threshold is high
enough.

It may be a little more load on your MTA, but you're rejecting email
because it's spam, not because someone has blackballed the originator.
That message still gets requeued on the relay, so the effect is still
an overloaded server.

I tried Amavis-new for SA checks at one point, and it works very
nicely.  I turned the spam checking off because I didn't like that it
was using global configs and preferences - I prefer per-user settings
because my mother and wife are signed up for mailings that set off a
lot of SA flags.  My Bayes DB is much better trained than theirs,
and I've got my threshold much lower (I use 2.0 with maybe 1 FP & < 20
FNs per 100,000 messages).  Not to say you can't rescan, or just
resort based on the score assigned through amavisd, but I'm more
inclined to put it aside and make darn sure it's spam myself.  So
Amavis scans email through the virus tools and leaves Spam checking to
Procmail and SA.

> > I do use the blackholes (check http://blackholes.us) at the MTA,
> > since rejecting mail outright from Asian (and a few African)
> > countries has reduced my spam intake by about 80%, without
> > reducing my legitimate mail by a single message.  Since I'm not
> > running a service for other people, and I carefully choose the
> > blackhole domains I use, it's not a problem for me.  Of course,
> > that may not be an option for you.  Someday I'll stop this
> > practice, but for now some of my doors are just plain closed.
> >
> 
> We don't use blackholes.us although I'll take a look at it.  About
> 50% of our incoming spam is blocked by the blacklist servers we do
> use.

I like the blackholes.  They have the upside of qualifying simply by
their country of origin.  They also have the downside of qualifying
simply because of their country of origin.  If you use them, you can
be fairly certain that you are only refusing connections - all
connections - from the country you intended.  The criteria is much
more concrete than the blacklists, and the lists are much more stable.

As I mentioned, I don't have acquaintances and don't do business with
anyone in Asia, so I feel fine simply not accepting email from the
biggest source of my spam.  When I turned them back on with my new
server, my spam instantly went down by 75%.  That's after using them
on my domains for over 2 years, and running my new server without them
for a few weeks.  Had I kept them off longer, I have no doubt the
stream would have increased - when I turned them on 2 years ago, my
spam went down by almost 95% in a matter of minutes, and over the
years the stream of rejects has diminished slowly.

Lou
-- 
Louis LeBlanc   [EMAIL PROTECTED]
Fully Funded Hobbyist, KeySlapper Extrordinaire :)
http://www.keyslapper.org ԿԬ

White dwarf seeks red giant for binary relationship.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: SpamAssassin-Milter accuracy...

[Ted Mittelstaedt]

> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Louis LeBlanc
> Sent: Tuesday, January 04, 2005 9:09 AM
> To: freebsd-questions@freebsd.org
> Subject: Re: SpamAssassin-Milter accuracy...
>
>
> On 01/04/05 05:17 PM, Matthias Buelow sat at the `puter and typed:
> > Louis LeBlanc wrote:
> >
> > > Use with care.  Some spam rbls are overly zealous, and often block out
> > > whole netblocks just because one IP has been reported as an offender.
> >
> > And all dialup networks.  Which can lead to the bizarre situation that
> > if you're relaying through your mail server from a dialup IP, and mail
> > goes thru SA, you'll get a high score.  There're several ways
> to prevent
> > this from happening, of course, for example, to run an extra smtpd on a
> > nonstandard port that doesn't push mails through SpamAssassin, or just
> > to disable the damn RBL stuff in the SA config (I did both, greylisting
> > is more effective than the suspicious RBL stuff anyways).
>
> This includes most dynamically allocated IP blocks.  The only way to
> avoid getting tagged and/or outright rejected by some networks is to
> relay through the ISPs relay.
>
> It's because of this that I don't use the spamblock RBLs at the MTA
> level.  SA works almost perfectly with it's own clearing house checks
> (NJABL, SORBS, SPAMCOP, etc.) and modifies the score for each.  I've
> dug up some recipes that will further compound scores for multiple of
> these clearing houses too, so you get bonus points for getting
> reported to 3 or more :)
>

The only problem with doing this is that you have to completely receive
the e-mail message before SA can check it against the blacklists.

We do the blacklist checks at the MTA level and turn them off in SA.  As
a result the e-mail is never accepted by the server if it's in a blacklist.
As a result of that if the spam is coming from a compromised mailserver then
that mailserver will just requeue the message.  And with everyone on the
Internet doing this, it will make the compromised mailserver melt down
immediately,
which will punish the admin of it for running an open mailserver in the
first place.

> I do use the blackholes (check http://blackholes.us) at the MTA, since
> rejecting mail outright from Asian (and a few African) countries has
> reduced my spam intake by about 80%, without reducing my legitimate
> mail by a single message.  Since I'm not running a service for other
> people, and I carefully choose the blackhole domains I use, it's not a
> problem for me.  Of course, that may not be an option for you.
> Someday I'll stop this practice, but for now some of my doors are just
> plain closed.
>

We don't use blackholes.us although I'll take a look at it.  About 50% of
our incoming spam is blocked by the blacklist servers we do use.

Ted

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: SpamAssassin-Milter accuracy...

[Louis LeBlanc]

On 01/04/05 05:17 PM, Matthias Buelow sat at the `puter and typed:
> Louis LeBlanc wrote:
> 
> > Use with care.  Some spam rbls are overly zealous, and often block out
> > whole netblocks just because one IP has been reported as an offender.
> 
> And all dialup networks.  Which can lead to the bizarre situation that 
> if you're relaying through your mail server from a dialup IP, and mail 
> goes thru SA, you'll get a high score.  There're several ways to prevent 
> this from happening, of course, for example, to run an extra smtpd on a 
> nonstandard port that doesn't push mails through SpamAssassin, or just 
> to disable the damn RBL stuff in the SA config (I did both, greylisting 
> is more effective than the suspicious RBL stuff anyways).

This includes most dynamically allocated IP blocks.  The only way to
avoid getting tagged and/or outright rejected by some networks is to
relay through the ISPs relay.

It's because of this that I don't use the spamblock RBLs at the MTA
level.  SA works almost perfectly with it's own clearing house checks
(NJABL, SORBS, SPAMCOP, etc.) and modifies the score for each.  I've
dug up some recipes that will further compound scores for multiple of
these clearing houses too, so you get bonus points for getting
reported to 3 or more :)

I do use the blackholes (check http://blackholes.us) at the MTA, since
rejecting mail outright from Asian (and a few African) countries has
reduced my spam intake by about 80%, without reducing my legitimate
mail by a single message.  Since I'm not running a service for other
people, and I carefully choose the blackhole domains I use, it's not a
problem for me.  Of course, that may not be an option for you.
Someday I'll stop this practice, but for now some of my doors are just
plain closed.

Lou
-- 
Louis LeBlanc   [EMAIL PROTECTED]
Fully Funded Hobbyist, KeySlapper Extrordinaire :)
http://www.keyslapper.org ԿԬ

Volley Theory:
  It is better to have lobbed and lost than never to have lobbed at all.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: SpamAssassin-Milter accuracy...

[Matthias Buelow]

Louis LeBlanc wrote:
Use with care.  Some spam rbls are overly zealous, and often block out
whole netblocks just because one IP has been reported as an offender.
And all dialup networks.  Which can lead to the bizarre situation that 
if you're relaying through your mail server from a dialup IP, and mail 
goes thru SA, you'll get a high score.  There're several ways to prevent 
this from happening, of course, for example, to run an extra smtpd on a 
nonstandard port that doesn't push mails through SpamAssassin, or just 
to disable the damn RBL stuff in the SA config (I did both, greylisting 
is more effective than the suspicious RBL stuff anyways).
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: SpamAssassin-Milter accuracy...

[Louis LeBlanc]

On 01/03/05 08:34 PM, Martin Hepworth sat at the `puter and typed:
> Eric
> 
> you'll prob need to retrain the bayes filters ( or a good starter at
> www.fsl.com/support).
> 
> also alot of rules from the www.rulesemporium.com/rules.html can be useful.

I believe that's actually www.rulesemporium.com/rules.htm - the .html
is 404.

> Might want to look at some of the RBL.s and esp the URI rbl provided
> by surbl.org and built into SA3.x

Use with care.  Some spam rbls are overly zealous, and often block out
whole netblocks just because one IP has been reported as an offender.

> Could ask on the sa-user list

You have to subscribe - the list is now closed because the nature of
the traffic necessitates piping the list mail around SA.  Because of
this, spammers always knew they could get by spamassassin by sending
to the list.

> and backup the config:-)

Definitely.  And you might also want to keep a spam "sampler" around
for just such a case.  This can be used to get your bayes learner back
up to speed a little quicker.  IIRC, the bayes learner needs a minimum
number of messages to learn from before it will kick in and start
working.

Lou
-- 
Louis LeBlanc   [EMAIL PROTECTED]
Fully Funded Hobbyist, KeySlapper Extrordinaire :)
http://www.keyslapper.org ԿԬ

Hlade's Law:
  If you have a difficult task, give it to a lazy person --
  they will find an easier way to do it.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: SpamAssassin-Milter accuracy...

[Martin Hepworth]

Eric

you'll prob need to retrain the bayes filters ( or a good starter at
www.fsl.com/support).

also alot of rules from the www.rulesemporium.com/rules.html can be useful.

Might want to look at some of the RBL.s and esp the URI rbl provided
by surbl.org and built into SA3.x

Could ask on the sa-user list

and backup the config:-)

--
Martin


On Mon, 3 Jan 2005 11:52:25 -0600, Eric F Crist
<[EMAIL PROTECTED]> wrote:
> Hello list,
> 
> I recently had to rebuild my server (bad surge protector, all hardware
> died).  I've reinstalled spamass-milter from ports, but I don't
> remember what I put in my old local.cf file for it to work so well
> before.  I've pretty much got the base config file.  Can some of you
> share your local.cf files with me, so I can figure out what I'm
> missing?  I used to have maybe one or two emails get through a day, now
> I'm getting about 20-30 getting through spamassassin, of those, 15-20
> are being caught by Apple's Mail.app.
> 
> Thanks.
> 
> ___
> Eric F Crist  "I am so smart, S.M.R.T!"
> Secure Computing Networks  -Homer J Simpson
> 
> 
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: spamassassin port not reading local.cf?

[Ruben de Groot]

On Tue, Nov 09, 2004 at 10:16:58AM -0500, Rohit Kumar Mehta typed:
> 
> Hi Toomas I have this same problem Amavisd-new and SA 3.0.
> I think the problem is that SA is invoked through amavisd (not spamc or
> spamassassin).
> I hope I do not have to make all my local changes through amavisd.conf.
> Please do let me know if you discover another way.

I suffered the same problem when using MIMEDefang and SA. My "solution"
was to run spamass-milter instead. But that sort of limits you to 
sendmail as an MTA :-)

Ruben

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: Spamassassin

[Eric Crist]

It is possible the default install on RedHat has a lower 'score'
necessary for it to be flagged as spam.  You can set this in the
configuration file.

Eric F Crist
President
AdTech Integrated Systems, Inc
(612) 998-3588



> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Chris Sechiatano
> Sent: Monday, June 21, 2004 12:04 PM
> To: [EMAIL PROTECTED]
> Subject: Spamassassin
>
>
> Hi,
>
> I just converted my RedHat box to BSD 5.2.1 and installed
> Spamassassin with Sendmail and Procmail.  This is the same
> configuration I had on the RedHat machine, but Spamassassin
> seems to not catch as much spam as it did before. I get so
> much more junk in my inbox and they only get one or two hits
> with Spamassassin.
>
> Anybody have any ideas on what may be happening?
>
> --
> Chris Sechiatano
> [EMAIL PROTECTED]
> www.chris-s.com
>
> PGP Key 0x0021EFA0
>
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/free> bsd-questions
>
> To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"
>


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: Spamassassin

[Rajamani, Rajarajan (Rajarajan)]

I had a quick question regarding this.
If I use sa-learn as root, does it learn just
for the root account or on a system wide basis.

Thanks

RR


-Original Message-
From: Rafi Jacoby [mailto:[EMAIL PROTECTED]
Sent: Monday, June 21, 2004 1:38 PM
To: [EMAIL PROTECTED]
Subject: Re: Spamassassin


> Hi,
>
> I just converted my RedHat box to BSD 5.2.1 and installed Spamassassin
> with
> Sendmail and Procmail.  This is the same configuration I had on the RedHat
> machine, but Spamassassin seems to not catch as much spam as it did
> before.
> I get so much more junk in my inbox and they only get one or two hits with
> Spamassassin.
>
> Anybody have any ideas on what may be happening?

If you were using the Bayes functionality, it won't kick in till you feed
it 250 or 300 spams (don't remember #).

That definitely made a big difference for me.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Spamassassin

[Rafi Jacoby]

> Hi,
>
> I just converted my RedHat box to BSD 5.2.1 and installed Spamassassin
> with
> Sendmail and Procmail.  This is the same configuration I had on the RedHat
> machine, but Spamassassin seems to not catch as much spam as it did
> before.
> I get so much more junk in my inbox and they only get one or two hits with
> Spamassassin.
>
> Anybody have any ideas on what may be happening?

If you were using the Bayes functionality, it won't kick in till you feed
it 250 or 300 spams (don't remember #).

That definitely made a big difference for me.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Spamassassin

[Remko Lodder]

Chris Sechiatano wrote:
Hi,
I just converted my RedHat box to BSD 5.2.1 and installed Spamassassin with
Sendmail and Procmail.  This is the same configuration I had on the RedHat
machine, but Spamassassin seems to not catch as much spam as it did before.
I get so much more junk in my inbox and they only get one or two hits with
Spamassassin.  

Anybody have any ideas on what may be happening?
Hi,
Spammers get more smart... My SA is well trained and still i recieve a 
couple of spam messages a day (50/50 almost)
But you can train SA by using sa-learn.. and use the bayesian filtering...

Did you use that on RedHat as well?
--
Kind regards,
Remko Lodder   |[EMAIL PROTECTED]
Reporter DSINet|[EMAIL PROTECTED]
Projectleader Mostly-Harmless  |[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: spamassassin, clamav with sendmail - not scanning local mails.

[Warren Block]

On Mon, 14 Jun 2004, Rajamani, Rajarajan (Rajarajan) wrote:
I have installed the spamassassin milter and the clam av milter ports
and have made the following changes to the freebsd.mc file.
INPUT_MAIL_FILTER(`spamassassin', `S=local:/var/run/spamass-milter.sock,
F=,T=C:15m;S:4m;R:4m;E:10m')
INPUT_MAIL_FILTER(`clmilter',`S=local:/var/run/clamav/clmilter.sock,
F=,T=S:4m;R:4m')dnl
define(`confINPUT_MAIL_FILTERS', `spamassassin, clmilter')
then restarted sendmail by # make, # make install,# make restart, #
newaliases
Now I am noticing that all mails that are being sent directly to my
machine are tagged properly both for spam and viruses.  Mails that are
sent from one account to another are not being scanned.
Am I missing something. How do I force sendmail to use the mail
filters for local mails. Any info would be appreciated.
See the options for clamav-milter(5).  In particular, --local and 
--outgoing; these are set in /etc/rc.conf.  Spamassassin may have 
similar options.

-Warren Block * Rapid City, South Dakota USA
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: spamassassin, clamav with sendmail - not scanning local mails .

[Rajamani, Rajarajan (Rajarajan)]

>>  Since I use fetchmail/fetchyahoo/gotmail to retreive my
>>  ISP/yahoo/hotmail accounts (where I get most spam), the mails
>>  delivered to my mbox are not scanned by either clamd or spamd. I
>>  checked that these tools are having the appropriate switches to
>>  forward the pop'd mails to my account instead of putting it directly
>>  into the mbox.
>>
>>  Am I missing something. How do I force sendmail to use the mail
>>  filters for local mails. Any info would be appreciated.
>
> I think you will have to configure your fetching tools to inject
> messages to localhost port 25 or 587 instead of execing sendmail. 
> Fetchmail should do this by default (it will fall back to execing
> sendmil if the port isn't open); not sure about the others.
>
> -- 
>   Dan Nelson
>   [EMAIL PROTECTED]

That thought struck me as soon as I posted my question.
Your hunch is right. When I used fetchmail to
redirect the mail to port 25 it worked (earlier it was
piping it to procmail directly - my mistake). Now
I have to figure out how to do the same with fetchyahoo/gotmail.

Thanks

Rajarajan.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: spamassassin, clamav with sendmail - not scanning local mails.

[Dan Nelson]

In the last episode (Jun 14), Rajamani, Rajarajan (Rajarajan) said:
> I have installed the spamassassin milter and the clam av milter ports
> and have made the following changes to the freebsd.mc file.
> 
> INPUT_MAIL_FILTER(`spamassassin', `S=local:/var/run/spamass-milter.sock, 
> F=,T=C:15m;S:4m;R:4m;E:10m')
> INPUT_MAIL_FILTER(`clmilter',`S=local:/var/run/clamav/clmilter.sock, 
> F=,T=S:4m;R:4m')dnl
> define(`confINPUT_MAIL_FILTERS', `spamassassin, clmilter')
> 
> then restarted sendmail by # make, # make install,# make restart, #
> newaliases
> 
> Now I am noticing that all mails that are being sent directly to my
> machine are tagged properly both for spam and viruses.  Mails that
> are sent from one account to another are not being scanned.

I think this is because milters only act on things received via the TCP
port.  If you pipe a message into /usr/bin/sendmail or /usr/bin/mail,
that all gets skipped and the sendmail process dumps it directly into
the queue directory for delivery.
 
> Since I use fetchmail/fetchyahoo/gotmail to retreive my
> ISP/yahoo/hotmail accounts (where I get most spam), the mails
> delivered to my mbox are not scanned by either clamd or spamd. I
> checked that these tools are having the appropriate switches to
> forward the pop'd mails to my account instead of putting it directly
> into the mbox.
>
> Am I missing something. How do I force sendmail to use the mail
> filters for local mails. Any info would be appreciated.

I think you will have to configure your fetching tools to inject
messages to localhost port 25 or 587 instead of execing sendmail. 
Fetchmail should do this by default (it will fall back to execing
sendmil if the port isn't open); not sure about the others.

-- 
Dan Nelson
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: spamassassin+filtering with kmail

[Admin]

Think I got it.
Not that I claim I know what I'm doing, but at last I got it somewhat working.
It's now filtering my " Test Spam messages " and ONLY those, to the desired 
Spamfolder :-), but I doubt it's filtering on the number of  " stars " as I 
wants it to do.

What I did was the following steps :

Create a new filter and rename it to Spam.
Setting Filter Criteria to match any of the following
X-Spam-Flag containsYES
X-Spam-Scorecontains*

Filter Actions :
file into folderSpam

Advanced Options
x   Apply this filter to incoming messages
x   on manual filtering
x   If this filter matches, stop processing here.

Still intersted in tips and hints on how to get this properly working :-)

/ Regards Hasse.

On Friday 21 May 2004 17.37, Hasse wrote:
> Hi everybody.
>
> FreeBSD 4.10-PRERELEASE #0
>
> Just installed MIMEDefang+SpamAssassin+ClamAV on my mailserver,
> and everything is running fine but don't seem to get spamfiltering  on " *
> " to work with KMail.
> My filter looks like this : X-Spam-Score  contains  *Action: File in
> folder Spam
> Tried different options, but it either moves ALL or NONE to the Spam
> folder. I have changed the report order in mimedefang filter so the stars
> come first. Looks kike this :
> X-Spam-Score:  (1000.999)
>
> Any hints ?
>
> / Hasse.
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: SpamAssassin

[Kevin Kinsey]

On Mon, Mar 29, 2004 at 12:31:25PM -0500, Bart Silverstrim wrote:
> Question...Is anyone else running amavisd-new with spamassassin from 
> ports?
>

Just started about a week ago, with dual-Sendmail setup + SA and 
ClamAV.
 
> If so, where/how should I be updating or altering the spamassassin 
> rules?
> 
> I'd like to try updating some of the rules from the spamassassin site, 
> but didn't know where the ports version was putting the rulesets...
> a) what directory should I put them into?
> b) is there a config file I'd have to alter to get spamassassin to use 
> them?
> c) can I just plonk new SA files into that directory and they would be 
> used automatically?
> d) should I just wait until the ports version of SA is updated to get 
> new rules, or does ports have the newer rules integrated into it?
> e) do I need to alter anything in amavisd-new to get the new rules to 
> work?
> 
> Thanks!
> -Bart
> 

Most everything of the rules/config nature is plonked into
/usr/local/etc/spamassassin/.  I'm not so sure about adding
to those files, but if you're brave, you might go ahead.

The comments in the files might be helpful.

And, there's this, from /usr/local/share/spamassassin/user_prefs.template:

# SpamAssassin user preferences file.  See 'perldoc Mail::SpamAssassin::Conf'  
 
# for details of what can be tweaked.

HTH,

Kevin Kinsey

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Spamassassin: sa-learn scope question ??

[Dan Nelson]

In the last episode (Mar 09), Pat said:
> I was wondering exactly what the scope is on sa-learn.
> what i mean by this is:
> if i run sa-learn as root, does it get applied to the
> global spam-assassin ruleset or only for my user?
> 
> do all my users need to run sa-learn on their spam/ham
> files or does it affect everyone if only I do it?

It's an either-or thing.  You can't have both a private and a public
bayes db.  By default, every user has a private bayes database, in
~/.spamassassin.  If you want them to share a common one, add something
like this to your local.cf:

# Note this is a basename, not a path
bayes_path /usr/tmp/spamassassin/bayes
bayes_file_mode 0777

, which will tell spamassassin to use files in /usr/tmp/spamassassin
(or pick some other directory writable by everyone), and to create the
files so that everyone can update them.
 
-- 
Dan Nelson
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"