Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • dailybuild_linux-x64
  • dailybuild_win32
  • sqlite
  • rip_abstraction
  • dailybuild_macos-armv8
  • dd_file_lister_filanem_in_desc_color
  • mode7
  • dd_msg_reader_are_you_there_warning_improvement
  • c23-playing
  • syncterm-1.3
  • syncterm-1.2
  • test-build
  • hide_remote_connection_with_telgate
  • 638-can-t-control-c-during-a-file-search
  • add_body_to_pager_email
  • mingw32-build
  • cryptlib-3.4.7
  • ree/mastermind
  • new_user_dat
  • sbbs320d
  • syncterm-1.6
  • syncterm-1.5
  • syncterm-1.4
  • sbbs320b
  • syncterm-1.3
  • syncterm-1.2
  • syncterm-1.2rc6
  • syncterm-1.2rc5
  • push
  • syncterm-1.2rc4
  • syncterm-1.2rc2
  • syncterm-1.2rc1
  • sbbs319b
  • sbbs318b
  • goodbuild_linux-x64_Sep-01-2020
  • goodbuild_win32_Sep-01-2020
  • goodbuild_linux-x64_Aug-31-2020
  • goodbuild_win32_Aug-31-2020
  • goodbuild_win32_Aug-30-2020
40 results

sbbs

  • Clone with SSH
  • Clone with HTTPS
  • Rob Swindell (on Debian Linux)'s avatar
    Rob Swindell authored
    If an original references header field was supplied with the message, include
    *that* in the header (since it should contain all the IDs of the replied-to
    message thread) rather than just the message's reply_id (a single message
    ID) when sending via NNTP. This maintains more NNTP post integrity when
    sending back out via NNTP.
    
    Not sure why we were storing received "references" in the hdr.references
    returned by parse_news_header(), we don't seem to be using it anywere. Maybe
    copied from 822header.js or mailproc_util.js? Seems like cruft, so remove it.
    
    Also, don't ever send an "In-Reply-To" heder field via NNTP (it's not valid
    /used for NNTP articles, per RFC 5536).
    9bf86ab1
    History
    Name Last commit Last update