starlight.201...@binnacle.cx skrev den 2013-05-09 15:56:
Of course, otherwise why would it work
with the older 'sa-update' rules?
Perhaps you should read the original
query again.
spamassassin can guess, but it is not configured to know all defaults
that fits all servers out there, for instance trusted_networks shoul
list all wan ip that you know does forward email to you, else spf will
fail on this domains that does not send mail direct to your wan ip(s)
its allways best to make it stable with stable config so updates does
not change how it works
trusted_networks 172.29.0.0/16
trusted_networks 10.6.0.64/27
why not complete rfc 1918 ?
it does not make sense really to have this small ranges, when there is
no mx hosts pointing to it in lan
is you server on ipv6?
have IPv6 configured but in this case the
sending MUA is at 172.29.87.12
okay
Like I said, I put back the 2/22/2013
rules (2/23 was a typo) and it is working
again. Probably will just leave it
that way forever unless someone knows
what was broken by the 'sa-update'.
spamassassin 2>&1 -D -t msg
on both versions should show what happen
--
senders that put my email into body content will deliver it to my own
trashcan, so if you like to get reply, dont do it
