[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [sup-devel] [PATCH] Decode messages according to their Content-Transfer-Encoding

To: Michael Stapelberg <michael+sup@stapelberg.de>
Subject: Re: [sup-devel] [PATCH] Decode messages according to their Content-Transfer-Encoding
From: Rich Lane <rlane@club.cc.cmu.edu>
Date: Fri, 04 Jun 2010 22:54:24 -0400
Authentication-results: mx.google.com; spf=pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org
Cc: sup-devel <sup-devel@rubyforge.org>
Delivered-to: eg@gaute.vetsj.com
Delivered-to: sup-devel@rubyforge.org
In-reply-to: <1275689764-sup-3384@midna.zekjur.net>
List-archive: <http://rubyforge.org/pipermail/sup-devel>
List-help: <mailto:sup-devel-request@rubyforge.org?subject=help>
List-id: Sup developer discussion <sup-devel.rubyforge.org>
List-post: <mailto:sup-devel@rubyforge.org>
List-subscribe: <http://rubyforge.org/mailman/listinfo/sup-devel>, <mailto:sup-devel-request@rubyforge.org?subject=subscribe>
List-unsubscribe: <http://rubyforge.org/mailman/options/sup-devel>, <mailto:sup-devel-request@rubyforge.org?subject=unsubscribe>
References: <1275689764-sup-3384@midna.zekjur.net>
Reply-to: Sup developer discussion <sup-devel@rubyforge.org>
Sender: sup-devel-bounces@rubyforge.org
User-agent: Sup/git

Excerpts from Michael Stapelberg's message of 2010-06-04 18:17:54 -0400:
>     Decode messages according to their Content-Transfer-Encoding
>         
>     This is necessary for MIME-messages (for example as part of multipart/signed)
>     which are encoded in base64.

Do we need to do this in other places too?
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel

Follow-Ups:
- Re: [sup-devel] [PATCH] Decode messages according to their Content-Transfer-Encoding
  - From: Michael Stapelberg <michael+sup@stapelberg.de>

References:
- [sup-devel] [PATCH] Decode messages according to their Content-Transfer-Encoding
  - From: Michael Stapelberg <michael+sup@stapelberg.de>

Prev by Date: Re: [sup-devel] [PATCH] Bugfix: Charset conversion needs to take place *after* verifying inline GPG signatures
Next by Date: Re: [sup-devel] [PATCH] Decode messages according to their Content-Transfer-Encoding
Previous by thread: [sup-devel] [PATCH] Decode messages according to their Content-Transfer-Encoding
Next by thread: Re: [sup-devel] [PATCH] Decode messages according to their Content-Transfer-Encoding
Index(es):
- Date
- Thread