We've got 7,487 people for whom bakery won't work. How can we mail this many people? Vauxia suggested creating a mailman list that we use just for this purpose and then delete.

select count(1) from users where migrated = 0 and login > unix_timestamp() - (365*24*60*60) and status = 1 and length(mail) > 0

Can you help, Gerhard?

Comments

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

Already 10 webmaster issues about people not being able to log on to groups.drupal.org... :(

gerhard killesreiter’s picture

gerhard killesreiter commented

We need to wait for Narayan to get home and recuperate to create this list.

With the query I actually only get 7446 now, so some delay won't hurt.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

Down to 6226. I'd like to get usermerge installed and test out the self synch before we do this, though.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

Now at 15,676...

I think initially there were a lot of people marked as "migrated" who actually "weren't" :(

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

Using migrated = 0 is kind of a horrible test.

select count(1) from users where init like 'http://drupal.org/user/%' and login > unix_timestamp() - (365*24*60*60) and status = 1 and length(mail) > 0

That works better.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

Actually, that's wrong too:

select count(1) from users where init not like 'http://drupal.org/user/%' and login > unix_timestamp() - (2*365*24*60*60) and status = 1 and length(mail) > 0;

Now uses "init NOT like" and looks for people from the last 2 years. The current count is 8,594 so we've got a lot more folks synched up since my comment on February 2.

Our attrition in general (i.e. user creates account, uses it, never comes back) is not super so perhaps these 8,594 represent mostly "real" cases.

I could be in favor of mailing them now. Anyone else have strong feelings on that?

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Title: send a mail to notify people of problem with single sign on » Send a mail to notify people of problem with single sign on

Could not such email report a note saying that a similar problem could be present in other sub-domains as well?
It's rather possible that who has a synchronization problem with g.d.o would have the same problem on association.d.o, in example. If then the email would explain that on drupal.org, and subdomains is not possible to have two different accounts, users with the problems on g.d.o would check their account on other subdomains too.

deviantintegral’s picture

deviantintegral commented

Subscribing - I've been wanting to do this for the Association as well as an opportunity to encourage membership renewals and so on.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

We could definitely do this in a coordinated way with three groups:

1. Those who have a problem on g.d.o and a.d.o
2. Those with a problem a g.d.o only
3. Those with a problem on a.d.o only

None of the other subsites have this problem because they didn't exist or didn't allow logins until after Bakery.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Project: Drupal.org site moderators » Groups.drupal.org
Component: Groups.drupal.org » User account
greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Version: » 6.x-1.x-dev
Status: Active » Closed (won't fix)

I'm not sure this is so necessary any more. There is a self service tool which takes care of it for most folks.