Hi,
We're experiencing some significant delays with our mailman lists. Some
messages are delivered instantly, while others can take hours (or over a
day) before it's delivered. For example, a message came in at 4:07am and
was passed on to mailman for processing:
Dec 13 04:07:43 cork
At 3:23 PM -0500 12/14/06, Jason Rotunno wrote:
We're experiencing some significant delays with our mailman lists. Some
messages are delivered instantly, while others can take hours (or over a
day) before it's delivered.
A certain amount of delay is not unusual, and variable amounts of
Jason Rotunno wrote:
Does mailman do any kind of
prioritizing depending on system load?
No. Each of mailman's queues (only 'in' and 'out' for message
processing and delivery) is processed FIFO and as quickly as
resources, and in the case of 'out', MTA responses allow.
Brad has given some good
Thanks for the replies. I checked out the log files and saw problems. The
example I gave in my previous message, for example, generated a bunch of
stuff. In the post logs I saw this repeated throughout the day until the
message was delivered:
post.1:Dec 13 04:39:48 2006 (23382) post to star from
[EMAIL PROTECTED] wrote:
post.1:Dec 13 04:39:48 2006 (23382) post to star from [EMAIL PROTECTED],
size=28696, message-id=[EMAIL PROTECTED],
16 failures
The smtp-failure entries give more info about the same event.
The same goes for these in the smtp-failure logs:
Dec 13 04:29:46 2006 (23382)
At 7:54 PM -0500 12/14/06, [EMAIL PROTECTED] wrote:
Anyone know what exactly these mean or how to handle it? Or point me in
the right direction of where to look to get this resolved since it's an
smtp problem?
The error Connection unexpectedly closed points to a problem within
your MTA.
