Paul F. wrote:
i'm having trouble with the next two points:
> > - If you try to "attach" after a "mime", you get an error.
> > - send runs "mhbuild -auto -nodirectives". "-auto" means, "don't
> > error out if there's a MIME-Version header, just don't process the
> > draft". "-nodirectives" means "don't process directives". But ...
> > Nmh-Attachment headers are still processed.
if "mhbuild -auto -nodirectives" can still process Nmh-Attachment
directives at this point, then why can't "attach" after a "mime"
still work? couldn't running "attach" after a "mime" simply do the
same thing that makes the "send" case work?
If I understand correctly, with both -auto and -nodirectives,
Nmh-Attachment headers won't be processed if the message has
already been mime'd (run through mhbuild). If we were to allow
them to be processed after the message was mime'd, the new
attachments would have to be inserted into the existing MIME
structure. Doable but I agree that it's not a good idea.
If that's right and we want to revisit this, mhfixmsg does
that kind of insertion. But for our current purpose, we
wouldn't be using mhbuild, at least in its entirety, so I
would still agree that it's not a good idea. The limitation
of no "attach" after "mime" is not onerous and can be easily
Nmh-workers mailing list