1. Forum
  2. FidoNet
  3. SYNC SYSOPS

  • DKIM Support

    From Michael J. Ryan@1:103/705 to GitLab note in main/sbbs on Thu Feb 18 10:43:35 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/215#note_1627

    I would make one suggestion... if you're using synchro.net dyndns, it would be nice if the public key could be sent as part of the update, so that synchro.net dns can add it directly. Maybe even add an SPF record with `SPF A ~ALL` or similar. Would do a lot for being able to better support bbses using that system.As to why, similar to why integrate letsencrypt, when there are/were existing solutions to generate keys and reverse-proxy even over adding https for example. To make it easier for those sysops using synchronet to integrate the security measures.Also, many of the major mail providers are less likely to send DKIM signed messages to the spam bucket, or outright deny the email altogether. I'm using an outbound relay for this myself, but can see the reasoning behind having the option in the box.
    --- SBBSecho 3.12-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Fernando Toledo@1:103/705 to GitLab note in main/sbbs on Mon Mar 9 06:13:52 2026
    https://gitlab.synchro.net/main/sbbs/-/issues/215#note_8519

    I agree with @nelgin; nowadays, SPF+DKIM is a kind of minimum standard for email servers.

    I think SBBs should support it. However, I believe it shouldn't be necessary for SBBs to handle it directly; it could be used, for example, through OpenDKIM. A possible alternative solution is to relay via Postfix and then sign with OpenDKIM.
    --- SBBSecho 3.37-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 Mar 9 07:52:13 2026
    https://gitlab.synchro.net/main/sbbs/-/issues/215#note_8520

    There is no point in having a mail server if you're just going to relay it off. I did ponder that but I'd rather fix it at the core.

    Yes, OpenDKIM long with OpenDMARC would be an ideal solution. It's not difficult to setup though it does get away from the "all in one" type of solution. I have no problem running them separately.
    --- SBBSecho 3.37-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From deon@1:103/705 to Nigel Reed on Tue Mar 10 08:55:09 2026
    Re: DKIM Support
    By: Nigel Reed to GitLab note in main/sbbs on Mon Mar 09 2026 07:52 am

    Howdy,

    There is no point in having a mail server if you're just going to relay it off. I did ponder that but I'd rather fix it at the core.

    Its not uncommon that an inbound mail server frontends incoming mail before sending it to backend systems. That system can be the "last hop" in your network before going out to the world.

    I've been running mail that way for a long time, and Sync's mail is a part of that.

    IE: The inbound server rejects mail (spam) before getting to Sync, and Sync's mail goes out to it and signs it before it is released to the internet.


    ...����

    ---
    � Synchronet � AnsiTEX bringing back videotex but with ANSI
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Mon Mar 9 17:39:25 2026
    https://gitlab.synchro.net/main/sbbs/-/issues/215#note_8528

    This issue should be split into 2 separate feature requests:
    1. incoming DKIM validation
    2. outgoing DKIM support (signing?)

    These are separate efforts with separate justifications/rationale. We might do one and not the other.
    --- SBBSecho 3.37-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 Mar 9 17:40:21 2026
    https://gitlab.synchro.net/main/sbbs/-/issues/215#note_8529

    All this said, mail.synchro.net does not use/support DKIM and I've yet to have any outbound mail rejected because of that. Are we sure this is a problem?
    --- SBBSecho 3.37-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)