search

mozilla / bugbot

A Mozilla release management tool to send reminders to Firefox developers and improve Bugzilla metadata
BSD 3-Clause "New" or "Revised" License
41 stars 68 forks source link

Disabled accounts due to mail server connection issues are considered as inactive #1554

Open suhaibmujahid opened 2 years ago

suhaibmujahid commented 2 years ago

As an example, @smaug---- had an issue in his mail server which got his Bugzilla account to be disabled: https://mozilla.slack.com/archives/C5F7KFJ4R/p1658153225222019. As an effect, autonag considered him as inactive: https://bugzilla.mozilla.org/show_bug.cgi?id=1779206#c8

Account disabling messages:

Your Bugzilla account has been disabled due to issues delivering emails to your address.

Your mail server said: (failed) Amazon SES has suppressed sending to this address because it has a recent history of bouncing as an invalid address. For more information about how to remove an address from the suppression list, see the Amazon SES Developer Guide: http://docs.aws.amazon.com/ses/latest/DeveloperGuide/remove-from-suppressionlist.html

Your Bugzilla account has been disabled due to issues delivering emails to your address.

Your mail server said: (failed) smtp; 553 5.1.2 Unknown mail server. Could not find a mail server for pettay.fi

marco-c commented 2 years ago

Is there a way to know how long an account has been disabled? If so we could consider an account to be really disabled if it has been disabled for a week. Any other idea?

suhaibmujahid commented 2 years ago

Is there a way to know how long an account has been disabled? If so we could consider an account to be really disabled if it has been disabled for a week.

We have last_seen_date, it could serve for this purpose.

Any other idea?

We could check if the email is disabled because of an email bouncing issue by checking email_enabled or login_denied_text. If so, we could use last_seen_date to allow a week before considering the user as inactive.