On 04 August 2018 at 10:25 Lüko Willms wrote and made these points LW> please excuse me to break in again, but here a correction is called for:
... <snip> >> Because it's not the message. The only way of using HTML for email is >> to make it an attachment. It's how email works. LW> This is wrong. This is not how Internet email works today. ... <snip> LW> A single body part can be text, binary, or application LW> specific, and if it is text, the content-type would be mostly text/html or text/plain.[1] ... <snip> LW> Marck Pearlstone is wrong writing "The only way of using HTML LW> for email is to make it an attachment." Thanks for this correction. You are absolutely right. LW> Look at Ira's message which Marck Pearlstone is replying to, identified by these headers: ... <snip> >> Content-Type: text/html; charset=utf-8 >> Content-Transfer-Encoding: quoted-printable LW> and this single body part was certainly not an "attachment". LW> There was no other body part in it. LW> But the mailing list processor Mailman added another body part with the headers ... <snip> LW> and only content being the footer for this mailing list ... <snip> In which case, I can see and sympathise with the point Ira made that an email consisting only of an HTML part shouldn't be showing as an attachment. I wouldn't like to see TB functionality compromised by smoothing out that interface element at the expense of the ability to save message parts externally in the correct content-type file type. Perhaps a switchable option to "Attachments: Show all parts / Show only real attachments" would provide the flexibility for power and standard users alike. -- Cheers -- Marck D Pearlstone -- List moderator and fellow end user TB! v8.5.8.2 (ALPHA) on Windows 10.0.17134
pgpmsCNwrLVhM.pgp
Description: PGP signature
________________________________________________________ Current beta is 8.5.8.2 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
