On Tue, 29 Apr 2008 10:31:45 -0500, G. A. Edgar wrote:
[re "Open in browser"]
> Doesn't work when the message is split in two, as in this case, right?
A message "split in two" may not have been sent (or delivered) correctly,
which if so is the real problem at hand, so although working hard
to personally correct badly sent messages may be worthwhile
for the sake of already-sent messages,
the avoidance of future messages sent the same way
may also be a useful pursuit.
Even if optional "message chunking" (RFC3030)
were employed between SMTP servers,
the complete message should have been re-assembled into one whole
before POP downloading -- "chunking" is also so uncommon that
even our mail screening vendor recommends refusing to handle it,
because one of its most popular real-world applications turns out
to be the attempt to impede virus detection in transit;
no personal email programs that I'm aware of
can even handle sending this way.
In any case, it should have nothing to do with x-html content,
nor "Eudora showing its age" (just like Thunderbird?)
which the OP seems to have presumed, because parsing
of message parts (and end-of-message boundaries)
has nothing to do with the content of those parts,
since these are different "layers" of the entire process
of first trans****ting whole messages (potentially
containing MIME parts), then subsequently displaying
the parts only when individual messages are opened
(and finally using "Open in browser" to send it all
to a fully-capable browser for display,
instead of the internal, intentionally limited display pakage).
By the way, how large is each part of a "split" message?
--
|
