Date: Sun, 3 Feb 2002 08:00:06 -0800 (PST) From: Thomas Hurst <tom.hurst@clara.net> To: freebsd-ports@FreeBSD.org Subject: Re: ports/34585: Mail-SpamAssassin problem when invoked from .forward Message-ID: <200202031600.g13G06e77761@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/34585; it has been noted by GNATS.
From: Thomas Hurst <tom.hurst@clara.net>
To: "Andrey V. Pevnev" <andrey@mgul.ac.ru>
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: ports/34585: Mail-SpamAssassin problem when invoked from .forward
Date: Sun, 3 Feb 2002 15:52:32 +0000
* Andrey V. Pevnev (andrey@mgul.ac.ru) wrote:
> >Number: 34585
> >Category: ports
> >Synopsis: Mail-SpamAssassin problem when invoked from .forward
> When user adds "|/usr/local/bin/spamassassin || exit 75" to his/her
> .forward file in order to check mail against spam filtering rules,
> spamassassin can't deliver mail to users's mailbox, because
> spamassassin can't find mailbox.
Personally I'd suggest running it as a filter through procmail/maildrop.
> # some bits of code from Mail::Audit here:
> - $file ||= $ENV{'MAIL'} || "/var/spool/mail/".getpwuid($>);
> + $file ||= $ENV{'MAIL'} || "/var/mail/".getpwuid($>);
This'll break systems where /var/spool/mail is correct.. doesn't $MAIL
get set in .forward's environment? That's pretty poor.
I'll raise this on the ml and get this sorted upstream. A check for
the /var/spool/mail or /var/mail directory should be sufficient,
although personally I wouldn't feel at all bad if all delivery
capabilities were dumped :)
--
Thomas 'Freaky' Hurst - freaky@aagh.net - http://www.aagh.net/
-
When a person goes on a diet, the first thing he loses is his temper.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200202031600.g13G06e77761>