Re: smtpd[68513]: warn: lost processor: spamassassin exited abnormally
Hi Omar, On 2023-11-09 18:22:41, Omar Polo wrote: I've committed the update and backported to -STABLE so the fixed package should appear in the next days. Thanks for the report and sorry for the breakage I highly appreciate your fast response and the fix you have provided. Regards Harri
Re: smtpd[68513]: warn: lost processor: spamassassin exited abnormally
I've committed the update and backported to -STABLE so the fixed package should appear in the next days. Thanks for the report and sorry for the breakage
Re: smtpd[68513]: warn: lost processor: spamassassin exited abnormally
On 2023/11/07 22:44:56 +0100, Giovanni Bechis wrote:
> On 11/7/23 20:16, Omar Polo wrote:
> > On 2023/11/07 19:30:43 +0100, Harald Dunkel wrote:
> >> Hi Omar,
> >>
> >> sorry for the delay, but I have good news: The patch seems to
> >> work. Of course I will continue to watch it.
> > Thanks for verifying!
> >
> > Before bumping the smtp-filter protocol version I took at look at what
> > we had in the port tree to know what would break, but this slipped.
> > apologize.
> >
> > If it's OK for Giovanni and Joerg I'd like to commit this and backport
> > to 7.4-stable (same diff tested by Harald, reattaching for convenience.)
> [...]
> > +Index: filter-spamassassin.go
> > +--- filter-spamassassin.go.orig
> > filter-spamassassin.go
> > +@@ -211,7 +211,7 @@ func run() {
> > + for in.Scan() {
> > + f := strings.Split(in.Text(), "|")
> > + t, ver, ev, sid := f[0], f[1], f[4], f[5]
> > +- if (t != "filter" && t != "report") || ver != "0.6" {
> > ++ if (t != "filter" && t != "report") || ver != "0.7" {
> > + l3.Err(fmt.Sprintln(sid, "protocol", t, ver))
> does this still works with previous protocol versions ?
The only difference between 0.6 and 0.7 is the order of the link-auth
fields (`result' and `username' were swapped.) As far as I can see,
filter-spamassassin doesn't use it, so it should work as usual on both
0.6 and 0.7 versions.
> ok giovanni@ in any case for current and 7.4 since it will be a no-op on
> OpenBSD.
Thanks :)
Re: smtpd[68513]: warn: lost processor: spamassassin exited abnormally
On 11/7/23 20:16, Omar Polo wrote:
On 2023/11/07 19:30:43 +0100, Harald Dunkel wrote:
Hi Omar,
sorry for the delay, but I have good news: The patch seems to
work. Of course I will continue to watch it.
Thanks for verifying!
Before bumping the smtp-filter protocol version I took at look at what
we had in the port tree to know what would break, but this slipped.
apologize.
If it's OK for Giovanni and Joerg I'd like to commit this and backport
to 7.4-stable (same diff tested by Harald, reattaching for convenience.)
[...]
+Index: filter-spamassassin.go
+--- filter-spamassassin.go.orig
filter-spamassassin.go
+@@ -211,7 +211,7 @@ func run() {
+ for in.Scan() {
+ f := strings.Split(in.Text(), "|")
+ t, ver, ev, sid := f[0], f[1], f[4], f[5]
+- if (t != "filter" && t != "report") || ver != "0.6" {
++ if (t != "filter" && t != "report") || ver != "0.7" {
+ l3.Err(fmt.Sprintln(sid, "protocol", t, ver))
does this still works with previous protocol versions ?
ok giovanni@ in any case for current and 7.4 since it will be a no-op on
OpenBSD.
Cheers
Giovanni
Re: smtpd[68513]: warn: lost processor: spamassassin exited abnormally
On 2023/11/07 19:30:43 +0100, Harald Dunkel wrote:
> Hi Omar,
>
> sorry for the delay, but I have good news: The patch seems to
> work. Of course I will continue to watch it.
Thanks for verifying!
Before bumping the smtp-filter protocol version I took at look at what
we had in the port tree to know what would break, but this slipped.
apologize.
If it's OK for Giovanni and Joerg I'd like to commit this and backport
to 7.4-stable (same diff tested by Harald, reattaching for convenience.)
Index: Makefile
===
RCS file: /home/cvs/ports/mail/opensmtpd-filters/spamassassin/Makefile,v
retrieving revision 1.8
diff -u -p -r1.8 Makefile
--- Makefile26 Sep 2023 12:28:14 - 1.8
+++ Makefile5 Nov 2023 09:20:27 -
@@ -4,7 +4,7 @@ V = 0.7
FILTER_NAME = spamassassin
DISTNAME = filter-spamassassin-${V}
HOMEPAGE = https://www.umaxx.net/
-REVISION = 0
+REVISION = 1
CATEGORIES = mail
Index: patches/patch-filter-spamassassin_go
===
RCS file: patches/patch-filter-spamassassin_go
diff -N patches/patch-filter-spamassassin_go
--- /dev/null 1 Jan 1970 00:00:00 -
+++ patches/patch-filter-spamassassin_go7 Nov 2023 19:14:58 -
@@ -0,0 +1,14 @@
+handle the smtpd filter-protocol version 0.7
+
+Index: filter-spamassassin.go
+--- filter-spamassassin.go.orig
filter-spamassassin.go
+@@ -211,7 +211,7 @@ func run() {
+ for in.Scan() {
+ f := strings.Split(in.Text(), "|")
+ t, ver, ev, sid := f[0], f[1], f[4], f[5]
+- if (t != "filter" && t != "report") || ver != "0.6" {
++ if (t != "filter" && t != "report") || ver != "0.7" {
+ l3.Err(fmt.Sprintln(sid, "protocol", t, ver))
+ return
+ }
Re: smtpd[68513]: warn: lost processor: spamassassin exited abnormally
Hi Omar, sorry for the delay, but I have good news: The patch seems to work. Of course I will continue to watch it. Thank you very much Harri
Re: smtpd[68513]: warn: lost processor: spamassassin exited abnormally
On 2023-11-05 10:21:10, Omar Polo wrote: Can you try the following diff to see if it helps? I will try this evening after work, stay tuned. Its been a while since I used CVS. Regards Harri
smtpd[68513]: warn: lost processor: spamassassin exited abnormally
Hi folks,
since OpenBSD 7.4 the spamassassin filter seems to be broken. On
the first EMail opensmtpd dies with a message in maillog saying
Nov 5 08:59:23 mhost smtpd[60460]: bcc4f33a095bb28e smtp connected
address=xx.xx.xx.xx host=mail.example.com
Nov 5 08:59:23 mhost filter-spamassassin[7782]: bcc4f33a095bb28e protocol
report 0.7
Nov 5 08:59:23 mhost filter-spamassassin[7782]: exit
Nov 5 08:59:23 mhost smtpd[68513]: warn: lost processor: spamassassin exited
abnormally
Nov 5 08:59:23 mhost smtpd[68513]: Exiting
smtpd is configured according to /usr/local/share/doc/pkg-readmes/\
opensmtpd-filter-spamassassin (except for the tls option):
xname = "mailhost.example.de"
pki $xname cert "/etc/ssl/example.de/fullchain.pem"
pki $xname key "/etc/ssl/example.de/privkey.pem"
pki $xname dhe auto
filter "spamassassin" proc-exec "filter-spamassassin"
listen on all tls pki $xname filter "spamassassin"
listen on socket filter "spamassassin"
:
:
If I kick out the tls stuff, it is still broken.
Can anybody reproduce this? Every helpful hint is highly
appreciated.
Harri
Re: smtpd[68513]: warn: lost processor: spamassassin exited abnormally
On 2023/11/05 09:59:14 +0100, Harald Dunkel wrote:
> Hi folks,
>
> since OpenBSD 7.4 the spamassassin filter seems to be broken. On
> the first EMail opensmtpd dies with a message in maillog saying
>
> Nov 5 08:59:23 mhost smtpd[60460]: bcc4f33a095bb28e smtp connected
> address=xx.xx.xx.xx host=mail.example.com
> Nov 5 08:59:23 mhost filter-spamassassin[7782]: bcc4f33a095bb28e protocol
> report 0.7
> Nov 5 08:59:23 mhost filter-spamassassin[7782]: exit
This seems to suggest that it's due the filter-protocol version bump.
(+cc filter-spamassassin maintainers)
I don't use filter-spamassassin and can't test, but since it doesn't
seem to use link-auth it shouldn't care about this protocol change, so
just bumping the version should be enough.
Can you try the following diff to see if it helps?
Index: Makefile
===
RCS file: /home/cvs/ports/mail/opensmtpd-filters/spamassassin/Makefile,v
retrieving revision 1.8
diff -u -p -r1.8 Makefile
--- Makefile26 Sep 2023 12:28:14 - 1.8
+++ Makefile5 Nov 2023 09:20:27 -0000
@@ -4,7 +4,7 @@ V = 0.7
FILTER_NAME = spamassassin
DISTNAME = filter-spamassassin-${V}
HOMEPAGE = https://www.umaxx.net/
-REVISION = 0
+REVISION = 1
CATEGORIES = mail
Index: patches/patch-filter-spamassassin_go
===
RCS file: patches/patch-filter-spamassassin_go
diff -N patches/patch-filter-spamassassin_go
--- /dev/null 1 Jan 1970 00:00:00 -
+++ patches/patch-filter-spamassassin_go5 Nov 2023 09:20:36 -
@@ -0,0 +1,14 @@
+handle the smtpd filter-protocol version 0.7
+
+Index: filter-spamassassin.go
+--- filter-spamassassin.go.orig
filter-spamassassin.go
+@@ -211,7 +211,7 @@ func run() {
+ for in.Scan() {
+ f := strings.Split(in.Text(), "|")
+ t, ver, ev, sid := f[0], f[1], f[4], f[5]
+- if (t != "filter" && t != "report") || ver != "0.6" {
++ if (t != "filter" && t != "report") || ver != "0.7" {
+ l3.Err(fmt.Sprintln(sid, "protocol", t, ver))
+ return
+ }
spamassassin filtering problem
Hello,
I was using spamassassin+smtpd for a while and everything worked as
expected. Now I added support for more tan one domain and incoming mails
are locked into allop, I can't figure out why.
Here is my /etc/mail/smtpd.conf
table aliases file:/etc/mail/aliases
table virtuals file:/etc/mail/virtuals
table domains file:/etc/mail/domains
pki certsssl key "/etc/ssl/acme/private/mydomain.net-privkey.pem"
pki certsssl certificate "/etc/ssl/acme/mydomain.net-fullchain.pem"
ca certsssl certificate "/etc/ssl/acme/mydomain.net-fullchain.pem"
listen on lo0 port 10028 tag DKIM
listen on lo0 port 10026 tag NOSPAM
listen on lo0
listen on re0 port smtp tls pki certsssl
listen on re0 port submission tls-require pki certsssl auth
accept from local for local alias deliver to maildir
"~/Maildir"
accept tagged NOSPAM for domain virtual deliver to
maildir "/mnt/bigstorage/vmail/%{dest.domain}/%{dest.user}/Maildir"
accept from any for domain relay via smtp://127.0.0.1:10025
accept tagged DKIM for any relay
accept from local for any relay via smtp://127.0.0.1:10027
table virtuals contains :
us...@mydomain.net user1
us...@otherdomain.net user2
and table domains contains :
mydomain.net
otherdomain.net
In logs, I can see such messages
May 13 08:10:39 master smtpd[22622]: 9d2709d2fddd9a03 smtp
event=message address=127.0.0.1 host=localhost msgid=f23a6ab6
from= to= size=4665 ndest=1 proto=ESMTP
May 13 08:10:39 master smtpd[22622]: 9d2709d115477347 mta
event=delivery evpid=2fc2606678f20fd0 from=
to= rcpt=<-> source="127.0.0.1" relay="127.0.0.1
(localhost)" delay=1s result="Ok" stat="250 2.0.0: f23a6ab6 Message accepted
for delivery"
May 13 08:10:39 master spampd[11644]: processing message
<20170513054818.gg33...@openbsd.my.domain> for
ORCPT=rfc822;t...@yeuxdelibad.net
May 13 08:10:40 master spampd[11644]: clean message
<20170513054818.gg33...@openbsd.my.domain> (1.19/5.00) from
for ORCPT=rfc822;t...@yeuxdelibad.net in 0.68s, 4764
bytes.
May 13 08:10:40 master smtpd[22622]: 9d2709d2fddd9a03 smtp
event=message address=127.0.0.1 host=localhost msgid=cb35fe0a
from= to= size=4828 ndest=1 proto=ESMTP
May 13 08:10:40 master smtpd[22622]: 9d2709d115477347 mta
event=delivery evpid=f23a6ab6dbaeb160 from=
to= rcpt=<-> source="127.0.0.1" relay="127.0.0.1
(localhost)" delay=1s result="Ok" stat="250 2.0.0: cb35fe0a Message accepted
for delivery"
May 13 08:10:40 master spampd[11644]: processing message
<20170513054818.gg33...@openbsd.my.domain> for
ORCPT=rfc822;t...@yeuxdelibad.net
May 13 08:10:41 master spampd[11644]: clean message
<20170513054818.gg33...@openbsd.my.domain> (1.19/5.00) from
for ORCPT=rfc822;t...@yeuxdelibad.net in 0.67s, 4931
bytes.
May 13 08:10:41 master smtpd[22622]: 9d2709d2fddd9a03 smtp
event=message address=127.0.0.1 host=localhost msgid=994ab936
from= to= size=4991 ndest=1 proto=ESMTP
Please, any advise is welcome.
Regards.
--
Re: opensmtpd-extras-[clamav|spamassassin] packages in 6.0
Thanks Joerg. I wasn't aware that amavis would play nicely with OpenSMTPD, as such problem solved. I will simply use amavisd-new. Original Message Subject: Re: opensmtpd-extras-[clamav|spamassassin] packages in 6.0 Local Time: October 11, 2016 11:27 PM UTC Time: October 11, 2016 9:27 PM From: m...@umaxx.net To: mabi misc@openbsd.org > Am 10.10.2016 um 17:59 schrieb mabi : > > Hi, > > Just noticed that the OpenBSD 6.0 release does not include the opensmtpd-extras-clamav nor the opensmtpd-extras-spamassassin packages. I would like to upgrade my 5.9 OpenBSD mail gateway to 6.0 and was wondering if I can use the old packages from 5.9 with 6.0? No. > Or what is the alternative to these two packages? Various options. One could be to proxy mails through spampd and clamsmtp. Amavisd might also be an option. > Regards, > Mabi
Re: opensmtpd-extras-[clamav|spamassassin] packages in 6.0
> Am 10.10.2016 um 17:59 schrieb mabi : > > Hi, > > Just noticed that the OpenBSD 6.0 release does not include the opensmtpd-extras-clamav nor the opensmtpd-extras-spamassassin packages. I would like to upgrade my 5.9 OpenBSD mail gateway to 6.0 and was wondering if I can use the old packages from 5.9 with 6.0? No. > Or what is the alternative to these two packages? Various options. One could be to proxy mails through spampd and clamsmtp. Amavisd might also be an option. > Regards, > Mabi
opensmtpd-extras-[clamav|spamassassin] packages in 6.0
Hi, Just noticed that the OpenBSD 6.0 release does not include the opensmtpd-extras-clamav nor the opensmtpd-extras-spamassassin packages. I would like to upgrade my 5.9 OpenBSD mail gateway to 6.0 and was wondering if I can use the old packages from 5.9 with 6.0? Or what is the alternative to these two packages? Regards, Mabi
Re: spamassassin sa-update error in 6.0
An perl bug made it into 6.0:
http://www.openbsd.org/errata60.html
> I am running 6.0 and each time I try to run sa-update, I get the
> following error:
> Argument "1.38_01" isn't numeric in numeric lt (<) at
> /usr/libdata/perl5/IO/Socket/IP.pm line 847
>
> line 847 is:if( $IO::Socket::VERSION < 1.35 ) {
>
> And IO::Socket is part of base
>
> Best Regards
spamassassin sa-update error in 6.0
Hello,
I am running 6.0 and each time I try to run sa-update, I get the
following error:
Argument "1.38_01" isn't numeric in numeric lt (<) at
/usr/libdata/perl5/IO/Socket/IP.pm line 847
line 847 is:if( $IO::Socket::VERSION < 1.35 ) {
And IO::Socket is part of base
Best Regards
[demime 1.01d removed an attachment of type application/pkcs7-signature which
had a name of smime.p7s]
Re: OpenSMTPD with filter-spamassassin / max-children
Thanks for the precisions regarding max-inflight. That would be great if there could be a max session limit which would simply return a temporary failure when too busy. Maybe for a next version of OpenSMTPD... On Wednesday, April 20, 2016 8:51 AM, Gilles Chehade wrote: On Tue, Apr 19, 2016 at 06:23:18PM +0200, Joerg Jung wrote: > > Am 18.04.2016 um 16:56 schrieb ML mail : > > > > I have configured OpenSMTPD on OpenBSD 5.9 with the filter-spamassassin as a > relay for a few of my webapp servers and have the problem when a webapp > suddently sends over 30 mails at the same time. Basically the problem is that > as I have configured spamd with 30 as max-children, as soon as I receive 30 > mails at the same time OpenSMTPD stops answering because all spamd childs are > in busy state. This means that as long as all spamd child are in busy state I > can not receive any more mails during that time. > > So you get what you configured/requested. > > > So in theory I would just raise the max-children setting of spamassassin but > then it just postpones the problem really... so is there maybe another way to > deal better with that issue? > > Not really. > > If these are your own web servers they > will not send spam, right? > So considering skip the filtering for them? > > There is a max-inflight limit in smtpd.conf(5) > which you may want to lower (below your 30). > Generally speaking, I'd really avoid playing with max-inflight, it is a scheduler knob from developers to developers. Tweaking it for one particular case means it is tweaked for all cases. > Also, the most recent git head of -extras contains > a limit option which restricts the messages piped > to spamassassin based on their size. The idea is: > fewer/smaller mails are checked (fast), > assuming that larger ones are rarely spam. > much better strategy, maybe it should also contain a max session count to tempfail incoming mail if there are already enough pending sessions I don't know. What I know is that max-inflight is not THE solution for sure. -- Gilles Chehade https://www.poolp.org @poolpOrg
Re: OpenSMTPD with filter-spamassassin / max-children
On Tue, Apr 19, 2016 at 06:23:18PM +0200, Joerg Jung wrote: > > Am 18.04.2016 um 16:56 schrieb ML mail : > > > > I have configured OpenSMTPD on OpenBSD 5.9 with the filter-spamassassin as a > relay for a few of my webapp servers and have the problem when a webapp > suddently sends over 30 mails at the same time. Basically the problem is that > as I have configured spamd with 30 as max-children, as soon as I receive 30 > mails at the same time OpenSMTPD stops answering because all spamd childs are > in busy state. This means that as long as all spamd child are in busy state I > can not receive any more mails during that time. > > So you get what you configured/requested. > > > So in theory I would just raise the max-children setting of spamassassin but > then it just postpones the problem really... so is there maybe another way to > deal better with that issue? > > Not really. > > If these are your own web servers they > will not send spam, right? > So considering skip the filtering for them? > > There is a max-inflight limit in smtpd.conf(5) > which you may want to lower (below your 30). > Generally speaking, I'd really avoid playing with max-inflight, it is a scheduler knob from developers to developers. Tweaking it for one particular case means it is tweaked for all cases. > Also, the most recent git head of -extras contains > a limit option which restricts the messages piped > to spamassassin based on their size. The idea is: > fewer/smaller mails are checked (fast), > assuming that larger ones are rarely spam. > much better strategy, maybe it should also contain a max session count to tempfail incoming mail if there are already enough pending sessions I don't know. What I know is that max-inflight is not THE solution for sure. -- Gilles Chehade https://www.poolp.org @poolpOrg
Re: OpenSMTPD with filter-spamassassin / max-children
Thanks for the pointer to limit scheduler max-inflight that sounds exactly what I need. I checked the smtpd.conf man page and it looks like there are no default values so I am guessing here that the default is unlimited. I will have a try at it. Regarding spamd in theory you are right I would not need a spam filter for sending mails from various web apps, but I simply can not trust web apps from third-parties, e.g. a WordPress website gets hacked and is abused to send mails in mass... by the way I also use the filter-clamav, you never know. Regards ML On Tuesday, April 19, 2016 6:30 PM, Joerg Jung wrote: > Am 18.04.2016 um 16:56 schrieb ML mail : > > I have configured OpenSMTPD on OpenBSD 5.9 with the filter-spamassassin as a relay for a few of my webapp servers and have the problem when a webapp suddently sends over 30 mails at the same time. Basically the problem is that as I have configured spamd with 30 as max-children, as soon as I receive 30 mails at the same time OpenSMTPD stops answering because all spamd childs are in busy state. This means that as long as all spamd child are in busy state I can not receive any more mails during that time. So you get what you configured/requested. > So in theory I would just raise the max-children setting of spamassassin but then it just postpones the problem really... so is there maybe another way to deal better with that issue? Not really. If these are your own web servers they will not send spam, right? So considering skip the filtering for them? There is a max-inflight limit in smtpd.conf(5) which you may want to lower (below your 30). Also, the most recent git head of -extras contains a limit option which restricts the messages piped to spamassassin based on their size. The idea is: fewer/smaller mails are checked (fast), assuming that larger ones are rarely spam.
Re: OpenSMTPD with filter-spamassassin / max-children
> Am 18.04.2016 um 16:56 schrieb ML mail : > > I have configured OpenSMTPD on OpenBSD 5.9 with the filter-spamassassin as a relay for a few of my webapp servers and have the problem when a webapp suddently sends over 30 mails at the same time. Basically the problem is that as I have configured spamd with 30 as max-children, as soon as I receive 30 mails at the same time OpenSMTPD stops answering because all spamd childs are in busy state. This means that as long as all spamd child are in busy state I can not receive any more mails during that time. So you get what you configured/requested. > So in theory I would just raise the max-children setting of spamassassin but then it just postpones the problem really... so is there maybe another way to deal better with that issue? Not really. If these are your own web servers they will not send spam, right? So considering skip the filtering for them? There is a max-inflight limit in smtpd.conf(5) which you may want to lower (below your 30). Also, the most recent git head of -extras contains a limit option which restricts the messages piped to spamassassin based on their size. The idea is: fewer/smaller mails are checked (fast), assuming that larger ones are rarely spam.
OpenSMTPD with filter-spamassassin / max-children
Hello, I have configured OpenSMTPD on OpenBSD 5.9 with the filter-spamassassin as a relay for a few of my webapp servers and have the problem when a webapp suddently sends over 30 mails at the same time. Basically the problem is that as I have configured spamd with 30 as max-children, as soon as I receive 30 mails at the same time OpenSMTPD stops answering because all spamd childs are in busy state. This means that as long as all spamd child are in busy state I can not receive any more mails during that time. So in theory I would just raise the max-children setting of spamassassin but then it just postpones the problem really... so is there maybe another way to deal better with that issue? Regards ML
Re: filter-spamassassin
On Sat, Jan 02, 2016 at 07:21:13PM -0600, Edgar Pettijohn wrote: > I finally got around to trying out filter-spamassassin. It appears to work > correctly. However, I was trying to change the default action from accept > to reject. I've tried everything I can think of but continue to get syntax > errors. I assumed something like this would work: > > filter spam spamassassin -s reject You need to quote the args: filter spam spamassassin "-s reject" > listen on egress filter spam > > But it didn't. > > Any help is appreciated. > > Edgar Pettijohn
filter-spamassassin
I finally got around to trying out filter-spamassassin. It appears to work correctly. However, I was trying to change the default action from accept to reject. I've tried everything I can think of but continue to get syntax errors. I assumed something like this would work: filter spam spamassassin -s reject listen on egress filter spam But it didn't. Any help is appreciated. Edgar Pettijohn
SpamAssassin Consult
We have a mailserver that will not post email, and it appears that SpamAssassin is not running [via Mailscanner]. Load isn't the problem, something apparently changed this evening. Looking for someone that can take a look [paid gig] now, .. if possible. [Not a current system.] Thanks! Lee
Re: Spamassassin fails to start after upgrade to latest snapshot
.. Thu 28.Mar'13 at 14:01:10 +0100 Remco ... > James Griffin wrote: > > > Hi > > > > Basically, as the subject says: I upgraded to the latest snapshot and now > > spamassassin fails start. > > > > This is the error out when I try to start it from the command-line: [snip] > > Cheers, Jamie. > > > > > > Maybe you're bitten by the perl update as described in > http://www.openbsd.org/faq/current.html. Yes, looks like it. I'll just wait for the updates then. Cheers Remco. -- James Griffin: jmz at kontrol.kode5.net jmzgriffin at gmail.com A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
Re: Spamassassin fails to start after upgrade to latest snapshot
James Griffin wrote: > Hi > > Basically, as the subject says: I upgraded to the latest snapshot and now > spamassassin fails start. > > This is the error out when I try to start it from the command-line: > > > Bad arg length for NetAddr::IP::Util::mask4to6, length is 128, should be > 32 at /usr/local/libdata/perl5/site_perl/amd64-openbsd/NetAddr/IP/Lite.pm > line 625. Compilation failed in require at > /usr/local/libdata/perl5/site_perl/amd64-openbsd/NetAddr/IP.pm line 7. > BEGIN failed--compilation aborted at > /usr/local/libdata/perl5/site_perl/amd64-openbsd/NetAddr/IP.pm line 7. > Compilation failed in require at > /usr/local/libdata/perl5/site_perl/Mail/SpamAssassin/NetSet.pm line 25. > BEGIN failed--compilation aborted at > /usr/local/libdata/perl5/site_perl/Mail/SpamAssassin/NetSet.pm line 25. > Compilation failed in require at > /usr/local/libdata/perl5/site_perl/Mail/SpamAssassin/Conf.pm line 86. > BEGIN failed--compilation aborted at > /usr/local/libdata/perl5/site_perl/Mail/SpamAssassin/Conf.pm line 86. > Compilation failed in require at > /usr/local/libdata/perl5/site_perl/Mail/SpamAssassin.pm line 71. BEGIN > failed--compilation aborted at > /usr/local/libdata/perl5/site_perl/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. > > Not sure exactly what the problem is. Has anyone else seen this and does > anyone know what I can do to fix it? > > Cheers, Jamie. > > Maybe you're bitten by the perl update as described in http://www.openbsd.org/faq/current.html.
Spamassassin fails to start after upgrade to latest snapshot
Hi Basically, as the subject says: I upgraded to the latest snapshot and now spamassassin fails start. This is the error out when I try to start it from the command-line: Bad arg length for NetAddr::IP::Util::mask4to6, length is 128, should be 32 at /usr/local/libdata/perl5/site_perl/amd64-openbsd/NetAddr/IP/Lite.pm line 625. Compilation failed in require at /usr/local/libdata/perl5/site_perl/amd64-openbsd/NetAddr/IP.pm line 7. BEGIN failed--compilation aborted at /usr/local/libdata/perl5/site_perl/amd64-openbsd/NetAddr/IP.pm line 7. Compilation failed in require at /usr/local/libdata/perl5/site_perl/Mail/SpamAssassin/NetSet.pm line 25. BEGIN failed--compilation aborted at /usr/local/libdata/perl5/site_perl/Mail/SpamAssassin/NetSet.pm line 25. Compilation failed in require at /usr/local/libdata/perl5/site_perl/Mail/SpamAssassin/Conf.pm line 86. BEGIN failed--compilation aborted at /usr/local/libdata/perl5/site_perl/Mail/SpamAssassin/Conf.pm line 86. Compilation failed in require at /usr/local/libdata/perl5/site_perl/Mail/SpamAssassin.pm line 71. BEGIN failed--compilation aborted at /usr/local/libdata/perl5/site_perl/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. Not sure exactly what the problem is. Has anyone else seen this and does anyone know what I can do to fix it? Cheers, Jamie. -- James Griffin: jmz at kontrol.kode5.net jmzgriffin at gmail.com A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
Re: sptmd(8), MDA and SpamAssassin? (semi-OT)
On Sun, Dec 20, 2009 at 11:10:21PM -0600, Adam Thompson wrote: > Is there a better way? Can I skip procmail? (Do I want to? Procmail > also seems to be the only way to have Maildir-format for some users and > mbox-format for others, when using smtpd(8).) Is there any (useful) way > to invoke spamc(1L) as an MDA? If there are needs such as having different mbox formats for different users, then using a program like procmail is natural.
sptmd(8), MDA and SpamAssassin? (semi-OT)
OK, so (despite running -stable, not -current) smtpd(8) seems to be working well for me in local testing. I love the compact configuration system. There may come a time when I need more flexibility to handle corner cases, but until then I'll gladly use an MTA that only needs ~10 lines of config file! I wish to integrate SpamAssassin before moving my MX records. Is it correct to say that SpamAssassin can be used as a filter, i.e. it takes the unchanged message on stdin and emits a changed message on stdout? It seems obvious that I can tie smtpd(8) and spamc(1L) together with procmail(1L); smtpd(8) seems to have no issue whatsoever with using procmail as its MDA. I then would configure procmail to invoke SpamAssassin in the "site-wide" scenario that is reasonably well- documented. Is there a better way? Can I skip procmail? (Do I want to? Procmail also seems to be the only way to have Maildir-format for some users and mbox-format for others, when using smtpd(8).) Is there any (useful) way to invoke spamc(1L) as an MDA? FYI: For those of you who are wondering why I'm not just slapping this together and hoping for the best, i.e. why do I keep whining on -misc when I already seem to know the answers... as soon as I change the MX record, this server will be immediately hit with peaks of up to ~ 2kmsgs/hr and will sustain constant levels of ~10kmsgs/day with occasional peaks to ~20kmsgs/day. Approximately 50 msgs/day (0.5%) of that is *not* spam. Thanks in advance for any suggestions or advice. -Adam Thompson
Re: Contemporary Sendmail, Clamav, SpamAssassin et al
--- Chris [Thu, Jul 30, 2009 at 12:01:43PM -0400]: --- > Hello. > > About 4 years ago I installed this combo on an obsd 3.6 box, and it has > worked quite well for me. I really like the obsd way of things. Now I'm > ready to undertake this again, but rather than just blindly recreate what > I had before, I wanted to check how this is handled in this day & age -- > with obsd 4.5. i built up a 4.5 box this past spring, and sendmail, clamav, and spamassassin are what i used. for me the only question was to use sendmail or postfix. in the end, i chose sendmail because it's in base. that's really all it came down to for me---i don't like the idea of passing up all the hardwork that goes into sendmail by the devs for something shiny and new. i get to (have to?) support postfix at $work, so at least i do get the resume-building benefit of knowing more than one MTA. > Specifically, I wanted to know how clamav and spamassassin are invoked > by sendmail. In the old days, I used smtp-vilter. Is that still the > method of choice? i belive that balmer@ wrote smtp-vilter, so i'd venture to say there's not much need to look elsewhere. this is what i ended up with. works flawlessly for me. > Also > > What are people using these days for IMAP/POP/SMTP and encryption of > those protocols as well as encryption of smtp? I've been reading a bit > on Dovecot for IMAP/POP -- any opinions there? For smtp auth I used > Cyrus-sasl... that still recommended. Also interested in the best way > implement tls/ssl on smtp now days as well. i went with Dovecot in this case. although i haven't done much with TLS/SSL on sendmail, i am pretty sure ssl(8) has most of what you'll be looking for. i think there's a writeup mostly apropos at calomel.org, but last i recall looking at it, it might have been a bit stale. it will most certainly get you in the right direction.
Contemporary Sendmail, Clamav, SpamAssassin et al
Hello. About 4 years ago I installed this combo on an obsd 3.6 box, and it has worked quite well for me. I really like the obsd way of things. Now I'm ready to undertake this again, but rather than just blindly recreate what I had before, I wanted to check how this is handled in this day & age -- with obsd 4.5. Specifically, I wanted to know how clamav and spamassassin are invoked by sendmail. In the old days, I used smtp-vilter. Is that still the method of choice? Also What are people using these days for IMAP/POP/SMTP and encryption of those protocols as well as encryption of smtp? I've been reading a bit on Dovecot for IMAP/POP -- any opinions there? For smtp auth I used Cyrus-sasl... that still recommended. Also interested in the best way implement tls/ssl on smtp now days as well. If anyone knows of any good documentation on these subjects, I'd love a url. Thank you very much for the input.
SUMMARY: Problem getting packages (SpamAssassin)
Simon Loewen wrote: > Hi all, > > > I have tried to download some packages from these mirrors, > > http://openbsd.berkeley.edu/pub/OpenBSD/4.5/packages/i386 > http://anga.funkfeuer.at/ftp/pub/OpenBSD/4.5/packages/i386 > http://obsd.cec.mtu.edu/pub/OpenBSD/4.5/packages/i386 > > ...And am told these packages don't exist. I am following an > installation document here to install SpamAssasin: > http://www.kernel-panic.it/openbsd/mail/mail6.html > > Where can I get these from? > > Can't resolve p5-Compress-Raw-Zlib > Can't resolve p5-IO-Compress-Base > Can't resolve p5-IO-Compress-Zlib > Can't resolve p5-Compress-Zlib > Can't resolve p5-IO-Zlib > Can't resolve p5-Archive-Tar > Can't resolve p5-IO-INET6 > > Best regards, S. > > Thank-you to all who replied. Solution: pkg_add p5-Mail-SpamAssassin Thanks for everyone who replied. The best answer was from: Kili That guide is retarded. It seems to list nearly all dependencies that amavisd-new & friends required at a certain point in time. If you need spamassassin, pkg_add p5-Mail-SpamAssassin. If you need amavisd-new, pkg_add amavisd-new. And from Daniel: In base: http://marc.info/?l=openbsd-ports-cvs&m=123088683223617&w=2 >From me: I noticed it was dropped from ports in March 2009: http://openports.se/archivers/p5-Archive-Tar Version History (View Complete History) (2009-03-09) *Package deleted from Ports* (2008-07-28) Updated to version: p5-Archive-Tar-1.38 (2007-12-18) Updated to version: p5-Archive-Tar-1.36 (2006-09-19) Updated to version: p5-Archive-Tar-1.30 (2006-08-01) Updated to version: p5-Archive-Tar-1.29 (2006-07-21) Package added to openports.se, version p5-Archive-Tar-1.26p0 (created)
Re: Spamassassin overwrites manual of OpenBSD spamd
Darren Spruell wrote: The 'man -M' method gives you good flexibility for choosing what page. Not to mention doing something like 'man -a spamd'.
Re: Spamassassin overwrites manual of OpenBSD spamd
Woodchuck wrote: As a work-around, you can name the spamassassin spamd's man pages something else, say Spamd. I don't know if there is an easy solution for this (I don't want to call it a problem), but I think this shouldn't happen. This is probably a matter for the spamassassin port maintainter. Renaming its spamd would not be hard. it's already in a different section of the manual, SpamAssassins spamd manpage is spamd(1) whereas the base spamd manpage is spamd(8).
Re: Spamassassin overwrites manual of OpenBSD spamd
Woodchuck wrote: On Tue, 20 Feb 2007, Mike Erdely wrote: Guido Tschakert wrote: The first and the last entry are both spamd (8), but spamassassin from ports has overwritten /usr/local/man/man8/spamd.8 from the system (which I am looking for) The man page for OpenBSD's spamd is not in /usr/local. On my system, SpamAssassin's spamd is (1) not (8). For OpenBSD's spamd: man 8 spamd For SpamAssassin: man 1 spamd That spamd (8) in /usr/local must be from something else: The version of spamassassin (p5-Mail-SpamAssassin-3.1.4p0) I have installed does install that file. This is, I believe, the latest 4.0-stable port. The -current version (3.1.8) definitely does not.
Re: Spamassassin overwrites manual of OpenBSD spamd
On 2/20/07, Woodchuck <[EMAIL PROTECTED]> wrote: On Tue, 20 Feb 2007, Mike Erdely wrote: > Guido Tschakert wrote: > > The first and the last entry are both spamd (8), but spamassassin from > > ports has overwritten /usr/local/man/man8/spamd.8 from the system (which > > I am looking for) > > The man page for OpenBSD's spamd is not in /usr/local. > On my system, SpamAssassin's spamd is (1) not (8). > > For OpenBSD's spamd: man 8 spamd > For SpamAssassin: man 1 spamd > > That spamd (8) in /usr/local must be from something else: The version of spamassassin (p5-Mail-SpamAssassin-3.1.4p0) I have installed does install that file. This is, I believe, the latest 4.0-stable port. Sure enough: $ PKG_PATH=ftp://ftp.openbsd.org/pub/OpenBSD/4.0/packages/i386 pkg_info -L p5-Mail-SpamAssassin-3.1.4p0 |grep man |grep spamd /usr/local/man/man1/spamd.1 /usr/local/man/man8/spamd.8 The 'man -M' method gives you good flexibility for choosing what page. DS
Re: Spamassassin overwrites manual of OpenBSD spamd
Guido Tschakert <[EMAIL PROTECTED]> wrote: > Hello, > > while reading the discussion about spamd, I decided to learn a little > bit about it and have a look in the manual, but man spamd yields to the > manual of "spamd - daemonized version of spamassassin" what is not > exactly what I was looking for. (I installed p5-Mail-SpamAssasin from > ports/packages) > > apropos spamd shows: > spamd (8) - spam deferral daemon > spamd-setup (8) - parse and load file of spammer addresses > spamd.conf (5) - configuration file read by spamd-setup(8) for spamd(8) > spamdb (8) - spamd database tool > spamlogd (8) - spamd whitelist updating daemon > Mail::SpamAssassin::Client (3p) - Client for spamd Protocol > spamc (1) - client for spamd > spamd (1) - daemonized version of spamassassin > spamd (8) - daemonized version of spamassassin > > The first and the last entry are both spamd (8), but spamassassin from > ports has overwritten /usr/local/man/man8/spamd.8 from the system (which > I am looking for) > > I don't know if there is an easy solution for this (I don't want to call > it a problem), but I think this shouldn't happen. > > For now I go to > http://www.openbsd.org/cgi-bin/man.cgi?query=spamd&apropos=0&sektion=0&manpath=OpenBSD+Current&arch=i386&format=html > and read the manual online :-) > > thanks > guido The manpage of the in-system spamd lives in /usr/share/man/cat8/spamd.0
Re: Spamassassin overwrites manual of OpenBSD spamd
On Tue, 20 Feb 2007, Mike Erdely wrote: > Guido Tschakert wrote: > > The first and the last entry are both spamd (8), but spamassassin from > > ports has overwritten /usr/local/man/man8/spamd.8 from the system (which > > I am looking for) > > The man page for OpenBSD's spamd is not in /usr/local. > On my system, SpamAssassin's spamd is (1) not (8). > > For OpenBSD's spamd: man 8 spamd > For SpamAssassin: man 1 spamd > > That spamd (8) in /usr/local must be from something else: The version of spamassassin (p5-Mail-SpamAssassin-3.1.4p0) I have installed does install that file. This is, I believe, the latest 4.0-stable port. Dave
Re: Spamassassin overwrites manual of OpenBSD spamd
On Tuesday 20 February 2007 15:14, Woodchuck wrote: > > I don't know if there is an easy solution for this (I don't want to > > call it a problem), but I think this shouldn't happen. > > This is probably a matter for the spamassassin port maintainter. > Renaming its spamd would not be hard. > > Dave Sure, the maintainer *could* rename the spamassassin "spamd" to supposedly prevent confusion and/or supposedly make thing easy for a novice but the best answer is accepting the fact that names are not unique and accepting the fact that learning to correctly use the system will give the desired results. $ man -w spamd /usr/share/man/cat8/spamd.0 /usr/local/man/man8/spamd.8 $ man -M /usr/local/man: spamd __or__ $ man -M /usr/share/man: spamd If we start fighting the battle to keep all names unique across all software, we are bound to lose, miss things, and eventually have a system that is even more confusing to use due to the mistakes, oversights and omissions. my .02 Kind Regards, JCR
Re: Spamassassin overwrites manual of OpenBSD spamd
Jason McIntyre wrote: > On Tue, Feb 20, 2007 at 10:19:31PM +0100, Guido Tschakert wrote: >> The first and the last entry are both spamd (8), but spamassassin from >> ports has overwritten /usr/local/man/man8/spamd.8 from the system (which >> I am looking for) >> >> I don't know if there is an easy solution for this (I don't want to call >> it a problem), but I think this shouldn't happen. >> > > you can change the order man(1) looks for its pages in /etc/man.conf, i > think. but probably best is to contact the port maintainer and ask them > to rename the page to stop it squashing base spamd(8). > > jmc > Hi, I already have send my mail to the maintainer of the port. I have looked in /etc/man.conf and read the manual: you can change the order of the subdirs with _subdir, but the order of how the sections are searched (with _default) seems to be alphabetically and /usr/local comes before /usr/share. (correct me, if I'm wrong) Digging in man (1) gives me the following help: $ man -w spamd /usr/local/man/man1/spamd.1 /usr/share/man/cat8/spamd.0 /usr/local/man/man8/spamd.8 $ more /usr/share/man/cat8/spamd.0 BTW, I was wrong with saying the port overwrites the manual of the system-spamd. The system manuals are stored in /usr/share/man while the port manuals go to /usr/local/man, as some guys told me privatly. Stupid me, thanks guido
Re: Spamassassin overwrites manual of OpenBSD spamd
On Tue, 20 Feb 2007, Guido Tschakert wrote: > Hello, > > while reading the discussion about spamd, I decided to learn a little > bit about it and have a look in the manual, but man spamd yields to the > manual of "spamd - daemonized version of spamassassin" what is not > exactly what I was looking for. (I installed p5-Mail-SpamAssasin from > ports/packages) > > apropos spamd shows: > spamd (8) - spam deferral daemon > spamd-setup (8) - parse and load file of spammer addresses > spamd.conf (5) - configuration file read by spamd-setup(8) for spamd(8) > spamdb (8) - spamd database tool > spamlogd (8) - spamd whitelist updating daemon > Mail::SpamAssassin::Client (3p) - Client for spamd Protocol > spamc (1) - client for spamd > spamd (1) - daemonized version of spamassassin > spamd (8) - daemonized version of spamassassin > > The first and the last entry are both spamd (8), but spamassassin from > ports has overwritten /usr/local/man/man8/spamd.8 from the system (which > I am looking for) The system's version is in /usr/share/man/cat8/spamd.0 by default. You can see them all with man -a spamd. (At least on my 4.0-stable) As a work-around, you can name the spamassassin spamd's man pages something else, say Spamd. > I don't know if there is an easy solution for this (I don't want to call > it a problem), but I think this shouldn't happen. This is probably a matter for the spamassassin port maintainter. Renaming its spamd would not be hard. Dave -- When the mandate of Heaven passes, there occurs the rule of concubines and eunuchs. The rule of concubines and eunuchs endures until the righteous take arms. This is the Tao. -- A fragment from the I Wu Juk, or "Book of Burrowing"
Re: Spamassassin overwrites manual of OpenBSD spamd
On 2/20/07, Guido Tschakert <[EMAIL PROTECTED]> wrote: The first and the last entry are both spamd (8), but spamassassin from ports has overwritten /usr/local/man/man8/spamd.8 from the system (which I am looking for) The base system doesn't install any components under /usr/local/ by default. /usr/share/man/cat8/spamd.0 DS
Re: Spamassassin overwrites manual of OpenBSD spamd
Guido Tschakert wrote: The first and the last entry are both spamd (8), but spamassassin from ports has overwritten /usr/local/man/man8/spamd.8 from the system (which I am looking for) The man page for OpenBSD's spamd is not in /usr/local. On my system, SpamAssassin's spamd is (1) not (8). For OpenBSD's spamd: man 8 spamd For SpamAssassin: man 1 spamd That spamd (8) in /usr/local must be from something else: $ apropos spamd spamd (8) - spam deferral daemon spamd-setup (8) - parse and load file of spammer addresses spamd.conf (5) - configuration file read by spamd-setup(8) for spamd(8) spamdb (8) - spamd database tool spamlogd (8) - spamd whitelist updating daemon Mail::SpamAssassin::Client (3p) - Client for spamd Protocol spamc (1) - client for spamd spamd (1) - daemonized version of spamassassin $ -ME
Re: Spamassassin overwrites manual of OpenBSD spamd
On Tue, Feb 20, 2007 at 10:19:31PM +0100, Guido Tschakert wrote: > > The first and the last entry are both spamd (8), but spamassassin from > ports has overwritten /usr/local/man/man8/spamd.8 from the system (which > I am looking for) > > I don't know if there is an easy solution for this (I don't want to call > it a problem), but I think this shouldn't happen. > you can change the order man(1) looks for its pages in /etc/man.conf, i think. but probably best is to contact the port maintainer and ask them to rename the page to stop it squashing base spamd(8). jmc
Spamassassin overwrites manual of OpenBSD spamd
Hello, while reading the discussion about spamd, I decided to learn a little bit about it and have a look in the manual, but man spamd yields to the manual of "spamd - daemonized version of spamassassin" what is not exactly what I was looking for. (I installed p5-Mail-SpamAssasin from ports/packages) apropos spamd shows: spamd (8) - spam deferral daemon spamd-setup (8) - parse and load file of spammer addresses spamd.conf (5) - configuration file read by spamd-setup(8) for spamd(8) spamdb (8) - spamd database tool spamlogd (8) - spamd whitelist updating daemon Mail::SpamAssassin::Client (3p) - Client for spamd Protocol spamc (1) - client for spamd spamd (1) - daemonized version of spamassassin spamd (8) - daemonized version of spamassassin The first and the last entry are both spamd (8), but spamassassin from ports has overwritten /usr/local/man/man8/spamd.8 from the system (which I am looking for) I don't know if there is an easy solution for this (I don't want to call it a problem), but I think this shouldn't happen. For now I go to http://www.openbsd.org/cgi-bin/man.cgi?query=spamd&apropos=0&sektion=0&manpath=OpenBSD+Current&arch=i386&format=html and read the manual online :-) thanks guido
Re: Openbsd+Spamassassin+milter-spamd
Hi, You may be interested in trying milter-greylist. It's been very effective for me in blocking spam email. http://hcpnet.free.fr/milter-greylist/ Best regards, Tiago Marques On 1/18/07, Tim Jones <[EMAIL PROTECTED]> wrote: > > On Jan 17, 2007, at 11:41 PM, Mike Spenard wrote: > > > Could someone direct me to a howto on setting up Openbsd,sendmail > > and spamassassin > > to use milter-spamd? > > > > Thank you, > > -Mike > > > Mike - > > Check out: > > > http://erdelynet.com/2005/03/26/openbsd/site-side-spamassassin-for- > openbsd-36/ > > While this uses Postfix instead of Sendmail, it's a pretty good set > of instructions: > > http://www.kernel-panic.it/openbsd/mail/ > > HTH, > > Tim
Re: Openbsd+Spamassassin+milter-spamd
On Jan 17, 2007, at 11:41 PM, Mike Spenard wrote: Could someone direct me to a howto on setting up Openbsd,sendmail and spamassassin to use milter-spamd? Thank you, -Mike Mike - Check out: http://erdelynet.com/2005/03/26/openbsd/site-side-spamassassin-for- openbsd-36/ While this uses Postfix instead of Sendmail, it's a pretty good set of instructions: http://www.kernel-panic.it/openbsd/mail/ HTH, Tim
Openbsd+Spamassassin+milter-spamd
Could someone direct me to a howto on setting up Openbsd,sendmail and spamassassin to use milter-spamd? Thank you, -Mike
Re: Spamassassin segfaults
To Karel You should learn what ports and packages are Read FAQ 15 Ports and Packages Fetching port tree read 15.3.2 p5-Mail-SpamAssassin-3.1.0p0.tgz is it this package can't see from your mail. You dont need the ports maintainer when you use the package do you? You need the package mantainer. If you dont understand what i'm talking of, read FAQ 15 First from top to bottom. So you would use the pkg_xxx tools to find out that information i will give you a hint: try man pkg_add (read the doc) check the references (SEE ALSO) to other pkg_xxx commands, and one will reveal it self to be the command thy doth seek for. The tools also work on Compiled ports, see point 3 below. Ports 101: 1)Ports and packages are different. 2)Packages are the recommended(supported) way to install apps, especially for users that don't read docs (you). 3)A Port is compiled into a package (but is not an official package) Docs 101: READ THE DOCS, properly, don't just skim them, please. Reading the /ports.html you should also know that your question (about ports), should have been sent to ports. Though your using packages so the right place is here. Regards Michael
Re: Spamassassin segfaults
On Thu, Dec 28, 2006 at 11:30:27AM +0100, Karel Kulhavy wrote: > Hi > > How do I figure out who is the maintainer of Spamassassin? I put > "How to figure out who is a maintainer of an openbsd package" into google > and got to http://www.openbsd.org/faq/faq15.html > Where they write: > "To see who is the maintainer of the port, type, for example: > $ cd /usr/ports/archivers/unzip > $ make show=MAINTAINER" > > [EMAIL PROTECTED]:~$ cd /usr/ports > bash: cd: /usr/ports: No such file or directory You've already been pointed to pkg_info; in this case, it's [EMAIL PROTECTED] > My OpenBSD is 3.9 installed from packages. > When I run sa-learn, Perl segfaults after some time and leaves a stale lock. > Seems in some database library: > > #0 0x05cce49a in hash_access (hashp=0x87dcb000, action=HASH_GET, > key=0xcfbea700, val=0xcfbea6f8) at /usr/src/lib/libc/db/hash/hash.c:624 > rbufp = (BUFHEAD *) 0x89cfb700 > bufp = (BUFHEAD *) 0x2 > save_bufp = (BUFHEAD *) 0x89cfb700 > bp = (u_int16_t *) 0x86b0a1fe > n = 670 > ndx = 255 > off = -2121377408 > size = 53 > kp = 0x818e5980 "[EMAIL PROTECTED]" > pageno = 563 > #1 0x0b49cb0c in XS_DB_File_FETCH () >from /usr/lib/perl5/5.8.6/OpenBSD.i386-openbsd/auto/DB_File/DB_File.so > No symbol table info available. > #2 0x1c064c4e in Perl_pp_entersub () > No symbol table info available. > #3 0x1c05eac4 in Perl_runops_standard () > No symbol table info available. > #4 0x1c0188e6 in S_call_body () > No symbol table info available. > #5 0x1c01882f in Perl_call_sv () > No symbol table info available. > > When I clear the stale lock and re-run it, then it segfaults again. Are you > familiar with this problem? No, it's not supposed to happen. And quite a few people use it without issues. > I will try yet erasing the .spamassassin directory > (no idea how to erase the db without corrupting the contents of .spamassassin) > and then retrain. What I also don't like is that SA is very slow. I don't > believe Bayesian statistics are so computationally expensive. > > Can you recommend a different tool than spamassassin? I wonder what CRM114 is > http://crm114.sourceforge.net/ dspam is supposed to be a better Bayesian filtering tool than SA. A nontrivial percentage of SA's time is spent doing stuff other than Bayesian filtering, though - various network checks, and static filter rules. Joachim
Re: Spamassassin segfaults
On Thu, Dec 28, 2006 at 11:30:27AM +0100, Karel Kulhavy wrote: > Can you recommend a different tool than spamassassin? I wonder > what CRM114 is http://crm114.sourceforge.net/ I've some unfinished ports for crm114 available, and i'm using it for quite some time now to classify mail. Works quite well, but you've to train it a lot in the beginning, and you've still to watch out for false positives, especially after training new false negatives. Ciao, Kili
Re: Spamassassin segfaults
On 2006/12/28 11:30, Karel Kulhavy wrote: > How do I figure out who is the maintainer of Spamassassin? I put > "How to figure out who is a maintainer of an openbsd package" into google > and got to http://www.openbsd.org/faq/faq15.html > Where they write: > "To see who is the maintainer of the port, type, for example: That requires an unpacked ports tree. You may like to try sqlports and sqlitebrowser (or look at the Maakefile with cvsweb, or http://ports.openbsd.nu/). > What I also don't like is that SA is very slow. I don't > believe Bayesian statistics are so computationally expensive. > > Can you recommend a different tool than spamassassin? I wonder what CRM114 is > http://crm114.sourceforge.net/ The other checks take their time (unpacking html, lots of regex searches, DNS lookups, and lots of compilation if you don't run it as a daemon). I haven't tried it myself but maybe dspam would be suitable? It's in ports. Or feed a greylisting spamd with some good spamtraps...
Re: Spamassassin segfaults
On Thu, Dec 28, 2006 at 11:30:27AM +0100, Karel Kulhavy wrote: > When I clear the stale lock and re-run it, then it segfaults again. Are you > familiar with this problem? I will try yet erasing the .spamassassin directory > (no idea how to erase the db without corrupting the contents of .spamassassin) > and then retrain. What I also don't like is that SA is very slow. I don't > believe Bayesian statistics are so computationally expensive. > > Can you recommend a different tool than spamassassin? I wonder what CRM114 is > http://crm114.sourceforge.net/ I don't use spamassassin for its bayesian filters. I have a combo spamassassin + bogofilter, where spamassassin only sees the stuff when bogofilter cannot classify it.
Spamassassin segfaults
Hi How do I figure out who is the maintainer of Spamassassin? I put "How to figure out who is a maintainer of an openbsd package" into google and got to http://www.openbsd.org/faq/faq15.html Where they write: "To see who is the maintainer of the port, type, for example: $ cd /usr/ports/archivers/unzip $ make show=MAINTAINER" [EMAIL PROTECTED]:~$ cd /usr/ports bash: cd: /usr/ports: No such file or directory My OpenBSD is 3.9 installed from packages. When I run sa-learn, Perl segfaults after some time and leaves a stale lock. Seems in some database library: #0 0x05cce49a in hash_access (hashp=0x87dcb000, action=HASH_GET, key=0xcfbea700, val=0xcfbea6f8) at /usr/src/lib/libc/db/hash/hash.c:624 rbufp = (BUFHEAD *) 0x89cfb700 bufp = (BUFHEAD *) 0x2 save_bufp = (BUFHEAD *) 0x89cfb700 bp = (u_int16_t *) 0x86b0a1fe n = 670 ndx = 255 off = -2121377408 size = 53 kp = 0x818e5980 "[EMAIL PROTECTED]" pageno = 563 #1 0x0b49cb0c in XS_DB_File_FETCH () from /usr/lib/perl5/5.8.6/OpenBSD.i386-openbsd/auto/DB_File/DB_File.so No symbol table info available. #2 0x1c064c4e in Perl_pp_entersub () No symbol table info available. #3 0x1c05eac4 in Perl_runops_standard () No symbol table info available. #4 0x1c0188e6 in S_call_body () No symbol table info available. #5 0x1c01882f in Perl_call_sv () No symbol table info available. When I clear the stale lock and re-run it, then it segfaults again. Are you familiar with this problem? I will try yet erasing the .spamassassin directory (no idea how to erase the db without corrupting the contents of .spamassassin) and then retrain. What I also don't like is that SA is very slow. I don't believe Bayesian statistics are so computationally expensive. Can you recommend a different tool than spamassassin? I wonder what CRM114 is http://crm114.sourceforge.net/ CL<
Re: Spamassassin install from ports fail.
Woodchuck skrev: On Wed, 27 Sep 2006, Hans Almqvist wrote: Hi all! I am trying to install Spamassaassin from the ports tree on an OpenBSD 3.9 system. I have removed /usr/ports an downloaded a fresh copy starting from scratch. I did one prior run with make which of course gave the same result. I get the fallowing: *Error in package*: # cd /usr/ports/mail/p5-Mail-SpamAssassin/ # make ===> p5-Mail-SpamAssassin-3.1.0p0 depends on: p5-IO-Socket-SSL-* - not found ===> Verifying install for p5-IO-Socket-SSL-* in security/p5-IO-Socket-SSL ===> Checking files for p5-IO-Socket-SSL-0.97 `/usr/ports/distfiles/IO-Socket-SSL-0.97.tar.gz' is up to date. Checksum OK for IO-Socket-SSL-0.97.tar.gz. (sha1) ===> p5-IO-Socket-SSL-0.97 depends on: p5-Net-SSLeay->=1.21 - not found ===> Verifying install for p5-Net-SSLeay->=1.21 in security/p5-Net_SSLeay ===> Building package for p5-Net-SSLeay-1.25p0 *Error in package*: does not exist ===> Cleaning for p5-Net-SSLeay-1.25p0 rm -f /usr/ports/packages/i386/all/p5-Net-SSLeay-1.25p0.tgz *** Error code 1 Hmmm. Works for me. Just rebuilt the p5-Net-SSLeay-1.25p0 package from source. My source: MD5 (/usr/ports/distfiles/Net_SSLeay.pm-1.25.tar.gz) = 87de8a06802fbb63c7c85e89eedbe139 Try again. Could you have run out of disk space or had some other sort of transient error? Dave Ok. I fetched "p5-Net-SSLeay-1.25p0.tgz" and did a pkg_add. After that the install proceeded. Thanks Dave. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Re: Spamassassin install from ports fail.
On Wed, 27 Sep 2006, Hans Almqvist wrote: > Hi all! > > I am trying to install Spamassaassin from the ports tree on an OpenBSD 3.9 > system. > > I have removed /usr/ports an downloaded a fresh copy starting from scratch. > I did one prior run with make which of course gave the same result. > > I get the fallowing: *Error in package*: > > ==== > # cd /usr/ports/mail/p5-Mail-SpamAssassin/ > # make > ===> p5-Mail-SpamAssassin-3.1.0p0 depends on: p5-IO-Socket-SSL-* - not found > ===> Verifying install for p5-IO-Socket-SSL-* in security/p5-IO-Socket-SSL > ===> Checking files for p5-IO-Socket-SSL-0.97 > `/usr/ports/distfiles/IO-Socket-SSL-0.97.tar.gz' is up to date. > >> Checksum OK for IO-Socket-SSL-0.97.tar.gz. (sha1) > ===> p5-IO-Socket-SSL-0.97 depends on: p5-Net-SSLeay->=1.21 - not found > ===> Verifying install for p5-Net-SSLeay->=1.21 in security/p5-Net_SSLeay > ===> Building package for p5-Net-SSLeay-1.25p0 > *Error in package*: > does not exist > ===> Cleaning for p5-Net-SSLeay-1.25p0 > rm -f /usr/ports/packages/i386/all/p5-Net-SSLeay-1.25p0.tgz > *** Error code 1 Hmmm. Works for me. Just rebuilt the p5-Net-SSLeay-1.25p0 package from source. My source: MD5 (/usr/ports/distfiles/Net_SSLeay.pm-1.25.tar.gz) = 87de8a06802fbb63c7c85e89eedbe139 Try again. Could you have run out of disk space or had some other sort of transient error? Dave
Spamassassin install from ports fail.
Hi all! I am trying to install Spamassaassin from the ports tree on an OpenBSD 3.9 system. I have removed /usr/ports an downloaded a fresh copy starting from scratch. I did one prior run with make which of course gave the same result. I get the fallowing: *Error in package*: # cd /usr/ports/mail/p5-Mail-SpamAssassin/ # make ===> p5-Mail-SpamAssassin-3.1.0p0 depends on: p5-IO-Socket-SSL-* - not found ===> Verifying install for p5-IO-Socket-SSL-* in security/p5-IO-Socket-SSL ===> Checking files for p5-IO-Socket-SSL-0.97 `/usr/ports/distfiles/IO-Socket-SSL-0.97.tar.gz' is up to date. >> Checksum OK for IO-Socket-SSL-0.97.tar.gz. (sha1) ===> p5-IO-Socket-SSL-0.97 depends on: p5-Net-SSLeay->=1.21 - not found ===> Verifying install for p5-Net-SSLeay->=1.21 in security/p5-Net_SSLeay ===> Building package for p5-Net-SSLeay-1.25p0 *Error in package*: "/usr/ports/security/p5-Net_SSLeay/w-p5-Net-SSLeay-1.25p0/fake-i386//usr/local/man/man3p/Net::SSLeay::Handle.3p" does not exist ===> Cleaning for p5-Net-SSLeay-1.25p0 rm -f /usr/ports/packages/i386/all/p5-Net-SSLeay-1.25p0.tgz *** Error code 1 Stop in /usr/ports/security/p5-Net_SSLeay (line 2075 of /usr/ports/infrastructure/mk/bsd.port.mk).*** Error code 1 Stop in /usr/ports/security/p5-Net_SSLeay (line 1308 of /usr/ports/infrastructure/mk/bsd.port.mk).*** Error code 1 Stop in /usr/ports/security/p5-IO-Socket-SSL (line 1422 of /usr/ports/infrastructure/mk/bsd.port.mk). *** Error code 1 Stop in /usr/ports/security/p5-IO-Socket-SSL (line 1750 of /usr/ports/infrastructure/mk/bsd.port.mk).*** Error code 1 Stop in /usr/ports/mail/p5-Mail-SpamAssassin (line 1422 of /usr/ports/infrastructure/mk/bsd.port.mk). # ls /usr/ports/security/p5-Net_SSLeay/w-p5-Net-SSLeay-1.25p0/fake-i386//usr/local/man/man3p Net::SSLeay.3p There is no "Net::SSLeay::Handle.3p" in that directory as written by the error message. Just "Net::SSLeay.3p". Any clue? /Hasse -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Re: SpamAssassin autolearn problem
Per-Olov Sjvholm wrote:
>On Thursday 06 April 2006 16.15, Gabriel George POPA wrote:
>
>
>>Some e-mails I receive have autolearn=no and others have
>>autolearn=failed. I use the classic combination of spamd/spamc and the
>>OpenBSD 3.8 provided p5-SpamAssassin package, installed as OpenBSD
>>recommends. I tried to follow the instructions at
>>spamassassin.apache.org (to use for example /var/spamassassin (0777
>>mode) in order to store learnt data, bayes_path and bayes_file_mode,
>>restarted spamd etc., nothing worked). What should I do next? I must
>>create all those files by hand (the files in /var/spamassassin). I must
>>mention that when I was using spamassassin alone (not spamc/spamd) for
>>my account autolearn worked correctly.
>>
>>
>>Respectfully yours,
>>
>>Gabriel George POPA
>>
>>
>
>This is what I have got (On 3.8 stable with spamassassin 3.0.4)
>[EMAIL PROTECTED]:/tmp#ls -al /var/spamassassin
>total 20
>drwxr-x--- 5 _spamass _spamass 512 Jan 31 15:42 .
>drwxr-xr-x 32 root wheel 1024 Feb 26 18:45 ..
>drwxr-x--- 2 _spamass _spamass 512 Apr 5 16:42 .razor
>drwx-- 2 _spamass _spamass 512 Apr 6 23:49 .spamassassin
>
>The files and directories in /var/spamassassin will be automatically created
>Note that the _spamass users home directory is /var/spamassassin
>
>
>In /etc/rc.local I have...
>if [ X"${spamassassin_spamd}" == X"YES" -a -x /usr/local/bin/spamd \
>-a -e /etc/mail/spamassassin/local.cf ]; then
> echo -n ' Spamassassin spamd'; /usr/local/bin/spamd -d -p 3312
>-u _spamass --max-children=5 --max-conn-per-child=2000 -x
>fi
>
>It's called from sendmail through the smtp-vilter connector and it just works.
>
>smtp-vilter talks to spamd.
>
>The only thing you need in /etc/mail/spamassassin/local.cf is... nothing. Well
>you should probably to some tuning. You should probably have:
>--snip--
>required_score 5.0
>report_safe 1
>use_bayes 1
>skip_rbl_checks 0
>--snip--
>
>No path statement is needed in local.cf if you have the correct path for the
>Bayesian db as stated above.
>
>Hope it could be of any use.
>
>Regards
>/Per-Olov
>
>
Very interesting indeed. Anyway, I don't want to use vilter for the
moment. The problem was the following: I thought bayes_path represents a
DIRECTORY (not true, obviously). I was too tired to read well the man
"Mail:SpamAssassin::Conf". I understood wrong the indications there. Sorry.
Re: SpamAssassin autolearn problem
Vielen dank. I now made a configuration based on your own. I thought that bayes_path is a directory (obviously it should not be this way). I started spamd with -u and -d; I realized that -r is useful for sending SIGHUP (otherwise spamd will shut down). George POPA Andreas Vvgele wrote: Gabriel George POPA wrote: Some e-mails I receive have autolearn=no and others have autolearn=failed. I use the classic combination of spamd/spamc and the OpenBSD 3.8 provided p5-SpamAssassin package, installed as OpenBSD recommends. I tried to follow the instructions at spamassassin.apache.org (to use for example /var/spamassassin (0777 mode) in order to store learnt data, bayes_path and bayes_file_mode, restarted spamd etc., nothing worked). What should I do next? I must create all those files by hand (the files in /var/spamassassin). I must mention that when I was using spamassassin alone (not spamc/spamd) for my account autolearn worked correctly. I've created a spamassassin user and group. The user's home directory is /var/spamassassin. Amongst other settings the following paths are set in /etc/mail/spamassassin/local.cf: bayes_path /var/spamassassin/bayes bayes_file_mode 0770 auto_whitelist_path /var/spamassassin/auto-whitelist auto_whitelist_file_mode 0770 spamd is started with the following command line arguments: /usr/local/bin/spamd -d -u spamassassin -H /var/spamassassin -r /var/spamassassin/spamd.pid How do you start spamd?
Re: SpamAssassin autolearn problem
On Thursday 06 April 2006 16.15, Gabriel George POPA wrote:
> Some e-mails I receive have autolearn=no and others have
> autolearn=failed. I use the classic combination of spamd/spamc and the
> OpenBSD 3.8 provided p5-SpamAssassin package, installed as OpenBSD
> recommends. I tried to follow the instructions at
> spamassassin.apache.org (to use for example /var/spamassassin (0777
> mode) in order to store learnt data, bayes_path and bayes_file_mode,
> restarted spamd etc., nothing worked). What should I do next? I must
> create all those files by hand (the files in /var/spamassassin). I must
> mention that when I was using spamassassin alone (not spamc/spamd) for
> my account autolearn worked correctly.
>
>
> Respectfully yours,
>
> Gabriel George POPA
This is what I have got (On 3.8 stable with spamassassin 3.0.4)
[EMAIL PROTECTED]:/tmp#ls -al /var/spamassassin
total 20
drwxr-x--- 5 _spamass _spamass 512 Jan 31 15:42 .
drwxr-xr-x 32 root wheel 1024 Feb 26 18:45 ..
drwxr-x--- 2 _spamass _spamass 512 Apr 5 16:42 .razor
drwx-- 2 _spamass _spamass 512 Apr 6 23:49 .spamassassin
The files and directories in /var/spamassassin will be automatically created
Note that the _spamass users home directory is /var/spamassassin
In /etc/rc.local I have...
if [ X"${spamassassin_spamd}" == X"YES" -a -x /usr/local/bin/spamd \
-a -e /etc/mail/spamassassin/local.cf ]; then
echo -n ' Spamassassin spamd'; /usr/local/bin/spamd -d -p 3312
-u _spamass --max-children=5 --max-conn-per-child=2000 -x
fi
It's called from sendmail through the smtp-vilter connector and it just works.
smtp-vilter talks to spamd.
The only thing you need in /etc/mail/spamassassin/local.cf is... nothing. Well
you should probably to some tuning. You should probably have:
--snip--
required_score 5.0
report_safe 1
use_bayes 1
skip_rbl_checks 0
--snip--
No path statement is needed in local.cf if you have the correct path for the
Bayesian db as stated above.
Hope it could be of any use.
Regards
/Per-Olov
--
GPG keyID: 4DB283CE
GPG fingerprint: 45E8 3D0E DE05 B714 D549 45BC CFB4 BBE9 4DB2 83CE
Re: SpamAssassin autolearn problem
Gabriel George POPA wrote: Some e-mails I receive have autolearn=no and others have autolearn=failed. I use the classic combination of spamd/spamc and the OpenBSD 3.8 provided p5-SpamAssassin package, installed as OpenBSD recommends. I tried to follow the instructions at spamassassin.apache.org (to use for example /var/spamassassin (0777 mode) in order to store learnt data, bayes_path and bayes_file_mode, restarted spamd etc., nothing worked). What should I do next? I must create all those files by hand (the files in /var/spamassassin). I must mention that when I was using spamassassin alone (not spamc/spamd) for my account autolearn worked correctly. I've created a spamassassin user and group. The user's home directory is /var/spamassassin. Amongst other settings the following paths are set in /etc/mail/spamassassin/local.cf: bayes_path /var/spamassassin/bayes bayes_file_mode 0770 auto_whitelist_path /var/spamassassin/auto-whitelist auto_whitelist_file_mode 0770 spamd is started with the following command line arguments: /usr/local/bin/spamd -d -u spamassassin -H /var/spamassassin -r /var/spamassassin/spamd.pid How do you start spamd?
SpamAssassin autolearn problem
Some e-mails I receive have autolearn=no and others have autolearn=failed. I use the classic combination of spamd/spamc and the OpenBSD 3.8 provided p5-SpamAssassin package, installed as OpenBSD recommends. I tried to follow the instructions at spamassassin.apache.org (to use for example /var/spamassassin (0777 mode) in order to store learnt data, bayes_path and bayes_file_mode, restarted spamd etc., nothing worked). What should I do next? I must create all those files by hand (the files in /var/spamassassin). I must mention that when I was using spamassassin alone (not spamc/spamd) for my account autolearn worked correctly. Respectfully yours, Gabriel George POPA
smtp-vilter + spamassassin Subject header rewrites
Does the smtp-vilter.conf line "spam-subject-prefix=*SPAM*" override spamassassins "rewrite_header subject ***SPAM***" (from /etc/mail/spamassassin/local.cf) because I never see the subject being modified by spamassassin? Thanks, -JG
OpenBSD3.8 + smtp-vilter + spamassassin
Hello,
Apologies if this is slightly OT, but I've been over this with the SA list
and they tell me spamassassin is working correctly. Also since smtp-vilter
is one of two milters in packages, I thought there must be people on this
list with experience with it (And I know the author posts here)
I have been running an OpenBSD (now at 3.8) Sendmail relay in my dmz for a
couple years now that forwards to an internal Exchange server. It's nothing
fancy and I'm not really a sendmail or unix expert but it's been getting the
job done.
So the time has come for taking anti-spam measures. To start I'd just like
to mark spam instead of block it (so no OpenBSD's spamd yet), and to that
end I've installed SpamAssassin 3.0.4 and smtp-vilter 1.1.9, both from
packages.
It 'works' to a certain extent, in that smtp-vilter headers are added to all
messages. The problem is, the scores assigned to spam messages are clearly
much too low, and the large majority of spam is not marked as such and much
of it is actually scored negatively.
However, testing manually on a spam I received...
# spamassassin < testspam.txt
and
# spamc -R < testspam.txt
...the message scores a 14.3. However, when I actually received this
message in my mailbox, it was scored -1.6.
So I am thinking that there is a problem somewhere between smtp-vilter and
spamassassin, but where? Has anyone seen this behavior or have a
suggestion? smtp-vilter and (spamassassin's) spamd are both running, are
writing to maillog, and appear to be 'working' as far as I can tell.
This is how smtp-vilter and spamassassin are called:
>From my sendmail.mc:
INPUT_MAIL_FILTER(`smtp-vilter', `S=unix:/var/smtp-vilter/smtp-vilter.sock,
F=T, T=S:10m;R:10m;E:10m')dnl
>From my /etc/rc.conf.local:
smtp_vilter=yes
>From my /etc/rc.local:
# start smtp-vilter
if [ X"${smtp_vilter}" != X"NO" -a \
-x /usr/local/sbin/smtp-vilter ]; then
echo -n ' smtp-vilter'
/usr/local/sbin/smtp-vilter -m -u _vilter -g _vilter
fi
# Start Spamassassin daemon
/usr/local/bin/spamd -u _vilter -d -s mail -x && echo -e "spamd started..."
My entire /etc/smtp-vilter/smtp-vilter.conf: (comments removed)
user=_vilter
group=_vilter
chroot=/var/smtp-vilter
backend=spamd
config-file=spamd:/var/smtp-vilter/etc/spamd.conf
virus-strategy=notify-recipient
recipient-notification=/etc/smtp-vilter/recipient-notification
spam-strategy=mark
spam-subject-prefix="* SPAM *"
unwanted-strategy=mark
error-strategy=tempfail
port=unix:smtp-vilter.sock
tmpdir=/tmp
pidfile=/var/smtp-vilter/smtp-vilter.pid
log-facility=mail
logfile=/var/smtp-vilter/smtp-vilter.log
option=logspam
option=markall
My entire /var/smtp-vilter/etc/spamd.conf: (comments removed)
host=localhost
port=783
tries=3
timeout=600
maxsize=25
option=chroot-scanrealpath
I've read the man pages for smtp-vilter and smtp-vilter.conf, but I must be
doing something stupidly wrong. Does anyone have any ideas or suggestions?
File permissions? Something with the chrooting of smtp-vilter?
Thanks in advance for any and all help.
Mike Sassaman
Re: SpamAssassin - solved
Thanks to all who replied. After seeing that my fellow OpenBSDers had no problem with installing sa-learn through ports, I decided to go back and re-run the install. This time, package Net-DNS-0.47.tar.gz was downloaded and installed and that solved the problem. Not sure why it wasn't retrieved the first time - maybe the server was down. Anyway, this time it worked as advertised. > Now just a simple question : > Did you run a locate database update after installing SpamAssassin ?... > locate's not find. > #/usr/libexec/locate.updatedb & Yes, I did, but thanks for mentioning it. > Try with "whereis sa-learn". When you're looking for a binary, whereis > is a nice choice (it doesn't rely on databases that must be updates like > locate does). Also a good reminder - again, thanks. cheers, Robert
Re: SpamAssassin
Hi, > While SpamAssassin itself seems to be installed, > what is apparently missing is the utility sa-learn which is needed to update > the Bayesian database. It's not in the path, and I scoured the hard disk with > "locate" - it's not there. No man page for sa-learn either. On 3.7-stable, I get: % pkg_info -L p5-Mail-SpamAssassin | grep sa-learn /usr/local/bin/sa-learn /usr/local/man/man1/sa-learn.1 % Regards, Roland
Re: SpamAssassin
--On 16 September 2005 14:14 +0800, Robert Storey wrote: Hello folks. I'm trying to use SpamAssassin (not Spamd) on OpenBSD 3.7. I installed using the port mail/p5-Mail-SpamAssassin. Try the package, in case something went wrong with your port-building. It's not in the path, and I scoured the hard disk with "locate" - it's not there. No man page for sa-learn either. On mine: $ pkg_info -f p5-Mail-SpamAssassin-3.0.4|grep sa-learn bin/sa-learn @man man/man1/sa-learn.1 -- so it should go in /usr/local/bin/sa-learn.
Re: SpamAssassin
$ uname -a OpenBSD jasper 3.7 GENERIC.RAID#1 i386 $ pkg_info -L p5-Mail-SpamAssassin | grep sa-learn /usr/local/bin/sa-learn /usr/local/man/man1/sa-learn.1
Re: SpamAssassin
El vie, 16-09-2005 a las 14:14 +0800, Robert Storey escribis: > [...] > what is apparently missing is the utility sa-learn which is needed to update > the Bayesian database. It's not in the path, and I scoured the hard disk with > "locate" - it's not there. No man page for sa-learn either. > [...] > I'd be happy for any advice on this. Try with "whereis sa-learn". When you're looking for a binary, whereis is a nice choice (it doesn't rely on databases that must be updates like locate does). regards, Juanjo -- Desarrollo y sistemas: http://www.usebox.net/ Pagina Personal: http://www.usebox.net/jjm/
Re: SpamAssassin
Hi, On my OpenBSD 3.6, sa-learn is there : /usr/bin/sa-learn Now just a simple question : Did you run a locate database update after installing SpamAssassin ?... locate's not find. #/usr/libexec/locate.updatedb & Regards Oreste -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Robert Storey Envoyi : vendredi 16 septembre 2005 08:15 @ : misc@openbsd.org Objet : SpamAssassin Hello folks. I'm trying to use SpamAssassin (not Spamd) on OpenBSD 3.7. I installed using the port mail/p5-Mail-SpamAssassin. Everything seemed to go OK, no errors of any kind. While SpamAssassin itself seems to be installed, what is apparently missing is the utility sa-learn which is needed to update the Bayesian database. It's not in the path, and I scoured the hard disk with "locate" - it's not there. No man page for sa-learn either. I did some googling on "sa-learn openbsd", got many hits but nothing to indicate that there was a problem or a separate procedure for installing this utility. So I'm stumped. My experience with OpenBSD so far is that it's always better to use the ports rather than trying to download source and installing manually. So I haven't tried yet installing SpamAssassin manually through CPAN - if I can't get the port to work, that will be my next move. I'd be happy for any advice on this. best regards, Robert
SpamAssassin
Hello folks. I'm trying to use SpamAssassin (not Spamd) on OpenBSD 3.7. I installed using the port mail/p5-Mail-SpamAssassin. Everything seemed to go OK, no errors of any kind. While SpamAssassin itself seems to be installed, what is apparently missing is the utility sa-learn which is needed to update the Bayesian database. It's not in the path, and I scoured the hard disk with "locate" - it's not there. No man page for sa-learn either. I did some googling on "sa-learn openbsd", got many hits but nothing to indicate that there was a problem or a separate procedure for installing this utility. So I'm stumped. My experience with OpenBSD so far is that it's always better to use the ports rather than trying to download source and installing manually. So I haven't tried yet installing SpamAssassin manually through CPAN - if I can't get the port to work, that will be my next move. I'd be happy for any advice on this. best regards, Robert
Re: OpenBSD 3.7 w/ Amavisd-New,SpamAssassin,Postfix
On Tue, 2005-06-21 at 17:00 -0700, Timothy Horie wrote: > I installed amavisd and I'm using Postfix but since I am using the > proxy_filter for amavisd, I can't use the REDIRECT keyword in > /etc/postfix/relay_recipients. In relay_recipient_maps the RHS is ignored anyway. The files listed under relay_recipient_maps are only checked for matches in the first column (at least in all versions of postfix I've encountered so far). > Is there a way to use both? I would like e-mails that go to, for > example, [EMAIL PROTECTED] to actualy be redirected to > [EMAIL PROTECTED] which actually does exist on the internal MS > exchange server. Relay_recipient_maps aren't the right tool for this. Use alias_maps, virtual_alias_maps or recipient_canonical_maps to achieve this. All of these do will do the above, but behave somewhat differently in other regards. Read up on them and pick the one you prefer. I suggest you start with alias_maps. Cheers Steffen.
OpenBSD 3.7 w/ Amavisd-New,SpamAssassin,Postfix
Hello, I installed amavisd and I'm using Postfix but since I am using the proxy_filter for amavisd, I can't use the REDIRECT keyword in /etc/postfix/relay_recipients. I get the following error message: --- Jun 21 16:47:22 inc_wall2 postfix/smtpd[24530]: warning: access table hash:/etc/postfix/relay_recipients: with smtpd_proxy_filter specified, action REDIRECT is unavailable --- Is there a way to use both? I would like e-mails that go to, for example, [EMAIL PROTECTED] to actualy be redirected to [EMAIL PROTECTED] which actually does exist on the internal MS exchange server. The only solution I could think of was to run two copies of postfix (on two different machines) and have one use amavisd/spamassassin and the second do the relay to the internal MS exchange server and relay_recipients. Any suggestions, tips? Thanks, Tim
