Thanks Gerald. I read your message on the 10th - which I realised
must by the 9th in your time zone - so I just managed to make
the deadline. I ftp'd it to your site and checked
http://www.phorce1.us/bogacki/
to verify it was there.
I'd welcome any constructive suggestions but I'll keep working on it
myself - Dallman was probably right on that. I have previously
had procmail working correctly which makes this situation a bit
frustrating.
Adam Bogacki,
afb(_at_)paradise(_dot_)net(_dot_)nz
On Thu, 06 Jan 2005 12:43:50 +0100 Dallman Ross wrote:
On Thu, Jan 06, 2005 at 10:10:44PM +1100, Adam Bogacki wrote:
Dallman, & Ruud ..
current etc-procmail.log is below.
adam-procmail.log still not appearing
in /home/adam/Mail.
<wan smile, not yet exasperated but heading in that direciton>
OK, this is only available until Sunday the 9th while I'm here to monitor
it for abuse. At the first sign of unauthorized files being transferred on
the site I'll pull the plug. (extremely large files, non text files, etc.)
FTP --- phorce1.us
Username --- bogacki
Password --- (sent to Adam and Dallman for now -- request it if you want to
upload a file for review)
WEB --- http://www.phorce1.us/bogacki
Adam, upload your /etc/procmailrc, /home/adam/.procmailrc and log files to
the site as plain text files. I suggest you rename them like this:
adam.jan07.etc.procmailrc.txt
adam.jan07.adam.procmailrc.txt
adam.jan07.etc.procmail.log.txt
adam.jan07.adam.procmail.log.txt <--- if it ever shows up. ;-D
I've turned on indexes for that web folder so you don't have to create an
index.html, people who wish to help can go to the web page and view the
files directly.
Anyone who wishes to help diagnose problems will be able to get a better
idea of what's going on if they can see the whole rcfile(s). People can
upload suggested corrections as snippets or complete rcfiles
(ie. dman.jan07.etc.procmailrc.txt).
If it's needed beyond Sunday let me know.
I'm driving 1500 miles (one way) starting Monday for a Volkswagen
show/campout in Arizona. I will be gone for 10 days minimum. I'll check up
on the site once or twice on my trip and, once again, shut it down on signs
of abuse.
Adam, Dallman -- separate email to follow this one with the password.
Gerald
------------------------------
Message: 6
Date: Sat, 08 Jan 2005 06:17:07 +0100
From: "Ruud H.G. van Tol" <rvtol(_at_)isolution(_dot_)nl>
Subject: Re: 'Folder: bounced '
To: "[procmail]" <procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE>
Message-ID: <006601c4f541$4d8de240$0a01a8c0(_at_)isolution(_dot_)nl>
Content-Type: text/plain; charset=iso-8859-1
Toen wij Ruud H.G. van Tol kietelden, kwam er dit uit:
Adam Bogacki:
drwxr-sr-x 44 adam adam 4096 Jan 4 17:05 /home/
/home owned by adam?
Things like that happen because /home/adam/../ goes up.
Run-as-root:
chown root:root /home
--
Grtz, Ruud
------------------------------
Message: 7
Date: Fri, 07 Jan 2005 23:08:58 -0700
From: Justin Gombos <mindfuq(_at_)fairfieldi(_dot_)com>
Subject: Impossibly complex problem
To: procmail(_at_)lists(_dot_)rwth-aachen(_dot_)de
Message-ID: <20050108060857(_dot_)GA3471(_at_)tango(_dot_)mindfuq(_dot_)org>
Content-Type: text/plain; charset=us-ascii
I have a really irritating complex problem, and I doubt anyone can
solve it, but I'll post anyway -- just in case.
Inbound mail from this procmail list is getting munged such that the
string "Subject:" is getting replaced with a space. But this doesn't
happen all the time, just most of the time. It seems the anomaly does
not occur when I have exactly one procmail message at the time I
retrieve email, and no other messages. As soon as I download multiple
messages, all the procmail list messages lose the subject header
field.
At the same time this problem began, messages from the wget mailing
list also began losing the "subject:" header, but are then dumped in a
folder called "Segmentation," instead of wget_2005 (procmail messages
are correctly dumped in procmail_2005). I never defined a folder to
be called segmentation, so procmail is seriously screwing things up.
There is no reason for procmail to have this problem in isolation,
because the sole script that processes my procmail mail is generalized
and processes other mailing lists (which don't have this problem):
BEENTHERE_PREFIX_ML = (\
dia-list\
|gnupg-[a-z0-9]+\
|latex2rtf[a-z0-9.-]*\
|magick-users\
|sox-users\
|gimp-user\
|procmail)
BEENTHERE_SUFFIX_ML = (\
(lists|informatik)\.RWTH-Aachen\.DE\
|[a-z0-9.]*berkeley\.edu\
|[a-z0-9.]*sourceforge\.net\
|gnome\.org\
|gnupg\.org\
|imagemagick\.org)
# BeenThere mailing lists
#
:0
*$ ^X-BeenThere:(_dot_)*$BEENTHERE_PREFIX_ML(_at_)$BEENTHERE_SUFFIX_ML
*$ ^X-BeenThere:.*\/$BEENTHERE_PREFIX_ML@
* MATCH ?? ()\/[^(_at_)]+
{
LISTNAME=$MATCH
# commented out code here removed for clarity
:0 :
mailing_lists/${LISTNAME}_${YEAR:-0000}
}
And wget is another class of lists that is not a "Beenthere" list, and
has its problem in isolation from the other lists of its class.
My library of scripts is very large. This problem is impossible to
troubleshoot, because when I process one message at a time and watch
the log files, all goes well. As soon as a batch of messages go to
procmail, messages from the procmail list and wget list are hosed.
The logs are impossible to follow because the output is all out of
sequence. To keep things thoroughly confusing, I'm running two
processors with the symmetrical multiprocessor kernel.
------------------------------
Message: 8
Date: Fri, 07 Jan 2005 23:18:16 -0700
From: Justin Gombos <mindfuq(_at_)fairfieldi(_dot_)com>
Subject: Re: remove text from body and change subject and author
To: procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
Message-ID: <20050108061816(_dot_)GB3471(_at_)tango(_dot_)mindfuq(_dot_)org>
Content-Type: text/plain; charset=us-ascii
* Fabian Braennstroem <f(_dot_)braennstroem(_at_)gmx(_dot_)de> [2005-01-07
10:21]:
I would like to get rid of the top and the bottom of the
body text (so actually just keep the stuff between the
second and third '---------').
I see you're using mutt. I once used procmail to remove all the
repetitive types of junk that comes from mailing lists, and someone
here pointed me to a tool that saves me the constant burdon of writing
scripts for every list: TOFU Protection. This is a perl script that
you can integrate with mutt to make the job easier. You might want to
search around for a file named t-prot.pl.
Procmail is a sledge hammer solution, and while it's a powerful tool,
I try to look for other ways to handle a problem when practical
because the scripts seem to get out of control and take on a mind of
their own. It's aaalliiiivvvve!
------------------------------
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail
End of procmail Digest, Vol 24, Issue 9
***************************************
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail