|
⇤ ← Revision 1 as of 2007-03-20 18:51:58
Size: 987
Comment:
|
← Revision 2 as of 2007-03-20 18:55:34 ⇥
Size: 37
Comment: Page renamed to DEV/MemberAdaptor Semantics
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| #pragma page-filename DEV/versions/163857 == Semantics of changeMemberAddress == It is clear that when changing a member address that bounce_info for the old address and an old address delevery_status of BYBOUNCE should not be carried forward to the new address. However, if delivery for the old address is disabled BYADMIN or BYUSER and this is a straight change of address (i.e., nodelete = False), delivery most likely should remain disabled. There is a [[https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1642388&group_id=103|bug report]] from a user who was surprised when a global change of address resulted in enabling delivery for a high volume list. OldStyleMemberships.py has been changed so that if nodelete is False and delivery_status is BYUSER or BYADMIN, this is set for the new address. In all other cases the new address has delivery status ENABLED. In all cases the new address has no bounce_info. Other MemberAdaptors should be consistent with this. |
#REDIRECT DEV/MemberAdaptor Semantics |
Differences between revisions 1 and 2
MailmanWiki: DEV/MemberAdaptorSemantics (last edited 2007-03-20 18:55:34 by msapiro)