| .github/workflows | ||
| man/en | ||
| migrations | ||
| src | ||
| test_samples | ||
| .gitignore | ||
| build.rs | ||
| Cargo.toml | ||
| deny.toml | ||
| LICENSE-APACHE-2.0.txt | ||
| LICENSE-MIT.txt | ||
| README.md | ||
| rustfmt.toml | ||
Filter DKIMout
DKIM filter for OpenSMTPD.
Project status
This is a work in progress, it is not supposed to work yet.
Building and packaging
cargo build --release
Packagers may want to set the VARLIBDIR to a custom value (default is /var/lib):
VARLIBDIR="/usr/local/var/lib" cargo build --release
Frequently Asked Questions
Does this filter signs outgoing emails using DKIM or check the DKIM signature of incoming emails?
It only signs outgoing emails.
Why create another filter for that?
Currently, the options to sign outgoing emails with DKIM are the following:
DKIMproxy is not an OpenSMTPD filter and is therefore more inconvenient to use. Moreover, its development stopped in 2013 and it is therefore dangerous to use.
The two other are fine, however I think they lack a few features, like automatic key rotation and publication of obsolete private keys.
Why would anyone publish private keys, even obsolete ones? Are you crazy?
DKIM's goal is to fight spam, that's all, and for that it only need the keys to be safe when the recipients receives the email. But because it includes a cryptographic proof over the content it is being used for other usages, mostly as a legal proof long after the email has been sent and received. Publishing the obsolete/revoked private keys allows the sender to regain deniability.
Matthew Green wrote an excellent article on this subject: Ok Google: please publish your DKIM secret keys.
Where is the documentation?
The complete documentation can be found in the filter-dkimout (8) man page.
One of my keys has been compromised, how do I revoke it?
Keys are stored in an SQLite format 3 database. You may access it using the sqlite3 CLI tool or any other compatible tool.
The simplest way to revoke a key is to set its not_after field at the current timestamp. A new key will automatically be generated. You may also set the revocation field to a different timestamp in order to publish the key when desired.
UPDATE key_db SET not_after = unixepoch(), revocation = unixepoch('now', '+20 days') WHERE selector = 'dkim-755512d8f51b4da6936d565a1ddbaf17';