Re: [Mailman-Users] unbanning a member?
I'm going to assume you meant to post to the list, and send there myself. For security reasons, Mailman lists do not munge reply-to. Frequently messages contain private information (IP addresses, domain names, email addresses, and even passwords) that the sender would not want broadcasted to a publicly archived list.
Adam Morris writes:
How do you try to subscribe that address? By web or by mail?
In the admin page Privacy Options, there is a ban_list option near the bottom of the page (this is version 2.1.21, I believe yours was older so there may be variations). AFAIK that is the only way to ban an address from subscribing in "stock" Mailman.
Make sure that the member is not in that list. I believe you reported that you have cleared out that list already, in which case it's possible that you didn't click the Submit button at the bottom of the page, and it's still there. I guess it's barely possible that you cleared the ban_list for a different list than the one you're trying to subscribe that address to.
If the web interface reports an empty ban list and you attempted to subscribe by mail, it's possible that there are two Mailman installations, one handling mail, and the other web (and this one has no effect on actual list operation). Multiple installations can arise for a number of reasons such as an incomplete upgrade where either the mailserver or the webserver was not properly configured.
Otherwise, I don't know what's going on. Perhaps Mark has an idea.
Regards,
Hi Stephen and all,
I didn't realise I hadn't clicked the submit changes after deleting the name from the banned list.
All sorted, thanks!
On 28/09/16 12:10, Stephen J. Turnbull wrote:
--
Adam Morris Jaws certified 2016 email: adam@damorris.com
On 09/27/2016 07:10 PM, Stephen J. Turnbull wrote:
I am a bit lost, but I think a summary of the issue is
- an address was added to the ban_list of a list.
- the address was subsequently removed from the ban_list.
- subsequent attempts to subscribe the formerly banned address get an "address is banned" response.
Everything Steve said in his reply is relevant and possible, but let's assume you now go to the web admin UI for the list and Privacy options -> Subscription rules -> ban_list is empty and you then go to Membership Management... -> Mass Subscription and subscribe the address and get the banned response.
The actual response should look something like
Error subscribing:
jdoe@apot.com -- Banned address (matched ^.*[@.]apot(mail)?\.com$)with a different address and match of course (at least since Mailman 2.1.7). Is that what happens?
If all the above describes what happens, then I think the issue must be that the address/pattern that matched is in the GLOBAL_BAN_LIST that was added in Mailman 2.1.21.
Have you set GLOBAL_BAN_LIST in mm_cfg.py (or Defaults.py)?
If the above does not describe what happens, where does the actual result differ?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hi Stephen and all,
I didn't realise I hadn't clicked the submit changes after deleting the name from the banned list.
All sorted, thanks!
On 28/09/16 12:10, Stephen J. Turnbull wrote:
--
Adam Morris Jaws certified 2016 email: adam@damorris.com
On 09/27/2016 07:10 PM, Stephen J. Turnbull wrote:
I am a bit lost, but I think a summary of the issue is
- an address was added to the ban_list of a list.
- the address was subsequently removed from the ban_list.
- subsequent attempts to subscribe the formerly banned address get an "address is banned" response.
Everything Steve said in his reply is relevant and possible, but let's assume you now go to the web admin UI for the list and Privacy options -> Subscription rules -> ban_list is empty and you then go to Membership Management... -> Mass Subscription and subscribe the address and get the banned response.
The actual response should look something like
Error subscribing:
jdoe@apot.com -- Banned address (matched ^.*[@.]apot(mail)?\.com$)with a different address and match of course (at least since Mailman 2.1.7). Is that what happens?
If all the above describes what happens, then I think the issue must be that the address/pattern that matched is in the GLOBAL_BAN_LIST that was added in Mailman 2.1.21.
Have you set GLOBAL_BAN_LIST in mm_cfg.py (or Defaults.py)?
If the above does not describe what happens, where does the actual result differ?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Adam Morris -
Mark Sapiro -
Stephen J. Turnbull