From: Dave Abrahams <dave@boostpro.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: "ding@gnus.org" <ding@gnus.org>
Subject: Re: A way to mark off enclosed messages?
Date: Thu, 2 Feb 2012 13:55:54 -0600 [thread overview]
Message-ID: <0C3150B9-16E6-44BB-AF7E-BCB830E771C3@boostpro.com> (raw)
In-Reply-To: <87fwet5z0h.fsf@gnus.org>
BoostPro Computing * http://boostpro.com
[Sent from coveted but awkward mobile device]
--
On Feb 2, 2012, at 4:07 AM, Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Dave Abrahams <dave@boostpro.com> writes:
>
>> 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?
>
> 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
>
> -------------------- Start of forwarded message --------------------
> -------------------- End of forwarded message --------------------
>
> around the message/rfc822 part?
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 presented to the user with no visible distinction from the other text in the outer message body. I can add delimiters manually of course, but it's cumbersome and I'm likely to forget.
next prev parent reply other threads:[~2012-02-02 19:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 17:34 Dave Abrahams
2012-02-01 17:47 ` Greg Troxel
2012-02-01 18:35 ` Dave Abrahams
2012-02-01 18:43 ` Edward O'Connor
2012-02-02 10:07 ` Lars Ingebrigtsen
2012-02-02 19:55 ` Dave Abrahams [this message]
2012-02-06 22:13 ` Lars Ingebrigtsen
2012-02-06 23:27 ` Ted Zlatanov
2012-02-06 23:35 ` Lars Ingebrigtsen
2012-02-07 15:33 ` Ted Zlatanov
2012-02-07 20:32 ` Lars Ingebrigtsen
2012-02-07 22:30 ` Ted Zlatanov
2012-02-08 0:37 ` Dave Abrahams
2012-02-08 23:41 ` Lars Ingebrigtsen
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=0C3150B9-16E6-44BB-AF7E-BCB830E771C3@boostpro.com \
--to=dave@boostpro.com \
--cc=ding@gnus.org \
--cc=larsi@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).