Exmh is tolerant of the output format that 'scan' returns, which it uses to build the ftoc. It does require that the first token be the message number in the folder.. However, it fails silently and mysteriously if 'scan' returns a bad message
number - the failure mode I hit was when my Bugtraq folder rolled over to
10K messages, but still had a %4 width specifier in my scan format. It was
unable todo a 'next' from message '9999' to '?001', and would lock up for inordinate amounts of time in Scan_Folder when new mail arrived.
Suggested fix: Check the first token against a [0-9]* regexp and flag an error if it's unacceptable, so the user *knows* what's wrong....
Log in to post a comment.