1 Topic by jdelisle

  • jdelisle
  • Member
  • Offline
  • Registered: 2015-11-27
  • Posts: 17

Topic: Notify and Vacation emails are not DKIM signed

==== Required information ====
- iRedMail version (check /etc/iredmail-release): 0.9.5-1
- Linux/BSD distribution name and version: CentOS 7.x
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): LDAP
- Web server (Apache or Nginx): Apache
- Manage mail accounts with iRedAdmin-Pro? Yes
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

My users wish to use filters to deliver vacation notifications, and new-email notifications to alternate addresses. 

Emails sent by users are properly signed with DKIM.  Emails auto-generated by the system for vacation and notify filters are not. 

Users configure the notify and vacation filters to send from their email address.

Can I sign those emails?  Should users send from a different address?  The default (when sending address is left blank in the filter) is root@host.domain.tld.  It is rejected due to our domain-level SPF (which is why they use their own emails as the sending address).

Thanks

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,091

Re: Notify and Vacation emails are not DKIM signed

jdelisle wrote:

Emails auto-generated by the system for vacation and notify filters are not. 

Do you have settings like below in Amavisd config file?

$policy_bank{'MYNETS'} = {
    originating => 1,
    enable_dkim_signing => 1,
};

3 Reply by jasongo (edited by jasongo 2019-09-01 22:48:19)

  • jasongo
  • Member
  • Offline
  • Registered: 2019-09-01
  • Posts: 8

Re: Notify and Vacation emails are not DKIM signed

[SOLVED]

As discussed in https://bitbucket.org/zhb/iredmail/issu … e-not-dkim

1. Open /etc/postfix/master.cf, then look for the pickup transport configuration.
2. Add the following code below the pickup transport code

-o content_filter=smtp-amavis:[127.0.0.1]:10026

This should look something like

pickup     unix  n       -       n       60      1       pickup
        -o content_filter=smtp-amavis:[127.0.0.1]:10026

Then restart postfix.

This code was suggested by Zhang. All the thanks to this great man!