|
From: | Lyndon Nerenberg |
Subject: | Re: [Nmh-workers] thread mangling python-list mailing list to comp.lang.python google group |
Date: | Wed, 19 Aug 2015 09:54:38 -0700 (PDT) |
User-agent: | Alpine 2.20 (BSF 67 2015-01-07) |
Here's an idea. Ken will like this because there's no indication of how the work would get done. What if nmh warned that a non-RFC-compliant header were produced? It takes care of encoding Subject, etc., at the moment, if needed. It could look out for In-Reply-To, References, etc., and warn or error if they're bad. Probably not at format time, since who knows to what warped ends I'm deploying nmh, but when an email is trundling towards being sent.
You don't need to hack nmh for this. Just find (or write) an external program that does RFC(pick your favourite) validation, then run your message through it at the 'what now?' prompt.
[Prev in Thread] | Current Thread | [Next in Thread] |