You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DKIM (DomainKeys Identified Mail) signing provides cryptographic authentication for outgoing emails. This feature signs all outgoing emails from configured domains with a private key, allowing recipients to verify email authenticity through DNS records.
4
+
5
+
## Implementation details
6
+
7
+
DKIM signing is implemented using the Rspamd DKIM module. Each domain requires a separate DKIM key pair consisting of a private key (stored in docker-mailserver) and a public key (published in DNS).
8
+
9
+
Rspamd verifies the DNS record for each domain before signing outgoing messages. This ensures that only domains with valid DKIM DNS records will have their emails signed, preventing false signatures.
10
+
11
+
## Configuration steps
12
+
13
+
Configure DKIM through the management interface:
14
+
15
+
1. Access the management interface
16
+
2. Navigate to DKIM in the menu bar
17
+
3. Select the domain for DKIM configuration
18
+
4. Generate the private key
19
+
5. Add the provided DNS TXT record to your domain's DNS
20
+
6. Verify the DNS record through the management interface
21
+
7. Enable DKIM signing for the domain
22
+
23
+
## DNS Record
24
+
25
+
The management interface provides a DNS TXT record that must be added to your domain's DNS configuration. The record contains the public key used for DKIM verification by receiving mail servers.
26
+
27
+
## Operation
28
+
29
+
Once enabled, all outgoing emails from the configured domain are automatically signed with the DKIM private key. Receiving mail servers can verify the signature using the public key published in DNS, confirming the email's authenticity and integrity.
Local address extension allows multiple unique email addresses to be delivered to a single mailbox without additional configuration. This feature implements RFC 5233 subaddressing and is commonly known as plus-addressing.
4
+
5
+
## Implementation
6
+
7
+
The feature appends a configurable delimiter followed by any string to the base email address. All emails sent to extended addresses are delivered to the original mailbox. The default delimiter is `-` (dash).
Configure the delimiter using the `RECIPIENT_DELIMITER` environment variable:
28
+
29
+
```yaml
30
+
environment:
31
+
- RECIPIENT_DELIMITER=+
32
+
```
33
+
34
+
This changes the delimiter from `-` to `+`, allowing addresses like `[email protected]`.
35
+
36
+
## Sieve Integration
37
+
38
+
Extended addresses can be used in Sieve filtering rules for automated email processing. Sieve rules can sort emails into folders, apply actions, or forward based on the extension used.
0 commit comments