|
Re: problem with procmail
2003-03-28 19:02:41
At 18:07 2003-03-28 -0500, Dan Gahlinger did say:
I'm using solaris 9 and having a problem with procmail.
it doesn't seem to work at all.
Now we know your OS version (sorta), what's your Procmail version? Of the
two things you mention above, it'd be a lot more useful if you declared the
procmail version.
I've turned on verbose=on, I've uncommented the console line in config.h
(and redid make/etc)
The latter is wholly unnecessary given the nature of the error, as you'll
find when you run 'man procmail'.
I get no logging at all, no messages at all, nothing. the only thing I've
gotten recently is
in /var/adm/messages which says "suspicious rcfile" pointing to my
.procmailrc - why ?
It might come as a major revelation, but the error messages ARE documented
in the manpages. Pretty much all of them in fact. Have you tried looking
there?
and when my .forward is there, I get NO mail at all.
Well, your mail log should reveal what action your MTA took when the
message was rejected by procmail. Surely, there's an explanation as to why
your email is bouncing (since, if it isn't heading into your mail spool, it
is bouncing, or being requeued, as in EX_TEMPFAIL - the "exit 75" bit in
the .forward).
I've tried three different variations of the .forward file with or
without a .procmailrc
I see only one, and have no idea whether this is the one which relates to
the symptoms you're describing as sometimes happening. Is there a
.procmailrc file when you're using this one, does it cause the above log
entries, etc?
I realize you're probably absolutely frustrated as you try to get this
program running without reading the manual, but you're not providing a
single diagram of _one_complete_test_scenario_ along with the results of
that specific scenario. Instead, you're providing fragmented bits of
information about various things you've tried, and some characteristics of
some of the problems you've had - no lines drawn between any two items to
correlate them.
When, some day, you get stuck having to resolve this sort of stuff by
yourself in the dead of night, perhaps with an isolated network connection,
the importance of keeping track of the cause and effect relationships will
become clear to you. You should get an early start on tracking those
relationships whenever diagnosing a problem, or asking others to diagnose
your problems, so that it's an automatic reflex for you later on. Much
like reading manpages (which, I've been guilty of not checking very closely
from time to time as well).
with a blank .procmailrc and one with options and one with just logging.
no matter what I do, the same thing happens - no mail.
I suspect when you have _no_ .procmailrc, the /var/adm/messages error isn't
the same. This interrelates with that _one_complete_test_scenario_ bit I
just mentioned.
here's the .forward
Certainly you mean one of the THREE forwards. Is there a ~/.procmailrc
when you use this? What other syntaxes have you used? Is the procmail
path itself VALID?
"|IFS=' ' && exec /usr/bin/procmail -f- || exit 75 #TEST_PROCMAIL"
Trying to run procmail via a .forward, without actually having a
~/.procmailrc would cause procmail to deliver normally.
Have you tried, from another account, sending mail to this account you're
bodging away on, to see what the sender gets in response to their sent mail?
I've used -Yf- and verbose=on -Yf- and verbose=on -f-
nothing works.
The solution is in the manpages. Also, check out:
<http://www.professional.org/procmail/procdiag.sh>
Download it, carefully *READ* it, then invoke it. It should point out some
of the more common user-induced faults.
---
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.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail
|
|