On Fri, 27 Feb 2015, Ian Zimmerman wrote:
Header of test message, massaged for privacy, is here:
http://pastebin.com/EV6g15aN
I have this in user_prefs:
trusted_networks 198.1.2.3/32
[...lots snipped...]
whitelist_from_rcvd *@wetransfer.com *.wetransfer.com
Why is the whitelist not firing?
whitelist_from_rcvd can be a bit fragile because it depends upon
multiple factors (trust chain, full-circle-DNS) working correctly.
First thing, that second parameter is not an address but part
of a DNS name, so use 'wetransfer.com' instead of that *.wet...
second thing, check to see if your trust chain is working as you
expect. whitelist_from_rcvd is applied at the point of the
first trusted relay (IE where the last untrusted hands the
message to the first trusted relay). Add the 'X-Spam-Relays-Trusted'
and 'X-Spam-Relays-Untrusted' pseduo headers to your report
to see if things are working as expected.
Note that a DNS fubar (even temporary) will break whitelist_from_rcvd.
Also if the sender changes MSP, it will break thus is a maintanance
head-ache.
I see that message has a valid DKIM signature, why not use
whitelist_auth. Same goodness with less head-aches.
--
Dave Funk University of Iowa
<dbfunk (at) engineering.uiowa.edu> College of Engineering
319/335-5751 FAX: 319/384-0549 1256 Seamans Center
Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527
#include <std_disclaimer.h>
Better is not better, 'standard' is better. B{
