Bug 552860 – mail-filter/amavisd-new should have the ipv6 USE flag added to it

• Product: Gentoo Linux
• Status: RESOLVED OBSOLETE

[Description Nathan Zachary (RETIRED) 2015-06-22 15:29:07 UTC]

Recently, I wrote a blog post about amavisd and debugging.  In the comments section:

http://z-issue.com/wp/amavisd-debugging-and-logging-startup-failures/#comments

Toralf Förster brought up a good point that amavis should have the ipv6 USE flag available.  In my reply, I mentioned that disabling the ipv6 USE flag would ship a different amavisd.conf file with the IPV6 sections of the @mynetworks directive removed:

***
@mynetworks = qw( 127.0.0.0/8 [::1] [FE80::]/10 [FEC0::]/10
10.0.0.0/8 172.16.0.0/12 192.168.0.0/16 );
***

Cheers,
Nathan Zachary

[Comment 1 Tomáš Mózes 2016-11-12 06:00:22 UTC]

Yes, I would also vote for ipv6 flag. Today, after a new kernel with IPV6 amavisd-new reported to be running, but the logs were showing errors that INET6 perl libs are needed.

[Comment 2 Michael Orlitzky 2018-11-17 03:25:15 UTC]

I looked into this but I can't reproduce the problem. Specifically, I'm on an ipv4-only host, and the default amavisd-new configuration works for me out-of-the-box. Is this something they fixed in the meantime?

To be sure, I still have ipv6 stuff in my /etc/amavisd.conf:

  @mynetworks = qw( 127.0.0.0/8 [::1] [FE80::]/10 [FEC0::]/10
                  10.0.0.0/8 172.16.0.0/12 192.168.0.0/16 );

but it doesn't appear to hurt anything.

[Comment 3 Michael Orlitzky 2019-07-07 00:42:53 UTC]

Please reopen if I'm mistaken, but since this bug is a few years old and I can't reproduce it, I'm assuming that it was fixed in the meantime.

Digging through the code I see that there is a variable called $have_inet6 (which gets set based on whether or not amavis can load the INET6 module), and that some changes were made to tests involving that variable. But, amavisd is one long perl file so honestly I can't say that there is a smoking gun in the commit log.