Gnus development mailing list
 help / color / mirror / Atom feed
From: "François Pinard" <pinard@iro.umontreal.ca>
Cc: ding@gnus.org
Subject: Re: test: empty line missed
Date: 22 Sep 1998 07:03:19 -400	[thread overview]
Message-ID: <oq1zp4v288.fsf@icule.progiciels-bpi.ca> (raw)
In-Reply-To: Lee Willis's message of "22 Sep 1998 09:12:12 +0100"

Lee Willis <lee@gbdirect.co.uk> writes:

> Vladimir Volovich <vvv@vvv.vsu.ru> writes:

> > Are you sure that decoding from base64 was made by gnus? In my case,
> > the original message contained the following headers:

> > X-MIME-Autoconverted: from base64 to 8bit by vvv.vsu.ru id UAA12807

> Erm yep. Good point, well made. :)

If you decode Base64 by `procmail', say, make real sure your adjust headers
consistently, or else, you really ran for trouble (and Gnus is not guilty!).
I once used without much problems these rules:

	:0 fbw
	* ^Content-Transfer-Encoding:.*quoted-printable
	| recode /qp
	  :0 Afhw
	  | formail -i 'Content-Transfer-Encoding: 8bit'

	:0 fbw
	* ^Content-Transfer-Encoding:.*base64
	| recode /64
	  :0 Afhw
	  | formail -i 'Content-Transfer-Encoding: 8bit'

The key is to rewrite CTE when you convert the contents.  But for Gnus
users, such rules should not be needed anymore, as we may expect Gnus to
nicely do the equivalent for us, on the fly.

-- 
François Pinard                            mailto:pinard@iro.umontreal.ca
Join the free Translation Project!    http://www.iro.umontreal.ca/~pinard


  reply	other threads:[~1998-09-22 11:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-09-16 15:16 zsh
1998-09-19 12:10 ` Lars Magne Ingebrigtsen
1998-09-19 22:58   ` Matt Armstrong
1998-09-21 15:29     ` Lee Willis
1998-09-21 16:06       ` Vladimir Volovich
1998-09-22  8:12         ` Lee Willis
1998-09-22 11:03           ` François Pinard [this message]
1998-09-22  1:55       ` Matt Armstrong
1998-09-22  1:48 ` Matt Armstrong

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=oq1zp4v288.fsf@icule.progiciels-bpi.ca \
    --to=pinard@iro.umontreal.ca \
    --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).