MSGID: 2:221/10 65b2aa42
REPLY: 2:341/234.1 65b20419
PID: JamNNTPd/Linux/IPv6 m32 20240124
CHRS: CP437 2
TZUTC: 0200
Carlos Navarro wrote:

CN>  TK> I've been studying this. It's pretty funny that there is no
CN>  TK> problems in my OS/2 Jamnntpd. Yesterday I did more research of
CN>  TK> the code, and in nntpserv.c I commented out the line:
CN>
CN>  TK> //   strcpy(mimefrom,&mimefrom[6]);
CN> [...]
CN>
CN> I think that you have found the source of text corruption problems
CN> in Smapi/JamNNTPd: it may not be safe to use strcpy that way.

Wow..!

Could it be also the reason why there are no text corruption problems in my
OS/2 version of jamnntpd which is compiled with ancient gcc3 ?

Old code, old compiler...? ;)

'Tommi

--- Sylpheed 3.8.0beta1 (GTK+ 2.24.30; i686-pc-mingw32)
 * Origin: 2a01:4f9:c011:1ec5:f1d0:2:221:10 (2:221/10)
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/1 6 242 360 226/30
SEEN-BY: 227/114 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/81
SEEN-BY: 423/120 460/58 256 1124 467/888 633/280 712/848 770/1 5020/400
SEEN-BY: 5054/30
PATH: 221/1 280/464 460/58 229/426