Oct 31, 2019 Configure SPF and DKIM With Postfix on Debian 8 Updated Thursday, October 31, 2019 by Linode Contributed by Todd Knarr Try this guide out by signing up for a Linode account with a $20 credit. At Oracle Dyn Email Delivery, we love proper email authentication and like it even better when our senders update their DKIM key length from the standard 1024 or even 728. For those not technically inclined, moving to a 2048 bit key length is seen favorably by mailbox providers like Gmail.

1. Generate 1024 Bit Key Opendkim Windows 7
2. Generate 1024 Bit Key Opendkim Download

Translation(s): English - Русский

How To Configure and Validate DKIM Records on Zimbra. Opendkim-testkey: checking key ‘dcarter.domainkey.domain.cl’. You can use -b options when generate.b 1024 to generate become 1024 bit 2. You can change value 2048 into 1024 on zmdkimkeyutil file. Generate a DKIM Core Key. Domain name: Enter the domain you'd like to generate keys for, for example dkimcore.org and hit the button. Security notes. This online wizard is fine for generating keys for testing and evaluation. If you decide to use DKIM Core in production, though, you might want to. Generate the keys: sudo opendkim-genkey -s mail -d example.com -s specifies the selector and -d the domain, this command will create two files, mail.private is our private key and mail.txt contains the public key. Change the owner of the private key to opendkim: sudo chown opendkim:opendkim mail.private Add the public key to the domain’s DNS. If your DNS provider doesn't support long keys (a problem I encountered about a year ago with one provider), you can create a shorter key by adding the parameter -b 1024 to your opendkim-genkey command. Do not create shorter keys than 1024 bits.

The opendkim package contains a full-featured DKIM milter implementation suitable for use with MTAs (mail servers) such as Postfix.

DomainKeys Identified Mail (DKIM) combines several existing antiphishing and antispam methods to improve the quality of the classification and identification of legitimate e-mail. Instead of the traditional IP-address, to determine the message sender DKIM adds a digital signature associated with the domain name of the organization.

Jump to #Quickstart for an overview and minimal setup, and refer to #Configuration for the complete picture.

Contents

1. Configuration

The quickstart instructions in this section describe setting up a minimal, but functional installation of opendkim for signing and verifying, integrated with Postfix. This is the five-minute version of opendkim configuration for the impatient. For a fuller discussion of the setup options available, please refer to the subsequent sections.

Let’s go! First, install opendkim:

Next, generate the private key for your domain and selector pair:

Now, edit /etc/opendkim.conf. Four parameters need to be adapted: the domain/selector/key file triple, and the socket. For the socket, the easiest option is to use a TCP socket listening on a local port.

That’s it for opendkim. Restart the service with sudo systemctl restart opendkim.

The final step is integrating the opendkim service with Postfix. Edit /etc/postfix/main.cf to connect the two:

And finally reload the Postfix configuration with sudo systemctl reload postfix.

Done! Your mail is now being signed and verified. Don’t forget to publish your public key as a TXT record in DNS at 2020._domainkey.yourdomain.com. The generated file /etc/dkimkeys/2020.txt contains that record for your convenience.

The following sections discuss opendkim configuration options in more detail. See the manual page opendkim.conf(5)for reference.

These sections assume that you have installed the opendkim and opendkim-tools packages.

The opendkim configuration file can be found at /etc/opendkim.conf. All configuration parameters should be set in this file. Windows xp cd key generator.

This needs to be stated, because there is a lot of older, now misleading information on this online. Previously, one would edit the default settings at /etc/default/opendkim, and then execute /lib/opendkim/opendkim.service.generate to generate systemd override files at /etc/systemd/system/opendkim.service.d/override.conf and /etc/tmpfiles.d/opendkim.conf. While this is still possible, it is now recommended to adjust the settings directly in /etc/opendkim.conf.

Generating keys

For key generation, the opendkim-tools package provides the opendkim-genkey program. This program generates a private key named <selector>.private in the specified directory, as well as a public key ready for installation in a DNS zone file. An example invocation:

You will want to tweak some of these options. For example, you might not want to forbid subdomain signing with --nosubdomains, or you might want to restrict usage to email with --restrict. In Debian, the cryptographic options use reasonably strong defaults, so it is usually not necessary to specify --bits (default: 2048) and --hash-algorithms (default: SHA-256).

In Debian, the directory /etc/dkimkeys serves as the canonical key storage location, and is created by the opendkim package on installation. The owner is set to opendkim by default.

Notice how we execute opendkim-genkey as user opendkim. That way, opendkim-genkey produces key files with the correct, restricted permissions, owned by opendkim.

It is also possible to restrict key ownership further to user root by invoking opendkim-genkey directly as root:

However, while this does work, opendkim will not be able to reload keys during operation: during startup, the key file may be read into memory as root, but subsequently, after root privileges are dropped, the keys will be accessed as user opendkim. This is discussed in the following section.

User and privileges

By default, the opendkim service runs as user opendkim. This is because the default configuration contains a setting for parameter UserID in /etc/opendkim.conf:

This setting instructs opendkim to become user opendkim. So, more accurately, what happens is that the opendkim service is started as root, does everything it needs to do as root – such as reading private keys and writing the pid file –, and then, before beginning normal operation, it drops the root privileges and becomes user opendkim. This is a standard, secure procedure that should be appropriate for most users.

An alternative setup is possible where the opendkim service runs as an unprivileged user from the very start, and this is described in the following section.

Running as an unprivileged user

