(04-21-2009 01:32 AM)nesto Wrote: Hello - I do have quite the same problem.
Great... :-)
(04-21-2009 01:32 AM)nesto Wrote: - Do I have to fully deactivate policyd-weight or can I make further modifications to only prevent from rejecting these mismatches? I wouldn't mind if emails were marked as spam if at least not rejected
No you don't as I mentioned above...
Alter or generate a config policyd-weight.conf (in /etc or /usr/local/etc or distro specific depends on how you have installed policyd-weight) that contains:
Code:
$dnsbl_checks_only = 1;
and restart policyd-weight
(04-21-2009 01:32 AM)nesto Wrote: - What is the difference of reject_invalid_helo_hostname and reject_non_fqdn_helo_hostname?
from man 5 postconf
Code:
reject_invalid_helo_hostname (with Postfix < 2.3: reject_invalid_hostname)
Reject the request when the HELO or EHLO hostname syntax is invalid.
The invalid_hostname_reject_code specifies the response code for rejected requests (default: 501).
reject_non_fqdn_helo_hostname (with Postfix < 2.3: reject_non_fqdn_hostname)
Reject the request when the HELO or EHLO hostname is not in fully-qualified domain form, as required by the RFC.
The non_fqdn_reject_code parameter specifies the response code for rejected requests (default: 504).
means some none ascii chars in helo is rejected by reject_invalid_helo_hostname,
helos like "MSEXCH01" (yes this is very common;-)) are rejected by reject_non_fqdn_hostname
(04-21-2009 01:32 AM)nesto Wrote: - Why do I have authentication failures (e.g. with scripts using .NET trying to send email - see Type II, two warnings)?
you might need to enable some other mechanisms -> output of postconf -n might help...