• nntpservice shouldn't send blank subject lines

    From Nigel Reed@1:103/705 to GitLab issue in main/sbbs on Mon Feb 1 13:05:50 2021
    open https://gitlab.synchro.net/main/sbbs/-/issues/212

    I believe this breaks nntp protocol, in fact it crashes tin newsreader and may affect other newsreaders. When viewing posts via nntp and the subject is blank it should be filled with something like <no subject> or something to make it not blank.
    --- SBBSecho 3.12-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Mon Feb 1 13:23:28 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/212#note_1437

    A blank subject appears to be RFC-compliant: subject = "Subject:" SP unstructured CRLF"unstructured" would include blank (nothing).The space character (SP) should be there, even when the subject is blank. If it wasn't, I suppose that would be a violation (a bug). Do you have a packet capture or someway to confirm exactly what's being sent by the server?Also, knowing exactly which NNTP command is be sent by the client to trigger this problem may be helpful.
    --- SBBSecho 3.12-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nigel Reed@1:103/705 to GitLab note in main/sbbs on Mon Feb 1 13:26:52 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/212#note_1438

    Actually, I mis-spoke. The bug was caused when trying to follow up to an article with a blank subject line, so sending a blank subject wasn't the main reason, but still. I don't have a dump but I can take one and let you have it but it'll be a bit later.
    --- SBBSecho 3.12-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)