ralph wrote:
Hi Paul,
Because the mhbuild step can only turn a non-MIME email into a MIME
one; it can't handle being given a MIME email as input.
that's what i thought. but if that's so, then how does the last bit:
"But ... Nmh-Attachment headers are still processed."
work?
They can "only" be put there by "attach" which refuses to do so if
"mime" has already been run. It knows this by seeing MIME-Version is
present.
that's not true. Nmh-Attachment headers can be inserted manually as
well, bypassing that "attach" error check.
but i now see that i mis-parsed ken's original description. if i
add some [clarification edits], does it still mean what ken meant
to begin with?
- send runs "mhbuild -auto -nodirectives". "-auto" means, "don't
error out if there's a MIME-Version header, just don't process
the draft" [including any Nmh-Attachment headers]. "-nodirectives"
means "don't process directives". But ... [ even with -nodirectives, ]
Nmh-Attachment headers are still processed.
paul
Cheers, Ralph.
_______________________________________________
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers
----------------------
paul fox, pgf@foxharp.boston.ma.us (arlington, ma, where it's 20.1 degrees)
_______________________________________________
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers