1. Forum
  2. FidoNet
  3. JAMNNTPD

  • From Carlos Navarro@2:341/234.99 to All on Wed Jan 31 19:25:46 2024
    Another issue with Thunderbird...

    If there is no FTN origin address in messages (like in local areas), JamNNTPd renders it in the From field as "<unknown>". But my Thunderbird (latest version) is confused by this and it shows incorrect From's in headers.

    The fix: change it to <unknown@unknown>, so that it is a valid RFC-5322 address.

    Edit nntpserv.c and replace:

    if(fromaddr[0] == 0) strcpy(fromaddr,"unknown");

    by:

    if(fromaddr[0] == 0) strcpy(fromaddr,"unknown@unknown");

    It is curious that SmapiNNTPd doesn't have this issue - it seems that since the beginning it uses <unknown@unknown>, but this wasn't applied to JamNNTPd.

    Carlos

    --- Mozilla Thunderbird
    * Origin: cyberiada-NNTP (2:341/234.99)
  • From Tommi Koivula@2:221/1 to Carlos Navarro on Wed Jan 31 21:00:52 2024
    On 31.01.2024 20:25, Carlos Navarro wrote:

    Another issue with Thunderbird...

    If there is no FTN origin address in messages (like in local areas),
    JamNNTPd renders it in the From field as "<unknown>". But my Thunderbird (latest version) is confused by this and it shows incorrect From's in headers.

    Hmm.. I don't see any problems with "<unknown>" in this Jamnntpd & TB 115.7.0..

    'Tommi

    ---
    * Origin: 2a01:4f9:c011:1ec5:f1d0:2:221:1 (2:221/1.0)
  • From Carlos Navarro@2:341/234.99 to Tommi Koivula on Wed Jan 31 21:48:50 2024
    Hmm.. I don't see any problems with "<unknown>" in this Jamnntpd & TB 115.7.0..

    Same TB version here. It happened to me yesterday with your +localtest+ group in both mxo.fidonet.fi and rbb.fidonet.fi. Now I'm only having that issue with the latter (it seems you have patched mxo...).

    I remembered I had the same issue when I started testing JamNNTPd with JAM bases not created by CrashMail II. I had "<unknown>" in all messages and incorrect From's, unless I enabled "readorigin".

    Maybe my TB profile has something broken... :-?

    Carlos

    --- Mozilla Thunderbird
    * Origin: cyberiada-NNTP (2:341/234.99)
  • From Tommi Koivula@2:221/1 to Carlos Navarro on Thu Feb 1 08:11:26 2024
    On 31.01.2024 22:48, Carlos Navarro wrote:

    Hmm.. I don't see any problems with "<unknown>" in this Jamnntpd & TB 115.7.0..

    Same TB version here. It happened to me yesterday with your +localtest+
    group in both mxo.fidonet.fi and rbb.fidonet.fi. Now I'm only having
    that issue with the latter (it seems you have patched mxo...).

    Actually I did not patch any of my Jamnntpd's. However, I did recompile both yesterday at mxo:

    -rwxr-xr-x 1 root root 109128 Jan 31 08:26 /usr/sbin/smapinntpd*
    -rwxr-xr-x 1 root root 109308 Jan 31 08:27 /usr/sbin/jamnntpd*

    Maybe you connected Smapinntpd at port 1119, not Jamnntpd at port 119. :)

    jamnntpd.log.2:30-Jan-24 21:43:15 (::ffff:88.18.53.54:52514) jamnntpd.log.2:30-Jan-24 21:45:36 (::ffff:88.18.53.54:52536)

    smapinntpd.log.1:31-Jan-24 21:36:44 (::ffff:88.18.53.54:60327) smapinntpd.log.1:31-Jan-24 21:53:10 (::ffff:88.18.53.54:60386) smapinntpd.log.1:31-Jan-24 22:25:28 (::ffff:88.18.53.54:60504)

    I remembered I had the same issue when I started testing JamNNTPd with
    JAM bases not created by CrashMail II. I had "<unknown>" in all messages
    and incorrect From's, unless I enabled "readorigin".

    Yes.

    Maybe my TB profile has something broken... :-?

    Also reloading messages helps after any change.

    'Tommi

    ---
    * Origin: 2a01:4f9:c011:1ec5:f1d0:2:221:1 (2:221/1.0)