Am 20.10.2014 um 16:43 schrieb Axb:
On 10/20/2014 04:37 PM, Reindl Harald wrote:Am 20.10.2014 um 16:25 schrieb Axb:On 10/20/2014 02:56 PM, Reindl Harald wrote:seems your recursor couldn't resolve it, so your MTA added unknown... Received: from nm46-vm10.bullet.mail.bf1.yahoo.com (nm46-vm10.bullet.mail.bf1.yahoo.com [216.109.114.203])what happens in case of a temporary DNS error? postfix anserwers in such cases with a 450 even with "unknown_hostname_reject_code = 550"only if you do tell Postfix to do so..no trueoh yes it is...http://www.postfix.org/postconf.5.html#reject_unknown_client_hostname The unknown_client_reject_code parameter specifies the response code for rejected requests (default: 450). The reply is *always 450* in case the address->name or name->address lookup failed due to a *temporary problem*reject_unknown_client_hostname reject_unknown_reverse_client_hostname are NOT default. had he set such check it would have not hit SA..
i asked *what does SA* in case of a *temporary* error and brought postfix as *example* that it could be handeled different to a response
not relevant..it's relevant in case the OP had a temporary DNS error because no nameserver responded resulting in a FPit resulted in a FORGED_YAHOO_RCVD hit - takes way more than that to trigger a FP
> anyway.. EOT... > (why am I wasting my time?)sorry for asking a simple question and bringing an example - you could have just answered "not handling different and i don't" bother, frankly that is the most hostile list i remember
signature.asc
Description: OpenPGP digital signature
