1

Topic: Cluebringer and IPv6

==== Required information ====
- iRedMail version: 1.8.1
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Linux/BSD distribution name and version: Centos 6.5
- Related log if you're reporting an issue:
====

I already posted about cluebringer last year. I still use policyd 1.82 but due to the missing IPv6 support for greylisting I tried to switch to cluebringer. After 2 weeks i gave up and switched back to policyd 1.82. Still cluebringer is not integrated into iredadmin pro and the version available in the iredmail repository (2.x) does not implement IPv6 well. With cluebringer 2.1 I get rid of some error messages however greylisting does not work at all (cant tell you how many configurations i tested but not less than 100).

I was happy with iredmail and therefore i spent the money. But now I start to get disappointed. I really would like to see a full IPv6 and cluebringer (the cluebringer UI is horrible) integration as well as easy upgrades (one file to start and not fiddling 2 hours in various places).

There is not much movement in the development lately. When can we expect to get those features mentioned above?

Regards

Michael

2

Re: Cluebringer and IPv6

*) First of all, thank you very much for your purchase of iRedAdmin-Pro.
*) I'm sorry that components shipped in iRedMail don't match your needs, but we don't develop Cluebringer, so it's better to ask Cluebringer developers to support IPv6 or report bugs in its mailing list: http://wiki.policyd.org/support
*) As mentioned in Cluebringer wiki page, IPv6 is supported: http://wiki.policyd.org/policies#specifications
*) The latest iRedAdmin-Pro supports Cluebringer management.

3

Re: Cluebringer and IPv6

Thank you for your quick response.

ZhangHuangbin wrote:

*) As mentioned in Cluebringer wiki page, IPv6 is supported: http://wiki.policyd.org/policies#specifications

As from the wiki: present in r493+ and v2.1.x
But you ship cluebringer 2.0. Have you patched your version?

ZhangHuangbin wrote:

*) The latest iRedAdmin-Pro supports Cluebringer management.

I have the latest version running but greylisting did not work at all. Would you suggest to install a fresh version of iredmail on a blank server? If this is the way to go what will happen if my license is running on two different servers during the migration?

4

Re: Cluebringer and IPv6

mensmaximus wrote:

But you ship cluebringer 2.0. Have you patched your version?

No.
I guess i misunderstood its wiki, it's not very clear which features are in r4xx or v2.1.x.

mensmaximus wrote:

I have the latest version running but greylisting did not work at all.

It's better to report this issue in Cluebringer mailing list to get it fixed.

mensmaximus wrote:

Would you suggest to install a fresh version of iredmail on a blank server?

A new iRedMail server won't give you Cluebringer-2.1.x.

mensmaximus wrote:

If this is the way to go what will happen if my license is running on two different servers during the migration?

It's fine during the migration.

5

Re: Cluebringer and IPv6

I have migrated my server to a fresh install and I can definitely say the provided cluebringer package is not ipv6 aware which causes a lot of trouble if you make use of ipv6. Even sending smtp authenticated emails from ipv6 clients (servers and virtual machines in a datacenter) fails with the postfix configuration from iRedMail.

To avoid this trouble you can modify the postfix main.cf file:

1. Add permit_mynetworks and permit_sasl_authenticated to smtpd_end_of_data_restrictions:
smtpd_end_of_data_restrictions = permit_mynetworks,
                        permit_sasl_authenticated,
                        check_policy_service inet:127.0.0.1:10031

2. Move permit_mynetworks and permit_sasl_authenticated above check_policy_service inet:127.0.0.1:10031 in smtpd_recipient_restrictions:
smtpd_recipient_restrictions = ...
                        permit_mynetworks,
                        permit_sasl_authenticated,
                        check_policy_service inet:127.0.0.1:7777,
                        check_policy_service inet:127.0.0.1:10031,
                        ...

This way authenticated clients and members of mynetworks can bypass cluebringer and the missing ipv6 support does not harm your sending process and fallback mx servers. Even if ipv6 would work it is a good idea to bypass smtp authenticated users from cluebringer unless you want to apply quota checks.

I understand you are not the one to blame for features in third party applications like cluebringer. I myself develop software for widely spread applications and in such a case i would either provide a cluebringer 2.1 package with a note to my customers that this is still an unstable branch although it is rock solid (from what people report). Or i would check for other working solutions like sqlgrey (http://sqlgrey.sourceforge.net/) which i use on my fallback mx servers.

Ignoring ipv6 today can be fatal due to the fact many services (e.g. googlemail) have already switched to ipv6 and new ipv4 blocks (at least in the RIPE region) are not available anymore. It is likely more and more providers will migrate to ipv6. As I already mentioned I like iRedMail and value your work (otherwise I would use the free version for my 10 mailboxes). Don't hide behind the development issues others have ;-) Having no full ipv6 support delays the email transport heavily (the time until the sender will fall back to ipv4).

Regards

Michael

6

Re: Cluebringer and IPv6

Thanks for your sharing, i will think about this.