On Tue, 01 Oct 2002, mis(_at_)host1(_dot_)tyes(_dot_)tyc(_dot_)edu(_dot_)tw
wrote:
It seems like procmail is being called by some other program
here.
-----------------------------------------------
Sanitizing MIME attachment headers in \"php-db Digest 1 Oct 2002 11:39:57
-0000 Issue 1442\" from php-db-digest-help(_at_)lists(_dot_)php(_dot_)net to
<fongming(_at_)host1(_dot_)tyes(_dot_)tyc(_dot_)edu(_dot_)tw>
msgid=<1033472397(_dot_)68309(_dot_)ezmlm(_at_)lists(_dot_)php(_dot_)net>
procmail: Error while writing to \" perl -p -e \' #\\
$pastmsghdr = 1 if /^\\s*$/; #\\
$XCS = \"X-Content-Security: [\" . $ENV{\"HOST\"} . \"]\" unless $XCS;
#\\
if ($pastmsghdr) { #\\
if (!$mimebdry && $mimebdrs[0]) { #\\
warn \" Found no MIME boundary.\\n\" if $ENV{\"DEBUG\"}; #\\
This is a very long command line script. Perhaps it is exceeding
some procmail buffer limit?
LINEBUF Length of the internal line buffers, cannot be
set smaller than 128. All lines read from the
rcfile should not exceed $LINEBUF characters
before and after expansion. If not specified,
it defaults to 2048. This limit, of course,
} #\\
\' 2>> $LOGFILE\"
procmail: Rescue of unfiltered data succeeded
Well at least you didn't lose the mail ;-)
I guess you have to try debugging the perl script from the command line.
Pipe the mail to the script.
--
Greg Matheson Those who can do.
Chinmin College Those who can't operate.
--G B Shaw
Taiwan Penpals Archive <URL: http://netcity.hinet.net/kurage>
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail