-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 21 January 2004 11:51, Andres Tello Abrego wrote:
> If I use a global procmailrc, bayes is used by only one user (spam).
>
> So, statistically, is better to have one bayes database per user, so,
> how to make a single procmailrc to have
If I use a global procmailrc, bayes is used by only one user (spam).
So, statistically, is better to have one bayes database per user, so,
how to make a single procmailrc to have one bayes databse for each user?
Any ideas?
Thanxs
---
The SF
Hello all,
Figured out the error of my ways, (I'm such a bone
head). Now I'm having a blast with both SA and procmail. Awesome
combo!
Rich
In addition, this looks wrong:
> :0:
> * ^X-Spam-Flag: YES
> /Spamfolder
It looks as if you're trying to deposit the spam into a folder that lives
just
below the root directory. Perhaps you meant:
:0:
* ^X-Spam-Flag: YES
Spamfolder
> -Original Message-
> From: Martin Radford
> Sent: Mon
At Tue Dec 2 07:19:42 2003, Rich H. wrote:
>
> Hello again,
> I am playing with different recipies of procmailrc, and I am still =
> having some time with features of .procmailrc files. I added a line like
>
> :0:
> * ^X-Spam-Flag: YES
> /Spamfolder
>
> In the headers of my message I get
>
> X
Hello again,
I am playing with different recipies of procmailrc,
and I am still having some time with features of .procmailrc files. I added a
line like
:0:* ^X-Spam-Flag:
YES/Spamfolder
In the headers of my message I get
X-Spam-Flag: YES
Yet in the log file I have set up I get a
> I have been running SA on a server for several months with no problems. I
> walk in this morning and have a stack of voice mail about people not being
> able to receive mail. I've narrow this down to the delivery agent,
> procmail, which seems to be removing the very first charactor from every
On Thu, 2003-06-19 at 14:28, Bill Fisher, W4AN wrote:
> I have been running SA on a server for several months with no problems. I
> walk in this morning and have a stack of voice mail about people not being
> able to receive mail. I've narrow this down to the delivery agent,
> procmail, which see
I have been running SA on a server for several months with no problems. I
walk in this morning and have a stack of voice mail about people not being
able to receive mail. I've narrow this down to the delivery agent,
procmail, which seems to be removing the very first charactor from every
mail.
It seems that the documentation could use a more complete example of a .procmailrc
file. Here is one that I use. It checks for evil mail loops. Hope you find it
useful. [I don't read this list, so Cc: me if want a response]
DROPPRIVS=yes # Become the recipient
COMSAT=no
At 06/27/2002 22:13, Steve Wingate wrote:
>Hello,
>
>I'm using the p5-Mail-SpamAssassin-2.30 port on FreeBSD along with
>procmail 3.22. I'm having a few problems. I have this in my
>~/.procmailrc file (procmail has been working fine for a long while)
>
># Added for SpamAssassin
>:0fw
>| spamassas
Steve Wingate wrote:
> # Added for SpamAssassin
> :0fw
> | spamassassin -P
>
> :0:
> * ^X-Spam-Status: Yes
> caughtspam
>
> The above entry was taken directly from the documentation.
This is kind of a procmail question, but...
I think the documentation - the README at least - specifies a path.
Hello,
I'm using the p5-Mail-SpamAssassin-2.30 port on FreeBSD along with
procmail 3.22. I'm having a few problems. I have this in my
~/.procmailrc file (procmail has been working fine for a long while)
# Added for SpamAssassin
:0fw
| spamassassin -P
:0:
* ^X-Spam-Status: Yes
caughtspam
The
If I use spamc instead of spamassassin I get this:
spamd[6030]: bad protocol: header error: (closed before headers)
:0fw
| /usr/local/bin/spamassassin
/usr/local/bin/spamd -u smmsp -a -d -x
This doesn't work
:0fw
| /usr/local/bin/spamc -s 10
So it looks like spamc isn't getting the me
On Wed, 2002-01-23 at 15:23, Charlie Watts wrote:
> You mean for delivery to a Maildir, so that courier-imap can use it,
Yes, I interpreted his request as being for courier-imap Maildir format,
which is what I use.
> I don't think you need locking for delivery to a maildir ... you can
> probably
On 23 Jan 2002, Craig Hughes wrote:
> Oops, I misread "Courier" as "Cyrus" -- still might be helpful for
> someone using Cyrus.
Hilarious that I just typoed the reverse of that ... Cyrus into Courier.
--
Charlie Watts
[EMAIL PROTECTED]
Frontier Internet, Inc.
http://www.frontier.net/
___
Oops, I misread "Courier" as "Cyrus" -- still might be helpful for someone using Cyrus.
C
On Wed, 2002-01-23 at 15:35, Craig Hughes wrote:
I use this for procmail invoked by postfix as
proccyrus unix - n n - - pipe flags
I use this for procmail invoked by postfix as
proccyrus unix - n n - - pipe flags=R user=cyrus argv=/usr/bin/procmail -p /etc/procmailrc.cyrus CYRUSER=${user} EXTENSION=${extension}
In otherwords, procmail is invoked running as the cyrus user, wit
On 23 Jan 2002, Sidney Markowitz wrote:
> On Wed, 2002-01-23 at 14:50, Mike Coughlan wrote:
> > Can someone please send a sample .procmailrc for courier.
You mean for delivery to a Maildir, so that courier-imap can use it,
right? Please keep in mind that there is also a complete SMTP server
call
On Wed, 2002-01-23 at 14:50, Mike Coughlan wrote:
> Can someone please send a sample .procmailrc for courier.
Here is what I use. spamc makes it a whole lot faster than calling
spamassassin directly. The test for X-Spam-Flag works whether or not you
set your options to mess with the subject. As f
Can someone please send a sample .procmailrc for courier.
This seems to work, I made it up, but I'd like a sanity check before I go
live.
Thanks
=
# This added for Maildir support (Courier-IMAP)
MAILDIR=$HOME/Maildir/
DEFAULT=$MAILDIR
:0fw
| spamassassin -P
:0e
{
21 matches
Mail list logo
