Re: Mutt - decoding of QP-escaped headers
On Tue, Feb 10, 2004 at 02:08:48AM +0100, Shot wrote: | Hello. | | Derrick 'dman' Hudson: | | Note that this does not have any spaces in the encoded portion. Edit | the message mentioned above and change the header line to | | Subject: =?iso-8859-2?Q?czu=B3y=20barbarzy=F1ca=20-=20zaproszenie?= | or | Subject: =?iso-8859-2?Q?czu=B3y=20barbarzy=F1ca?= - zaproszenie | | and it will work. | | So that's the trick! Thanks, thanks a lot. I've read somewhere that the | QP works by converting to the equals-and-two-hex-digits notation | everything above ASCII 127 and the equals sign itself, and so must've | missed the part about converting the spaces as well. Thanks again. Basically the Quoted-Printable encoding is =XX where XX is the ASCII hexidecimal representation of the character in $CHARSET. Any and every character in the charset can be encoded, however plain ASCII characters do not need to be encoded, except for newlines if the newline was added to prevent the line length limit from being exceeded. (for all the particulars read the RFC) The issue with spaces is only in headers that allow MIME extensions. The issue is not with the quoted-printable specification but with the MIME specification. | Cheers, | -- Shot (who now wonders whether the question mark, if it happened to | be part of the string in question, should also be represented as =3F | rather than verbatim ?... anywhere I can see the specs?) RFC's 2045-2049 define MIME (Multipurpose Internet Mail Extensions) RFC 2047 is the one that defines the message header extensions. -D -- There are 10 types of people in the world: those who understand binary, and those who do not. www: http://dman13.dyndns.org/~dman/jabber: [EMAIL PROTECTED] signature.asc Description: Digital signature
Mutt - decoding of QP-escaped headers
Hello. My Mutt (binary from unstable) seems not to decode some QP-escaped headers for display, nor QP-escaped attachments names (for display and saving). I'd suspect it's an error on the sender's part, but other mailers do decode such headers properly; an example: Subject: =?iso-8859-2?Q?czu=B3y barbarzy=F1ca - zaproszenie?= MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 8bit the Subject of the above email is displayed verbatim in Mutt and decoded properly by The Bat. Is there a way to make Mutt decode this kind of headers? *My own* emails, coded by Mutt, seem to have headers such as Subject: Re: GLOS =?iso-8859-2?Q?MI=B3ki?= Malzahn Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: 8bit and they work. Emails looking like this Subject: =?iso-8859-2?Q?Fw:_BUD=AFETOWANIE?= MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 8bit work also. I can't pinpoint the problem... Cheers, -- Shot -- .--- http://shot.pl/ --- http://shot.pl/hovercraft/ --- -- - | A distributed system is one in which I cannot get something | done because a machine I've never heard of is down. | -- Leslie Lamport `- --- -- - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Mutt - decoding of QP-escaped headers
On Mon, Feb 09, 2004 at 05:48:50PM +0100, Shot wrote: | My Mutt (binary from unstable) seems not to decode some QP-escaped | headers for display, nor QP-escaped attachments names (for display and | saving). I'd suspect it's an error on the sender's part, but other | mailers do decode such headers properly; an example: | | Subject: =?iso-8859-2?Q?czu=B3y barbarzy=F1ca - zaproszenie?= | MIME-Version: 1.0 | Content-Type: text/plain; charset=iso-8859-2 | Content-Transfer-Encoding: 8bit | | the Subject of the above email is displayed verbatim in Mutt and decoded | properly by The Bat. Is there a way to make Mutt decode this kind of | headers? I guess the only solutions are : 1) Correct the sender's software to encode the data *correctly* 2) Patch mutt to handle this incorrect encoding the way you want it to 3) Put a filter in your delivery chain that re-codes the bad headers correctly | *My own* emails, coded by Mutt, seem to have headers such as | | Subject: Re: GLOS =?iso-8859-2?Q?MI=B3ki?= Malzahn | and they work. Emails looking like this Note that this does not have any spaces in the encoded portion. Edit the message mentioned above and change the header line to Subject: =?iso-8859-2?Q?czu=B3y=20barbarzy=F1ca=20-=20zaproszenie?= or Subject: =?iso-8859-2?Q?czu=B3y=20barbarzy=F1ca?= - zaproszenie and it will work. -D -- Love is not affectionate feeling, but a steady wish for the loved person's ultimate good as far as it can be obtained. --C.S. Lewis www: http://dman13.dyndns.org/~dman/jabber: [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: Mutt - decoding of QP-escaped headers
Hello. Derrick 'dman' Hudson: Note that this does not have any spaces in the encoded portion. Edit the message mentioned above and change the header line to Subject: =?iso-8859-2?Q?czu=B3y=20barbarzy=F1ca=20-=20zaproszenie?= or Subject: =?iso-8859-2?Q?czu=B3y=20barbarzy=F1ca?= - zaproszenie and it will work. So that's the trick! Thanks, thanks a lot. I've read somewhere that the QP works by converting to the equals-and-two-hex-digits notation everything above ASCII 127 and the equals sign itself, and so must've missed the part about converting the spaces as well. Thanks again. Cheers, -- Shot (who now wonders whether the question mark, if it happened to be part of the string in question, should also be represented as =3F rather than verbatim ?... anywhere I can see the specs?) -- .--- http://shot.pl/ --- http://shot.pl/hovercraft/ --- -- - | The outcome of any serious research can only be to | make two questions grow where only one grew before. | -- Thorstein Veblen `- --- -- - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
