Re: Unexpected output of "notmuch new --quiet"

Subject: Re: Unexpected output of "notmuch new --quiet"

Date: Fri, 19 Apr 2019 03:03:31 -0400

To: Ralph Seichter,


From: Daniel Kahn Gillmor

On Thu 2019-04-18 15:52:19 +0200, Ralph Seichter wrote:
> Personally, I'd go with these decreasing levels of severity:
>   Fatal: Execution must stop immediately to prevent damage, error
>   message may or may not be displayed before exiting the process.
>   Error: Serious trouble, program may or may not be able to recover,
>   user intervention required.
>   Warning: Minor trouble, program will recover without user
>   intervention.
>   Notice: Inform the user of a less-than-ideal situation (non-mail file
>   found, deprecated functionality used, etc). Program will ignore the
>   cause and carry on.

Why is "non-mail file found" in my maildir such a low priority?  If
there's a malformed message in my maildir i want to know about it as
soon as possible, that could be an important e-mail that some other part
of my mail ecosystem mangled that i could de-mangle to have access to it
if only i know to look there?

Seems like using new.ignore to ignore the files that you know are
supposed to be there but aren't mail is a cleaner way to go.

signature.asc (application/pgp-signature)
notmuch mailing list