http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5761
------- Additional Comments From [EMAIL PROTECTED] 2007-12-31 19:49 ------- I think I may have found what it is about jails that is causing the problem. I did a bit of Googling about FreeBSD jails and I found this quote at http://www.ascilite.org.au/ajet/ajet21/armitage.html "A jail host does not completely replicate the environment of a regular FreeBSD host. The limitations primarily relate to the jail host's networking and kernel functionality. In FreeBSD 4.x these include: * Networking * A jail host has a single network interface and a single IP address [...] Some applications need fine tuning to handle the fact that localhost (traditionally 127.0.0.1) is silently mapped to the jail host's actual IP address. For example, the ssh daemon within each jail host must be told not to use 'localhost' when setting up X11 forwarding back across inbound ssh connections" And here the same thing is phrased a little differently, explaining how spamc can reach spamd at ip address 127.0.0.1 but have it look like it is coming from 10.0.0.200, and how traceroute 127.0.0.1 seems to work when there really is no 127.0.0.1, from "Maximising Student Exposure to Unix Networking using FreeBSD Virtual Hosts" http://caia.swin.edu.au/reports/030320A/CAIA-TR-030320A.pdf "The localhost address of 127.0.0.1 is silently mapped to the jail's real IP address" In other words, it is not the host name 'localhost' that is silently mapped, as implied by the first quote, but the ip address 127.0.0.1 itself is mapped to the real ip address. So when make test runs spamd and spamc using 127.0.0.1, everything works except that spamd sees the connection coming in from the jail's ip address which is not authorized in the spamd command line (option -A). As far as I can tell the only thing that is affected would be the spamc and apamd tests that are using 127.0.0.1. If you install spamassassin and run spamd using -i 10.0.0.200 -A 10.0.0.200 and run spamc using -d 10.0.0.200 then it should run ok. I don't see a way to get make test to work in that environment. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
