Skip to content
Snippets Groups Projects
  1. Jan 24, 2021
    • Rob Swindell's avatar
      Better charset handling of outbound mail · 41847fa7
      Rob Swindell authored
      The default character set for outbound mail is now auto-determined (when not explicitly specified for a message) between UTF-8, ASCII, and CP437. The [mail] DefaultCharset setting (which fell-back to iso-8859-1 if blank) is no longer "a thing".
      
      Also: specify 8-bit content-transfer-encoding for the (potentially UTF-8 or CP-437) plain text portion of a MIME-encoded message with file attachment (7-bit was wrong) and pass down the text sub-type (e.g. could be "html") for inclusion in the mime-part header (don't assume text/plain, but still use that as default).
      
      Also: log an error when failing to delete an attached file (e.g. from data/file/*.out).
      41847fa7
  2. Aug 16, 2020
  3. Jul 20, 2018
    • rswindell's avatar
      Cosmetic/helpful improvements to the log output (a lot of search and replace). · d2068dde
      rswindell authored
      The "official" log line format is (as of right now at least):
      "[socket] [protocol] [user/host-ID] [! if error]message"
      Hopefully I can remember that when I add new log messages.
      
      Also setting the protocol to SMTPS, POP3S, SEND/TLS, when appropriate and
      passing it around to pretty much any function that can log a message.
      Added debug-level log output when the mail sever is sending message body text
      (every 100 lines).
      d2068dde
  4. Mar 04, 2018
    • deuce's avatar
      Mail server support for Opportunistic TLS. · f1910cbe
      deuce authored
      Support STARTTLS in SMTP and STLS in POP3.  This includes the sendmail
      thread.  Clients can now be configured to use STARTTLS with Synchronet
      mail services, and Synchronet will attempt to deliver securely when
      possible (though it will fall back to plain text delivery when necessary.)
      
      This touches a *lot* of mail server stuff, so some instability is not
      unlikely.
      
      Of course, RFC8314 (Jan, 2018) officially recommends implicit TLS on the TLS
      ports now, so support for that should be next.
      f1910cbe
  5. Nov 26, 2017
  6. Feb 02, 2002
  7. Jan 20, 2002
  8. Dec 20, 2001
  9. Sep 19, 2001
  10. Nov 02, 2000
  11. Oct 10, 2000
Loading