We are using the procmailrc in /etc, globally, the users do not have one.
Is this:
mailbox_command = /usr/local/bin/procmail -f- -a "$USER"
not what I should be using for a global setting in /etc?
I tried
mailbox_command = /usr/local/bin/procmail -pm /etc/procmailrc
and that didn't work either.
I have not tried just the:
mailbox_command = /usr/local/bin/procmail
could this be this issue? I can try it in test here soon.
Thanks for your help.
Kyle Reynolds
972-731-4731
[EMAIL PROTECTED]
"jdow"
<[EMAIL PROTECTED] To:
<users@spamassassin.apache.org>
et> cc:
Subject: Re: how to call
procmail for spam delete?
01/26/2005 04:43
PM
And is the procmailrc you showed earlier the one in /etc or is it in
the each of the user directories for customization?
(And I idly wonder if postfix is in its little chroot jail it prefers
how does it find /usr/local/bin/procmail? I thought the purpose of a
chroot jail was to remove the ability to access things outside the
jail. But I see you do not have that problem IF you restarted the
postfix service after changing your master.cf.)
As a note I've been successfully using procmail by calling it without
the added -f- -a "$USER" incantation. I simply use the line "DROPPRIVS=
yes" at the top of the .procmailrc.
The serious guts I use are:
===8<---
############################################################################
##
# run spamassassin on things not from the spamassassin list
############################################################################
##
:0 fw: spamassassin.lock
* < 250000
* !^List-Id: .*(spamassassin\.apache.\org)
| /usr/bin/spamc -t 150 -u jdow
#| nice -n 1 /usr/bin/spamassassin
:0 Efw: spamassassin.lock
* !^List-Id: .*(spamassassin\.apache.\org)
| nice -n 1 /usr/bin/spamassassin
===8<---
I am the only user of this "shake down" 3.0.2 install at the moment.
So I moved all my personal rules and such into /etc/mail/spamassassin
as a .cf file. Otherwise I'd be using the commented out call to
spamassassin itself. 3.0.x has a problem with user scores, at least
when per user rules are enabled. (Since only two people will ever be
using the machine I could work around the user rules problem easily
enough with two spamd starts with the second one on a different IP
address and config directory. But that's cheating. Besides, for some
of the things Loren does 3.0.x is clearly "defective". It lacks some
of 2.63's reporting capabilities.
For debugging I found a clever trick for tracking progress through the
procmailrc files. It provides me with some diagnostic info, too.
===8<---
:0 fw
| formail -A "X-Jdow: user $LOGNAME"
===8<---
{^_^}
----- Original Message -----
From: <[EMAIL PROTECTED]>
>
> Kyle Reynolds
> To: "jdow"
<[EMAIL PROTECTED]>
> 01/26/2005 04:03 cc:
> PM Subject: Re: how to call
procmail for spam delete?(Document link: Kyle Reynolds)
>
>
>
>
>
>
> here, in main.cf:
>
>
****************************************************************************
****************************************
>
> queue_directory = /var/spool/postfix
> command_directory = /usr/local/sbin
> daemon_directory = /usr/local/libexec/postfix
> mail_owner = postfix
> myhostname = smtp.transplace.com
> mydomain = transplace.com
> myorigin = $mydomain
> local_recipient_maps =
> unknown_local_recipient_reject_code = 450
> mynetworks = drycims2.dryden.weyer.com
> relay_domains = transplace.com, weyer.com
> relayhost = sheweb1.transplace.com
> masquerade_domains = transplace.com
>
> mailbox_command = /usr/local/bin/procmail -f- -a "$USER"
>
> debug_peer_level = 2
> debugger_command =
> PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
> xxgdb $daemon_directory/$process_name $process_id & sleep 5
>
> sendmail_path = /usr/local/sbin/sendmail
> newaliases_path = /usr/local/bin/newaliases
> mailq_path = /usr/local/bin/mailq
> setgid_group = maildrop
> manpage_directory = /usr/local/man
> sample_directory = /usr/local/etc/postfix
> readme_directory = no
> smtpd_sender_restrictions = permit_mynetworks
> check_sender_access hash:/usr/local/etc/postfix/sender_access
> reject_unknown_sender_domain
> #warn_if_reject reject_unverified_sender
> smtpd_banner = $myhostname NO UCE ESMTP
> ##message_size_limit = 5246976
> ##smtpd_delay_reject = no
> ##smtpd_helo_required = yes
> #strict_rfc821_envelopes = yes
> ##strict_rfc821_envelopes = no
> ##smtpd_delay_reject = no
> depug_peer_list = drycims2.dryden.weyer.com
>
>
****************************************************************************
*************************************************
>
>
> Kyle Reynolds
> 972-731-4731
> [EMAIL PROTECTED]
>
>
>
>
> "jdow"
> <[EMAIL PROTECTED] To:
<users@spamassassin.apache.org>
> et> cc:
> Subject: Re: how to call
procmail for spam delete?
> 01/26/2005 03:55
> PM
>
>
>
>
>
>
> Where do you tell postfix to use procmail?
> {^_^}
> ----- Original Message -----
> From: <[EMAIL PROTECTED]>
> >
> > Thanks, but my procmailrc already looks like that. The strange thing
is
> > that it won't delete the messages marked spam, but the one that was
> > previously tagged as spam and accidentally got through again was
> deleted...
> > so it appears that the procmail recipe is correct, but that procmail
> isn't
> > being called in the order that it should be?
> >
> > Here is my procmailrc:
> >
> >
>
****************************************************************************
>
> ***********************
> > LOGFILE=/var/log/procmail.log
> > DROPPRIVS=yes
> >
> > :0fw: spamassassin.lock
> > * < 256000
> > | /usr/local/bin/spamc
> >
> > :0:
> > * ^X-Spam-Status: Yes
> > /tmp/spam
> >
> > :0
> > * ^^rom[ ]
> > {
> > LOG="*** Dropped F off From_ header! Fixing up. "
> >
> > :0 fhw
> > | sed -e '1s/^/F/'
> > }
> >
> >
>
****************************************************************************
>
> *************************
> >
> > and my postfix master.cf:
> >
> >
>
****************************************************************************
>
> *************************
> >
> > # Setup Spamassassin
> > spamassassin unix - n n - - pipe
> > user=filter argv=/usr/local/bin/sa-filter.csh -f ${sender} --
> ${recipient}
> >
>
>
>
>
>
>
>
