Topic: DKIM-signature (amavis problem)
Hi, Zhang.
You are my last hope.
The problem is when I send mail from outside (connecting to 587 port) using mailclient (thunderbird/android mail/etc) it doesn't get dkim-signature.
My amavis can't set originating flag while passing originating policy. Here it is on 10026 (only for sasl_authenticated on 587 (submission port is configured in postfix master.cf), foreign senders go to 10024 by default):
interface_policy{'10026'} = 'ORIGINATING';
$policy_bank{'ORIGINATING'} = {
originating => 1,
allow_disclaimers => 1,
virus_admin_maps => ["virusalert\@$mydomain"],
spam_admin_maps => ["virusalert\@$mydomain"],
warnbadhsender => 1,
smtpd_discard_ehlo_keywords => ['8BITMIME'],
bypass_banned_checks_maps => [1],
terminate_dsn_on_notify_success => 0,
};
Nevertheless, mails from @mynetworks (e.g. roundcube, or console, or local network) successfully get DKIM-signature without problem. DKIM keys are correct and configured properly.
I had an experiment adding client's ip-address to @mynetworks - and guess what? Mail was successfully signed, of course.
So that is the question: why can't amavis set this originating flag (originating => 1)? (now it says "dkim: not signing mail which is not originating from our site"). The policy 'ORIGINATING' really works, i see it in a maillog.
Thanks for any advice!
==== Required information ====
- iRedMail version (check /etc/iredmail-release): iredadmin 0.6.3
- Linux/BSD distribution name and version: FreeBSD 11
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): Apache
- Manage mail accounts with iRedAdmin-Pro? Nope.
- Related log if you're reporting an issue:
====
----
Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.