Re: [Mutt] #3067: PGP/MIME signatures incorrectly assigned
#3067: PGP/MIME signatures incorrectly assigned "Content-Disposition: inline"
Comment (by jrollins):
Thanks a lot for your response, brendan. I appreciate you keeping this
ticket open to discussion as well.
While I think it may mean something that the RFC author set the
disposition this way, I'm still not sure I think it's the correct
approach. The PGP/MIME signature is *supposed* to be an attachment, which
is in the RFC. It therefore seems that setting the disposition to be
"inline", and therefore suggesting that MUAs display the signature inline,
just doesn't make sense, at least not to me.
I also agree with dkg that displaying signature is more meaningless that
leaving it as an attachment. If the signature is not being processed by
an OpenPGP tool, then it really is just a random string of characters, in
which case it really doesn't make sense to display it.
I think either the suggestion to make it a config-controllable option, or
removing the Content-Disposition header entirely are better than leaving
the disposition hard coded in.
My broader worry is that the current setting might discourage some people
from using or accepting PGP signatures because they might think it makes
there email "look messy". This might seem like a trite concern, but it is
a reaction I've encountered many times because of this issue.
Thanks again for your time with this.
--
Ticket URL: <http://dev.mutt.org/trac/ticket/3067#comment:4>