From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/81208 Path: news.gmane.org!not-for-mail From: Dave Abrahams Newsgroups: gmane.emacs.gnus.general Subject: Re: A way to mark off enclosed messages? Date: Thu, 2 Feb 2012 13:55:54 -0600 Message-ID: <0C3150B9-16E6-44BB-AF7E-BCB830E771C3@boostpro.com> References: <87fwet5z0h.fsf@gnus.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 (1.0) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1328212624 20421 80.91.229.3 (2 Feb 2012 19:57:04 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 2 Feb 2012 19:57:04 +0000 (UTC) Cc: "ding@gnus.org" To: Lars Ingebrigtsen Original-X-From: ding-owner+M29489@lists.math.uh.edu Thu Feb 02 20:57:03 2012 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Rt2mE-0001fI-LY for ding-account@gmane.org; Thu, 02 Feb 2012 20:57:02 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1Rt2lU-000856-IM; Thu, 02 Feb 2012 13:56:16 -0600 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1Rt2lT-00084u-5C for ding@lists.math.uh.edu; Thu, 02 Feb 2012 13:56:15 -0600 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx1.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1Rt2lO-0002Qb-3S for ding@lists.math.uh.edu; Thu, 02 Feb 2012 13:56:14 -0600 Original-Received: from mail-gy0-f172.google.com ([209.85.160.172]) by quimby.gnus.org with esmtp (Exim 4.72) (envelope-from ) id 1Rt2lM-00020N-6B; Thu, 02 Feb 2012 20:56:08 +0100 Original-Received: by ghbg16 with SMTP id g16so1728039ghb.17 for ; Thu, 02 Feb 2012 11:56:01 -0800 (PST) Original-Received: by 10.101.134.12 with SMTP id l12mr2016308ann.76.1328212561602; Thu, 02 Feb 2012 11:56:01 -0800 (PST) Original-Received: from [10.29.207.93] ([166.205.14.126]) by mx.google.com with ESMTPS id b4sm7696589and.18.2012.02.02.11.55.59 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 02 Feb 2012 11:56:00 -0800 (PST) In-Reply-To: <87fwet5z0h.fsf@gnus.org> X-Mailer: iPhone Mail (9A405) X-Spam-Score: -2.9 (--) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:81208 Archived-At: BoostPro Computing * http://boostpro.com [Sent from coveted but awkward mobile device] -- On Feb 2, 2012, at 4:07 AM, Lars Ingebrigtsen wrote: > Dave Abrahams writes: >=20 >> Bad iOS! I'd like to work around the problem by forwarding as MIME with >> MML /and/ adding delimiters. Is there a reasonably painless way to >> achieve that? >=20 > I'm not quite sure what you mean. Do you want to forward the message as > MIME, but, er, add new textual MIME parts that look like >=20 > -------------------- Start of forwarded message -------------------- > -------------------- End of forwarded message -------------------- >=20 > around the message/rfc822 part? =20 That would work > I don't really see how that would help > any? I mean, if the iOS reader can't view message/rfc822 parts, the iOS > reader can't view message/rfc822 parts, no matter what you put in the > text/plain parts... The iOS reader *can* view message/rfc822 parts; it's just that they are pres= ented to the user with no visible distinction from the other text in the out= er message body. I can add delimiters manually of course, but it's cumbersom= e and I'm likely to forget. =20=