Gnus development mailing list
 help / color / mirror / Atom feed
From: Jorge Godoy <godoy@conectiva.com>
Cc: ding@gnus.org
Subject: Re: Verifying GPGP signed messages: mailcrypt bug or Gnus configuration problem?
Date: 21 Nov 2000 19:35:20 -0200	[thread overview]
Message-ID: <kpk89x6mav.fsf@dagon.conectiva> (raw)
In-Reply-To: <5bbsv9qovk.fsf@brandy.cs.rochester.edu>

On 21 Nov 2000, zsh@cs.rochester.edu wrote:
> Jorge Godoy <godoy@conectiva.com> writes:
> 
>> How can I see the full message without any post-processing
>> (i.e. beautification after receiving the message) from Gnus? I want
>> to cut the message, cut the signature and try running gpg by hand.
> 
> C-u g


Thanks! 


I've seen the message and there are the codes I thought there would
be, e.g., 

,----
| =C9, sim. N=E3o tem word-wrapping ou coisa parecida ligada a=ED?
| Estou assinando de novo.
`----

instead of

,----
| É, sim. Não tem word-wrapping ou coisa parecida ligada aí?
| Estou assinando de novo.
`----


I think this is because there's no description of what encoding to use
for the body on the headers. These are the relevant parts of it:

,----
| Mime-Version: 1.0
| Content-Type: multipart/signed; micalg=pgp-md5;
|         protocol="application/pgp-signature"; boundary="i0/AhcQY5QxfSsSZ"
| Content-Disposition: inline
| User-Agent: Mutt/1.2.5i
`----

(I've inserted that elisp to change the mutt signature from MD5 to
SHA1, but this didn't help)


Is there any way to tell Gnus to always use ISO-8859-1 for messages it
don't receive any other encoding instruction?



Thanks!
-- 
Godoy. <godoy@conectiva.com>

Departamento de Publicações       Conectiva S.A.
Publishing Department             Conectiva Inc.



  reply	other threads:[~2000-11-21 21:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-21 16:00 Jorge Godoy
2000-11-21 16:19 ` ShengHuo ZHU
2000-11-21 21:35   ` Jorge Godoy [this message]
2000-11-21 21:45     ` ShengHuo ZHU
2000-11-21 23:06       ` Jorge Godoy
2000-11-22  1:09         ` ShengHuo ZHU
2000-11-22  1:46           ` Jorge Godoy

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=kpk89x6mav.fsf@dagon.conectiva \
    --to=godoy@conectiva.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).