Broken Message-ID headers

["Matthias Urlichs" <smurf@noris.net>]

Mails with broken Message-ID: headers tend to crash the router.

IMHO, these mail should be bounced and rejected, and the offending header
should not be looked at further, just to forestall any problems arising
from their unparseability.

Example:

	Message-ID: 64317946789@

I don't know what your router does with this thing, but mine dies a 
rather horrible death somewhere in the middle of processing the routing
scripts...


NB: Related to this: the offending message caused a core dump. Which
duly got copied out of the router directory. Then, the next router
tried to process the thing, created a core dump ... my $POSTOFFICE
now contained 2 GBytes of coredumps. IMHO, if a core is seen, then
files of the form ###-## lying around should be moved off to a
subdirectory. Trying to process them again tends to be a Bad Thing.

-- 
Matthias Urlichs  |  noris network GmbH   |   smurf@noris.de  |  ICQ: 20193661
The quote was selected randomly. Really.    |      http://www.noris.de/~smurf/
-- 
I know how to do SPECIAL EFFECTS!!
		-- Zippy the Pinhead