Remove from mailman list when a contact is deleted about ixp-manager HOT 6 CLOSED

Also when contact e-mail address is changed, delete the old mailing list subscription from the mailing list.

from ixp-manager.

There are other issues with the mailing list code.. it seems not to do what we want. When a user unsubscribes via mailman, IXP manager puts them back on the list again. If mailman's bounce detection kicks in and auto-unsubscribes a list member, IXP manager puts them back on the list and the process starts again.

Ideally, we'd like to disable access to mailman entirely and get users to manage this via the portal, but there isn't a way for all the subscriptions for a given member to be maintained at present. (only the e-mail address for a given user and not, say, the NOC/peer contact can be edited.)

from ixp-manager.

Note we are in a total mess with this and it's holding us back from setting up new lists. Wondering if we should just turn this feature off for now and give up with it, or if it can be fixed?

from ixp-manager.

Situation is less than ideal, because I would really like to split the
mailman lists up so it's made of multiple lists:

members@ list which auto-includes the following:

members-ixpman - managed via ixpman
members-mailman - managed via mailman
members-post-only - post only list (can post but receives no copies
managed from ixpman)

We set up this mailman config but were unable to proceed further because
of the IXP manager side of things not really working for us. Members
have been asking us for years that they want an "announce" list which
does not have general discussion but only LONAP announcements.

The problem is that it insists on every subscriber of the list being a
user in IXP manager (not just a contact), and only allows for one e-mail
address per user account. Managing it via IXP manager is somewhat
clunky for the admin. There's no simple "get me a list of all
subscribers for this customer and what they're subscribed to" it's a lot
of clicking around, switching back and forth between user accounts etc.

Ideally we'd have it all managed in one place in IXP manager and not
have users in mailman at all (all subscriptions and unubscriptions have
to be manually checked and approved, and it can be difficult to relate
which members the list subscription belongs to.) I'd sooner that
somebody just login to IXP Manager and do what they want.

Also we need to check that in the process, a member does not manage to
unsubscribe ALL contacts from the lists. (i.e, I need to enforce that at
least one contact is subscribed to the announce list.)

So, whilst I set up the lists, we did not proceed with telling members
to update anything, otherwise it would be a massive shambles.
Hoping that a fix would be forthcoming in IXP Manager sometime soon,
I left it like that. :)

Reminds me that we (LONAP) should probably turn off the mailing list
sync feature for now as it doesn't work for us and causes more problems
that it solves.

Rob

This is a forwarded message

From: barryo [email protected]
To: inex/IXP-Manager [email protected]
Date: Wednesday, June 1, 2016, 1:59:35 PM
Subject: [inex/IXP-Manager] getMailingListSubscribers() does not handle customers which have left (#261)

===8<==============Original message text===============
Regarding the OP:

If a customer leaves, they are still subscribed to mailing lists.

Yes, unless a staged approach is taken:

1. user has mailing list subscription managed by IXP Manager
2. admin unsubs user
3. admin runs sync process
4. admin deletes user

This is not ideal and in practice for the very odd member leaving event, we've handled this manually.

This is all effectively covered by the feature request that is #22 so closing.

from ixp-manager.

Thanks @listerr - the above is uber-useful for trying to sketch out how the next iteration of this should work.

from ixp-manager.

Housekeeping Sept 2021

@barryo closing long running issues (open multiple years).

Where appropriate, will:

1. relocate to the IDEAS file.
2. Add additional information below.
3. No relocation / additional information for uber-stale issues.

Additional information: mailing list management, if to be kept within IXP Manager, needs a complete rework rather than tweaks on the current system which was INEX-specific.

from ixp-manager.