Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Thomas Persson <thomas@spacecentre.se>
Subject: Re: stored mail differs from the sent
Date: Thu, 22 Apr 2004 12:59:53 +0200	[thread overview]
Message-ID: <87d660jn12.fsf@spacecentre.se> (raw)
In-Reply-To: <m365bspw7b.fsf@defun.localdomain>

Jesper Harder <harder@myrealbox.com> writes:

> Thomas Persson <thomas@spacecentre.se> writes:
>
>> Jesper Harder <harder@myrealbox.com> writes:
>>
>>> The archived message is not corrupt.  It verifies correctly for me in
>>> Gnus 5.10.

I installed Gnus v5.10.6 but my old archived messages still don't
verify correctly. Not with mailcrypt and not with
pgg-verify-region. In fact none of my old messages, not even the
really old ones I wrote in pine works anymore after the upgrade. They
(the old pine messages with 8bit encoding) if I export them to a file
and verify them with gpg -d. 

>> I tried the same procedure of signing and sending a mail to myself but
>> this time with an email account where the MTA didn't convert the
>> content-transfer-encoding from quoted-printable to 8bit and this time
>> neither the archived nor the received mail verified correctly.
>
> This is probably a bug in Mailcrypt as your previous QP example
> verified for me.

Yes it does seem to be a bug in mailcrypt. Mailcrypt probably creates
the signature assuming that the non ASCII characters will be sent as
8bit. I see now that the fact that the messages I sent verified
correctly was just a fluke. The MTA translated them into 8bit.

>> I have done some research and my working theory is that digitally
>> signed messages cannot be quoted-printable. Is this correct?
>
> Yes and no.  If your message includes 8bit characters you shouldn't
> really be using old-style inline PGP in the first place.  However, if
> you do, the message should be QP encoded.
>
> The right thing for messages with non-ASCII characters is to use
> PGP/MIME which works reliably in this case.
>
>> What I have to do then is to make sure that emacs sets the
>> content-transfer-encoding to 8bit whenever I send a digitally signed
>> message. There is a variable called
>> `mm-content-transfer-encoding-defaults' but I feel that I do not
>> enough about this yet.
>
> That is the wrong approach.  As I suggested previously you should
> rather upgrade to Gnus 5.10 (and use PGP/MIME).  If you really *must*
> use inline PGP in combination with 8bit, then this works in 5.10 as
> well.

I'm convinced. I'll start using PGP/MIME instead. I was just annoyed
that using inline PGP with non ASCII characters shouldn't work with
Gnus when I did it with pine for over a year. 


      reply	other threads:[~2004-04-22 10:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87brlm6yr1.fsf@spacecentre.se>
     [not found] ` <m3ekqiw7un.fsf@defun.localdomain>
2004-04-21  9:21   ` Thomas Persson
     [not found]     ` <m365bts74p.fsf@defun.localdomain>
     [not found]       ` <87isftxphz.fsf@spacecentre.se>
     [not found]         ` <m38ygpqjin.fsf@defun.localdomain>
     [not found]           ` <87y8opw4np.fsf@spacecentre.se>
     [not found]             ` <m3d661p0av.fsf@defun.localdomain>
2004-04-21 22:43               ` Thomas Persson
2004-04-22  2:45                 ` Jesper Harder
2004-04-22 10:59                   ` Thomas Persson [this message]

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=87d660jn12.fsf@spacecentre.se \
    --to=thomas@spacecentre.se \
    /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).