==== Required information ====
- iRedMail version (check /etc/iredmail-release): 0.9.3
- Linux/BSD distribution name and version:
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): Apache
- Manage mail accounts with iRedAdmin-Pro? Yes
- Related log if you're reporting an issue:
====

Hello iRedMail community,

After applying this fix - "Amavisd: Fix incorrect setting which signs DKIM on inbound messages"  with this documentation: http://www.iredmail.org/docs/upgrade.ir … 0.9.3.html

I cannot send emails and I get this error on sending:

Can't connect to socket [127.0.0.1]:10027 using module IO::Socket::INET6:

I use DKIM (and SPF), and looking at amavisd.conf

----------------------------------------------------------------------------------------------------------------
$interface_policy{'10026'} = 'ORIGINATING';

$policy_bank{'ORIGINATING'} = {  # mail supposedly originating from our users
  originating => 1,  # declare that mail was submitted by our smtp client
  allow_disclaimers => 1,  # enables disclaimer insertion if available
  # notify administrator of locally originating malware
  virus_admin_maps => ["postmaster\@$mydomain"],
  spam_admin_maps  => ["postmaster\@$mydomain"],
  warnbadhsender   => 1,
  # forward to a smtpd service providing DKIM signing service
  forward_method => 'smtp:[127.0.0.1]:10027',
  # force MTA conversion to 7-bit (e.g. before DKIM signing)
  smtpd_discard_ehlo_keywords => ['8BITMIME'],
  bypass_banned_checks_maps => [1],  # allow sending any file names and types
  terminate_dsn_on_notify_success => 0,  # don't remove NOTIFY=SUCCESS option
};
----------------------------------------------------------------------------------------------------------------

I've checked that:    forward_method => 'smtp:[127.0.0.1]:10027  was implied if a DKIM was active. Since I use it, the only workaround was to add port 10027 to the line:

$inet_socket_port = [10024, 10026, 10027, 9998];

Now it works perfectly, but is this correct way to do it? Can someone support this workaround please.

Thank you.