Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 2142  |
|  Tommi Koivula to Nil Alexandrov  |
|  jamnntpd issues, smapinntpd  |
|  01 Jan 20 20:30:26  |
 MSGID: 2:221/0 5e0ce53c REPLY: 2:5015/46 5e0bad3d PID: SmapiNNTPd/Linux-Pi/IPv6 1.3 20191227 EID: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32) CHRS: IBMPC 2 TZUTC: 0200 TID: hpt/lnx 1.9.0-cur 2019-12-05 Nil Alexandrov - All <0@46.5015.2> wrote: NAA> Hi Folks, NAA> NAA> Here's my recent experience w/ jamnntpd. NAA> Cloned from https://github.com/ftnapps/smapinntpd and built for Ubuntu 14.04.6. Ubuntu 64bit? NAA> Second issue was w/ posting an article - it will break the JAM database! This is a known JAM API problem in 64bit systems. :( NAA> * Jamnntpd will not be able to read back posted message (the message NAA> counter remains the same). NAA> * GoldED+/LNX 1.1.5 will show a new completely empty message w/o headers NAA> and body NAA> * Husky HPT 1.9 will core dump while dealing w/ that JAM file (which is NAA> actually bad). Yes. I have seen it happening too. My experience with Jamnntpd is that it compiles and works quite fine in my 32bit systems: OS/2, Cygwin/32 and Ubuntu 32bit in Raspberry Pi2. 'Tommi --- * Origin: smapinntp://rpi.rbb.bbs.fi (2:221/0) SEEN-BY: 1/123 90/1 154/10 203/0 221/1 6 242 360 227/114 229/426 452 SEEN-BY: 229/1014 240/1120 5832 249/206 317 280/464 5003 5555 310/31 SEEN-BY: 317/3 322/757 342/200 423/81 PATH: 221/1 280/464 229/426 |
[ << oldest | < older | list | newer > | newest >> ]