-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 18 January 2002 7:13 am, Alan Chandler wrote:
> On Friday 18 January 2002 1:04 am, dman wrote:
> > On Thu, Jan 17, 2002 at 09:27:36PM +, Alan Chandler wrote:
>
> ...
>
> > | # This transport does a spam check to look for spam and then
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 18 January 2002 1:04 am, dman wrote:
> On Thu, Jan 17, 2002 at 09:27:36PM +, Alan Chandler wrote:
...
>
> | # This transport does a spam check to look for spam and then re-injects
> | # the message into exim
> |
> | command = spamc |
dman <[EMAIL PROTECTED]> writes:
> I think a command line option should be available to say "don't create
> a prefs file". That should be the user's job anyways.
Uhh, use the spamd/spamc combination. Then edit the
/etc/default/spamassassin file. Remove the -c option from OPTIONS and
you won't h
On Thu, Jan 17, 2002 at 09:27:36PM +, Alan Chandler wrote:
| On Wednesday 16 January 2002 2:33 am, dman wrote:
| > I'm now trying to set up spamassassin on my system, but am running
| > into some hurdles. I use exim as my MTA, so I'm following the guides
| > at
| > http://bogmog.sourceforg
On Thu, Jan 17, 2002 at 04:52:40PM +0100, Paul Slootman wrote:
| On Wed 16 Jan 2002, martin f krafft wrote:
| >
| > sounds like (a) exim does it just like postfix. maybe they document it
| > more sophisticatedly, (b) you doubling the load unnecessarily, and (c)
| > you are asking for trouble. why
On Wed, Jan 16, 2002 at 05:30:55PM +0100, martin f krafft wrote:
| also sprach dman <[EMAIL PROTECTED]> [2002.01.16.1704 +0100]:
| > Exim doesn't run pipe commands immediately like procmail does (with
| > 'f' flag). It schedules the command to be run later, and later
| > (during the actual deliver
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 16 January 2002 2:33 am, dman wrote:
> I'm now trying to set up spamassassin on my system, but am running
> into some hurdles. I use exim as my MTA, so I'm following the guides
> at
> http://bogmog.sourceforge.net/document_show.php3?d
On Wed 16 Jan 2002, martin f krafft wrote:
>
> sounds like (a) exim does it just like postfix. maybe they document it
> more sophisticatedly, (b) you doubling the load unnecessarily, and (c)
> you are asking for trouble. why not let procmail be MDA?
procmail is in no way light-weight; I'd hesitat
also sprach dman <[EMAIL PROTECTED]> [2002.01.16.1704 +0100]:
> Exim doesn't run pipe commands immediately like procmail does (with
> 'f' flag). It schedules the command to be run later, and later
> (during the actual delivery) it runs the command. Thus the command
> _must_ deliver the message to
On Wed, Jan 16, 2002 at 02:35:05PM +0100, martin f krafft wrote:
| also sprach dman <[EMAIL PROTECTED]> [2002.01.16.0507 +0100]:
| > | does exim already have the recipient user by the time the filter is
| > called?
| >
| > It does, and I _could_ run the script as the user. The problem there
| > i
also sprach dman <[EMAIL PROTECTED]> [2002.01.16.0507 +0100]:
> | does exim already have the recipient user by the time the filter is
> called?
>
> It does, and I _could_ run the script as the user. The problem there
> is only "privileged" (in exim's eyes) users are allowed to set the
> received_
On Wed, Jan 16, 2002 at 03:47:14AM +0100, martin f krafft wrote:
| also sprach dman <[EMAIL PROTECTED]> [2002.01.16.0333 +0100]:
| > 1) Why is spamassassin trying to create a preferences file in /?
|
| $HOME isn't set in the script.
Good point. If I set
HOME=/tmp
in the script, then spamas
also sprach dman <[EMAIL PROTECTED]> [2002.01.16.0333 +0100]:
> 1) Why is spamassassin trying to create a preferences file in /?
$HOME isn't set in the script. does exim already have the recipient
user by the time the filter is called?
> 2) How can users have their own preferences files? It do
13 matches
Mail list logo
