Re: Why rewrite QP-encoded messages when t he receiver cannot take 8BITMIME?
Sam Varshavchik <[email protected]> Sun, 30 Jun 2024 19:41:09 -0400
| Newsgroups | gmane.mail.imap.courier.general |
|---|---|
| Message-ID | <[email protected]> |
Alessandro Vesely writes: > Hm... That code uses the same flag, has8bitchars, for both aspects. A vain > QP-encoding, which could be undone, and an unencoded message, which must be > rewritten if the receiver doesn't take 8bit. Thus, the meaning of that > flag, at the entity level, depends on the entity's declared encoding, > assuming that it's congruous. At the message level, it becomes a riddle. I looked at this again and I agree. I just uploaded build 20240630 that adds a separate indicator just for raw 8 bit content, that feeds into COMCTLFILE_8BIT, that drives reencoding. I can set up a rig to test it, but it'll take some time, perhaps someone can take it for a test drive. _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
signature.asc
(application/pgp-signature, 228 B)
-----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQRupkKLJP96aW75pIOKYPgoojZS4gUCZoHtFQAKCRCKYPgoojZS 4nPOAP4r2J939BgzGGW4MrZURZbdkRoWsb4jFPkcgk1J1xnPhgEAipV5KQcd5Er3 iNtoHT+9Q+FF7aFLJtTbbu5paCfP9wY= =yczn -----END PGP SIGNATURE-----