Hello, Ryan Butler made a patch for older 1.x series code (probably around 1.0, maybe a little prior) that was a simple enable/disable bit. You could find his patch in dbmail list archives (and he used to have a web or ftp site with a few patches on it, including that one). He was planning on making it a more flexible capabilities type system that you could enable/disable various components on a per-account basis (eg. offer webmail to some users, pop3 to others, imap to others...). I don't know that it's been worked on any recently (nor if he still wishes to do so), but now would be a good time to stick it in 2.x, as it requires some schema changes, and 2.x is still accepting those. If Ryan's not in a position to work on that right now, I'd bet he'd be willing to share his notes w/ whomever would. He's helpful like that. :)
Jesse ---- Original Message ---- From: Brian Blood <[email protected]> To: <[email protected]> Subject: [Dbmail-dev] user account exists but disabled Sent: Sun, 25 Jan 2004 14:52:02 -0600 > any previous discussion on this? > > How is everyone handling accounts that are simply administratively disabled > from logging and/or receiving mail, but want to keep the "users" account > around? > > currently, the only way I see to do this is to change the passwd to > something totally unguessable. > > the user will get an authentication error, but is that the proper message > for this state? > > In our current primary mail server, we can have an account that will collect > mail, but the login is disabled. > > Trying to login (POP) with the correct name/pwd gives this error: > > -ERR [AUTH] login for this account is disabled > > > > Regards, > Brian > > _______________________________________________ > Dbmail-dev mailing list > [email protected] > http://twister.fastxs.net/mailman/listinfo/dbmail-dev > -- End Original Message -- -- Jesse Norell jesse (at) kci.net
