Exim has stopped using SpamAssassin
I've just noticed that for the last month Exim does not appear to have been using SpamAssassin to check incoming emails. Previously all my incoming emails contained the following headers: X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: X-Spam-Checker-Version: X-Spam-Level: X-Spam-Status: But I'm not seeing any of them now. I've compared things with a ZFS snapshot from a time when it was working and both Exim and SpamAssassin are the same versions as before and there has been no changes in /usr/local/etc/exim/configure or /usr/local/etc/exim/sa-exim.conf. Current versions are: FreeBSD curlew.lan 9.1-RELEASE-p4 FreeBSD 9.1-RELEASE-p4 #0: Mon Jun 17 11:42:37 UTC 2013 root@amd64 builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 exim-sa-exim-4.80.1+4.2_2 p5-Mail-SpamAssassin-3.3.2_8 perl-5.14.4 (was 5.14.2_3 when SpamAssassin was working) I've re-installed Exim and SpamAssassin using the same make options as before to see if that had any effect but still no joy. I've set SAEximDebug to 1 in sa-exim.conf but there's still nothing in the logs to help. Any suggestions where I should look next? -- Mike Clarke ___ 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
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
Re: Spamassassin not working after update of Perl
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
Re: Spamassassin not working after update of Perl
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
Spamassassin not working after update of Perl
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
Re: Spamassassin not working after update of Perl
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-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions
Re: Spamassassin not working after update of Perl
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
On 23 Jun 2011, at 21:37, Matthew Seaman m.sea...@infracaninophile.co.uk 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
sendmail || mail and SpamAssassin
This is the other question: how do I get the builtin SpanAssassin working? sendmail is working and I've built mail/p5-SpamAssassin [or whatever]. Still getting spam. Also, when /etc/mail/* starts up, on the console I notice a warning saying something like Can't find Xspamassassin All lower case after the first X. I keep getting Spanish language spam message and other junk or spam. I just need to figure out howto get the builtin or the port that kills this krap. thanks for any insights, gary -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Journey Toward the Dawn, E-Book: http://www.thought.org The 8.51a release of Jottings: http://jottings.thought.org ___ 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
spamassassin config help
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. ___ 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
On Wed, 17 Nov 2010 15:42:51 + (UTC) AN a...@neu.net 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
Re: spamassassin config help
2010/11/17 AN a...@neu.net: 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
[Solved] Re: SpamAssassin 3.3.0/sa-update problem
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
SpamAssassin 3.3.0/sa-update problem
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.485 [31554] dbg: logger: adding facilities: all Feb 13 15:32:07.486 [31554] dbg: logger: logging level is DBG Feb 13 15:32:07.486 [31554] dbg: generic: SpamAssassin version 3.3.0 Feb 13 15:32:07.486 [31554] dbg: generic: Perl 5.010001, PREFIX=/usr/local, DEF_RULES_DIR=/usr/local/share/spamassassin, LOCAL_RULES_DIR=/usr/local/etc/mail/spamassassin, LOCAL_STATE_DIR=/var/db/spamassassin Feb 13 15:32:07.486 [31554] dbg: config: timing enabled Feb 13 15:32:07.487 [31554] dbg: config: score set 0 chosen. Feb 13 15:32:07.534 [31554] dbg: dns: is Net::DNS::Resolver available? yes Feb 13 15:32:07.534 [31554] dbg: dns: Net::DNS version: 0.66 Feb 13 15:32:07.535 [31554] dbg: generic: sa-update version svn897929 Feb 13 15:32:07.535 [31554] dbg: generic: using update directory: /var/db/spamassassin/3.003000 Feb 13 15:32:07.839 [31554] dbg: diag: perl platform: 5.010001 freebsd Feb 13 15:32:07.839 [31554] dbg: diag: [...] module installed: Digest::SHA1, version 2.12 Feb 13 15:32:07.839 [31554] dbg: diag: [...] module installed: HTML::Parser, version 3.64 Feb 13 15:32:07.839 [31554] dbg: diag: [...] module installed: Net::DNS, version 0.66 Feb 13 15:32:07.839 [31554] dbg: diag: [...] module installed: NetAddr::IP, version 4.027 Feb 13 15:32:07.839 [31554] dbg: diag: [...] module installed: Time::HiRes, version 1.9719 Feb 13 15:32:07.839 [31554] dbg: diag: [...] module installed: Archive::Tar, version 1.56 Feb 13 15:32:07.839 [31554] dbg: diag: [...] module installed: IO::Zlib, version 1.10 Feb 13 15:32:07.840 [31554] dbg: diag: [...] module installed: Digest::SHA1, version 2.12 Feb 13 15:32:07.840 [31554] dbg: diag: [...] module installed: MIME::Base64, version 3.09 Feb 13 15:32:07.840 [31554] dbg: diag: [...] module installed: DB_File, version 1.82 Feb 13 15:32:07.840 [31554] dbg: diag: [...] module installed: Net::SMTP, version 2.31 Feb 13 15:32:07.840 [31554] dbg: diag: [...] module installed: Mail::SPF, version v2.007 Feb 13 15:32:07.840 [31554] dbg: diag: [...] module installed: IP::Country::Fast, version 604.001 Feb 13 15:32:07.840 [31554] dbg: diag: [...] module installed: Razor2::Client::Agent, version 2.84 Feb 13 15:32:07.840 [31554] dbg: diag: [...] module installed: Net::Ident, version 1.20 Feb 13 15:32:07.840 [31554] dbg: diag: [...] module installed: IO::Socket::INET6, version 2.56 Feb 13 15:32:07.840 [31554] dbg: diag: [...] module installed: IO::Socket::SSL, version 1.31 Feb 13 15:32:07.840 [31554] dbg: diag: [...] module installed: Compress::Zlib, version 2.015 Feb 13 15:32:07.840 [31554] dbg: diag: [...] module installed: Mail::DKIM, version 0.37 Feb 13 15:32:07.840 [31554] dbg: diag: [...] module installed: DBI, version 1.609 Feb 13 15:32:07.840 [31554] dbg: diag: [...] module installed: Getopt::Long, version 2.38 Feb 13 15:32:07.841 [31554] dbg: diag: [...] module installed: LWP::UserAgent, version 5.834 Feb 13 15:32:07.841 [31554] dbg: diag: [...] module installed: HTTP::Date, version 5.831 Feb 13 15:32:07.841 [31554] dbg: diag: [...] module installed: Encode::Detect, version 1.01 Feb 13 15:32:07.842 [31554] dbg: gpg: Searching for 'gpg' Feb 13 15:32:07.842 [31554] dbg: util: current PATH is: /sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin Feb 13 15:32:07.842 [31554] dbg: util: executable for gpg was found at /usr/local/bin/gpg Feb 13 15:32:07.842 [31554] dbg: gpg: found /usr/local/bin/gpg Feb 13 15:32:07.843 [31554] dbg: gpg: release trusted key id list: 5E541DC959CB8BAC7C78DFDC4056A61A5244EC45 26C900A46DD40CD5AD24F6D7DEE01987265FA05B 0C2B1D7175B852C64B3CDC716C55397824F434CE Feb 13 15:32:07.848 [31554] dbg: channel: attempting channel updates.spamassassin.org Feb 13 15:32:07.848 [31554] dbg: channel: update directory /var/db/spamassassin/3.003000/updates_spamassassin_org Feb 13 15:32:07.848 [31554] dbg: channel: channel cf file /var/db/spamassassin/3.003000/updates_spamassassin_org.cf Feb 13 15:32:07.848 [31554] dbg: channel: channel pre file /var/db/spamassassin/3.003000/updates_spamassassin_org.pre 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. Regards, Marco -- Use an accordion. Go to jail
Re: spamassassin Y2010 bug
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
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
spamassassin - Y2K10 bug
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 -- Jerry ges...@yahoo.com |=== |=== |=== |=== | Just saying no prevents teenage pregnancy the way Have a nice day cures chronic depression. Faye Wattleton http://en.wikipedia.org/wiki/Faye_Wattleton ___ 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 - Y2K10 bug
On Sun, 3 Jan 2010 06:19:55 -0500 Jerry ges...@yahoo.com 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 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 Y2010 bug
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
On Sun, 03 Jan 2010 20:10:19 +
Matthew Seaman m.sea...@infracaninophile.co.uk 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
On Sun, 03 Jan 2010 20:10:19 +
Matthew Seaman m.sea...@infracaninophile.co.uk 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
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 wrote:
On Sun, 03 Jan 2010 20:10:19 +
Matthew Seaman m.sea...@infracaninophile.co.uk 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
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-perlid=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
On Sat, 02 Jan 2010 13:15:25 + Matthew Seaman m.sea...@infracaninophile.co.uk 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
On Jan 2, 2010, at 8:45 AM, RW wrote: On Sat, 02 Jan 2010 13:15:25 + Matthew Seaman m.sea...@infracaninophile.co.uk 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
spamassassin Y2010 bug
I've submitted a PR for this, but email administrators who use SpamAssassin may wish to take immediate action. There is a SpamAssassin rule which treats messages with dates after 2009 as far in the future. This adds about 3 points to the SA score, so is very substantial. I've posted details and links here http://jpgoldberg.blogspot.com/2010/01/sky-is-falling-first-y2010-bug.html But as an immediate, though possibly temporary, work around I would recommend just adding score FH_DATE_PAST_20XX 0 to your own local.cf file to disable the rule. 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. But if you aren't willing to wait or you don't use sa-update, I recommend the above workaround. 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
On Fri, 1 Jan 2010 15:05:54 -0600 Jeffrey Goldberg jeff...@goldmark.org 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 Y2010 bug
On Jan 1, 2010, at 5:19 PM, RW wrote: On Fri, 1 Jan 2010 15:05:54 -0600 Jeffrey Goldberg jeff...@goldmark.org 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
On Fri, 1 Jan 2010 18:05:59 -0600 Jeffrey Goldberg jeff...@goldmark.org 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 question
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
On Mon, 23 Nov 2009 02:30:47 + Marwan Sultan dead_l...@hotmail.com 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 unixuser or by starting it directly, with spamd_user=unixuser, 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 unixuser --virtual-config-dir=/var/db/spamassassin/conf/%u and then using: spamc -u vuser in the above unixuser is the unprivileged user and vuser 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
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
RE: spamassassin question
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 question
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
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/Perl eating enormous amounts of memory?
On Mon, 02 Mar 2009 17:21:53 -0800, Andrew Moran snee...@mac.com 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?
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?
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?
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?
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: snip 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?
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: snip 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 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/Perl eating enormous amounts of memory?
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?
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
SpamAssassin/Perl eating enormous amounts of memory?
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 The error messages I get when this is happening look like: swap_pager_getswapspace(16): failed swap_pager_getswapspace(16): failed swap_pager_getswapspace(16): failed swap_pager_getswapspace(16): failed pid 6035 (perl5.8.9), uid 1030, was killed: out of swap space Obviously I have a memory leak somewhere, but I can't tell where. I upgraded to the latest port (synced and compiled today). I spent the day doing the portupgrade -f R r p5-Mail-SpamAssassin to make sure everything was rebuilt. But alas, the problem persists. 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. --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: Problems upgrading SpamAssassin
On Mon, 16 Feb 2009 09:58:37 -0800 Tankko tan...@gmail.com wrote: I am having problems up grading SpamAssassin. The get the following errors when I do portupgrade. I hand corrected the first error by following the instructions listed below, then this error showed. Before I go though and hand correct these one by one, I thought I'd ask if I was doing something wrong. P.S. I ran perl-after-upgrade after upgrading perl. Did you run perl-after-upgrade -f ? Without '-f' it just tells you what it would do... Manfred -- Manfred Usselmann usselman...@icg-online.de ___ 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
Problems upgrading SpamAssassin
I am having problems up grading SpamAssassin. The get the following errors when I do portupgrade. I hand corrected the first error by following the instructions listed below, then this error showed. Before I go though and hand correct these one by one, I thought I'd ask if I was doing something wrong. P.S. I ran perl-after-upgrade after upgrading perl. Thanks === Installing for p5-Socket6-0.23 === p5-Socket6-0.23 depends on file: /usr/local/bin/perl5.8.9 - found === Generating temporary packing list === Checking if net/p5-Socket6 already installed === p5-Socket6-0.23 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 net/p5-Socket6 without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** Error code 1 Stop in /usr/ports/net/p5-Socket6. *** Error code 1 Stop in /usr/ports/net/p5-IO-INET6. *** Error code 1 Stop in /usr/ports/dns/p5-Net-DNS. *** Error code 1 Stop in /usr/ports/dns/p5-Net-DNS. *** Error code 1 Stop in /usr/ports/mail/p5-Mail-SpamAssassin. *** Error code 1 Stop in /usr/ports/mail/p5-Mail-SpamAssassin. ___ 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: Problems upgrading SpamAssassin
On Monday 16 February 2009 08:58:37 Tankko wrote: I am having problems up grading SpamAssassin. The get the following errors when I do portupgrade. I hand corrected the first error by following the instructions listed below, then this error showed. Before I go though and hand correct these one by one, I thought I'd ask if I was doing something wrong. P.S. I ran perl-after-upgrade after upgrading perl. We need the line that says: === p5-IO-INET6 depends on file That line is probably faulty. Also please list: grep ^PERL /etc/make.conf === Installing for p5-Socket6-0.23 === p5-Socket6-0.23 depends on file: /usr/local/bin/perl5.8.9 - found === Generating temporary packing list === Checking if net/p5-Socket6 already installed === p5-Socket6-0.23 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 net/p5-Socket6 without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** Error code 1 Stop in /usr/ports/net/p5-Socket6. *** Error code 1 Stop in /usr/ports/net/p5-IO-INET6. -- 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: Problems upgrading SpamAssassin
We need the line that says: === p5-IO-INET6 depends on file That line is probably faulty. This is the closest thing I can find to p5-IO-INET6 in the build output. === Installing for p5-Net-DNS-0.65 === p5-Net-DNS-0.65 depends on executable: ipcount - found === p5-Net-DNS-0.65 depends on file: /usr/local/lib/perl5/site_perl/5.8.9/Digest/HMAC_MD5.pm - found === p5-Net-DNS-0.65 depends on file: /usr/local/lib/perl5/site_perl/5.8.9/IO/Socket/INET6.pm - not found ===Verifying install for /usr/local/lib/perl5/site_perl/5.8.9/IO/Socket/INET6.pm in /usr/ports/net/p5-IO-INET6 === Extracting for p5-IO-Socket-INET6-2.56 = MD5 Checksum OK for IO-Socket-INET6-2.56.tar.gz. = SHA256 Checksum OK for IO-Socket-INET6-2.56.tar.gz. === p5-IO-Socket-INET6-2.56 depends on file: /usr/local/bin/perl5.8.9 - found === Patching for p5-IO-Socket-INET6-2.56 === p5-IO-Socket-INET6-2.56 depends on file: /usr/local/bin/perl5.8.9 - found === p5-IO-Socket-INET6-2.56 depends on file: /usr/local/lib/perl5/site_perl/5.8.9/mach/Socket6.pm - not found ===Verifying install for /usr/local/lib/perl5/site_perl/5.8.9/mach/Socket6.pm in /usr/ports/net/p5-Socket6 === Extracting for p5-Socket6-0.23 = MD5 Checksum OK for Socket6-0.23.tar.gz. = SHA256 Checksum OK for Socket6-0.23.tar.gz. === p5-Socket6-0.23 depends on file: /usr/local/bin/perl5.8.9 - found === Patching for p5-Socket6-0.23 === p5-Socket6-0.23 depends on file: /usr/local/bin/perl5.8.9 - found === p5-Socket6-0.23 depends on file: /usr/local/bin/perl5.8.9 - found === Configuring for p5-Socket6-0.23 Also please list: grep ^PERL /etc/make.conf This is what is listed in /etc/make.conf # added by use.perl 2009-02-16 09:12:57 PERL_VER=5.8.9 PERL_VERSION=5.8.9 ___ 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: Problems upgrading SpamAssassin
On Monday 16 February 2009 10:04:43 Tankko wrote: We need the line that says: === p5-IO-INET6 depends on file That line is probably faulty. This is the closest thing I can find to p5-IO-INET6 in the build output. === Installing for p5-Net-DNS-0.65 === p5-Net-DNS-0.65 depends on executable: ipcount - found === p5-Net-DNS-0.65 depends on file: /usr/local/lib/perl5/site_perl/5.8.9/Digest/HMAC_MD5.pm - found === p5-Net-DNS-0.65 depends on file: /usr/local/lib/perl5/site_perl/5.8.9/IO/Socket/INET6.pm - not found ===Verifying install for /usr/local/lib/perl5/site_perl/5.8.9/IO/Socket/INET6.pm in /usr/ports/net/p5-IO-INET6 === Extracting for p5-IO-Socket-INET6-2.56 = MD5 Checksum OK for IO-Socket-INET6-2.56.tar.gz. = SHA256 Checksum OK for IO-Socket-INET6-2.56.tar.gz. === p5-IO-Socket-INET6-2.56 depends on file: /usr/local/bin/perl5.8.9 - found === Patching for p5-IO-Socket-INET6-2.56 === p5-IO-Socket-INET6-2.56 depends on file: /usr/local/bin/perl5.8.9 - found === p5-IO-Socket-INET6-2.56 depends on file: /usr/local/lib/perl5/site_perl/5.8.9/mach/Socket6.pm - not found If: # grep 'Socket6.pm' /var/db/pkg/p5-Socket6*/+CONTENTS gives something with site_perl/5.8.8, you: pkg_delete -f p5-Socket6-* Then go back to building what you were building. If the output is empty, then still do the pkg_delete -f, then install p5-Socket6. Then run the above command again. If it's still empty, the port doesn't install Socket6.pm and p5-IO-Socket-INET6 port is broken because of it OR the pkg-plist for p5-Socket6 is broken. Either way a send-pr(1) is needed. If the output is anything else, please list here. This is what is listed in /etc/make.conf # added by use.perl 2009-02-16 09:12:57 PERL_VER=5.8.9 PERL_VERSION=5.8.9 That's correct. -- 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: Problems upgrading SpamAssassin
If: # grep 'Socket6.pm' /var/db/pkg/p5-Socket6*/+CONTENTS gives something with site_perl/5.8.8, you: pkg_delete -f p5-Socket6-* Then go back to building what you were building. If the output is empty, then still do the pkg_delete -f, then install p5-Socket6. Then run the above command again. If it's still empty, the port doesn't install Socket6.pm and p5-IO-Socket-INET6 port is broken because of it OR the pkg-plist for p5-Socket6 is broken. Either way a send-pr(1) is needed. If the output is anything else, please list here. I ran the grep, and it did come back with site_perl/5.8.8, so I ran: pkg_delete -f p5-Socket6-* pkgdb -F portupgrade p5-Mail-SpamAssassin and I get the following errors: ---cut--- Writing Makefile for IO::Socket::INET6 === Building for p5-IO-Socket-INET6-2.56 cp lib/IO/Socket/INET6.pm blib/lib/IO/Socket/INET6.pm Manifying blib/man3/IO::Socket::INET6.3 === Installing for p5-IO-Socket-INET6-2.56 === p5-IO-Socket-INET6-2.56 depends on file: /usr/local/lib/perl5/site_perl/5.8.9/mach/Socket6.pm - found === p5-IO-Socket-INET6-2.56 depends on file: /usr/local/bin/perl5.8.9 - found === p5-IO-Socket-INET6-2.56 depends on file: /usr/local/bin/perl5.8.9 - found === Generating temporary packing list === Checking if net/p5-IO-INET6 already installed === p5-IO-Socket-INET6-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 net/p5-IO-INET6 without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** Error code 1 Stop in /usr/ports/net/p5-IO-INET6. *** Error code 1 Stop in /usr/ports/dns/p5-Net-DNS. *** Error code 1 Stop in /usr/ports/dns/p5-Net-DNS. *** Error code 1 Stop in /usr/ports/mail/p5-Mail-SpamAssassin. *** Error code 1 Stop in /usr/ports/mail/p5-Mail-SpamAssassin. ___ 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: Problems upgrading SpamAssassin
On Monday 16 February 2009 11:19:35 Tankko wrote: If: # grep 'Socket6.pm' /var/db/pkg/p5-Socket6*/+CONTENTS gives something with site_perl/5.8.8, you: pkg_delete -f p5-Socket6-* Then go back to building what you were building. If the output is empty, then still do the pkg_delete -f, then install p5-Socket6. Then run the above command again. If it's still empty, the port doesn't install Socket6.pm and p5-IO-Socket-INET6 port is broken because of it OR the pkg-plist for p5-Socket6 is broken. Either way a send-pr(1) is needed. If the output is anything else, please list here. I ran the grep, and it did come back with site_perl/5.8.8, so I ran: pkg_delete -f p5-Socket6-* pkgdb -F portupgrade p5-Mail-SpamAssassin and I get the following errors: ---cut--- Writing Makefile for IO::Socket::INET6 === Building for p5-IO-Socket-INET6-2.56 cp lib/IO/Socket/INET6.pm blib/lib/IO/Socket/INET6.pm Manifying blib/man3/IO::Socket::INET6.3 === Installing for p5-IO-Socket-INET6-2.56 === p5-IO-Socket-INET6-2.56 depends on file: /usr/local/lib/perl5/site_perl/5.8.9/mach/Socket6.pm - found === p5-IO-Socket-INET6-2.56 depends on file: /usr/local/bin/perl5.8.9 - found === p5-IO-Socket-INET6-2.56 depends on file: /usr/local/bin/perl5.8.9 - found === Generating temporary packing list === Checking if net/p5-IO-INET6 already installed === p5-IO-Socket-INET6-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 net/p5-IO-INET6 without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. Same issue, different package. Apparently perl-after-upgrade didn't do it's job. I would: portupgrade -f p5-* Then go back to upgrade spamassasin. -- 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: Problems upgrading SpamAssassin
so do make deinstall and make install /usr/ports/net/p5-Socket6 === Installing for p5-Socket6-0.23 === p5-Socket6-0.23 depends on file: /usr/local/bin/perl5.8.9 - found === Generating temporary packing list === Checking if net/p5-Socket6 already installed === p5-Socket6-0.23 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 net/p5-Socket6 without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** Error code 1 Stop in /usr/ports/net/p5-Socket6. *** Error code 1 Stop in /usr/ports/net/p5-IO-INET6. *** Error code 1 Stop in /usr/ports/dns/p5-Net-DNS. *** Error code 1 Stop in /usr/ports/dns/p5-Net-DNS. *** Error code 1 Stop in /usr/ports/mail/p5-Mail-SpamAssassin. *** Error code 1 Stop in /usr/ports/mail/p5-Mail-SpamAssassin. ___ 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 ___ 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: Problems upgrading SpamAssassin
Same issue, different package. Apparently perl-after-upgrade didn't do it's job. I would: portupgrade -f p5-* Then go back to upgrade spamassasin. -- Mel OK, this solved the problem. Everything upgrades fine now. Thank you very much for all your help. Not sure why this happened in the first place. ___ 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
all mail arriving empty - spamassassin?
After some upgrades, all mail arriving via sendmail-provmail is empty - when I actually deinstall spamassassin - the mail starts arriving again. I haven't seen posts on this topic - I wonder if anyone has a guess as to where to look for answers on this. I am guessing if there is some way of logging what spamassassin is doing... ___ 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: all mail arriving empty - spamassassin?
On Mon, 9 Feb 2009 15:43:21 -0500 David Banning da...@skytracker.ca wrote: After some upgrades, all mail arriving via sendmail-provmail is empty - when I actually deinstall spamassassin - the mail starts arriving again. I haven't seen posts on this topic - I wonder if anyone has a guess as to where to look for answers on this. There is a problem where spamassassin is dying with SIGPIPE, but returning a non-zero error code. If you are using /usr/local/bin/spamassassin (i.e. not spamd), try editing it and changing sub kill_handler to exit with a non-zero value. ___ 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: all mail arriving empty - spamassassin?
On Mon, 9 Feb 2009 21:27:01 + RW rwmailli...@googlemail.com wrote: On Mon, 9 Feb 2009 15:43:21 -0500 David Banning da...@skytracker.ca wrote: After some upgrades, all mail arriving via sendmail-provmail is empty - when I actually deinstall spamassassin - the mail starts arriving again. I haven't seen posts on this topic - I wonder if anyone has a guess as to where to look for answers on this. There is a problem where spamassassin is dying with SIGPIPE, but returning a non-zero error code. that should have been returning a zero error code If you are using /usr/local/bin/spamassassin (i.e. not spamd), try editing it and changing sub kill_handler to exit with a non-zero value. ___ 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
Autolearn=fail SpamAssassin
Hello, I just installed SpamAssassin on FreeBSD 7.1 and am encountering an error with autolearn. It always says failed when attempting to learn. I followed the documentation for setting it up but I'm wondering if I missed something. Possibly the Bayes DB was not created? Or is this something I need to do manually? Thanks for any help :) spamassassin -V SpamAssassin version 3.2.5 running on Perl version 5.8.8 X-Spam-Status: Yes, score=23.2 required=5.0 tests=FH_HELO_EQ_D_D_D_D, HELO_DYNAMIC_IPADDR,HTML_MESSAGE,MIME_HTML_ONLY,MISSING_DATE,MISSING_MID, RAZOR2_CF_RANGE_51_100,RAZOR2_CF_RANGE_E4_51_100,RAZOR2_CF_RANGE_E8_51_100, RAZOR2_CHECK,RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_SORBS_WEB,RDNS_DYNAMIC, URIBL_AB_SURBL,URIBL_BLACK,URIBL_JP_SURBL,URIBL_OB_SURBL,URIBL_WS_SURBL autolearn=failed version=3.2.5 ___ 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: Autolearn=fail SpamAssassin
Tom Stuart wrote: Hello, I just installed SpamAssassin on FreeBSD 7.1 and am encountering an error with autolearn. It always says failed when attempting to learn. See http://wiki.apache.org/spamassassin/AutolearningNotWorking ___ 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
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
.. cut ..
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
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 .. cut .. 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
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
.. cut ..
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]
Spamassassin very slow
Hi guys, Last 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. What causes spamassassin to slow? Here is my config: snippet from sendmail.mc FEATURE(`local_procmail_lmtp') . . . FEATURE(dnsbl,`all.rbl.jp')dnl dnl MAILER(local) MAILER(procmail)dnl MAILER(smtp) INPUT_MAIL_FILTER(`spamassassin',`S=local:/var/run/spamass-milter.sock, F=, T=C:15m;S:4m;R:4m;E:10m')dnl INPUT_MAIL_FILTER(`clmilter', `S=local:/var/run/clamav/clmilter.sock, F=, T=S:4m;R:4m')dnl define(`confINPUT_MAIL_FILTERS', `clmilter,spamassassin')dnl I have .procmailrc in every home directory of my mail users and it goes like this: :0fw: spamassassin.lock | /usr/local/bin/spamc :0: * ^X-Spam-Level: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\* /dev/null :0: * ^X-Spam-Status: Yes Probably-Spam I also have RulesDuJour installed and spammassassin --lint does complain about it. spamassassin process: 11894 ?? Ss 0:30.74 /usr/local/bin/spamd -c -d -r -m 20 --round-robin /var/run/spamd/spamd.pid (perl5.8.8) 11903 ?? Ss 0:06.55 /usr/local/sbin/spamass-milter -f -p /var/run/spamass-milter.sock When my mail server became slow, my mqueue grows rapidly and there are lots of spamc processes. Please help, thnx. alyd ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Spamassassin very slow
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 very slow
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 very slow
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 .. cut .. 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 [EMAIL PROTECTED] wrote: What causes spamassassin to slow? Here is my config: snippet from sendmail.mc .. cut .. 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
James Tanis wrote:
lyd mc [EMAIL PROTECTED] wrote:
What causes spamassassin to slow?
Here is my config:
snippet from sendmail.mc
.. cut ..
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: Milters or SpamAssassin plugings
Robert Davison wrote: I'm running the base Sendmail with Mailscanner and SpamAssassin from the ports. A simple question I'm installing SPF to help the fight against spam. Which is the most efficient way of doing it.Sendmail milter or the p5-Mail SpamAssassin plug-in. They both do the same, but is one a better way than the other ? Ah -- actually there is a crucial difference in the way SpamAssassin and milter-spf work. SpamAssassin uses the SPF status of a message to add to the spam score it calculates -- typically, a message which passes all the SPF checks has an approximately zero result on Spam scoring, as will a message where there is no SPF stuff available at all; but one which fails the SPF tests will get about 3 spam points. (Which means that even a message failing SPF checks can be passed as ham) milter-spf however operates in a binary fashion -- anything that fails is rejected, anything that passes is accepted. In general I prefer the SpamAssassin behaviour -- not all the world has immediately accepted SPF as a good tool against spam; there are any number of edge cases where a legitimate message can contradict what the SPF settings say (mail forwarding is a particular problem) and one of the groups that has adopted SPF most wholeheartedly are in fact, the Spammers themselves. SpamAssassin processing is however much heavier on system resources than milter-spf. 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
spamassassin and amavisd with stock sendmail
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. ___ 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
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]
Milters or SpamAssassin plugings
I'm running the base Sendmail with Mailscanner and SpamAssassin from the ports. A simple question I'm installing SPF to help the fight against spam. Which is the most efficient way of doing it.Sendmail milter or the p5-Mail SpamAssassin plug-in. They both do the same, but is one a better way than the other ? - Yahoo! for Good helps you make a difference ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Milters or SpamAssassin plugings
At 04:10 PM 4/11/2008, Robert Davison wrote: I'm running the base Sendmail with Mailscanner and SpamAssassin from the ports. A simple question I'm installing SPF to help the fight against spam. Which is the most efficient way of doing it.Sendmail milter or the p5-Mail SpamAssassin plug-in. They both do the same, but is one a better way than the other ? If you have Mailscanner and spamassasin installed you just need to configure mailscanner. Check the setting in MailScanner.conf located in: /usr/local/etc/MailScanner -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: Milters or SpamAssassin plugings
Thanks, but that was not exactly what I was asking. I know I can configure it in MailScanner, but - which is the best way of doing it. Through Sendmail as a milter or the p5-mail-SPF plugin ?? Derek Ragona [EMAIL PROTECTED] wrote: At 04:10 PM 4/11/2008, Robert Davison wrote: I'm running the base Sendmail with Mailscanner and SpamAssassin from the ports. A simple question I'm installing SPF to help the fight against spam. Which is the most efficient way of doing it.Sendmail milter or the p5-Mail SpamAssassin plug-in. They both do the same, but is one a better way than the other ? If you have Mailscanner and spamassasin installed you just need to configure mailscanner. Check the setting in MailScanner.conf located in: /usr/local/etc/MailScanner -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. - Yahoo! for Good helps you make a difference ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Milters or SpamAssassin plugings
At 05:04 PM 4/11/2008, Robert Davison wrote: Thanks, but that was not exactly what I was asking. I know I can configure it in MailScanner, but - which is the best way of doing it. Through Sendmail as a milter or the p5-mail-SPF plugin ?? Derek Ragona [EMAIL PROTECTED] wrote: At 04:10 PM 4/11/2008, Robert Davison wrote: I'm running the base Sendmail with Mailscanner and SpamAssassin from the ports. A simple question I'm installing SPF to help the fight against spam. Which is the most efficient way of doing it.Sendmail milter or the p5-Mail SpamAssassin plug-in. They both do the same, but is one a better way than the other ? If you have Mailscanner and spamassasin installed you just need to configure mailscanner. Check the setting in MailScanner.conf located in: /usr/local/etc/MailScanner -Derek Sendmail has milter built-in to it for some time. All the mail scanning tools need milter. The easy way to configure these tools is to configure MailScanner. It sits at the top of the tree so to speak, depending on whatever AV you configure it to use, and MailScanner uses spamassasin and many perl libraries. You can see all the dependencies if you do: make depends on the mailscanner port. You will need to configure your AV to get updates. Also you may want to setup some of the rules files for mailscanner for whitelisting, blacklisting, and phishing. One last note, don't bounce spam. If you choose to bounce spam, as most has wrong return addresses you can start your own mail storm of rejected bounces. A mail storm like that will easily bring down an email server. -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]
Import bayes_* for SpamAssassin from Debian to FreeBSD
Hello, I must export a SpamAssassin configuration in a GNU/Linux Debian 4.0. See these files: [EMAIL PROTECTED] .spamassassin # file * auto-whitelist: Berkeley DB (Hash, version 7, native byte-order) auto-whitelist.mutex: ASCII text bayes_journal:ASCII text bayes.mutex: ASCII text bayes_seen: Berkeley DB (Hash, version 7, native byte-order) bayes_toks: Berkeley DB (Hash, version 8, native byte-order) bayes_toks.dump: ASCII text user_prefs: ASCII English text [EMAIL PROTECTED] .spamassassin # spamc -V SpamAssassin Client version 3.1.5 This is my SpamAssassin on FreeBSD (p5-Mail-SpamAssassin port) : [EMAIL PROTECTED] .spamassassin # spamc -V SpamAssassin Client version 3.2.4 compiled with SSL support (OpenSSL 0.9.8e 23 Feb 2007) However, when I use these files in my ~/.spamassassin, on my FreeBSD, I have errors: spamd[51854]: bayes: cannot open bayes databases /var/spool/spamd/.spamassassin/bayes_* R/O: tie failed: Inappropriate file type or format spamd[51854]: bayes: cannot open bayes databases /var/spool/spamd/.spamassassin/bayes_* R/O: tie failed: Inappropriate file type or format spamd[51854]: auto-whitelist: open of auto-whitelist file failed: auto-whitelist: cannot open auto_whitelist_path /var/spool/spamd/.spamassassin/auto-whitelist: Inappropriate file type or format I don't understand, because they're only Berkeley databases... See the command file on these files in FreeBSD: auto-whitelist: Berkeley DB (Hash, version 7, native byte-order) auto-whitelist.mutex: ASCII text bayes.mutex: ASCII text bayes_journal:ASCII text bayes_seen: Berkeley DB (Hash, version 7, native byte-order) bayes_toks: Berkeley DB (Hash, version 8, native byte-order) bayes_toks.dump: ASCII text user_prefs: ASCII English text I tried to just import a dump from Debian (with db4.1_dump) and rebuild the database in FreeBSD (with db41_load), the problem is the same. How could I re-use these files? They are very important. Thanks for your help. -Nicolas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Import bayes_* for SpamAssassin from Debian to FreeBSD
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Nicolas Letellier wrote: However, when I use these files in my ~/.spamassassin, on my FreeBSD, I have errors: spamd[51854]: bayes: cannot open bayes databases /var/spool/spamd/.spamassassin/bayes_* R/O: tie failed: Inappropriate file type or format spamd[51854]: bayes: cannot open bayes databases /var/spool/spamd/.spamassassin/bayes_* R/O: tie failed: Inappropriate file type or format spamd[51854]: auto-whitelist: open of auto-whitelist file failed: auto-whitelist: cannot open auto_whitelist_path /var/spool/spamd/.spamassassin/auto-whitelist: Inappropriate file type or format I don't understand, because they're only Berkeley databases... You'll need to install the same version of Berkeley DB on FreeBSD as you were using on Debian -- and you'll have to compile the perl modules SpamAssassin uses for BerkeleyDB access to use that version too. Same in this context means the first two field in the BDB version number should match -- the last field (a.k.a 'patchlevel') isn't significant. You can install multiple BDB versions in parallel from the ports tree, but to force the perl ports to link against the chosen variant you'll need something like: WITH_BDB_VER= 44 in /etc/make.conf. (See /usr/ports/Mk/bsd.database.mk for the possible values) Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. Flat 3 7 Priory Courtyard PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW, UK -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.8 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREDAAYFAkfVMEAACgkQ3jDkPpsZ+VaEDQCgpriBLoXycXtGmJPYDzMLfkoz a4AAoJsKhFvStJpGXdNBXyZnL4xYy8N9 =dNeE -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: Import bayes_* for SpamAssassin from Debian to FreeBSD
Matthew Seaman a écrit : You'll need to install the same version of Berkeley DB on FreeBSD as you were using on Debian -- and you'll have to compile the perl modules SpamAssassin uses for BerkeleyDB access to use that version too. I use the same BerkeleyDB. I use db41 on FreeBSD (and db41* commands) and db41 on Debian (and db.41* commands). `file`commands returns the same headers of the file on Debian and the defaults ~/.spamassassin/tok*. When I try this: [EMAIL PROTECTED] .spamassassin # sa-learn --import --dbpath . bayes: cannot open bayes databases ./bayes_* R/O: tie failed: Inappropriate file type or format upgrading to DB_File, please be patient: ./old_bayes_seen DB_File: no database of that kind found, nothing copied GDBM_File: no database of that kind found, nothing copied NDBM_File: no database of that kind found, nothing copied SDBM_File: no database of that kind found, nothing copied upgrading to DB_File, please be patient: ./old_bayes_toks DB_File: no database of that kind found, nothing copied GDBM_File: no database of that kind found, nothing copied NDBM_File: no database of that kind found, nothing copied SDBM_File: no database of that kind found, nothing copied import failed, original files saved with old prefix What must I do? Do you think it's a Perl problem? -Nicolas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Import bayes_* for SpamAssassin from Debian to FreeBSD
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Nicolas Letellier wrote: Matthew Seaman a écrit : You'll need to install the same version of Berkeley DB on FreeBSD as you were using on Debian -- and you'll have to compile the perl modules SpamAssassin uses for BerkeleyDB access to use that version too. I use the same BerkeleyDB. I use db41 on FreeBSD (and db41* commands) and db41 on Debian (and db.41* commands). `file`commands returns the same headers of the file on Debian and the defaults ~/.spamassassin/tok*. When I try this: [EMAIL PROTECTED] .spamassassin # sa-learn --import --dbpath . bayes: cannot open bayes databases ./bayes_* R/O: tie failed: Inappropriate file type or format upgrading to DB_File, please be patient: ./old_bayes_seen DB_File: no database of that kind found, nothing copied GDBM_File: no database of that kind found, nothing copied NDBM_File: no database of that kind found, nothing copied SDBM_File: no database of that kind found, nothing copied upgrading to DB_File, please be patient: ./old_bayes_toks DB_File: no database of that kind found, nothing copied GDBM_File: no database of that kind found, nothing copied NDBM_File: no database of that kind found, nothing copied SDBM_File: no database of that kind found, nothing copied import failed, original files saved with old prefix What must I do? Do you think it's a Perl problem? Hmmm assuming that the debian box and the new FreeBSD box have the same CPU architecture -- ie. both i386 machines the .db files should be compatible. I /think/ they're compatible between a 32 and a 64 bit machine of the same endian-ness BICBW. Can you confirm that the copies of the files on the FreeBSD box are byte-for-byte identical to the originals on the Debian box? The easiest way to do this is to generate MD5 or similar checksums on both. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. Flat 3 7 Priory Courtyard PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW, UK -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.8 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREDAAYFAkfVPmAACgkQ3jDkPpsZ+VYxAQCeJmgCIqh5A7SzvGfiOmV/lGWU jBoAnjYBv8F+fh/0Nx9Ms1nizDFz7oSu =OUTN -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: Perl error running lint on spamassassin? [NO MORE SPAMASSASSIN!!!]
Hey Drew! I learned long time ago to drop SpamAssassin altogether. I got hundreds of spam e-mails a day with SpamAssassin. But when I switched to a clean Postfix installation with Greylist (port 10023) and 3 different blocklist servers, my spams reduced to 0 a day, or 1-3 at most. $ cat /usr/local/etc/postfix/main.cf # FreeBSD/i386 # nigga.someshit.com mail_owner = postfix home_mailbox = .maildir/ mydomain = someshit.com myhostname = nigga.someshit.com mynetworks = 127.0.0.0/8 myorigin = $mydomain mydestination = $mydomain, localhost.$mydomain, $myhostname, someothershit.com smtpd_recipient_restrictions = reject_rbl_client zen.spamhaus.org reject_rbl_client dnsbl.ahbl.org reject_rbl_client dnsbl.njabl.org permit_mynetworks reject_unauth_destination check_policy_service inet:127.0.0.1:10023 unknown_local_recipient_reject_code = 450 queue_directory = /var/spool/postfix command_directory = /usr/local/sbin daemon_directory = /usr/local/libexec/postfix sendmail_path = /usr/local/sbin/sendmail newaliases_path = /usr/local/bin/newaliases mailq_path = /usr/local/bin/mailq sample_directory = /usr/local/etc/postfix Suggestions on improving this configuration file is always appreciated. Have fun! All the best, Kyrre - Original Message - From: Drew [EMAIL PROTECTED] Date: Tuesday, February 5, 2008 8:49 am Subject: Perl error running lint on spamassassin? To: [EMAIL PROTECTED] Hi, I know I've been noisy of late, but that should slow down if I ever get things working around here again. I've given up on my old server hardware,and put another machine in it's place. Unfortunately, everything but mail is working for me on this server. The problem seems to be with spamassassin.When I run spamassassin -D --lint from the command line, everything _seems_ to check out. However, when I run mailscanner --lint it segfaults: [EMAIL PROTECTED](/)# mailscanner --lint Checking version numbers... Version number in MailScanner.conf (4.64.3) is correct. Your envelope_sender_header in spam.assassin.prefs.conf is correct. Checking for SpamAssassin errors (if you use it)... SpamAssassin temp dir = /var/spool/MailScanner/incoming/SpamAssassin-Temp zsh: segmentation fault mailscanner --lint I wasn't real sure what was causing this, but running SA lint from mailwatch provides a clue, perhaps: /libexec/ld-elf.so.1: /usr/local/bin/perl5.8.8: Undefined symbol PL_exit_flags I've removed and reinstalled perl5.8 from ports, double checked everythingwith the perl-after-upgrade script, ensured that I've handled the use.perlports thing, etc. After all that failed to solve this, I rebuilt and reinstalled world. Still no joy. I like to try to solve stuff that looks easy like this on my own, but obviously at this point, I've overlooked something simple. Anyone care to pass me a clue-bat? Thanks in advance.___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [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: Perl error running lint on spamassassin? [NO MORE SPAMASSASSIN!!!]
/libexec/ld-elf.so.1: /usr/local/bin/perl5.8.8: Undefined symbol PL_exit_flags You may consider updating every Perl modules after you have upgraded Perl 5.8.8. Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Perl error running lint on spamassassin?
Hi, I know I've been noisy of late, but that should slow down if I ever get things working around here again. I've given up on my old server hardware, and put another machine in it's place. Unfortunately, everything but mail is working for me on this server. The problem seems to be with spamassassin. When I run spamassassin -D --lint from the command line, everything _seems_ to check out. However, when I run mailscanner --lint it segfaults: [EMAIL PROTECTED](/)# mailscanner --lint Checking version numbers... Version number in MailScanner.conf (4.64.3) is correct. Your envelope_sender_header in spam.assassin.prefs.conf is correct. Checking for SpamAssassin errors (if you use it)... SpamAssassin temp dir = /var/spool/MailScanner/incoming/SpamAssassin-Temp zsh: segmentation fault mailscanner --lint I wasn't real sure what was causing this, but running SA lint from mailwatch provides a clue, perhaps: /libexec/ld-elf.so.1: /usr/local/bin/perl5.8.8: Undefined symbol PL_exit_flags I've removed and reinstalled perl5.8 from ports, double checked everything with the perl-after-upgrade script, ensured that I've handled the use.perlports thing, etc. After all that failed to solve this, I rebuilt and reinstalled world. Still no joy. I like to try to solve stuff that looks easy like this on my own, but obviously at this point, I've overlooked something simple. Anyone care to pass me a clue-bat? Thanks in advance. ___ 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
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=78700cat=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]
Spamassassin: Fill /var/log/maillog
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? Regards, -- Martin Schweizer [EMAIL PROTECTED] PC-Service M. Schweizer GmbH; Bannholzstrasse 6; CH-8608 Bubikon Tel. +41 55 243 30 00; Fax: +41 55 243 33 22; http://www.pc-service.ch; public key : http://www.pc-service.ch/pgp/public_key.asc; fingerprint: EC21 CA4D 5C78 BC2D 73B7 10F9 C1AE 1691 D30F D239; ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Postfix/SpamAssassin Guru?
On 8/25/07, Eric Crist [EMAIL PROTECTED] wrote: On Aug 24, 2007, at 11:26 PMAug 24, 2007, Noel Jones wrote: [snip] an easier way is to run spamassassin under the control of amavisd-new and let amavisd-new add address extensions such as user+spam and to let dovecot file the mail in a spam folder. Noel, Are you saying I just need amavisd-new installed and properly configured? Is there something I need to tell dovecot? A bit more information in regards to where I can look for documentation would be appreciated! look in the amavisd-new, dovecot, and postfix docs for recipient delimiter. Followup questions should go to the list for one of those projects. -- Noel Jones ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Postfix/SpamAssassin Guru?
On Aug 24, 2007, at 11:26 PMAug 24, 2007, Noel Jones wrote: [snip] an easier way is to run spamassassin under the control of amavisd-new and let amavisd-new add address extensions such as user+spam and to let dovecot file the mail in a spam folder. Noel, Are you saying I just need amavisd-new installed and properly configured? Is there something I need to tell dovecot? A bit more information in regards to where I can look for documentation would be appreciated! - Eric F Crist Secure Computing Networks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Postfix/SpamAssassin Guru?
--On August 24, 2007 8:32:01 AM -0500 Eric Crist [EMAIL PROTECTED] wrote: Hey, Is there anyone that can help me do some funky filtering with postfix and spamassassin? I'm a new Postfix convert, and my knowledge is lacking. TIA for any help! What is it that you want to do? Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/
Postfix/SpamAssassin Guru?
Hey, Is there anyone that can help me do some funky filtering with postfix and spamassassin? I'm a new Postfix convert, and my knowledge is lacking. TIA for any help! - Eric F Crist Secure Computing Networks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Postfix/SpamAssassin Guru?
Eric why not stick with an MTA you know? -- martin On 8/24/07, Eric Crist [EMAIL PROTECTED] wrote: Hey, Is there anyone that can help me do some funky filtering with postfix and spamassassin? I'm a new Postfix convert, and my knowledge is lacking. TIA for any help! - Eric F Crist Secure Computing Networks ___ 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: Postfix/SpamAssassin Guru?
On August 24, 2007 at 09:32AM Eric Crist wrote: Is there anyone that can help me do some funky filtering with postfix and spamassassin? I'm a new Postfix convert, and my knowledge is lacking. Define funky! Before you start asking questions regarding configuring Postfix, it might behoove you to check out the Postfix documentation site http://www.postfix.com/documentation.html. It is loaded with lots of useful information. You might also consider joining the Postfix mailing list. -- Gerard A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? TOPIC: Posting Etiquette ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Postfix/SpamAssassin Guru?
On Aug 24, 2007, at 9:05 AMAug 24, 2007, Gerard wrote: On August 24, 2007 at 09:32AM Eric Crist wrote: Is there anyone that can help me do some funky filtering with postfix and spamassassin? I'm a new Postfix convert, and my knowledge is lacking. Define funky! Before you start asking questions regarding configuring Postfix, it might behoove you to check out the Postfix documentation site http://www.postfix.com/documentation.html. It is loaded with lots of useful information. You might also consider joining the Postfix mailing list. This is also a reply to Paul Schmehl. I've got Postfix with Dovecot and virtual users setup. What I'm looking for is some filtering based on the flags SpamAssassin sets, so that I can route any messages tagged as Spam to a Spam directory with a users maildir. I've done a ton of searches, etc, and I can't seem to figure this one out. Also, I'm having a hard time (partially due to lack of effort, I'm guessing), getting DKIM/DomainKeys setup for my domains within Postfix. TIA - Eric F Crist Secure Computing Networks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Postfix/SpamAssassin Guru?
On Aug 24, 2007, at 8:46 AMAug 24, 2007, Martin Hepworth wrote: Eric why not stick with an MTA you know? Martin, I've switched to postfix due to some of the features it supports. Thanks for your concern, though. - Eric F Crist Secure Computing Networks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Postfix/SpamAssassin Guru?
Eric Crist wrote: This is also a reply to Paul Schmehl. I've got Postfix with Dovecot and virtual users setup. What I'm looking for is some filtering based on the flags SpamAssassin sets, so that I can route any messages tagged as Spam to a Spam directory with a users maildir. I've done a ton of searches, etc, and I can't seem to figure this one out. Also, I'm having a hard time (partially due to lack of effort, I'm guessing), getting DKIM/DomainKeys setup for my domains within Postfix. Same setup here basically: Dovecot, Postfix, SA, clamav, postgrey and amavisd i use procmail to filter things. it works well and was easy to integrate. I never played with DKIM though. I must say that most of the spam that does come in I never see in a spam folder. its too high on the scores to even get delivered if you havent played with postgrey yet, give it a whirl. it works wonders. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re[2]: Postfix/SpamAssassin Guru?
On August 24, 2007 at 10:34AM Eric Crist wrote:
{snip]
I've got Postfix with Dovecot and virtual users setup. What I'm
looking for is some filtering based on the flags SpamAssassin sets,
so that I can route any messages tagged as Spam to a Spam directory
with a users maildir. I've done a ton of searches, etc, and I can't
seem to figure this one out. Also, I'm having a hard time (partially
due to lack of effort, I'm guessing), getting DKIM/DomainKeys setup
for my domains within Postfix.
Have you tried posting on the 'Spamassassin' list also? That is
probably where this message belongs. The DKIM problem should be
directed to the Postfix forum for best results.
--
Gerard
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Postfix/SpamAssassin Guru?
--On Friday, August 24, 2007 09:46:32 -0500 Eric [EMAIL PROTECTED] wrote: Eric Crist wrote: This is also a reply to Paul Schmehl. I've got Postfix with Dovecot and virtual users setup. What I'm looking for is some filtering based on the flags SpamAssassin sets, so that I can route any messages tagged as Spam to a Spam directory with a users maildir. I've done a ton of searches, etc, and I can't seem to figure this one out. Also, I'm having a hard time (partially due to lack of effort, I'm guessing), getting DKIM/DomainKeys setup for my domains within Postfix. Same setup here basically: Dovecot, Postfix, SA, clamav, postgrey and amavisd i use procmail to filter things. it works well and was easy to integrate. I never played with DKIM though. I must say that most of the spam that does come in I never see in a spam folder. its too high on the scores to even get delivered if you havent played with postgrey yet, give it a whirl. it works wonders. You may also want to consider using policyd-weight (/usr/ports/mail/postfix-policyd-weight). A mail server I maintain is rejecting about 80% of the mail through policyd-weight before it ever reaches postfix (no false positives.) You should be able to use dkfilter to handle domain keys: /usr/ports]# make search name=dkfilter Port: dkfilter-0.11 Path: /usr/ports/mail/dkfilter Info: Domainkeys filter for Postfix -- Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/
Re: Postfix/SpamAssassin Guru?
Eric Crist wrote: On Aug 24, 2007, at 9:05 AMAug 24, 2007, Gerard wrote: On August 24, 2007 at 09:32AM Eric Crist wrote: I've got Postfix with Dovecot and virtual users setup. What I'm looking for is some filtering based on the flags SpamAssassin sets, so that I can route any messages tagged as Spam to a Spam directory with a users maildir. Assuming you got SA running: In my main.cf: header_checks = regexp:/etc/postfix/header_checks This is in my header_checks: /^X-Spam-Flag: YES/ REDIRECT [EMAIL PROTECTED] Peter -- http://www.boosten.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Postfix/SpamAssassin Guru?
On 8/24/07, Peter Boosten [EMAIL PROTECTED] wrote: Eric Crist wrote: On Aug 24, 2007, at 9:05 AMAug 24, 2007, Gerard wrote: On August 24, 2007 at 09:32AM Eric Crist wrote: I've got Postfix with Dovecot and virtual users setup. What I'm looking for is some filtering based on the flags SpamAssassin sets, so that I can route any messages tagged as Spam to a Spam directory with a users maildir. Assuming you got SA running: In my main.cf: header_checks = regexp:/etc/postfix/header_checks This is in my header_checks: /^X-Spam-Flag: YES/ REDIRECT [EMAIL PROTECTED] Peter Note that REDIRECT acts on all recipients of a message, and cannot be customized per-user. In the above example, *all* tagged spam would be delivered to a single mailbox. OK if that's what you want. an easier way is to run spamassassin under the control of amavisd-new and let amavisd-new add address extensions such as user+spam and to let dovecot file the mail in a spam folder. -- Noel Jones ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot post because of spamassassin blocking my mail
On Jul 31, 2007, at 1:29 PMJul 31, 2007, Adam J Richardson wrote: ytriffy wrote: Hi list. Whenever I try to post I get something like this: Your mail to 'freebsd-questions' with the subject [panic]page fault while in kernel mode Is being held until the list moderator can review it for approval. The reason it is being held: SpamAssassin identified this message as possible spam Although I'm subscribed user of mailing lists. What should I do? Hi ytriffy, You're posting from gmail.com. That's a known public email domain, that is. I would guess you'd get the same problem coming from yahoo.com or hotmail.com. Do you have a friend running their own email server, so you could get a private email address? Or does your ISP not supply you with a private email address? I don't know for sure, but I think SpamAssassin would label any publically accessible email server as possible spam source. That's what I'd do, for sure. Adam, I've been posting to the list through gmail for quite some time, without issue. I don't think that's the OP's problem. Eric Crist ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
