From: Robert Raschke <rrplan9@tombob.com>
To: 9fans@cse.psu.edu
Subject: [9fans] multipart/alternative encoded emails?
Date: Sat, 2 Apr 2005 13:11:45 +0100 [thread overview]
Message-ID: <da230de82754298a2df9e20fd6e06e47@tombob.com> (raw)
Hi,
before I embark on learning a lot about upas/fs (which, I guess, would
arguably be a good thing to do regardless) I thought I'd ask if anyone
has had any thoughts on how to handle multipart/alternative encoded
emails?
I have been receiving more and more emails of the following ilk:
> From: somebody
> To: me
> Subject: Your Newsletter 31/05/2005
> Date: Thu, 31 Mar 2005 14:10:02 +0100
> MIME-Version: 1.0
> Content-Type: multipart/alternative;
> boundary="----=_NextPart_09891202_825CBB53C42C97F2"
>
> ------=_NextPart_09891202_825CBB53C42C97F2
> Content-Type: text/plain; charset="us-ascii"
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
>
>
>
> ------=_NextPart_09891202_825CBB53C42C97F2
> Content-Type: text/html; charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
> Content-Disposition: inline
>
> [lotsa html]
That's an empty first part!
I have attempted to alert the senders to the wrongness of their
approach, but never got any replies. So, I am trying to figure out
how alternative content emails could fit into upas/fs.
(Hmm, a cursory glance at the upas/fs sources would lead me to believe
that I should see the alternatives just like regular multipart/mixed
attachments. Strange.)
Thanks for any pointers,
Robby
reply other threads:[~2005-04-02 12:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=da230de82754298a2df9e20fd6e06e47@tombob.com \
--to=rrplan9@tombob.com \
--cc=9fans@cse.psu.edu \
/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).