Matus UHLAR - fantomas <[EMAIL PROTECTED]> writes: >> But problem still persists that senders from the private >> 192.168.0.0/16 network are tagged with SPF_FAIL. > > aha, so you should check now, why do those fail.
Perhaps, because spamassassin does not provide an option to disable SPF scan for certain sender ips? Known and mentioned workarounds (private DNS views, SMTP auth) are too heavy weighted for my setup. > Is that your domain SPF checks fail for? What would be the sideeffects of adding '+ip4:192.168.0.0/16' to the SPF record? Enrico
