Bob Holtzman | 1 Nov 07:03 2003
Picon

Re: recipe problem

At 12:38 AM 10/31/2003 -0800, you wrote:
>At 20:10 2003-10-30 -0700, Bob Holtzman wrote:
>>I'm having a problem getting some recipes to work. I *think* they're 
>>setup correctly.I'm running procmail-3.22-5 on a Redhat 7.3 box. My 
>>./.procmailrc file looks like this:
>>
>>SHELL=/bin/sh                           PMDIR=$HOME/Procmail 
>>LOGFILE=$PMDIR/.procmail. VERBOSE=yes MAILDIR=/var/spool/mail
>>LOGABSTRACT=all
>>                INCLUDERC=$PMDIR/duplicates.rcINCLUDERC=$PMDIR/backup.rc 
>> INCLUDERC=$PMDIR/basics.rc#INCLUDERC=$PMDIR/testing.rc 
>> INCLUDERC=$PMDIR/lists.rc
>>INCLUDERC=$PMDIR/spamtrap.rc
>>
>>Notice basics.rc comes before spamtrap.rc.
>
>What I notice is that there are several lines which don't have proper 
>newline breaks in them.  Perhaps you should ensure that your procmailrc 
>file isn't similarly hosed, though I'm guessing that your mail client or 
>sending mail server is actually to blame for this
>malformed post.

The procmailrc file is O.K. The hosed email is the result of copying the 
info from linux to the Windows  partition, then booting Windows and pasting 
it into Eudora . Pine has started to refuse to send my authentication to 
the SMTP server so I'm forced to use Windows to send until I can 
troubleshoot Pine. It looked good when it left here. Eudora may be 
partially to blame. It's always been a PITA.

>>  $MAILDIR/holtzm Mail the log 
(Continue reading)

Alan Clifford | 3 Nov 01:16 2003

Re: Forwarding and errors

On Sat, 25 Oct 2003, Andrew Edelstein wrote:

AE>
AE> Unfortuantly that doesn't work. I use virtusertable (Sendmail) to do
AE> such forwards, and I still get all the bounces. Or what's worse, I get
AE> all the bounces back from the original sender's server (or more
AE> specifically, the MX host of the domain in the original "from" address)
AE> telling me that address doesn't exist.
AE>
AE>

:0
* TO_someone <at> example.com
| $SENDMAIL -oi -f "" someone <at> notat.example.com

To try to hide yourself, you need to use the -f in sendmail. The -f ""
should make them bounce to themselves.  I imagine you would need a
more sophisticated condition line.

Alan

( Please do not email me AS WELL as replying to the list.  Please
  address personal email to alan+1 <at>  as lists <at>  is not read. A
  password autoresponder may be invoked if this email is very old. )
Chris Barnes | 3 Nov 20:45 2003
Picon

recipe help

This should be a simple thing, but the multi line header has me baffled.
My .procmailrc script already takes the messages that SpamAssassin
identifies as spam and dumps them into a folder.

However, I want to first figure out which messages scored high enough
such that SA ran it's autolearn routine.  This appears in the header of
such messages:

X-Spam-Status: Yes, hits=17.5 required=5.0 tests=BAYES_99,BIZ_TLD,
 DATE_IN_PAST_96_XX,HTML_70_80,HTML_MESSAGE,HTML_TITLE_UNTITLED,
 MIME_BASE64_TEXT,MIME_HTML_NO_CHARSET,MIME_HTML_ONLY,ONLINE_PHARMACY,
 RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_DSBL,RCVD_IN_SORBS,RCVD_IN_SORBS_HTTP,
 RCVD_IN_SORBS_MISC autolearn=spam version=2.60

Note the "autolearn=spam" in the last line.  That's what I want to
identify.  If it's there, I have no need to save the message and can let
procmail dump it straight to /dev/null.

--

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Chris Barnes                                       AOL IM: CNBarnes
chris-barnes <at> tamu.edu                            Yahoo IM: chrisnbarnes
Computer Systems Manager                               ph: 979-845-7801
Department of Physics                                 fax: 979-845-2590
Texas A&M University
Scott Wiersdorf | 3 Nov 21:03 2003

Re: recipe help

On Mon, Nov 03, 2003 at 01:45:56PM -0600, Chris Barnes wrote:
> This should be a simple thing, but the multi line header has me baffled.
> My .procmailrc script already takes the messages that SpamAssassin
> identifies as spam and dumps them into a folder.

Bart Schaefer kindly pointed this out to me a few months ago. Procmail
unfolds headers for you, so this should work:

    :0
    * ^X-Spam-Status:.*autolearn=spam
    /dev/null

Scott
--

-- 
Scott Wiersdorf
scott <at> perlcode.org
Klaus Johannes Rusch | 3 Nov 21:06 2003
Picon

Re: recipe help

Chris Barnes wrote:

