Delete Ghost Mailing List User (Mailman Config Bug)

Question

I recently did something stupid. On the up side, I recognized that it was stupid right after I did it, but unfortunately my effort to undo what I did wasn't fast enough to correct the following issue. First, here's what I did:
I added a new group with the same name as an existing user.
Immediately after thinking about it and determining that this was probably a really bad idea, I deleted the group.
I thought everything was working fine until I realized that email was not coming in to the email address of the aforementioned user (the user that I had created a group of the same name)
Fortunately, I figured out the problem and a temporary fix. The purpose of this post is two fold: first, to submit what I believe is a bug, and secondly to figure out a way to permanently fix this issue on my system.
I have determined what happened on my system is this:
a mailing list group of the same name as my existing user was created thus diverting mail from that user to a now non-existant mailing list user. That results in the List Server Log reading the following when an email is sent to the user in question:
list_server_post[16378] <Error>: missing list GUID
Here's what I believe is a BUG: OS X Server 4.0 did not delete the mailing list group when I deleted the group. Now that's probably understandable because it's probably a protection against also deleting my user of the same name as a precaution, but it's not the expected behavior nonetheless.
Here's where I need help: In searching through various config files, I've determined that there entries located in /Library/Server/Mail/config/listserver/prefs which correspond to various lists (including my ghost list). I've also determined that /Library/Server/Mail/Data/listserver/aliases contains the references to the list that postfix uses to handle delivery. Unfortunately, according to the contents of /Library/Server/Mail/Data/listserver/aliases/list_server_virtual these files are generated "automatically" so deleting them does not rectify the problem. My assumption is that these files are generated from Open Directory, but for the life of me, I can't figure out what entry. In any case, I need assistance deleting the entry which should no longer be present. Any help would be GREATLY appreciated.
In the meantime, I have successfully worked around this problem by issuing:
sudo  /Applications/Server.app/Contents/ServerRoot/usr/sbin/serverctl disable  service=com.apple.list_server_mgr
which, of course, disables the list server (which I don't need), but I'm afraid it will be re-enabled if I restart (maybe I'm wrong about that, but I'd prefer to get to the root of the problem so it doesn't pop back up and bite me in the future).
Thanks in advance!

Answer 1

Where would the error be sent? If you send it back to the originator, you
disclose membership of the list. You can, however, configure the list
to have an address to which DSNs and NDNs are directed so that the
list maintainer (or whomever) can be alerted to these issues. This
is done with the mgrpErrorsTo LDAP attribute associated with the list
description. (I myself do not know how to set that via iDA.)
FWIW, there's a public mailing list for iMS issues. That mailing list is
read and responded to by many of the iMS engineers. It's
[email protected] Anyone can post to it; it's an unmoderated
list. You can subscribe by sending a message to [email protected] In the message place the single line
SUBSCRIBE