Amavis issue with IPv6

[Dionyssios Edwards]

Having an issue with Amavis starting when I set “$inet_socket_bind = undef;” in an attempt to get Amavis to listen to all interfaces instead of just localhost.

The logs show the following errors:

2025-04-13T18:29:06.865009-04:00 873b46bd964d amavis[492]: Net::Server: Resolved [*]:10021 to [::]:10021, IPv6

2025-04-13T18:29:06.865038-04:00 873b46bd964d amavis[492]: Net::Server: Not including resolved host [0.0.0.0] IPv4 because it will be handled by [::] IPv6

2025-04-13T18:29:06.865189-04:00 873b46bd964d amavis[492]: Net::Server: Resolved [*]:10030 to [::]:10030, IPv6

2025-04-13T18:29:06.865209-04:00 873b46bd964d amavis[492]: Net::Server: Not including resolved host [0.0.0.0] IPv4 because it will be handled by [::] IPv6

2025-04-13T18:29:06.867601-04:00 873b46bd964d amavis[492]: Net::Server: Binding to UNIX socket file "/var/lib/amavis/amavisd.sock"

2025-04-13T18:29:06.867787-04:00 873b46bd964d amavis[492]: Net::Server: Binding to TCP port 10021 on host :: with IPv6

2025-04-13T18:29:06.868000-04:00 873b46bd964d amavis[492]: (!)Net::Server: 2025/04/13-22:29:06 Can't connect to TCP port 10021 on :: [Invalid argument]\n  at line 66 in file /usr/share/perl5/Net/Server/Proto/TCP.pm

2025-04-13T18:29:06.868050-04:00 873b46bd964d amavis[492]: sd_notify (no socket): STOPPING=1\nSTATUS=Server rundown, notifying child processes.

2025-04-13T18:29:06.868076-04:00 873b46bd964d amavis[492]: Net::Server: 2025/04/13-22:29:06 Server closing!

There seems to be an issue trying to bind to IPv6 [::] which is the equivalent of Ipv4 0.0.0.0.

I guess the question is why does Amavis insist on using IPv6 instead of IPv4. I don’t have any IPv6 addresses in /etc/hosts. Additionally, how can I go about resolving this.

I would appreciate some help on this.








-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.amavis.org/pipermail/amavis-users/attachments/20250414/2873c799/attachment.htm>