https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7197
Remco Rijnders <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from Remco Rijnders <[email protected]> --- Hi Kevin, Thank you for your response. Yes, this does apply to apache-spamd (sorry for being unclear on that in the initial report). I am the packager of SpamAssassin for Mageia Linux and this is a bug I've ran into myself. It actually started with another bug I found: https://bugs.mageia.org/show_bug.cgi?id=13925 I think this is probably a configuration error of apache-spamd as we ship it in combination with an apache installation with virtual hosts enabled. After commenting out all offending values in spamd.conf which prevented Apache from starting, I bumped into this issue. The mod_perl version shipping with Mageia 4 is 2.0.7, and Apache is 2.4.7, though I think (but have not confirmed) that the same issue might be present with other recent versions too. >From the lack of similar bug reports I assume that one or both of the following is true: - This is a strange combination of versions that bring to light this bug; - apache-spamd is hardly used at all. To be frank, I myself am unclear on its use case completely, I just ran into these issues on my own home system. I will test the conn_rec->remote_ip and conn_rec->remote_addr changes on my system, and report my results in this report. I wonder if it is easy to make this change without breaking other cases with a pre 2.4 api in use. -- You are receiving this mail because: You are the assignee for the bug.