For setups that have additional security requirements, it is possible to run the opendkim service as user opendkim from the very beginning, with no root privileges involved at any stage. Please note that most users do not need this.

Create a systemd override file at /etc/systemd/system/opendkim.service.d/override.conf (you may need to create the directory too), with the following contents:

The UserID opendkim setting in /etc/opendkim.conf can now be removed, as no privilege dropping is necessary. Reload the systemd configuration with sudo systemctl daemon-reload, and restart the opendkim service. It now runs as an unprivileged user.

Make sure that the unprivileged user can actually read the keys in /etc/dkimkeys (see above), and write the pid file. (Since both /etc/dkimkeys and the runtime directory /run/opendkim come owned by user/group opendkim, this should work without further adjustment.)

Key selection

For a single-domain DKIM setup with only a single key, the configuration shown in #Quickstart, using the three parameters Domain, Selector, KeyFile is enough. However, opendkim configuration supports multiple domains and keys, read from a variety of sources (files, SQL databases, Lua scripts, …). KeyTable and SigningTable are the configuration parameters that enable this.

Setup the /etc/opendkim.conf:

Now in the file /etc/dkimkeys/keytable, put information about the private key:

In the file /etc/dkimkeys/signingtable, specify which key will sign a domain:

In the file /etc/dkimkeys/trustedhosts, specify which hosts will have messages signed. If needed, include localhost as it is not implicit:

Socket

The opendkim service has to provide a communication channel for the MTA (Postfix). A TCP socket listening on a port only accessible locally is a reasonable choice that is also easy to set up.

Sockets can be of IPv4 or IPv6 type, and can listen on all interfaces or on a specific interface only.

Some prefer setting up a UNIX domain socket instead, as a faster and more secure channel (though opinion on this point varies). This requires a little more configuration work, and is described in the following section.

Using a UNIX domain socket

The UNIX domain socket file must be accessible to the MTA. In Debian, Postfix runs in a chroot jail in /var/spool/postfix by default, so the socket must be below that path.

Postfix does not prescribe a standard location for UNIX sockets in its chroot. You can mimic the /run directory hierarchy, and place the socket below /var/spool/postfix/run/opendkim, or you can simply claim a top-level directory like /var/spool/postfix/opendkim. Here we go with the latter.

First, create the directory, owned by opendkim and world-inaccessible:

Then, configure the socket in /etc/opendkim.conf:

Generate 1024 Bit Key Opendkim Windows 7

Next, add user postfix to group opendkim. Postfix then relies on the group permissions to actually access the socket:

Finally, adjust the Postfix configuration in /etc/postfix/main.cf to use the desired socket path:

Don’t forget to restart opendkim and postfix to apply the settings.

DNS resolution

In Debian, opendkim is compiled with libunbound, a DNSSEC-capable asynchronous resolver library. It is important to be aware of this, because it means opendkim does DNS queries for DKIM keys independently, that is, it does not go through any local resolver and does not take into account configuration at /etc/resolv.conf.

The default opendkim configuration ships with a valid trust anchor setting, TrustAnchorFile /usr/share/dns/root.key, thus letting opendkim do DNSSEC queries out-of-the-box.

Advanced users should be aware of two additional configuration parameters.

The Nameservers parameter can be used to override the name servers that libunbound uses. For example, you may already have an Unbound resolver running locally (a relatively typical setup in a mail server). In that case, a setting like the following instructs opendkim to send DNS queries through that resolver:

The ResolverConfiguration parameter can be used to pass an Unbound configuration file (unbound.conf(5)) to libunbound. Using this, more sophisticated customization regarding DNS resolution in opendkim is possible.

The Debian unbound package installs a default configuration file at /etc/unbound/unbound.conf. Do not attempt to use this file unchanged with ResolverConfiguration! opendkim will just quietly shut down.

The reason for the incompatibility is that the shipped unbound.conf includes an auto-trust-anchor-file setting, for which opendkim does not have the necessary permissions. Unfortunately, libunbound is rather fragile in this area. Prepare your own unbound.conf for opendkim and test carefully.

Postfix integration

The opendkim service functions as a milter, that is, a plugin software hooked into the SMTP processing of the Postfix MTA. To enable a milter, it is enough to tell Postfix on which socket the milter application is listening. Example /etc/postfix/main.cf:

With opendkim, two additional milter configuration parameters in /etc/postfix/main.cf are useful.

The milter_default_action parameter determines what to do when a milter fails, for example, when it does not respond after a crash. In order to avoid losing mail, it is best to set this to accept:

Generate 1024 Bit Key Opendkim Download

Postfix does not pass internally-generated messages such as bounce messages to opendkim, so by default bounces are not DKIM-signed. This can be a problem if you also use a strict DMARC policy, because it may cause your unsigned bounce messages themselves to get rejected. The internal_mail_filter_classes parameter can be used to pass bounces through the milters as well:

Further details of milter usage in Postfix can be found in its MILTER_README.

Try to send a mail. If you see in /var/log/mail.log something like

then that probably means that you did not create the directory for the socket (see above) or you gave it the wrong permissions. Double-check!

If you see

then that means postfix could not read the socket. Did you put postfix in group opendkim? Are the permissions on /var/spool/postfix/opendkim/opendkim.sock correct?

If everything is correct, that does not mean your configuration of DKIM is complete: you must configure the DNS.

Add a TXT record for your example.com domain

You can test your installation with opendkim-testkey:

• http://www.opendkim.org/ : Official website

• opendkim.conf(5): Configuration parameters manual page

• opendkim-lua(3): Lua scripting interface manual page

CategoryNetwork