------------------------------------------------------------
revno: 1589
fixes bug: https://launchpad.net/bugs/1523273
committer: Mark Sapiro <m...@msapiro.net>
branch nick: 2.1
timestamp: Sun 2015-12-06 12:00:29 -0800
message:
  Submitting the user options form for a user who was asynchronously
  unsubscribed would throw an uncaught NotAMemberError.
modified:
  Mailman/Cgi/options.py
  NEWS


--
lp:mailman/2.1
https://code.launchpad.net/~mailman-coders/mailman/2.1

Your team Mailman Checkins is subscribed to branch lp:mailman/2.1.
To unsubscribe from this branch go to 
https://code.launchpad.net/~mailman-coders/mailman/2.1/+edit-subscription
=== modified file 'Mailman/Cgi/options.py'
--- Mailman/Cgi/options.py	2015-09-17 00:39:34 +0000
+++ Mailman/Cgi/options.py	2015-12-06 20:00:29 +0000
@@ -297,6 +297,14 @@
     # options.  The first set of checks does not require the list to be
     # locked.
 
+    # However, if a form is submitted for a user who has been asynchronously
+    # unsubscribed, uncaught NotAMemberError exceptions can be thrown.
+
+    if not mlist.isMember(user):
+        loginpage(mlist, doc, user, language)
+        print doc.Format()
+        return
+
     if cgidata.has_key('logout'):
         print mlist.ZapCookie(mm_cfg.AuthUser, user)
         loginpage(mlist, doc, user, language)

=== modified file 'NEWS'
--- NEWS	2015-11-24 14:11:28 +0000
+++ NEWS	2015-12-06 20:00:29 +0000
@@ -22,6 +22,9 @@
 
   Bug fixes and other patches
 
+    - Submitting the user options form for a user who was asynchronously
+      unsubscribed would throw an uncaught NotAMemberError.  (LP: #1523273)
+
     - It was possible under some circumstances for a message to be shunted
       after a handler rejected or discarded it, and the handler would be
       skipped upon unshunting and the message accepted.  (LP: #1519062)

_______________________________________________
Mailman-checkins mailing list
Mailman-checkins@python.org
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-checkins/archive%40jab.org

Reply via email to