Folder problem

Greetings, procmail-users !

    I'm new to this list , having had trouble subscribing via text mode. A web site
someone suggested finally worked.

I have not been able to get procmail automatically putting mail into designated folders - necessary for creating 'ham', 'spam', & 'trash' folders in configuring SA.
This has been true for some time with Mutt receiving incoming mail via Inbox
where I sort, read, delete, manually file, and reply via Moz-Mail.

Trying to configure SA after being heavily affected by Swen brought it to a head
and put it in the 'must-fix' box. I have raised it on 'debian-users' & 'mutt-users',
kept being directed to this list, but found myself unable to join. Then Xmas intervened ... 

I have summarised the last two messages in the thread below. I'd be grateful for
any constructive comments. I have the feeling I'm missing something obvious (eg. confusing  '$MAILDIR/procmaillog'  with './home/adam/Mail/procmaillog').

Adam Bogacki,
afb(_at_)paradise(_dot_)net(_dot_)nz
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I have looked at my
procmaillog again and, as far as I can make out, procmail was processing
mail folder recipes until July 28th. The next date mentioned in sequence
was September 29, from which time there is no record of it processing
them. It might be relevant that during that time I changed from
Mail to $MAILDIR mode and may have changed something inappropriately.

I have attached my environmental variables below for comment.
They are followed in procmail by SpamAssassin stuff, then recipes.

3) it's particularly difficult to divine your .procmailrc contents just
from the output of procmail, but I bet that you have something like
                                                                                           
  # put the Message-ID: in the cache to dedupe
  :0 Wh: msgid.lock
  * ! ^From:.*davidtg.*justpickone
  | $FORMAIL -D 16384 $HOME/.procmail/.msgid.cache
                                                                                           
in there to remove duplicates.  Note the colon line; msgid.lock is
specifically called as the name of the lock file to use (and the locking
is to avoid having more than one process doing something at a time, which in this case is writing to the msgid cache) See below.

                                                                                           

4) you'd probably get much better answers, and will certainly get much
more interest, on the procmail list

Fair comment, but I don't understand why my efforts to subscribe to it keep failing.
<procmail-users(_at_)procmail(_dot_)org> does not seem to be (yet) up, and the
current University of Aachen host keeps refusing to subscribe me. <debian-user>
seems to be having its problems with exploited servers ... which leaves
<mutt-user>...     
I've attached my environmental variables below. 

#SHELL=/bin/bash
LINEBUF=4096
#PATH=/usr/bin
PATH=/bin:/usr/bin:/usr/local/bin
VERBOSE=yes
#MAILDIR=$HOME/Mail
                                                                                           
SENDMAIL=/usr/sbin/sendmail
DEFAULT=$MAILDIR/INBOX
LOGFILE=$MAILDIR/procmaillog
LOGABSTRACT=all
DROPPRIVS=yes
#SED=/bin/sed
FORMAIL=/usr/bin/formail
#LBDBFETCH=/usr/bin/lbdb-fetchaddr
#MESSAGE="/usr/local/bin/gmsgp --no_hscrollbar -f -"
                                                                                           
#Nukes duplicate messages
:0 Wh: msgid.lock
| $FORMAIL -D 8192 .msgid.cache

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

% them. It might be relevant that during that time I changed from
% Mail to $MAILDIR mode and may have changed something inappropriately.
                                                                             
Maybe.  It seems to me more likely that you changed your .forward ...

I'm not sure what you are referring to here. None of the examples I used to set up
muttrc and procmailrc had a '.forward' entry.

% I have attached my environmental variables below for comment.
% They are followed in procmail by SpamAssassin stuff, then recipes.
                                                                             
OK.  How do you think you're getting mail to procmail?  Are you sure you
are?

No.  The bottom of my current procmaillog is

procmail: Executing "/usr/bin/formail,-D,8192,.msgid.cache"
procmail: Assigning "LASTFOLDER=/usr/bin/formail -D 8192 .msgid.cache"
procmail: Unlocking "msgid.lock"
procmail: Notified comsat: "adam@:/usr/bin/formail -D 8192 .msgid.cache"
>From MAILER-DAEMON Fri Nov 28 14:48:32 2003
 Subject: Warning: message 1AP6jl-0000WS-1V delayed 24 hours
  Folder: /usr/bin/formail -D 8192 .msgid.cache                             473
                                                           4589,3        Bot

I hope you make more sense of it than I do.

% >LOGFILE=$MAILDIR/procmaillog
                                                                             
And is this, in fact, where you find your procmail log file?
                                                                             

See below.

Tux:/# find -name procmaillog -print
./home/adam/Mail/procmaillog
./home/adam/.themes/adam/Mail/procmaillog
./home/adam/.themes/.themes/adam/Mail/procmaillog
./home/adam/.themes/.themes/.themes/adam/Mail/procmaillog

_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail