[Raw Msg Headers][Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

$POSTOFFICE/postman/ usage conventions (squirrel):




Hello,

	While I revised the squirrel() things, I also made an explicite
	way for the postmaster to notice that some file is in trouble,
	and also to determine, WHY:

nic.funet.fi$ ls /var/spool/postoffice/postman/
74619._badheader  74891._badheader  75091._badheader  75487._badheader
74658._badheader  74892._badheader  75097._badheader  75510._badheader
74670._badheader  74898._badheader  75104._badheader  75540.looped
74674._badheader  74908._badheader  75138._badheader  75571._badheader
74675._badheader  74915._badheader  75259._badheader  75592._badheader
74692._badheader  74932._badheader  75381._badheader  75602._badheader
74804._badheader  74938._badheader  75423._badheader  75610._badheader
74813._badheader  74984._badheader  75432._badheader  75620._badheader
74814._badheader  75021._badheader  75454._badheader

	All messages with "._" in their names have been squirrelled
	due to INFORMATIVE copying, those few (rare!) ones that don't
	have that character pair have been squirrel()ed because something
	is really wrong, and the system can't figure things out.

	So in above example there are N messages with busted headers,
	and ONE which deserves checking at it.  (Even that one is not
	such a one which has not been delivered anywhere.. thus I have
	altered the new name to be with "._", which means it can be
	deleted blindly..)

/Matti Aarnio <mea@nic.funet.fi>