Robert Allerstorfer schreef:
I recently found that not having a \n at the end of a procmail rc file
could make problems. In particular, unsetting a variable's value at
the end using something like
# unset $my_VAR
my_VAR
won't work when no byte is following my_VAR. So, in my latest release
of SoftlabsAV (0.8.4), available at
http://softlabsav.sourceforge.net/
I have made sure that each file read by procmail (there are currently
30) will have at least one newline at its end.
Hey, good catch. That would be a procmail-bug, I think.
A closing comment is a way to make sure that the newline is there
and remains there (some editors remove trailing empty lines from a
file, when saving).
So something like:
#EOF (workaround for procmail-v3.22-bug #13)
It is my habit to put '# unset' after the variable (lining up the equal
signs and the #) and that also works (the line isn't 'Skipped' if
without trailing newline, because of the trailing comment).
var_one = '1'
var_two = '2'
var_three = '3'
var_four # unset
--
Grtz, Ruud
____________________________________________________________
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