Unsubscribing via email not reflected in User_Mailman_Register
| Project: | User mailman register |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
I have posted a similar issue on Mailman_Manager's issues but will also post here because I do not know which module it relates most strongly to.
My problem is that when a I subscrib to a mailman list with Mailman_manager and/or user_mailman_register (hence forth subscribed with drupal) and then unsubscribe via email (ie send to list-request@server with unsubscribe in the subject) this is not reflected in Drupal.
This feature, to work with both a web interface and an email interface is vital to me and I am willing to try to find a way to implement it. However, I'm not sure if it would be best implemented with Mailman_manager or User_mailman_register. And of course I'm hoping that you and/or arturoramos will be agreeable and to my trying.
I've found that Joomla has a couple of extensions that are supposed to do this. And from researching on mailman it seems like it's easy to control mailman via http but less easy to extract information. However, the "who password [address=]" email command might be very useful, although probably too slow for most purposes, it could be added as a cron function so that the changes were updated periodically.
Let me know what you think.
Cheers
#1
You're right, currently user mailman register( and mailman manager) does not manage subcription actions with external methods, like email or mailman web interface. It needs that subscriptions are done with the module itself or syncronization is lost.
Find a way to implement it is already in my todos but i'm busy now for this.
Actually, my idea is to use a mailman url command to retrive users subscriptions (findmember?) and syncronize it with drupal state during the cron rotation, however any suggestion is well accepted.
#2
#3
According to #358532: Problems when users change their subscription with mailman manager, an experimental UMR submodule to import and syncronize user subscriptions from a mailman dump file is avaiable for testing.
This may temporary solve the problem of this issue, until the new subscription checking mechansim will be ready (i've already the idea how it will work, i need only more spare time to code it).
#4
Fixed in 5.x-2.x (http://drupal.org/node/408178) and 6.x-2.x (http://drupal.org/node/405024) releases with the new synchronization mechanism.
Please, open new issues for related bugs.
#5
Automatically closed -- issue fixed for 2 weeks with no activity.