[GH-ISSUE #330] git rid of zombie users #256

New issue

Closed

opened 2026-02-26 09:36:59 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 09:36:59 +03:00

Owner

Originally created by @ThomasWaldmann on GitHub (Mar 22, 2018).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/330

Originally assigned to: @ThomasWaldmann on GitHub.

on nsupdate.info, there are quite a big amount of users who last logged in more than 2y ago.

i guess we can assume that quite some of these do not use nsupdate.info any more (or even never really used it).

i guess we could delete a user account if:

there was no login for more than 1y
and there are no hosts linked to that user (we already have a mechanism that gets rid of unused hosts)
and there are no domains linked to that user (see #342)

Originally created by @ThomasWaldmann on GitHub (Mar 22, 2018). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/330 Originally assigned to: @ThomasWaldmann on GitHub. on nsupdate.info, there are quite a big amount of users who last logged in more than 2y ago. i guess we can assume that quite some of these do not use nsupdate.info any more (or even never really used it). i guess we could delete a user account if: - there was no login for more than 1y - and there are no hosts linked to that user (we already have a mechanism that gets rid of unused hosts) - and there are no domains linked to that user (see #342)

kerem closed this issue

2026-02-26 09:36:59 +03:00

kerem commented

2026-02-26 09:37:00 +03:00

Author

Owner

@bonki commented on GitHub (Mar 22, 2018):

I'm in favour of this. If you want to be extra nice you could mail all affected users (those whose profile includes an email address, anyway) and inform them first.

@bonki commented on GitHub (Mar 22, 2018): I'm in favour of this. If you want to be extra nice you could mail all affected users (those whose profile includes an email address, anyway) and inform them first.

kerem commented

2026-02-26 09:37:00 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Mar 22, 2018):

The problem with mailing (in general) is that quite a lot of users enter some crap email address.

When the service sends a mail to such an email address, an error occurs (no MX, no mailbox, mailbox full, ...) and postfix' mailer daemon message ends up in my mailbox. For the kind of user affected by the functionality discussed in this ticket, I assume that the percentage of crap accounts is even higher than for the more active accounts, so I suspect that I'ld get flooded with error messages. Not great.

@ThomasWaldmann commented on GitHub (Mar 22, 2018): The problem with mailing (in general) is that quite a lot of users enter some crap email address. When the service sends a mail to such an email address, an error occurs (no MX, no mailbox, mailbox full, ...) and postfix' mailer daemon message ends up in my mailbox. For the kind of user affected by the functionality discussed in this ticket, I assume that the percentage of crap accounts is even higher than for the more active accounts, so I suspect that I'ld get flooded with error messages. Not great.

kerem commented

2026-02-26 09:37:00 +03:00

Author

Owner

@bonki commented on GitHub (Mar 22, 2018):

That's why no-reply addresses exist? Dump incoming mails to that address into the æther or just use an Email as a Service-provider to send such mass-mail and let them deal with potential returning crap so you don't have to deal with it.

@bonki commented on GitHub (Mar 22, 2018): That's why no-reply addresses exist? Dump incoming mails to that address into the æther or just use an Email as a Service-provider to send such mass-mail and let them deal with potential returning crap so you don't have to deal with it.