Folks, TB handles MIME quite well. It is compatible and compliant.
MIME is a standard for labeling aggregating data objects to email. Does MIME recognize and process the labels? "Process" means that it matches the labels to local system mechanisms. MIME does that just fine. Does MIME recognize and process the aggregations and separations? Yes. So the concerns folks are raising are not with TB's handling of MIME, but rather with some of its user interface choices in presenting MIME "body-parts". As folks on this list might have noticed, user interface choices are often subject to widely different opinions. How should MIME body-parts be presented? The typical choice is at attachments, because that is the construct most familiar to users. Whether one must click on an icon, to invoke an external program to see the attachment, or whether My own opinion about TB's handling of the body-parts is that it does quite well. a) I have to click on the attachment icon -- that is, invoke an external program -- less often than with other mail user agents. b) placing different body-parts in tabbed windows within TB, for "native" access is quite nice. c) TB handles attachments of email far better than other mail user agents, in my limited experience. d/ Sunday, February 2, 2003, 4:38:05 AM, you wrote: MD> Greetings, Batties! :) MD> The Bat! does not seem to handle MIME messages well. Everything comes MD> through as an attachment. Based on this, my conclusion is that The MD> Bat! is not a MIME reader. MD> If that is correct, does anyone know if there are plans afoot to make MD> The Bat! MIME compatible? -- Dave <mailto:[EMAIL PROTECTED]> Brandenburg InternetWorking <http://www.brandenburg.com> t +1.408.246.8253; f +1.408.850.1850 ________________________________________________ Current version is 1.62 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
