https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7500
Bill Cole <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #14 from Bill Cole <[email protected]> --- (In reply to Adrian Pepper from comment #12) > Thanks to everyone for all the help. I am chagrined and appreciate your > patience. > > Everyone has pointed me to appropriate routes of experimentation. > > I actually do not have access to the actual remote spamd server which > exhibits > the problem. [...] > I have experimented in lxc containers on my workstation (3.4.0 and 3.4.1) > and, > together with reading, it's not clear a private subnet is supposed to be > automatically assumed to be trusted for this purpose. Seems clear to me. See 'perldoc Mail::SpamAssassin::Conf' In short: private address space is only automatically used in trusted_networks and internal_networks if both are unset. This is an entirely sane and safe limit on that inference, because there are many RFC1918 networks where only a few subnets (or only a few hosts) should be deemed "trusted" or "internal" [...] > But at this point I can cause "ALL_TRUSTED" to appear or not, on those > experimental containers, more-or-less at will. OK, so this is entirely a local config issue, not in any way a bug. As such, it belongs on the spamassassin-users mailing list, which has a much broader audience with a greater diversity of configurations than you can reach with a bug report. Presumably you can share what you have learned from your sandboxes with your local Lords of Spamd and work out a suitable fix but if not, please take it up on the mailing list where someone else is likely to have an environment involving IPv6 link-local addresses and a remote spamd. -- You are receiving this mail because: You are the assignee for the bug.
