1

Topic: iRedAPD Policy rejections: not logged in for IPv6 hosts

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

iRedAPD 1.7.0 rejects IPv6 hosts that are listed in MYNETWORKS variable with "Policy rejection not logged in":

$ telnet XXX::166 25
Trying XXX::166...
Connected to XXX::166.
Escape character is '^]'.
220 XXX ESMTP Postfix (Debian/GNU)
HELO YYY
250 YYY
MAIL FROM: aaa@bbb.cc
250 2.1.0 Ok
RCPT TO: aaa@bbb.cc
554 5.7.1 <aaa@bbb.cc>: Recipient address rejected: Policy rejection not logged in
quit
221 2.0.0 Bye
Connection closed by foreign host.

For IPv4 it is working.

$ telnet XXX.166 25
Trying XXX...
Connected to XXX.
Escape character is '^]'.
220 XXX ESMTP Postfix (Debian/GNU)
HELO YYY
250 YYY
MAIL FROM: aaa@bbb.cc
250 2.1.0 Ok
RCPT TO: aaa@bbb.cc
250 2.1.5 Ok
QUIT
221 2.0.0 Bye
Connection closed by foreign host.

Is there a bug in iRedAPD regarding IPv6 hosts/networks?

----

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

2

Re: iRedAPD Policy rejections: not logged in for IPv6 hosts

Please turn on debug mode in iRedAPD, test it again, extract FULL log related to this testing from iRedAPD log file, paste log here.

Reference: http://www.iredmail.org/docs/debug.iredapd.html

3

Re: iRedAPD Policy rejections: not logged in for IPv6 hosts

Sorry, my fault.

I expected iRedAPD to accept IPv6 addresses in postfix style syntax, which is not correct.

4

Re: iRedAPD Policy rejections: not logged in for IPv6 hosts

What's the value in MYNETWORKS setting?

5

Re: iRedAPD Policy rejections: not logged in for IPv6 hosts

It was [2001:240:587::]/64 instead of 2001:240:587::/64

6

Re: iRedAPD Policy rejections: not logged in for IPv6 hosts

Does '2001:240:587::/64' work for you?

7

Re: iRedAPD Policy rejections: not logged in for IPv6 hosts

Yes, it does.