On December 15, 2000 at 11:46, Eric Pretorious wrote:
Looking at the header information for these messages:
<!--X-Message-Id:
200008012223(_dot_)PAA00498(_at_)ha3mpk(_dot_)Eng(_dot_)Sun(_dot_)COM -->
<!--X-Message-Id:
200008012227(_dot_)QAA26246(_at_)bast(_dot_)Central(_dot_)Sun(_dot_)COM -->
<!--X-Reference:
200008012227(_dot_)QAA26246(_at_)bast(_dot_)Central(_dot_)Sun(_dot_)COM -->
<!--X-Message-Id:
200008021347(_dot_)HAA11397(_at_)bast(_dot_)Central(_dot_)Sun(_dot_)COM -->
<!--X-Reference:
200008021347(_dot_)HAA11397(_at_)bast(_dot_)Central(_dot_)Sun(_dot_)COM -->
*** No x-message-id information in this message ***
Is this disconnect being caused by our mailing list server?
Do you have the raw mail message? Check to see if the message-id header
is defined. If so, can you send a copy of the headers? This way I
can see if there is something MHonArc is not handling properly.
What, specifically, should I ask our mailing list admin to adjust to prevent
this disconnect?
I am not sure what you mean by "disconnect?".
--ewh
