Hi,

I noticed that in 2.1.6, subscription_cancel in Mailman/Cgi/confirm.py doesn't have the same SIGTERM unlocking parachute that subscription_confirm has; is this done on purpose, and why? Is there no risk of leaving a stale lock with what subscription_cancel does?

Without more info, I'd say this is "simply" oversight and that it would be needed.

Your opinion?

-- Lionel