[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nmh-workers] suppress Content-ID's with new mhbuild option?

From: Jon Steinhart
Subject: Re: [Nmh-workers] suppress Content-ID's with new mhbuild option?
Date: Sun, 29 Jan 2006 20:56:51 -0800

> > > I'd like to remove the manual steps, as well as support use
> > > of X-MH-Attachment headers, which doesn't give me a chance
> > > to edit the final draft before sending.
> > 
> > How would you propose doing this, since usually one is using
> > attachments for non-ASCII stuff?  Or am I not understanding
> > the question?  You can edit the list of attachments.
> It's got nothing to do with what's in the attachment,
> ASCII or otherwise.
> The problem is simply that I do not want Content-ID headers
> to appear in the message that I create.
> My big-hammer solution is to disable output of Content-ID's,
> under control of an option to mhbuild.
> Another approach might include (among other things) insertion of <> in
> the directives that X-MH-Attachment generates just before the [:
>   #text/plain; name="foo.txt"; x-unix-mode=0644 <>[ English text ] 
> /tmp/foo.txt
>   #application/pdf; name="foo.pdf"; x-unix-mode=0644 <>[ Adobe Portable 
> Document Format (PDF) v1.2 ] /foo/multiatt.pdf
> Would there be a reasonable way to do that?  I see where it
> would be done in the code, in make_mime_composition_file_entry ().
> But I don't see a convenient way to change what goes into those
> directives.  Maybe add a configure option?

I didn't understand your question.  Was fooled by "edit the final draft".

This sounds like a matter of personal taste as you never want content-id
headers; it's not something that you do on a message by mesage basis.  So
why not add a dash option and you can put it in your profile?  Seems nicer
than added more cryptic goo to something that is already too cryptic for
a sane person to use which is why I added the attachment handling code a
while back.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]