>>>>> "CM" == Chuck Milam <email@example.com> writes:
CM> More information: Both messages stuck in the queue came from the same
CM> site, both posted from a MS-Exchange environment.
CM> Here's posting after I cranked the debug level up to 500. Nothing more
CM> for the "cannot read file" error, but some more (harmless?) Perl
The debug level should not effect the warnings; they should always end up
in the logs. And they're not harmless at all; in fact, they're the cause
of the error.
But this still doesn't look like a full debug-level trace. Are you sure
the list's debug level is set to 500? I can figure out the problem now
anyway (that NonPost file doesn't seem to exist) and I'll make a bit of a
change to allow it to work, although the user will just see a nice message
like "The list administrator has specified a nonexistent file." It's
better than a crash. These fixes are in CVS now.
Better error checking on access_rules setting is in the pipeline.
Jason L Tibbitts III - firstname.lastname@example.org - 713/743-3486 - 660PGH - 94 PC800
System Manager: University of Houston Department of Mathematics
"You'll see the blood as we roll in it together..."