Why would this be working for people w/ maildrop 1.3.8 and not be working
for me w/ 1.5.2? This is the main thrust of my original question. What
changed?
-----Original Message-----
From: cour...@lists.sourceforge.net
[mailto:cour...@lists.sourceforge.net]On Behalf Of Sam
Varshavchik
Sent: Thursday, April 10, 2003 11:09 AM
To: cour...@lists.sourceforge.net
Subject: [maildropl] Re: syntax problem (did something change from 1.3.8
to 1.5.2?)
Benjamin Tomhave writes:
Excuse me, but WTF? That was certainly rude and not called for.
The original code was:
`test -d $VHOME/Maildir`
if ( $RETURNCODE == 1 )
{
echo "Sorry, no mailbox here by that name. (#5.1.1)"
EXITCODE=100
exit
}
The maildropfilter man page seems to indicate that RETURNCODE should get
populated with the value of the test statement. Is this the
case or not, oh
great master creator?
What part of "The RETURNCODE variable will be set to the exit code of the
command, after it completes" do you not understand? Do you see the word
"value" anywhere in there?
As you had suggested in your previous email, I tried assigning the test
statement to a variable and testing against that variable
instead of against
RETURNCODE,
I do not recall saying anything about RETURNCODE. I told you to assign
`command` to a dummy variable. That's it. No mention of RETURNCODE.
Don't slap me in the face for being confused by your documentation.
You are confused because you do not understand the difference between
"command output", and "command exit code". Both are traditional UNIX
concepts that have existed for decades.
14 messages in net.sourceforge.lists.courier-maildropRE: [maildropl] Re: syntax problem (d...
