A BUGNOTE has been added to this bug. ====================================================================== http://www.dbmail.org/mantis/bug_view_advanced_page.php?bug_id=0000006 ====================================================================== Reported By: Dead2 Assigned To: ====================================================================== Project: DBMail Bug ID: 6 Category: IMAP daemon Reproducibility: always Severity: feature Priority: normal Status: acknowledged ====================================================================== Date Submitted: 09-Jul-04 11:57 CEST Last Modified: 15-Oct-04 18:25 CEST ====================================================================== Summary: Access control for IMAP Description: In my setup I want only certain people to be allowed to use the IMAP service. I suggest we set up a flag for this in the database.
acl->can_imap ? ====================================================================== ---------------------------------------------------------------------- Dead2 - 09-Jul-04 11:59 CEST ---------------------------------------------------------------------- Actually, this should be added to pop3 and optionally webmail aswell. Since an ISP might want to disable a users access to his mailbox if he does not pay. But they might not want to delete the user or disable incoming mails. ---------------------------------------------------------------------- ilja - 09-Jul-04 14:11 CEST ---------------------------------------------------------------------- This can be done by adding the following fields to the users table: can_imap (obvious) can_pop (obvious) can_sieve (is allowed to have sieve scripts (for later, when Sieve is implemented) etc? ---------------------------------------------------------------------- aaron - 15-Oct-04 18:25 CEST ---------------------------------------------------------------------- With this response, let's pop over to the mailing list for a little while. But, I'm thinking, columns strikes me as a bad idea. It means a database upgrade for every new feature that we might want to control. Instead, we can add a permissions table that grants or removes privileges to the various daemons. With client_idnr in the mix, we can do things like say, "Client X pays for POP3, Client Y pays for IMAP and Client Z pays for both." We should consider how/if this will interact with the user account and client account suspensions feature that has been so often requested. Bug History Date Modified Username Field Change ====================================================================== 09-Jul-04 11:57Dead2 New Bug 09-Jul-04 11:59Dead2 Bugnote Added: 0000001 09-Jul-04 14:11ilja Bugnote Added: 0000002 09-Jul-04 14:11ilja Status new => acknowledged 09-Jul-04 14:11ilja Bug Monitored: ilja 15-Oct-04 18:25aaron Bugnote Added: 0000314 ======================================================================