> This should be a simple thing, but the multi line header has me baffled.
> My .procmailrc script already takes the messages that SpamAssassin
> identifies as spam and dumps them into a folder.
>
> However, I want to first figure out which messages scored high enough
> such that SA ran it's autolearn routine.  This appears in the header of
> such messages:
>
> X-Spam-Status: Yes, hits=17.5 required=5.0 tests=BAYES_99,BIZ_TLD,
>  DATE_IN_PAST_96_XX,HTML_70_80,HTML_MESSAGE,HTML_TITLE_UNTITLED,
>  MIME_BASE64_TEXT,MIME_HTML_NO_CHARSET,MIME_HTML_ONLY,ONLINE_PHARMACY,
>  RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_DSBL,RCVD_IN_SORBS,RCVD_IN_SORBS_HTTP,
>  RCVD_IN_SORBS_MISC autolearn=spam version=2.60
>
> Note the "autolearn=spam" in the last line.  That's what I want to
> identify.  If it's there, I have no need to save the message and can let
> procmail dump it straight to /dev/null.

* ^X-Spam-Status: Yes,.*autolearn=spam

should catch this

--
Klaus Johannes Rusch
KlausRusch <at> atmedia.net
http://www.atmedia.net/KlausRusch/

Re: recipe help

At 13:45 2003-11-03 -0600, Chris Barnes wrote:

[snip]
>Note the "autolearn=spam" in the last line.  That's what I want to
>identify.  If it's there, I have no need to save the message and can let
>procmail dump it straight to /dev/null.

It's not rocket science:

:0
* ^X-Spam-Status:.*autolearn=spam
/dev/null

---
  Sean B. Straw / Professional Software Engineering

  Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
  Please DO NOT carbon me on list replies.  I'll get my copy from the list.
Christopher L. Barnard | 3 Nov 21:24 2003

Re: recipe help


Seeing this post reminds me that I should ask about a problem that
happens very rarely.  The auto-unfolding of headers sometimes causes
"Out of the Office" to appear on multiple lines and therefore not be
caught by my oot recipe.  Is there a way to tell procmail *not* to
unfold a particular header?

+-----------------------------------------------------------------------+
| Christopher L. Barnard         O     When I was a boy I was told that |
| cbarnard <at> tsg.cbot.com         / \    anybody could become president.  |
| (312) 347-4901               O---O   Now I'm beginning to believe it. |
| http://www.cs.uchicago.edu/~cbarnard                --Clarence Darrow |
+----------PGP public key available via finger or PGP keyserver---------+

> On Mon, Nov 03, 2003 at 01:45:56PM -0600, Chris Barnes wrote:
> > This should be a simple thing, but the multi line header has me baffled.
> > My .procmailrc script already takes the messages that SpamAssassin
> > identifies as spam and dumps them into a folder.
> 
> Bart Schaefer kindly pointed this out to me a few months ago. Procmail
> unfolds headers for you, so this should work:
> 
>     :0
>     * ^X-Spam-Status:.*autolearn=spam
>     /dev/null
Chris Barnes | 3 Nov 23:08 2003
Picon

Re: recipe help

Professional Software Engineering <PSE-L <at> mail.professional.org> wrote:
> It's not rocket science:
>
> * ^X-Spam-Status:.*autolearn=spam
> /dev/null

I *thought* it would be easy.  It was the multi-line that had me
confused.  Once someone else said that procmail dealt with that already,
I had no worries.

Thanks

--

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Chris Barnes                                       AOL IM: CNBarnes
chris-barnes <at> tamu.edu                            Yahoo IM: chrisnbarnes
Computer Systems Manager                               ph: 979-845-7801
Department of Physics                                 fax: 979-845-2590
Texas A&M University
Alan Clifford | 3 Nov 23:42 2003

Re: recipe help

On Mon, 3 Nov 2003, Christopher L. Barnard wrote:

CLB>
CLB> Seeing this post reminds me that I should ask about a problem that
CLB> happens very rarely.  The auto-unfolding of headers sometimes causes
CLB> "Out of the Office" to appear on multiple lines and therefore not be
CLB> caught by my oot recipe.  Is there a way to tell procmail *not* to
CLB> unfold a particular header?
CLB>

I don't follow the logic of that.  If headers containing line breaks are
unfolded into a single line, how can it cause the phrase to appear on
multiple lines?

Perhaps you could show an example?

Alan

( Please do not email me AS WELL as replying to the list.  Please
  address personal email to alan+1 <at>  as lists <at>  is not read. A
  password autoresponder may be invoked if this email is very old. )
Scott Wiersdorf | 3 Nov 23:49 2003

Re: recipe help

On Mon, Nov 03, 2003 at 02:24:20PM -0600, Christopher L. Barnard wrote:
> 
> Seeing this post reminds me that I should ask about a problem that
> happens very rarely.  The auto-unfolding of headers sometimes causes
> "Out of the Office" to appear on multiple lines and therefore not be
> caught by my oot recipe.  Is there a way to tell procmail *not* to
> unfold a particular header?

I don't understand how something on one line could be made to appear
on multiple lines by UNfolding; but to answer your question, I don't
think there is a way to tell procmail not to unfold header lines. The
manpage states:

       To make `egrepping' of headers more  consistent,  procmail
       concatenates  all continued header fields; but only inter-
       nally.  When delivering the mail, line breaks will  appear
       as before.

So my guess is that you can't do it without going to a shell (e.g.,
sed or perl). You might be able to look for the multiple spaces or
tabs that might be part of the header otherwise.

Scott
--

-- 
Scott Wiersdorf
scott <at> perlcode.org

Gmane