Dear Thomas,

@8-May-2011, 23:52 +0700 (08-May 17:52 here) Thomas Fernandez [TOG]
in mid:[email protected] said to Marck:

... <snip>
MP>> When importing messages from a non-email compliant (news)
MP>> format, of course TB has to reformat the messages to be fully
MP>> MIME compliant and should certainly be allowed to do so.

TOG> I think I agree, but this might be out of my league: If TB! is
TOG> supposed to change from UUencode to MIME, why does it work
TOG> reliably with v4 and only for some people (and not for all)
TOG> with v5?

I think TB may have lost the ability to decode inline UUE in the
re-write. It clearly still has a UUE decoder for use in the
importer. As for why some can and some can't see the attachment
correctly in V5, I'd say the lucky few who can are downwind of an
MTA (mail server) that does the conversion en-route. In other
words, news style UUE message body encoding is not acceptable in the
RFC for email in transit, so these servers take it upon themselves
to be "helpful".

-- 
Cheers --  Marck D Pearlstone -- List moderator and fellow end user
TB! v5.0.12.1 on Windows 7 6.1.7601 Service Pack 1
'

Attachment: pgpK2adA1ZMAm.pgp
Description: PGP signature

________________________________________________________
 Current beta is 5.0.12.1 | 'Using TBBETA' information:
http://www.silverstones.com/thebat/TBUDLInfo.html

Reply via email to