@Lars, the placement from the sandbox picture looks great, thank you!

@AStein-WMF, Katie is out this week. I'll nudge her to check this phab on Monday, thank you!

I'll be there, thank you!

Thanks for the clarification, @Lars.

Resend is the goal. Thanks for checking, @Lars!

Thanks, @Lars! I shared the update with Yamini, and will flag here if she has any issues deduping.

The 'No Bulk Emails (User Opt Out)', which can also be done via this link https://civicrm.wikimedia.org/civicrm/a/#/email/unsubscribe, works as the unsubscribe from all emails: Civi and Acoustic.

Sharing one more transaction, from Adri, that matches this parameter:

For a US donor requesting to be unsubscribed (never contact me again), and until the unsubscribe button in https://phabricator.wikimedia.org/T404989 is implemented, the current process is to update their CID by selecting “No Bulk Emails (User Opt Out)” and “Do not SMS” under the privacy section. In the communications section, also ensure “Exclude from direct mail” is checked.

Yes, pretty please!!! Thank you :)

Hi @SBurnett-WMF! Do you have any updates from legal?

@Ejegg or @AKanji-WMF, I have shared a spreadsheet with updates on what’s been completed, and what’s needed to schedule and complete the email send.
Notes:

• Each tab contains the relevant email name and group
• I’ve already added the emails to CiviMail (Draft) with their respective recipient groups, including the DR for visibility
• Items marked in red indicate what’s still needed, as I wasn’t able to add the footer unsubscribe link in some languages. What remains is adding the link for a few languages, running a test, and scheduling the send, and then it’s all set 🙂

*Below is the screenshot of the email list

Great idea, thanks, @Ejegg. I'll be waiting for the file so we can ensure the email is sent tomorrow at the latest.

That would be great to add, @Ejegg, thank you!

Great, thanks a lot!

This is great, and I was able to follow the instructions easily. Thanks, team!

Thanks, @Lars and team, it sounds very promising! Looking forward to seeing how this develops, and please let us know if there’s anything needed from our side.

Using what I can to 'un-fry' what’s left of my brain, haha! That’s great news, thank you so much 🙌

Thanks for the explanation! I'm adding below a summary of what I understood from it:

Thanks, Lars!

https://wikimedia.zendesk.com/agent/tickets/1841649 and https://wikimedia.zendesk.com/agent/tickets/1840603 are a couple of examples --> by holding off, you mean not updating their emails entirely?

We’re already receiving responses from the double opt-in emails, including requests to update email addresses.
For contacts whose email addresses have already been updated, will an opt-in confirmation message be automatically sent after the feature is deployed, or will they fall out of next year’s email campaign for not completing the process?

@Lars, we can see the element, select a language from the full list of options, and click save; however, the change does not stick afterwards!

Thanks for the updates, guys! We'll wait to hear about the legal sorting before sharing this info with the team.

Hi @Ejegg, is the DR now able to update the double opt-in activities? If so, could you pls share the process? Ty!

Tysm :)

That's much better, thank you, @Lars!

@Lars, does this mean the “Cancel” button will appear on its own, between “View” and “More”? If so, I believe it to be an improvement, ty!

Thanks, @Lars - This is a great estimated volume to prep for team capacity.

@Eileenmcnaughton - Adding the notes here for your visibility:

@krobinson, the annual recurring donors have been mentioned in this suppress request phab: https://phabricator.wikimedia.org/T413907

I just filed an exclusion phab https://phabricator.wikimedia.org/T413907 and added the relevant info into this Asana task

I had a feeling this was on the Acoustic side—thanks for the explanation and for adding it to the 2026 list. I’m happy to discuss it further and help in any way I can!

@Lars, this isn’t about unsubscribing secondary emails per se... A good goal would be to add a cross-check to identify duplicate records, and if a recent donation exists under any associated email, remove those records from the segmentation (bucket them into a group for deduping?!). This would help prevent recently active donors from being included incorrectly, without changing anyone’s subscription status.

