Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: ding <ding@gnus.org>
Subject: Re: nnimap + mailcrypt
Date: Thu, 11 Apr 2002 14:24:26 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0204111413570.15012-100000@yxa.extundo.com> (raw)
In-Reply-To: <vqozo0ah1qu.fsf@astazou.imag.fr>

On Thu, 11 Apr 2002, Nicolas Kowalski wrote:

> Simon Josefsson <jas@extundo.com> writes:
> 
> >> This makes the nnimap backend "incompatible" with the mailcrypt
> >> package: for example, when I use the `decrypt' function, I will always
> >> get an error, since this require article modification.
> >> 
> >> Did someone managed to make mailcrypt work smoothly with nnimap ?
> >
> > Isn't the decrypt functionality in Oort Gnus enough?  What is missing?
> 
> Do you mean the "W s runs `gnus-summary-force-verify-and-decrypt'"
> feature of Oort ? If yes, this does nothing with my current setup.

MIME buttons aren't displayed per default, so you need to frob
gnus-buttonized-mime-types.  Hm.  W s should alter that default behaviour
temporarily.  Try this patch.

--- gnus-sum.el.~6.203.~	Mon Apr  8 11:16:34 2002
+++ gnus-sum.el	Thu Apr 11 14:17:35 2002
@@ -6680,7 +6680,10 @@
 (defun gnus-summary-force-verify-and-decrypt ()
   (interactive)
   (let ((mm-verify-option 'known)
-	(mm-decrypt-option 'known))
+	(mm-decrypt-option 'known)
+	(gnus-buttonized-mime-types (append (list "multipart/signed" 
+						  "multipart/encrypted")
+					    gnus-buttonized-mime-types)))
     (gnus-summary-select-article nil 'force)))
 
 (defun gnus-summary-set-current-mark (&optional current-mark)

> I certainly have forgot to configure something however :-(.

No Gnus configuration should be needed to get PGP to work.  Everything 
Should Just Work.  Consider it a bug if it doesn't.




  reply	other threads:[~2002-04-11 12:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-11  8:19 Nicolas Kowalski
2002-04-11 12:04 ` Simon Josefsson
2002-04-11 12:13   ` Nicolas Kowalski
2002-04-11 12:24     ` Simon Josefsson [this message]
2002-04-11 12:40       ` Nicolas Kowalski
2002-04-11 13:16         ` Simon Josefsson
2002-04-11 13:55           ` smime setup [was: Re: nnimap + mailcrypt] Nicolas Kowalski
2002-04-11 15:03             ` Simon Josefsson
2002-04-11 15:13               ` Nicolas Kowalski
2002-04-11 15:42                 ` Simon Josefsson
2002-04-11 15:59                   ` Nicolas Kowalski
2002-04-11 19:23                     ` Simon Josefsson
2002-04-11 19:27                       ` Simon Josefsson
2002-04-11 20:05                         ` Nicolas Kowalski
2002-04-11 20:10                           ` Simon Josefsson
2002-04-11 19:56                       ` Nicolas Kowalski
2002-04-11 20:25                         ` Simon Josefsson
2002-04-12  7:41                           ` Nicolas Kowalski
2002-04-12 10:51                             ` Kai Großjohann
2002-04-12 12:45                               ` [SOLVED: openssl issue] " Nicolas Kowalski
2002-04-12 20:47                                 ` Simon Josefsson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.44.0204111413570.15012-100000@yxa.extundo.com \
    --to=jas@extundo.com \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).