Bugs item #1956393, was opened at 2008-05-02 20:16
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1956393&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: (un)subscribing
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: niall shaw (sgpostie)
Assigned to: Nobody/Anonymous (nobody)
Summary: List Options change of address accepts mailto: 

Initial Comment:
One of my users changed their subscription address by copying and pasting in 
List Options, and accidentally included the mailto: protocol.  While they 
received messages at their new address, they were not recognised as subscribers 
when attempting to send.

Testing this, I find that the Mass Subscription page strips mailto: and 
subscribes the proper address.

**The normal deletion tools fail to operate on the invalid address**:
  Membership list unsub checkbox;
  Mass Removal page;
  Command Line remove_members
- all fail to remove an address with mailto:

remove_members produces the following error for the example address 
mailto:[EMAIL PROTECTED]:

-----
Traceback (most recent call last):
  File "/usr/sbin/remove_members", line 186, in ?
    main()
  File "/usr/sbin/remove_members", line 176, in main
    admin_notif, userack)
  File "/usr/lib/mailman/Mailman/MailList.py", line 1014, in 
ApprovedDeleteMember
    self.removeMember(emailaddr)
  File "/usr/lib/mailman/Mailman/OldStyleMemberships.py", line 220, in 
removeMember
    self.__assertIsMember(member)
  File "/usr/lib/mailman/Mailman/OldStyleMemberships.py", line 113, in 
__assertIsMember
    raise Errors.NotAMemberError, member
Mailman.Errors.NotAMemberError: [EMAIL PROTECTED]
-----

- indicating (I think) that the search function fails because it doesn't 
include mailto: as part of the address.

There *is* a workaround: clone_member -r will delete the invalid address. 
(Using clone_member without -r successfully creates a new valid subscription, 
e.g. [EMAIL PROTECTED] - but this then will be deleted by any of the above 
tools rather than "mailto:[EMAIL PROTECTED]"!)

However, the main problem here is that mailto: is accepted by the List Options 
page change of address mechanism.  Hopefully it would not be too hard to adapt 
the filtering used on the Mass Subscription page?



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1956393&group_id=103
_______________________________________________
Mailman-coders mailing list
[email protected]
http://mail.python.org/mailman/listinfo/mailman-coders

Reply via email to