LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Valdis Kletnieks <[log in to unmask]>
Mon, 10 May 2004 14:08:39 -0400
text/plain (38 lines)
On Mon, 10 May 2004 13:49:44 EDT, "Hiler, John" <[log in to unmask]>  said:

> I spoke with a FOLUSA rep last week, who indicated that as many as
> threemessages were sent to FOLUSA-L list but never made the distribution. I
> checkedthe achives to find two of them in the archives. Another message, sent
> Monday, did make the distribution, but not the archives. Is there any way to
> audit listserv to determine what messages it has received, distributed and
> archived? This problem has been persistent enough to warrant investigation of
> alternative MLM tools for FOLUSA (and maybe the INFOTRAC2000 list as well).

>  What is the resolution?

Step 0: Remind people that it does absolutely no good to go through the pain of
changing the MLM tool in use if you don't have a clear idea of why you're
changing it.  In general, the problem is *NOT*, repeat *NOT* in the MLM
software itself, so changing the MLM will do about as much good as swapping
tires on a car one at a time, when the real problem is the battery is dead...

Step 1: Check the logs for the MTA that Listserv is using (Sendmail, LMail, or
whatever), and see if those three messages ever even arrived at your Listserv
machine.  I've seen more than once where the user never actually hit "send"
when composing the message...

Step 2: If they never arrived, have the sender get somebody to check the logs
at their end.  Changing MLM tools won't do much good if the problem is
elsewhere.

Step 3: If they did arrive, see if your MTA handed it off to Listserv.

Step 4: Check the Listserv logs, see if they were processed.  It's not unusual
for people to misconfigure their MUA (especially if they use multiple "role"
templates, and Listserv bounces the mail because it showed up with an address
that isn't a subscriber, or a editor/moderator, etc...

Step 5: If in fact the message *was* sent, check the outbound MTA logs
to see if it was handed off to the recipient's site.  If so, it's their problem,
not yours...

ATOM RSS1 RSS2