Related to this: I had a hard time remembering my password after receiving the notification (I finally did), but I tried the "reset password" functionality and have yet to receive an email. Since I received the expiry notification emails, I suspect it's not a general sending issue and not related to my email provider.

Edit: I should add that I did receive an email now, after having logged in, changed my password, and logged out and in again. So the issue, if it still persists, may be restricted to inactive accounts or amounts with a very old password. Either way, people with inactive accounts having forgot their password may have a hard time activating their accounts again.

Hello,

@Micha: have you seen something similar in your forum? I expect this feature to be active in your installation for a longer time.

No. I have been running the forum with this feature for only a few years. Moreover, I use a no-reply-address.

/Micha

Hello

With the version 20220508.1 we introduced the feature to send an e-mail to users who was inactive over a specified time (default is 3 years). Last night this forum sent many of these messages. … Checking the users list of this forum I saw many accounts with a lastest login on 2022-05-09 at 3:30 am. This is exactly the time of the last automatic daily actions (last night) minus three years.

I can not imagine this to be a coincidence.

The answer is the code in functions.inc.php, line 212 (current state of the master branch). The query stores the information about the sent inactivity notification and sets the columns last_login and last_logout to (NOW() - INTERVAL 3 YEAR) (3 is the default value, we used here).

Is there a reason to reset the columns last_login and last_logout I don't realise?

Tschö, Auge

Hello

I have a next question about the behaviour of the selection of inactive accounts.

The query to select the affected accounts (functions.inc.php, currently line 195) is this one:

 
SELECT
    `user_id`,
    `user_name`,
    `user_email`
FROM `mlf2_userdata`
WHERE `user_lock` = 0
    AND `user_type` = 0
    AND `inactivity_notification` = FALSE
    AND (`last_login` - (NOW() - INTERVAL 3 YEAR)) < 0
ORDER BY `last_login` ASC LIMIT 20;
 

Especially I am interested in AND (`last_login` - (NOW() - INTERVAL 3 YEAR)) < 0. I tested the query part in phpMyAdmin with these two versions. First one with a test_date, that is definitely older than 3 years and the second one with a test_date that is only two years ago.

SELECT '2017-12-30 12:45:40' AS test_date, (NOW() - INTERVAL 3 YEAR) AS old_date, ('2017-12-30 12:45:40' - (NOW() - INTERVAL 3 YEAR)) AS subtraktion
SELECT '2020-12-30 12:45:40' AS test_date, (NOW() - INTERVAL 3 YEAR) AS old_date, ('2020-12-30 12:45:40' - (NOW() - INTERVAL 3 YEAR)) AS subtraktion

These are the results.

2020-12-30 12:45:40  2019-05-12 20:12:31  -20190512199211
2017-12-30 12:45:40  2019-05-12 20:20:15  -20190512199998

In both cases I get a warning.

Warning: #1292 Falscher DOUBLE-Wert gekürzt: '2017-12-30 12:45:40'
/* free translation: shortened wrong DOUBLE value: */

I think, the logic of the condition is broken. The condition AND (`last_login` - (NOW() - INTERVAL 3 YEAR)) < 0 returns a negative value (< 0) (and is therefore TRUE) in every single case. But that's a task for tomorrow.

Tschö, Auge