Skip to content

Latest commit

 

History

History
100 lines (75 loc) · 2.96 KB

setup-mta.md

File metadata and controls

100 lines (75 loc) · 2.96 KB
title up prev next
DKIM and ARC: Setup MTA
../dkim-arc.md
setup-keys.md
setup-sympa.md

DKIM and ARC: Setup MTA

  • Steps described in this chapter are required to support ARC. If you are not planning to support it, skip this chapter.

In this chapter, how to set up MTA so that the feature of sender domain validation with SPF, DKIM, DMARC and possiblly ARC are enabled and their results are added as the Authentication-Results: header field (AR).

Note

  • Since Sympa 6.2.71b.1 and later, Sympa is able to verify DKIM signatures and ARC seals in incoming messages by itself and add the results as AR, so it can work anyway even without the settings described in this chapter. However, those settings are strongly recommended to provide sufficient authentication results.

    With Sympa 6.2.70 or earlier, the settings are required.

Requirements

  • Working with the front MTA

    Note that the target of this setting is the front MTA which accepts messages bound for the lists from the Internet. It is the MTA in your mailing list server, if that server is directly connected to the Internet. But otherwise, it is in the different mail server(s).

  • Authentication Service Identifier (authserv-id)

    In this chapter you have to choose (or confirm) the "Authentication Service Identifier" (authserv-id) for your mail system. It will be used later when you configure ARC sealing on Sympa. It is preferable to be the FQDN of the MTA's host name or the mail domain name of the service.

    In this document mx.example.org is used for example.

Instruction by MTAs

Note

  • Some of the software described in below have DKIM signing and/or ARC sealing capability for outgoing messages, but we may not configure them for now: Sympa is responsible for those features.

Tests

  • Confirm that Authentication-Results: header field (AR) with expected authserv-id is added by the MTA towards the top of incoming message, for example:

    Received: (Information added by MTA...)
Authetication-Results: mx.example.org;
        dkim=pass ...;
        spf=pass ...;
        dmarc=none
(The other header fields and body follow...)
...

    Note: To prevent forgery, existing AR with the same authserv-id in incoming messages would like to be removed in advance. If they were not removed, please check the software documentation to find out how to do it.

After you finished setting up MTA, proceed to setup Sympa.