Am 06.01.2015 um 21:01 schrieb Matus UHLAR - fantomas:
On 06.01.15 03:34, Reindl Harald wrote:but you are far away from a SPF_HELO_PASS in context of the incoming mail, frankly it's wrong and unrelated until the envelope sender is not @helo-hostnameplease, post the problem mail header, thank you
i already statet the envelope @domaintechnik.at as well as the sending host, see below and i don't talk about a "problem mail" - i just don't accept "SPF_HELO_PASS,SPF_NONE" matching both - it's nonsense because i could as well send with "someb...@domaintechnik.at" from our server to match it too
as said i disabled that behavior in the meantime (while i am not happy at all about the log-complaints until you disable related meta-tests too instead have them also silent disabled by implicit dependencies)
meta __SPF_FULL_PASS 0 meta __SPF_RANDOM_SENDER 0 score SPF_HELO_PASS 0policyd-spf[11818]: None; identity=mailfrom; client-ip=213.145.228.32; helo=host5.ssl-gesichert.at; envelope-from=kundeninfo-return-1-***@domaintechnik.at; receiver=***
spamd: result: . -3 - BAYES_00,CUST_DNSWL_2,CUST_DNSWL_5,HTML_MESSAGE,SPF_HELO_PASS,SPF_NONE scantime=5.8,size=230534,user=sa-milt,uid=189,required_score=5.5,rhost=localhost,raddr=127.0.0.1,rport=45413,mid=<54aac6b1.1040...@domaintechnik.at>,bayes=0.000000,autolearn=disabled
signature.asc
Description: OpenPGP digital signature
