HTML mail (was: PHP contact manager)

[Bill McGonigle]

On Sep 27, 2005, at 09:47, Christopher Schmidt wrote:

> No. The problem is that Greg's client was sending text/plain -- but
> still munging it. The content in the URL that Ben linked to *was* the
> text/plain part of the message: the IPs were still being munged by
> whatever client was sending the content.
>
> Given plain text inputs, mail clients should not munge the text/plain
> content to be more like HTML. Greg's mailer was doing that.

Ah, weird.  I went back and looked at the original message.

It had a text/plain part and an HTML part.  Both parts had <url>'s 
inserted after each IP address in the message content.  I didn't see 
any HTML in the text/plain part.

I just did a little test via GMail - here's what I got, in the 
text/plain part coming in from GMail:

   192.168.0.1 <http://192.168.0.1>
   192.168.0.2 <http://192.168.0.2>

   this is some test

   192.168.0.3 <http://192.168.0.3>
   192.168.0.4 <http://192.168.0.4>

   some more test with 192.168.0.5 <http://192.168.0.5> in the middle of 
it.

The <url>'s were added by gmail.  Turning on 'plain text' mode in GMail 
seems to solve this problem, so this looks like a GMail bug.

> However, I can assure you that it is not Ben's MUA that is causing the
> problem in this situation,

Ben said he was seeing HTML.

> nor is mailman doing the wrong thing.

What's the point of displaying the raw MIME body in the archive's 
_.html_ page?  (not .mbox, not .txt) I could have sworn mailman could 
show you the text/plain part there (some would argue text/html is more 
appropriate) and made other parts available as attachment downloads.  I 
don't want to have to parse MIME in my head if I'm just browsing an 
archive.

-Bill
-----
Bill McGonigle, Owner           Work: 603.448.4440
BFC Computing, LLC              Home: 603.448.1668
bill at bfccomputing.com           Mobile: 603.252.2606
http://www.bfccomputing.com/    Pager: 603.442.1833
Jabber: flowerpt at gmail.com      Text: bill+text at bfccomputing.com
RSS: http://blog.bfccomputing.com/rss