Darren Griffith wrote:
In the following logs, we have:
(1) our customer: tbmailer.triobet.com [83.218.12.49] on thread 16846
(2) a spammer: OL12-45.fibertel.com.ar [24.232.45.12] on thread 16845
The spammer's server triggers the check_earlytalker plugin. Then it
triggers
the dnsbl plugin according to a spamhaus lookup. Our customer's server is
considered white by the greylisting plugin.
The error message is this one:
box[16846]: 550 http://www.spamhaus.org/query/bl?ip=24.232.45.12
(note the wrong PID). A copy of our customer's bounce message confirms
that they received this 550 error message verbatim.
Does anyone know why this would have happened? Is qpsmtpd not
threadsafe?
This can be caused by the dnsbl plugin if the seed for DNS has not been
initialised randomly enough and if you don't check response ID's against
the originating query (I can't recall if we do that or not). Which
backend are you using? forkserver?
Matt.
