From: David Rioja <rams@englobe-tec.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] procmail+spamassassin user filters
Date: Thu, 16 Oct 2008 13:51:33 +0200 [thread overview]
Message-ID: <48F72AC5.6020100@englobe-tec.com> (raw)
In-Reply-To: <20081016082006.7a97f62b.davidwei@newbread.tj.cn>
Hello!
I had did both mistakes you said:
1.- My recipe file was named .procmail instead of .procmailrc
2.- My recipe file had permissions other than 700
Both from an outdated (or mistaken) howto (I've reported it to the author).
Now it's working. Note that the option
--prefs-file=$HOME/.spamassassin/user_prefs
is unnecesary as this is the default path to user_prefs.
Thanks a lot!
David Wei escribió:
> One more tip, the .procmailrc file should belong and only belong to the mail owner user(right 700),procmail refuse to run when the .procmailrc 's right is not properly set on my box.
>
> On Wed, 15 Oct 2008 11:24:34 -0400
> Willie Wong <wwong@Princeton.EDU> wrote:
>
>
>> On Wed, Oct 15, 2008 at 09:08:49AM +0200, Penguin Lover David Rioja squawked:
>>
>>> Willie Wong escribi?:
>>>
>>>> On Tue, Oct 14, 2008 at 05:45:02PM +0200, Penguin Lover David Rioja
>>>> squawked:
>>>>
>>>>
>>>>> 2.- I created ~/.procmail with the following contents:
>>>>>
>>>>> SHELL=/bin/sh
>>>>> MAILDIR=$HOME/.maildir
>>>>> DEFAULT=$MAILDIR
>>>>> LOGFILE=$MAILDIR/procmail.log
>>>>>
>>>>> | spamassassin --prefs-file=$HOME/.spamassassin/user_prefs
>>>>>
>>>>>
>>>>>
>>>> Is that all you have in the recipe? I thought a recipe always begins
>>>> with 0: ? From my procmailrc file:
>>>>
>>>> -----------snip---------------
>>>> :0fw
>>>> | /usr/bin/spamc
>>>> ----------endsnip-------------
>>>>
>>>> since I use spamc/spamd. f makes it a filter and w waits for the
>>>> filter to finish.
>>>> W
>>>>
>>>>
>>> Ok, you win :)
>>>
>>> I actually have this on .procmail
>>>
>>> INCLUDERC=$HOME/.spamassassin.rc
>>>
>>> instead of that line. In the file .spamassassin.rc I have:
>>>
>>> :0fw
>>> | spamassassin --prefs-file=$HOME/.spamassassin/user_prefs
>>>
>> Another really stupid question, when you sayin your .procmail file, do
>> you mean $HOME/.procmailrc ? I certainly hope you just have a typo,
>> and not named your file something that procmail does not know is the
>> config file.
>>
>> (Was the ~/.maildir/procmail.log log file created?)
>>
>> I am pretty sure the $HOME in your command should parse properly even
>> if procmail passes control to a subshell, so there shouldn't be any
>> reason why your recipe doesn't work.
>>
>> W
>>
>> --
>> "It was real. At least, if it wasn't real, it did support
>> them, and as that is what sofas are supposed to do, this,
>> by any test that mattered, was a real sofa. "
>> Sortir en Pantoufles: up 677 days, 13:59
>>
>>
>
>
> -------------------------------
> 魏亮 David Wei
>
> 您可以通过下面的方式和我联系:
> MSN: inadavid@hotmail.com
> Gtalk: inadavid@gmail.com
> Email: davidwei@newbread.tj.cn
>
>
>
>
--
David Rioja Redondo
Tel. (34) 91 675 14 29
Fax: (34) 91 656 91 89
prev parent reply other threads:[~2008-10-16 11:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 15:45 [gentoo-user] procmail+spamassassin user filters David Rioja
2008-10-14 17:29 ` Willie Wong
2008-10-15 7:08 ` David Rioja
2008-10-15 15:24 ` Willie Wong
2008-10-15 23:20 ` David Wei
2008-10-16 11:51 ` David Rioja [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48F72AC5.6020100@englobe-tec.com \
--to=rams@englobe-tec.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox