I'm running 5.19.

When a user tries to reset their password with their email address, it says "emailaddress@something.com is not allowed to request a new password." The email address passes the "check rules" for the email address.

When you use a username, it works as it should.

Repeatable for any user I tried.

Skip

Comments

avskip’s picture

avskip commented
Priority: Normal » Critical

Are version 5 bugs being ignored? I'm having this happen at least once daily. Could another module being messing with this?

drumm’s picture

drumm
he/him
Location NY, US
commented
Priority: Critical » Normal

I use this all the time on a few sites without issues. Is the user account blocked? Have you checked spam filters?

This could certainly be affected by modules. This can be moved back up to critical if you can reproduce it with contrib modules disabled.

avskip’s picture

avskip commented

The user accounts are not blocked and the email address passes the filters per the test on that page.

I'll see if I can reproduce it with contribs disabled and get back to you asap.

Skip

avskip’s picture

avskip commented

Since my original posting of this, I've upgraded to 5.20.

Tonight I disabled all contrib modules. The only modules in use were core and optional core modules (Blog,Blog API,Book,Comment,Contact,Forum,Help,Menu,Path,Ping,Profile,Search,Statistics,Taxonomy).

The problem was instantly replicated. When using an existing email address to request a new password, it again said "emailaddress@something.com is not allowed to request a new password." (note the email address is not shown exactly as the example. I only provided that to cover the real email address on here)

jpowell’s picture

jpowell commented

I have this issue in a 5.12 site. We're making plans to get the site upgraded to 5.20. Does anyone know if this issue is resolved in the newer versions of the user system in Core?

dpearcefl’s picture

dpearcefl commented
Status: Active » Closed (won't fix)

Considering the lack of activity on this issue and that Drupal v5 is no longer supported by fixes or patches, I am going to close this ticket. If this issue still exists and you want to continue to ask for technical support, please reopen and update this ticket.