TID: FMail-lnx64 2.2.1.1
RFC-X-No-Archive: Yes
TZUTC: 0100
CHRS: UTF-8 2
PID: GED+LNX 1.1.5-b20240223
MSGID: 2:280/464 65d94306
REPLY: 1:154/10 65d923b6
Hi Nicholas,

On 2024-02-23 17:01:14, you wrote to you:

 NB>> Hello Carlos,

 NB>> On Mon, 5 Feb 2024 03:36:48 +0100, you wrote:

 CN>>> 27 Jan 2024 20:23:35 +0100 Carlos Navarro -> Tommi Koivula:

 CN>>>> This may be a possible way to fix the corrupted From field in
 CN>>>> headers: in nntpserv.c, instead of just removing this line:

 CN>>>>   strcpy(mimefrom,&mimefrom[6]);

 CN>>>> Replace it by:

 CN>>>>   memmove(mimefrom,mimefrom+6,strlen(mimefrom)-5);

 CN>>>> There could also be issues with the Subject field. The next line:

 CN>>>>   strcpy(mimesubj,&mimesubj[9]);

 CN>>>> could be changed to:

 CN>>>>   memmove(mimesubj,mimesubj+9,strlen(mimesubj)-8);

 CN>>>> As for the corruption in the body of messages posted with
 CN>>>> newsreaders that support flowed text (like Thunderbird), I think
 CN>>>> it may be fixed by changing this:

 CN>>>>   strcpy(line,&line[1]);

 CN>>>> to this:

 CN>>>>   memmove(line,line+1,strlen(line));

 CN>>>> These patches are for both JamNNTPd and SmapiNNTPd.

 NB>> Another reply to the same message, with another utf-8 editor. Does
 NB>> this one look better to you Wilfred and Tommi?

 NB> Another reply using Claws Mail. How about this one?

 NB> Just trying to narrow down if it's Thunderbird itself, or jamnntpd.. so I
 NB> know where to look.

This looks good too!


Bye, Wilfred.

--- FMail-lnx64 2.2.1.1
 * Origin: FMail development HQ (2:280/464)
SEEN-BY: 15/0 90/1 103/705 105/81 106/201 124/5016 128/260 135/225
SEEN-BY: 153/757 7715 154/10 30 203/0 218/700 221/0 226/30 227/114
SEEN-BY: 229/110 112 113 206 307 317 426 428 470 664 700 240/1120
SEEN-BY: 240/5832 266/512 280/464 5003 5555 282/1038 291/111 292/8125
SEEN-BY: 301/1 310/31 320/219 322/757 341/66 234 342/200 396/45 423/120
SEEN-BY: 460/58 256 1124 467/888 633/280 712/848 770/1 5020/400 5054/30
PATH: 280/464 460/58 229/426