From: Adam Bogacki [mailto:afb(_at_)paradise(_dot_)net(_dot_)nz]
Ahem... taking a straw out of Dallman's book and
perusing old procmailrc's I reorganised both
$HOME/.procmailrc and /etc/procmailrc and found
both logs (etc & adam) existing in $HOME/Mail.
Good.
I changed '/bin/sh' to '/bin/bash' - used in
earlier working copies - and commented out the entire
Probably quite unnecessary, as in many *nixes today
/bin/sh actually runs /bin/bash anyway, but /bin/sh
is the better shell for procmail if there is a different
such shell on the machine. The point is to avoid invalid
syntax (there's no such thing as "bin/sh" without a leading
slash, unless you have a copy of sh in the bin relative
to the current working directory of procmail, which is
probably unlikely).
bit with quotes indicating spaces on the assumption
there was something missing such as a space tab ..
If we spot something as being wrong, the idea is to fix it,
not erase it. Your logs posted earlier confirm that there
are a bunch of space characters in the var definition where
there should have been a tab char. Even though you keep
reminding us that you don't have a computer background, I
refuse to believe that you aren't basically intelligent --
and your statement of your previous professional activities
would corroborate this. I think you must therefore see that
if we say
TAB = ' '
and you see whitespace there inside the quotes but obviously can't
eyeball it to see what *kind* of whitespace, then the next thing
to do -- since it's been mentioned (several times, by me) that the
whitespace there is wrong -- is to, using your editor, take that
whitespace away that is suspect and replace it with a single character
that you know for damn certain to be a tab, because you put it there
by yourself!
Now, I know some of our emails are crossing and that I am partly
repeating myself before you can respond. But still...
Perhaps Ruud could indicate if there is a missing
TAB command somewhere.
All you need to do is put a tab character between the quotes.
You will know it's a tab, because you will have typed it in yourself.
End of story!
Dallman was right, DIY is best !
What he said! :-)
I attach excerpts from both logs, both currently verbose.
(2) adam-procmail.log
^^^^^^^^^^^^^^^^^^^^^
procmail: Rcfile: "/etc/procmailrc"
procmail: Assigning "PATH=/usr/local/bin:/usr/bin:/bin"
procmail: Assigning "DROPPRIVS=yes"
procmail: Assuming identity of the recipient, VERBOSE=off
procmail: Assigning "VERBOSE=yes"
procmail: Assigning "SHELL=bin/sh"
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This must get fixed. Until it is fixed, your procmail is
basically bolluxed.
(You keep having double assignments, one in /etc/procmailrc
and one in adam's .procmailrc, and sometimes they don't match
up. Just do it once and make sure it's clean.
(Here's a non-computer-person analogy: Pretend the "shell"
is your home phone number, and you teach it to your 4-year-old
in case he gets lost. Your number is 123-4567. The kid
says he's memorized it; he gets lost in Wal-Mart; the security
guards find him; and he says over and over that his phone
number is 234-5678. The security folks will never be able
to reach you to tell you they found your kid!!
(Similarly, as long as the shell is set to something bogus,
procmail will never be able to do anything that calls a shell.)
procmail: Assigning
"LASTFOLDER=/home/adam/Mail/.Inbox/new/1105324906.8679_2.Tux"
procmail: Notified comsat:
"adam(_at_)0:/home/adam/Mail/.Inbox/new/1105324906.8679_2.Tux"
Subject: The Password [WAS: Re: 'Folder: bounced ']
Folder: /home/adam/Mail/.Inbox/new/1105324906.8679_2.Tux
Wow. Something is actually working.
Dallman
____________________________________________________________
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