Hello fellow site maintainers,

A few weeks ago we scrapped our custom lsv_amin binary and replaced it with the 
standard lsv_amin in order to get back to a more simplistic, out-of-the-box 
configuration. The custom binary predated any of the current staff working on 
our listserv machine, so we don't even know why we had it in the first place.

One of the side effects seems to be that list owners are receiving a LOT 
more of failed messages with the text:

---
'The enclosed message has been identified as a delivery error for the LISTNAME
list because it was sent to [log in to unmask]
---

The owners are now receiving these errors in place of the usual daily monitoring 
reports, and I've noticed our total number of LISTNAME.autodel files has 
dropped. They have always received these errors from time to time, it is just 
that the frequency of these has increased, and again, the monitoring reports 
have dwindled.

Does anyone have an idea what may be going on here or some things I should be 
looking for? I'm kind of at a loss as where to go next with this. Also, we do 
use qmail as our MTA and our .qmail-owner-default alias reads:

|/var/qmail/bin/preline /ssa/listserv/bin/lsv_amin -s /ssa/listserv/spool -t "$LOCAL"

Can anyone offer some help or advice? Or let me know if this is all normal 
behavior and to be expected since we removed our custom lsv_amin?

Thank you in advance,
Jim

--
Jim Serwinowski                 [log in to unmask]
UB Listserv Administrator       http://listserv.acsu.buffalo.edu