Is it possible to sign the MAIL FROM address using OpenDKIM?

Email marketer from SuperUser forum mentions that the MAIL FROM address isn't typically signed directly because it's part of the SMTP transaction and handled differently from message headers.

Email marketer from StackOverflow mentions that the email headers and body are signed, therefore OpenDKIM will not authenticate the return path.

Email marketer from Reddit user u/example responds that standard DKIM implementations don't directly sign the MAIL FROM address. Instead, they focus on the From header. Signing the MAIL FROM might require custom configurations or extensions.

Email marketer from EmailSecurityBlog shares that standard DKIM configurations don't cover the MAIL FROM address due to its nature as part of the SMTP envelope. DMARC alignment relies on the From header's domain, not the MAIL FROM.

Email marketer from MailChannels support notes that OpenDKIM is designed to sign header fields of email messages, and that signing the return-path / MAIL FROM is not usually possible.

Email marketer from StackExchange shares that while OpenDKIM focuses on signing headers, some MTAs or configurations might offer ways to manipulate or include information related to the MAIL FROM address indirectly, but this is not a standard feature of OpenDKIM itself.

Email marketer from AuthSMTP support notes that DKIM will authenticate the headers of the email not the return path, the 'From:' header field will be used as an identifier.

Email marketer from Email On Acid shares that DKIM signatures are applied to the header and body fields of an email, not the MAIL FROM address itself.

Expert from Email Geeks explains that PowerMTA allows you to force set the d=domain for DKIM signing, but OpenDKIM might not have an obvious way to do so. Al suggests trying the _IdentityHeader_ setting in OpenDKIM, but ultimately advises against it due to potential DMARC alignment issues.

Expert from Email Geeks explains that you can't sign the MAIL FROM address directly with OpenDKIM because it's not a header created at the time of sending. It is created at the time of recipient server receipt.

Expert from Email Geeks shares how they configured OpenDKIM to sign every domain with the same key for easier configuration, and links to documentation on how to do so.

Expert from Email Geeks shares that if you set up multiple DKIM keys in OpenDKIM, it uses the key that matches your from address.

Expert from Email Geeks responds if the user means the 'Sender' header, then yes, it can be added to the SignHeaders setting in opendkim.conf.

Expert from Word to the Wise explains that DKIM signs email headers, not the MAIL FROM address, which is part of the SMTP protocol envelope. The Return-Path header reflects the MAIL FROM and is generated by the receiving server, not the sender.

Documentation from RFC 4871, which defines DKIM, explains that DKIM signatures apply to the header and body fields of a message. The MAIL FROM is part of the SMTP envelope, which is separate from the message content that DKIM signs.

Documentation from OpenDKIM.org explains that OpenDKIM primarily signs headers and the body of an email message, and typically does not directly sign the MAIL FROM (Return-Path) address, as this is generated during the SMTP transaction.

Documentation from Trusted Domain Project explains that DKIM is an authentication method that verifies the authenticity of emails and protects the integrity of their content. DKIM authenticates the header and body of emails.

Documentation from Postfix explains that while Postfix can integrate with DKIM signing tools like OpenDKIM, the signing process focuses on message headers rather than the MAIL FROM address itself. Some configuration tweaks might be possible, but direct signing is not standard.

Documentation from dkimproxy explains that dkimproxy signs headers and the body but does not automatically sign the return path. You would require to use the header of the 'From:' field.