[Mailman-Users] unsubscribe nonfictions duplicated daily

[Bill Heath]

After reviewing the member list, I did not see any of the domains with
caps in them, I did however see several entries in the format of
user at domain1.com/user2 at domain1.com/user3 at domain1.com.  I am suspecting
that this is not normal either.  After searching in the web interface,
they entry is there as well.  If I check the unsubscribe option on the
membership list and hit submit your changes, I get an response of
user at domain1.com/user2 at domain1.com/user3 at domain1.com -- Not subscribed.
Is there a way to manually remove these entries from the subscriber
database?

Bill Heath wrote:

>My apologies, I had the configuration information in my clipboard but
>forgot to paste it prior to hitting send.
>
>I am running mailman 2.1.9, with postfix 2.4.5 on an Ubuntu 7.10 server
>
>-----Original Message-----
>I have a situation where approximately 120 unsubscribe notifications
for
>one of my lists are being sent out repeatedly at basically the same
time
>every day.
>
>I am very new to the Mailman server and Linux as well.  Can anyone
>provide some guidance on where to look to begin troubleshooting this
>issue or to a solution to fix the problem?


My guess is these notices are being generated by the cron/disabled
process which by default runs daily at 9:00 am.

Normally, this process detects members whose delivery has been disabled
by bounce and sends them the periodic reminder or ultimately
unsubscribes them after enough notices have been sent.

It seems that something is wrong here such that the unsubscribe notice
to the admin is sent without the member actually being removed.

There is a bug not fixed until 2.1.10. If a member's email address
local_part was all lower case, but the domain was mixed/upper case
(e.g. janedoe at Example.com), the member would be added with the key in
member data not being all lower case. This could cause all sorts of
problems including (I think) not actually removing the member when the
member should be removed.

I think that might be what's happening here. Do the addresses reported
as being unsubscribed have all lower case local_part and mixed or
upper case domain? Does bin/list_members without the -p option report
members with upper case in the domain?

If so, I think that's the issue. The problem is that it will be tricky
to fix. If you can confirm that this is the case, I can work up a
script that will fix it.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan