Allen Coates
2016-07-21 23:28:09 UTC
For over a week now, I have been seeing DNS look-up failures - always
with mailspike, both whitelist and blacklist. It is affecting about
ten percent of my non-whitelisted connections.
Jul 21 15:10:28 geronimo postfix/dnsblog[27737]: warning: dnsblog_query:
lookup error for DNS query 163.123.219.112.bl.mailspike.net: Host or
domain name not found. Name service error for
name=163.123.219.112.bl.mailspike.net type=A: Host not found, try again.
Are other people experiencing similar difficulties, or is it my set-up?
Regards
Allen C
sooo familiar with the code, an idea must not be understood as a
proposal for a "nearly perfect" solution/implementation. Taking under
attention that the cleanup daemon already has the capabilities to
perform header_checks... I think it will be an interesting experience
to write a patch ;)
with mailspike, both whitelist and blacklist. It is affecting about
ten percent of my non-whitelisted connections.
Jul 21 15:10:28 geronimo postfix/dnsblog[27737]: warning: dnsblog_query:
lookup error for DNS query 163.123.219.112.bl.mailspike.net: Host or
domain name not found. Name service error for
name=163.123.219.112.bl.mailspike.net type=A: Host not found, try again.
Are other people experiencing similar difficulties, or is it my set-up?
Regards
Allen C
You're thinking of smtpd_end_of_data_restrictions, but there still
your idea has a problem: smtpd is not examining the DATA, but merely
passing it along to cleanup(8). The cleanup service is where the
only native Postfix content checking (header and body checks, see the
header_checks(5) manual and BUILTIN_FILTER_README) is done.
Yes, I ment something like xxx_end_of_data_restrictions. As I´m notyour idea has a problem: smtpd is not examining the DATA, but merely
passing it along to cleanup(8). The cleanup service is where the
only native Postfix content checking (header and body checks, see the
header_checks(5) manual and BUILTIN_FILTER_README) is done.
sooo familiar with the code, an idea must not be understood as a
proposal for a "nearly perfect" solution/implementation. Taking under
attention that the cleanup daemon already has the capabilities to
perform header_checks... I think it will be an interesting experience
to write a patch ;)
Your idea would bloat smtpd, and while not running as a separate
process, it certainly would cause more overhead.
That´s an argument!process, it certainly would cause more overhead.