<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<blockquote type="cite"
cite="mid:b9dd8682-31d9-d58f-0558-4a8533471615@unclet.net">
<blockquote type="cite">
<blockquote type="cite">How do I determine what exactly is wrong
with the header that the remote server is sending?
<br>
</blockquote>
<br>
What is your log_level and do you see "check_header: " log
lines?
<br>
</blockquote>
$log_level = 1;
<br>
<br>
I don't see check_header in the logs.
<br>
<br>
What should I set it to?
<br>
</blockquote>
$log_level = 2;<br>
<blockquote type="cite"
cite="mid:b9dd8682-31d9-d58f-0558-4a8533471615@unclet.net">
<br>
<blockquote type="cite">
<blockquote type="cite">If I can't get the remote site to fix
their stuff, is there a way to bypass the header check for
their domains only?
<br>
</blockquote>
<br>
If they DKIM-sign their mails, you can use
author_to_policy_bank_maps and disable header checks inside such
policy_bank.
<br>
</blockquote>
<br>
And if they don't, what's suggested?
<br>
</blockquote>
<p>Beyond author_to_policy_bank_maps there is not built-in mechanism
to define a sender-domain-based policy.<br>
</p>
<blockquote type="cite"
cite="mid:b9dd8682-31d9-d58f-0558-4a8533471615@unclet.net">
<br>
Is there a way to configure the system to reject messages with bad
headers, but to do the rejection with a temporary, rather than a
permanent code, so that the the remote system should attempt the
sending again later?
<br>
</blockquote>
D_TEMPFAIL instead of D_REJECT.<br>
</body>
</html>