Every time that happens (it's not every email, but 100 to 300 a day out of a total of 10,000), the email goes on to be delivered without being tagged by spamassassin.
I wasn't getting that message in syslog at all before setting up spamcopuri.
Is there a known fix to this weirdness?
-- Jason
This email and any attachments thereto may contain private, confidential, and privileged material for the sole use of the intended recipient. Any review, copying, or distribution of this email (or any attachments thereto) by others is strictly prohibited. If you are not the intended recipient, please contact the sender immediately and permanently delete the original and any copies of this email and any attachments thereto.
On Tuesday, August 10, 2004, 9:06:52 AM, Jason Burnett wrote:
Every time that happens (it's not every email, but 100 to 300 a day out of a total of 10,000), the email goes on to be delivered without being tagged by spamassassin.
I wasn't getting that message in syslog at all before setting up spamcopuri.
Is there a known fix to this weirdness?
My hunch is that it could be intermittent DNS timeouts.
We're trying to get all the public name servers switched over to rbldnsd, since it's much faster than BIND. That may help.
Can someone look through the sources and see how this message comes up: "timeout before data read" ?
Jeff C.
-
Jason M. Burnett -
Jeff Chan