All:
A sanitizer user who's been experiencing the "dropped F" problem has
been performing some tests and may be narrowing it down.
He seems to be able to reproduce it if the perl script attempts to log
to a file it cannot write to. He gets the "rescue of unfiltered data
succeeded" message, but the message is corrupted.
I haven't had a chance to look at this. I will see if I can duplicate
it here over the weekend.
Anybody else care to see if they can duplicate the "dropped F" problem
by piping the message through a filter that fails?
--
John Hardin KA7OHZ ICQ#15735746 http://www.impsec.org/~jhardin/
jhardin(_at_)impsec(_dot_)org pgpk -a
jhardin(_at_)impsec(_dot_)org
768: 0x41EA94F5 - A3 0C 5B C2 EF 0D 2C E5 E9 BF C8 33 A7 A9 CE 76
1024: 0xB8732E79 - 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
"To disable the Internet to save EMI and Disney is the moral
equivalent of burning down the library of Alexandria to ensure the
livelihood of monastic scribes."
-- John Ippolito of the Guggenheim
-----------------------------------------------------------------------
331 days until The Matrix Reloaded
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail