For Users of ASSP <[email protected]> schreibt: > >Which brings us back to the issue at hand. ASSP did not use the FROM >address, REPLY-TO address, or the SENDER address to check against the >whitelist. Instead it chose an obscure entry in a RECEIVED header, >inside a comment.
That is not true, ASSP uses the envelope-sender which is not part of the mail. It is correctly shown in the X-Assp-Envelope-From: ASSSP uses also all other addresses if told so: Only the envelope-sender is added/compared to the whitelist (NotGreedyWhitelist) Normal operation includes addresses in the FROM, SENDER, REPLY-TO, ERRORS-TO, or LIST-* header fields. This allows nearly all list email to be whitelisted. If set to 'envelope-sender only', only this address is compared/added. If set to 'check all addresses - one match for white - add all', one match in any of this fields is enough to get white and all addresses will be added to whitelist. If set to 'check all addresses - all matches for white - update all', all defined addresses in all defined fields must be already whitelisted for a message to get a whitelisted state and all addresses will updated in whitelist. If any address is found in redlist, no whitelist addition will be done and the message gets not white. Will not do anything if you add/remove whitelist entries via email-interface. This was valid for Whitelist entiries and is working. Up to now it was not working for whitelisted domains. It should do now, ------------------------------------------------------------------------------ Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
