--On Wednesday, October 23, 2013 1:35 AM +0200 Karsten Bräckelmann
<guent...@rudersport.de> wrote:
^^^^^^^^^^^ ^^^^^^^^^
204.14.232.64/28 204.14.234.64/28 202.129.242.65/32 96.43.144.64/32
96.43.144.65/32 96.43.148.64/32 96.43.148.65/32 182.50.78.64/28
208.91.2.22/31
Excuse me for being blunt, but it appears you didn't lint check in quite
a while. That is absolutely borked.
$ spamassassin --lint --cf="trusted_networks 127.0.0.0/8"
warn: netset: cannot include 127.0.0.0/8 as it has already been included
M::SA::Conf docs, section Network Test Options, option trusted_networks
states: "Note: 127/8 and ::1 are always included in trusted_networks,
regardless of your config."
$ spamassassin --lint --cf="trusted_networks [::1]/128"
warn: netset: illegal network address given: '[::1]/128'
Included by default as well. And even bad syntax.
However, it also does not cause harm to include the local addresses.
Whether or not the syntax is bad sounds like an argument you can take to
the postfix authors. Clearly their tool to generate it feels it is valid.
The values themselves are generated by postfix, via postconf -d mynetworks
And that last address range [fe80::%eth0]/64 on the first line is just
weird -- what's supposed to substitute that ethernet interface
placeholder?
Generally it just gets dropped:
Oct 22 12:09:24 edge02-zcs amavis[27883]: SA info: netset: ignoring
interface scope '%eth0' in IP address [fe80::%eth0]/64
However, it is a leftover from a bug in postfix a while back, I've fixed
that.
--Quanah
--
Quanah Gibson-Mount
Architect - Server
Zimbra, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
