On Fri, 8 May 2009, John Hardin wrote:
I suspect the sender is timing out waiting for the "250 OK" after
sending the message, hence my (humorous) "100 Please hold..."
suggestion. (Jeeze, SM, lighten up!)
(nod) I should not have said "data command". Apologies again.
And I can see a busy list server reducing those timeouts a bit - they
are sending a _lot_ of mail.
That was my guess. Just wondering if anyone *knew* for certain.
I suppose I could always test it, but as I said, I figured out how to stop
the problem. So another time, perhaps....
Charles, here's something you could try: using telnet, connect to your
MTA and pretend you're the yahoo listserv. Feed in one of the
problematic messages, and time how long it takes from sending the final
period to receiving the 250 OK. That will give you something to compare
to how long it takes to scan the message outside of your MTA
envrionment.
Actually, my logs are sufficiently verbose that I can check the times it
takes from DATA until the message is handed off to my LDA. I didn't make a
note of exact timing, but it wasn't 10 minutes. More like 4 or 5....
(though don't quote me on that - this is 'resolved' so I'm too busy to
double-check those logs). As a side note, for people wondering why my SA
is so slow, I thought I would mention that my SMTP front end ("Mail
Avenger") has a bug that prevents me from properly using 'spamc', so all
load issues are compounded buy having to use 'spamassassin'. Fortunately,
without those 'full' rules, it handles things quite well....
- Charles
