mailing list subscription email address are in NEW status

Bug #471770 reported by Curtis Hovey
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Unassigned

Bug Description

OOPS-1402EB708 shows an oops that occurs when ~lhavelund tries to edit his email addresses. This failure is SimpleVocabulary(terms), where terms are a list of SimpleTerm(email, email.email).

The user has 2 emails. one preferred email address. There is another NEW email address that came from the merged account. I do not think this is correct given that the merged account was used. maybe I am mistaken. Either way, the terms are preferred plus validated, so I expect to see only one email address in the choice.

Related branches

Curtis Hovey (sinzui)
Changed in launchpad-registry:
assignee: nobody → Curtis Hovey (sinzui)
Revision history for this message
Curtis Hovey (sinzui) wrote :

This issue appears to be a case where the current value is is not in the vocabulary. Since the vocabulary contains only the user's preferredemail address, the user appears to have another address from the merge set as the address for the mailing list. This is probably the address in NEW status.

If I can verify this is the case, we can update the email address in the production db to fix the user's issue. What we do not understand is how a preferred or confirmed email address can be set to NEW. The mailing lists could be set to use the preferred email address during the merge, but I think it is wrong to not honour the user's original choice.

Revision history for this message
Curtis Hovey (sinzui) wrote :

I have confirmed that lhavelund is subscribed to a mailing list under the old address. Since it is in the NEW state (1), it is not considered valid, which causes the oops. The email address must be forced to the VALIDATED state (2). Oh crumpets. I see there are 42 impossible mailing list subscriptions, each address is NEW. 40 of these are deactivated accounts, the remaining two are active accounts (~valsum, ~lhavelund)

summary: - ConstraintNotSatisfied in creating email address choice for mailng list
- fields.
+ mailing list subscription email address are in NEW status
Revision history for this message
Curtis Hovey (sinzui) wrote :

Hi Lasse and Aitor.

I am looking a ways to fix your broken mailing list subscriptions in the DB. It is probably easier for both you you to unsubscribe then resubscribe from the lists. In both your cases, I think there is an email address that must be reconfirmed. You can try to add your email broken addresses again, or subscribe to the mailing lists with your default email address.

Lasse, your subscription to https://launchpad.net/~planet-ubuntu-users uses the broken address. You can unsubscribe from the team page, then resubscribe when the page reloads.

Aitor, your subscription to https://launchpad.net/~ubuntu-es-locos uses the broken address. You can unsubscribe from the team page, then resubscribe when the page reloads.

Revision history for this message
Curtis Hovey (sinzui) wrote :

I have confirmed that AdminMergeBaseView.doMerge() intentionally resets the duplicate accounts email addresses to NEW to prevent identify theft. So what should be done in the case where the email address is used for a mailing list? Sending out emails to request confirmation of the email address would be a better experience. but that does not prevent this oops from happening. I see two options to fix this.

A) Set all subscriptions to the current preferred email address.
B) unsubscribe the user and send en email explaining how to resubscribe.

Changed in launchpad-registry:
status: Triaged → In Progress
Revision history for this message
Lasse Havelund (lhavelund) wrote : Re: [Bug 471770] Re: mailing list subscription email address are in NEW status

Done.

2009/11/10 Curtis Hovey <email address hidden>

> Hi Lasse and Aitor.
>
> I am looking a ways to fix your broken mailing list subscriptions in
> the DB. It is probably easier for both you you to unsubscribe then
> resubscribe from the lists. In both your cases, I think there is an
> email address that must be reconfirmed. You can try to add your email
> broken addresses again, or subscribe to the mailing lists with your
> default email address.
>
> Lasse, your subscription to https://launchpad.net/~planet-ubuntu-users
> uses the broken address. You can unsubscribe from the team page, then
> resubscribe when the page reloads.
>
> Aitor, your subscription to https://launchpad.net/~ubuntu-es-locos uses
> the broken address. You can unsubscribe from the team page, then
> resubscribe when the page reloads.
>
> --
> mailing list subscription email address are in NEW status
> https://bugs.launchpad.net/bugs/471770
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in The Launchpad Registry: Triaged
>
> Bug description:
> OOPS-1402EB708 shows an oops that occurs when ~lhavelund tries to edit his
> email addresses. This failure is SimpleVocabulary(terms), where terms are a
> list of SimpleTerm(email, email.email).
>
> The user has 2 emails. one preferred email address. There is another NEW
> email address that came from the merged account. I do not think this is
> correct given that the merged account was used. maybe I am mistaken. Either
> way, the terms are preferred plus validated, so I expect to see only one
> email address in the choice.
>

Revision history for this message
Lasse Havelund (lhavelund) wrote :

I've unsubscribed and re-subscribed to the mailing list (~planet-ubuntu-users) now.

Revision history for this message
Curtis Hovey (sinzui) wrote :

Fixed in launchpad devel r9877.

Changed in launchpad-registry:
status: In Progress → Fix Committed
Revision history for this message
Curtis Hovey (sinzui) wrote : Bug 471770 Fix released

Fixed released in launchpad-project 3.1.11.

Changed in launchpad-registry:
status: Fix Committed → Fix Released
Curtis Hovey (sinzui)
tags: added: merge-deactivate
Curtis Hovey (sinzui)
Changed in launchpad:
assignee: Curtis Hovey (sinzui) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.