Sounds good, thanks, Lars! I'll share the news with the team and report back.

Thanks for the update and for fixing the issue!

Gotcha - this makes total sense, ty!

Thanks for asking, @Lars. Could you confirm whether the goal is to remove the ‘on-hold’ emails from the CID list, remove the on-hold field entirely, or something different?

@Lars, I created CID 69158152: The country was originally set to France and appeared correctly on the summary page. After I changed it to the US and saved, the country field shows as blank on the summary. When you expand the address details, the US is there — it’s just not displaying properly in the summary view.

Deal, ty!

@Lars, I think it would be helpful for us to go over this on a call next week. PayPal was only one example to explain why I’m asking for this, but there are other scenarios too, so PP is not the main focus. I’m not explaining it well in the phab, so apologies for that!

Interestingly, we just received another CID 66180543 from Canada, who reached out about receiving a USD email and requested a refund because their donation was charged in USD. However, their address is listed as CA in Acoustic and US in Civi, and their previous donation was also in CAD (ticket https://wikimedia.zendesk.com/agent/tickets/1774649).

@Lars, while the system technically maintains the recurring donation, it doesn’t always preserve the donor’s additional info—like name and email—as the primary record. For example, if a donor has an active recurring via PayPal but makes a one-time donation via credit card with a different email—which happens frequently—Civi won’t automatically retain all info unless the correct box is checked during a merge. The “Recurring Active” indicator would help DR identify this and ensure the merge keeps the correct primary information. Let me know if you need more information.

Both Civi and Acoustic show CA as the country for this CID.

Here's some interesting information Cailtin shared, regarding Acoustic, also relevant to CID CID35879501 from Oct 31st.

Sharing the latest snooze flaps that were also shared with the email team, for everyone’s visibility:

For some users, it’s slow throughout the day (myself included), while for others it’s intermittent. For Lindsay, it was a complete outage at 13:29:45 and again at 14:17:41 Pacific on Nov 18.

Thanks, @Lars!

Another super slow day for Civi, also reported by the DR team. Deduping was almost impossible!

Flagging that Civi has been super slow again today.

@Lars, the unsubscribe info is showing under Change-Log and Activities for the CIDs, but it’s not triggering ‘No Bulk Emails (User Opt Out).’ I could swear we had a script in place to check the updated CIDs for the unsubscribe info and apply the “No Bulk Emails (User Opt Out)”. Thanks for digging into this!

Great, thanks for confirming!

@Lars would enabling wmf-cv also resolve similar cases involving RMLs? For example, CID 63213025 should have been merged into 68277079. Ty!

French CID 35879501 was snoozed until 10/31/25 and received the RML on 10/31/25, as shown under the mailing events. However, they donated on 10/17/25 under the same email — shouldn’t that have prevented the RML from sending?
Given that the criteria include both entry and existing program members, should we also check for donations within this fiscal year?
@ppenloglou and @Lars

Thanks for the link, @Lars — you weren’t kidding about the slow loading! Do you think there’s a way to split this massive group into smaller ones so the admin team can work on deduping them? I’m seeing a lot of bogus emails (CID examples: 20605649, 64765224, 10202889, 2180527).
Maybe a group could be created based on “(List) Contact Display Name = no more than two” to help narrow things down?

Thanks, @Lars! So to clarify, do we need to wait a few hours, or perhaps until the entire email send has been completed, before the description changes from the number string to the full description?

Today’s Power email description was sp75235855 — please see the mailing events for CID examples 59915242 and 21586918.

Unfortunately, the issue is still happening. CID 68339721 was snoozed by us on 9/9/25 until 1/2/26, but RML1 was sent on 10/25/25. The same happened with CID 33342357, which was snoozed on 10/8/25 until 8/1/26, yet an RML was sent on 10/23/25. Both CIDs reverted to the snoozed status after receiving RMLs that shouldn’t have been sent.

Hi Team! Civi has been super slow since yesterday. I thought it was just me, but it turns out others have asked me as well.

Yes, it is, thanks for checking!