Subj : Subject turned into an odd mess
To   : Michael =?ISO-8859-1?Q?B=E4uerle?=
From : Tommi Koivula
Date : Thu Jan 06 2022 08:45:32

On 02.01.2022 19:05, Michael Bäuerle wrote:

>
> Headers from original message:
> |
> | Message-ID: <Fkf4lZYJI8B@openxp.uk>
> | User-Agent: OpenXP/5.0.51 (Linux) (x86_64)
> | Subject: Re: OpenXP 5.0 =?ISO-8859-1?Q?f=FCr?= Windows
> |  =?ISO-8859-1?Q?verf=FCgbar?=
>
> Headers from first message with broken subject:
> |
> | Message-ID: <4157791155@f1.n221.z2.fidonet.fi>
> | User-Agent: VSoup v1.2.9.48Beta [OS/2]
> | Subject: OpenXP 5.0 =?ISO-8859-1?Q?f=FCr?= Windows =?ISO-8859-1?Q?verf=FCgba
>
> The trailing part "r?=" of the Subject is missing and breaks the
> second encoded-word.
>
> The length limit according to RFC 2047 was hit at 76 characters:
> <https://datatracker.ietf.org/doc/html/rfc2047#section-2>
> |
> | While there is no limit to the length of a multiple-line header
> | field, each line of a header field that contains one or more
> | 'encoded-word's is limited to 76 characters.
>
> Looks like the root cause of the problem was the removed/missing
> folding of the Subject header field.
>
> ---
>   * Origin: rbb.fidonet.fi - the fidonet nntp junction (2:221/10)

Sadly the fido gateway 'Soupgate' does not support chrs conversion in subject line. Some fido readers work ok but cutting the subject may cause that kind of a result. :(

'Tommi

--- 
 * Origin: nntp://news.fidonet.fi (2:221/6.0)

.