This may be what is causing us some problems - I have over 1300 files in
/home/listserv/spool and here are some of the oldest ones:


/home/listserv/spool>ls -l | more
total 61840
-rw-r--r--   1 listserv staff       4872 Jul 24 19:27 100046.mail
-rw-r--r--   1 listserv staff       4807 Jul 24 23:04 100173.mail
-rw-r--r--   1 listserv staff       5682 Jul 24 23:38 100240.mail
-rw-r--r--   1 listserv staff       4789 Jul 25 09:27 100742.mail
-rw-r--r--   1 listserv staff       8325 Jul 25 10:40 101051.mail

1: Why are these there?
2: Why aren't they being delivered or deleted?
3: Is there a maintenance/cleanup process I need to run periodically?

Thanks,
 Patrick Price
 West Virginia University

Dave Simon wrote:

>Jake,
>
>You may find that the problem is not with LSMTP but rather with a bad job
>or two clogging up the LISTSERV spool.  Have a look in the spool directory
>and move/delete any job that is older than you would expect (a day or so).
>You may find this clears up the problem -- as it has for us several times.
>
>Dave
>----------------
>Date:    Tue, 24 Sep 2002 10:43:33 -0700
>From:    "Brenneman, Jake (MSNBCi)" <[log in to unmask]>
>Subject: LSMTP "Bog Down" issue
>
>Does anyone else have a problem where after a large mailing (60-100,000
>subscribers), LSMTP slows down to crawl?
>Using Win2K box, dual 550Mhz, 1GB RAM
>I have a announce list called that often gets sent to multiple times a day.
>It seems that after a mailing has gone out, the proc and memory thresholds
>return to normal, and are by no means taxed.  However, after the large list
>is sent out, and everything on the box has returned to normal, our Editor
>mailboxes (Send= Editor, Hold, Confirm) don't get the "Confirmation
>required" emails back from Listserv for quite some time (> 10 mins).  If I
>check the Main directory, I can see the <newsletter>.OKxxxxxx file sitting
>there, so my conclusion is that LSMTP is "bogged" down somehow.  As
>confirmation of this, if I start and stop the LSMTP service, the
>confirmation immediately comes thru to the Editor mailbox.
>
>Here's what I've tried:
>The box has been totally rebuilt and tuned per LSoft Consulting's
>recommendations.
>Listserv and LSMTP are affinity mapped to different processors
>LSMTP destinations have been configured for most major domains (attbi.com,
>prodigy.net, earthlink.net, etc.)
>Every couple weeks, I remove all the address from all lists which generate
>the following errors
>            LSMTP-E-DNS_INVDOMAIN, LSMTP-E-DNS_NOIPADDR,
>LSMTP-E-DNS_NOANSWER, LSMTP-E-SMTP_OPENTMO, WSAECONNREFUSED,
>WSAENETUNREACH,
>WSAETIMEDOUT
>I'm NOT removing addresses that error with LSMTP-I-SMTP_WILLRETRY or
>WSAECONNRESET, as a couple of the big domains are amongst these errors and
>I
>figure the messages still have a chance.
>Maybe I need to remove these domains as well.  My theory is that LSMTP is
>reserving connections for the domains it can't get to initially, and only
>when I stop the service and restart it does it follow the Last In, First
>Out
>principle.
>
>Glad to provide more detail if you can help, as this is getting really,
>really frustrating.
>
>Thanks,
>Jake
>