From Miraheze Meta, Miraheze's central coordination wiki

Mail was running under The install made use of Postfix and Dovecot along with LDAP modules for authentication. Since 2024, Miraheze no longer uses this for mail. The below documentation is therefore no longer valid and unnecessary and only maintained for historical purposes.

Add new email accounts[edit | edit source]

To add a new email account, an LDAP account must first exist. You can read the documentation for this here.

To enable email on an LDAP account you need to add the following lines to the LDAP entry:

objectClass: postfixUser

maildrop: <cn>

mailacceptinggeneralid: <cn>

Remove email accounts[edit | edit source]

There are two ways to remove an email account:

  1. Delete the LDAP account by using the documentation here,
  2. Remove the 'maildrop' line from the LDAP entry.

Aliases[edit | edit source]

Aliases are now handled inside LDAP. To enable an alias for an individual account, e.g., to redirect johnflewis(at) to john(at) you would add the line mailacceptinggeneralid: johnflewis(at) to the LDAP account 'John'.

However, not all aliases will be for individual people - sometimes there will be groups of people which you might want to manage as a single entity or may be associated with an already existing LDAP group. For this, you can add the following code to an LDAP group;

objectClass: postfixGroup

mailacceptinggeneralid: <alias>

All mail would then be sent to either;

  1. All users who are a member of that group if they have a maildrop attribute, or
  2. You need to specify a maildrop: <email> attribute to have the emails sent to.

There can be multiple maildrop and mailacceptinggeneralid attributes.

Anti-spoofing[edit | edit source]

We use the following standard techniques to combat email address spoofing.

DKIM[edit | edit source]

DKIM is used to sign all emails out-going from mail1. The public key is stored in DNS (in TXT format) and the private key is stored in private git. It can be generated by doing opendkim-genkey -s mail -d

This generates a public and private key pair. The private key should be stored in private git while the public key should be added to the DNS repo to allow the world to verify emails.

SPF[edit | edit source]

SPF records are set to only accept mails from the mail server.

DMARC[edit | edit source]

Our DMARC policy informs to reject if the above techniques fail, incoming mail servers are instructed to not accept any mail that does not pass the requirements.