Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 2569  |
|  Carlos Navarro to Nicholas Boel  |
|  format=flowed  |
|  28 Apr 24 13:30:19  |
 TID: FMail-W64 2.3.2.2-B20240419 TZUTC: 0200 CHRS: UTF-8 4 MSGID: 2:341/234.1 662e337e REPLY: 1:154/10 66285260 23 Apr 2024 19:29, you wrote to me: NB>>> * Note no "format=flowed" on there. This seems to be the same NB>>> results found in Tommi's Wendzelnntp or whatever it was. CN>> As expected. SBBS's NNTP server does not use format=flowed. NB> So does that mean the NNTP server Tommi is using also does not use NB> f=f? NB> I've also been looking through as many FAQs as I can find on inn NB> (InterNetNews) which is/was/might+still+be a very popular news server, NB> and don't see much of anything mentioned about format=flowed at all. As far as I understand, standard NNTP servers do not generate the Content-type header (where "format=flowed" is specified), but it's stored in the messages themselves. If a client posted a message with f=f, that message will have it when received by any newsreader. Smapi/JamNNTPd and Synchronet insert the Content-type header when exporting from their JAM/SMB/... messagebase and sending to the client. The former adds the f=f part there. NB> Seems to me f=f is/was more of an email thing. Mainly, I suppose, but it's used by TB and Seamonkey for both mail and news. Carlos --- GoldED+/W32-MSVC 1.1.5-b20180707 * Origin: cyberiada (2:341/234.1) SEEN-BY: 15/0 90/1 103/705 105/81 106/201 124/5016 128/260 135/220 SEEN-BY: 135/225 153/757 7715 154/10 30 203/0 218/700 221/0 6 226/30 SEEN-BY: 227/114 229/110 112 113 206 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: 341/234 280/464 460/58 229/426 |
[ << oldest | < older | list | newer > | newest >> ]