Hi, When I sign and send an email with mutt, the signature file is automatically named "noname". I would prefer something like that "signature.asc". I found a solution to resolve this minor problem : I read somewhere that the variable which allows to name the pgp signature is pgp_mime_signature_filename. However this variable is not in the standard mutt package. By googling a bit more I found the vk.pgp_verbose_mime patch (here: http://www.doorstop.net/projects ). I adapted it to my current version of mutt (~)1.5.21-r1 and I wrote an overlay. After patching, compiling and installing, it works perfectly. I attached files : - patch-1.5.21-r1.vk.pgp_verbose_mime <- the patch, of course - mutt-1.5.21-r1.ebuild.patch <- the difference between the official mutt ebuild and my ebuild To use the feature offered by this patch, just add these two lines in your .muttrc file : set pgp_mime_signature_filename="signature.asc" set pgp_mime_signature_description="Digital signature" It would be great if this patch were added to the gentoo-patches package when gpg flag is enabled for mutt. JC Please find here the mails thread sent on gentoo-users ML : http://groups.google.com/group/linux.gentoo.user/msg/2a54398b522c0d04 Reproducible: Always Steps to Reproduce: 1. install mutt and gnupg 2. send an email that you sign with your key 3. look at the attached signature file : it is named "noname" Actual Results: The attached pgp signature file is named "noname". Expected Results: It is normal because the feature is not implemented. But it would great if we could name the pgp signature file (e.g. "signature.asc") when enabling the gpg USE flag.
Created attachment 256941 [details, diff] mutt patch adding pgp_mime_signature_filename variable
Created attachment 256943 [details] what I added to the mutt ebuild to use the patch
Would you please bring this up on mutt-dev as well, to see if the maintainers like to apply this patch to current hg? It seems small enough to me to be quite acceptable. Thanks in advance.
(In reply to comment #3) > Would you please bring this up on mutt-dev as well, to see if the maintainers > like to apply this patch to current hg? It seems small enough to me to be > quite acceptable. Thanks in advance. > Well, yes, if I succeed in creating an account on their bugtrack :) It is not very user friendly and for the moment I am blocked. My account has not been created and the mutt-dev ML seems to be private. I will try again. I saw that this patch was already submitted few years ago, but it does not seem to have been added to the main branch.
(In reply to comment #4) > (In reply to comment #3) OK, I filed a ticket on mutt tracker: http://dev.mutt.org/trac/ticket/3478 (Ticket #3478)
thanks
I've adjusted the patch formatting slightly (the posted version here has incorrect line counts) and posted a mutt-1.5.21-r2 ebuild in my `wtk` overlay for anyone who doesn't want to maintain their own overlay for this issue. This should make things more comfortable until this bug is fixed (either here or upstream).
fixed in mutt-1.5.21-r4, thanks!
This bug still affects the signing with gpgme on mutt 1.5.22-r3. A patch is available in https://dev.mutt.org/trac/attachment/ticket/3478/gpg_signature_name.patch which will superseed the current 13-pgp-verbose-mime.patch from ${PN}-gentoo-patches*. Alternatively, the patch can be added on top of 13. Will attach both to this bug report Incidentally, I apologize if I should've opened a new bug report instead of reviving an old one. I do not know what proper etiquette is in this case.
Created attachment 389036 [details, diff] Adding pgp_mime_signature_filename to gpgme codepath too This patch works on top of 13-pgp-verbose-mime.patch.
Created attachment 389038 [details, diff] Adding pgp_mime_signature_filename to pgp AND gpgme codepath This patch would supersede 13-pgp-verbose-mime.patch
