I checked the /usr/local/etc/procmailrc file and it only has the default
ClamAV stuff in it. Per Andy's suggestion, I put the colon in just in case
that was the issue. This rule already was the very first item in the
$HOME/.procmailrc. I turned the vebose on in the $HOME/.procmailrc file and
tomorrow morning when they send out the rate sheets I'll check to see what
shows up. Any other suggestions in the meantime are welcome. Thanks.
Jim Smith
-----Original Message-----
From: owner-vps-mail@xxxxxxxxxxxx
[mailto:owner-vps-mail@xxxxxxxxxxxx] On Behalf Of Scott Wiersdorf
Sent: Wednesday, June 01, 2005 12:07 PM
To: vps-mail@xxxxxxxxxxxx
Subject: Re: [vps-mail] Procmail rule help
On Wed, Jun 01, 2005 at 11:47:08AM -0400, Jim Smith wrote:
> I need another set of eyes to look at this. I have a client
wanting to get
> rate sheets from WellsFargo.com which of course the spam
filters have a
> field-day with. So I put a rule at the top of the
.procmailrc that sez:
>
> :0:
> * ^From.*wellsfargo.com
> /var/mail/clientsmailbox
>
> Stuff is still going to the spam folder. Here are the
headers to one of the
> messages:
>
> Reply-To: <corrrates@xxxxxxxxxxxxxx>
> From: "Wells Fargo" <corrrates@xxxxxxxxxxxxxx>
That recipe should work if it were the only recipe. You'll want to
look in /usr/local/etc/procmailrc for any recipes that might be
triggered first. After the system procmailrc file is run *and no
matching recipes were found*, THEN the user's .procmailrc file is
executed.
If you can't readily find where the mail is being shunted as spam, set
VERBOSE=on and LOGFILE=$HOME/procmail.log and send a sample message
through to see where it's getting caught.
Scott
--
Scott Wiersdorf
scottw@xxxxxxxxxxxx
======================================================================
This is <vps-mail@xxxxxxxxxxxx> <http://www.perlcode.org/lists/>
Before posting a question, please search the archives (see above URL).
======================================================================
This is <vps-mail@xxxxxxxxxxxx> <http://www.perlcode.org/lists/>
Before posting a question, please search the archives (see above URL).