Howdy all. Quick question for you. Can I use a # comment within a
multi-line command? exp (note, the sed line will proably wrap):
:0f
# Run it through spamassassin -d to remove the X-Spam* headers
| $SA -d | \
# Munge the userid(_at_)*(_dot_)sktc(_dot_)net
$SED -e
"s/\<[-+_a-zA-Z0-9]*(_at_)[-_a-zA-Z0-9\(_dot_)]*sktc\(_dot_)net/MUNGED(_at_)sktc(_dot_)net/gi"
\
# Remove the subject line ***SPAM*** string
-e "s/\*\*\*SPAM\*\*\* *//gi" | \
# Remove the ReSent, X-Envelope-To, and X-Scanned-By headers
$FORMAIL -I ReSent \
-I X-Envelope-To: \
-I X-Scanned-By:
The reason I ask is because I'm seeing some odd things in my log file.
procmail: Locking "/var/mail/spool/spamtrap.lock"
procmail: [10104] Sun Dec 8 12:52:56 2002
procmail: Executing " $SA -d | \
# Munge the userid(_at_)*(_dot_)sktc(_dot_)net"
procmail: Assigning "LASTFOLDER=/var/mail/spool/spamtrap"
procmail: Opening "/var/mail/spool/spamtrap"
procmail: Acquiring kernel-lock
/bin/sh: -c: line 3: syntax error: unexpected end of file
procmail: [10104] Sun Dec 8 12:52:56 2002
procmail: Error while writing to " $SA -d | \
# Munge the userid(_at_)*(_dot_)sktc(_dot_)net"
procmail: Unlocking "/var/mail/spool/spamtrap.lock"
procmail: Rescue of unfiltered data succeeded
procmail: Notified comsat: "spamtrap(_at_)5906893:/var/mail/spool/spamtrap"
The code and log I quote are just part of the whole recipe and error entry
but I figure it's enough. The 3rd line in the error message is what
caught my eye first. The /bin/sh error was next. Finally the "Error
while writing" line caught my attention. Can I use comments like that
without a \ on those lines too? Is it more proper to put the comment at
the end of the line after the \? Thanks
Justin
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail