Description of problem: Attempting to relay via localhost will fail if connecting via IPv6 localhost but works if connecting via IPv4 localhost. This is because /etc/exim.conf contains the line: hostlist relay_from_hosts = 127.0.0.1 This line should read: hostlist relay_from_hosts = localhost Since /etc/hosts contains both the IPv4 and IPv6 definitions of locahost. You could also use: hostlist relay_from_hosts = <; 127.0.0.1; ::1 I had come across this and it has just been raised on the exim.users mail list -- where I promised that I would raise a bug here.
This actually comes directly from upstream. https://github.com/Exim/exim/blob/master/src/src/configure.default#L59 Mark
After submitting the above I continued to browse the default exim.conf and I notice that the following should also be fixed: Line 96 and following has an IPv4 only discussion: # hostlist relay_from_hosts = 127.0.0.1 : 192.168.0.0/16 Line 635, the dnslookup router is IPv4 only: dnslookup: driver = dnslookup domains = ! +local_domains transport = remote_smtp ignore_target_hosts = 0.0.0.0 : 127.0.0.0/8 no_more You should replace the 5th line by: ignore_target_hosts = 0.0.0.0 : localhost I don't know what the IPv6 representation of 0.0.0.0 is.
Thanks for pointing that out Mark. I have made a change on github. I do not know how long that will take to be put into the default config (I have not used github before). I will also raise this as a bug onto exim's bugzilla.
This was raised on the exim bugs list some time ago: http://bugs.exim.org/show_bug.cgi?id=880 I have taken ownership of the bug.
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version. Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version. Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version, you are encouraged to change the 'version' to a later version prior this bug is closed as described in the policy above.
EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of EPEL please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.