[GH-ISSUE #42] Why is there a separate userbase for the application? #38

New issue

Closed

opened 2026-02-26 09:35:21 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 09:35:21 +03:00

Owner

Originally created by @lweijl on GitHub (Jun 9, 2013).
Original GitHub issue: https://github.com/opensolutions/ViMbAdmin/issues/42

Hi there,

What's the reason for ViMbAdmin to have a separate user base for the application itself? I would like to be able to have a super admin account, which also has a mailbox within a domain and have that account be the domain admin of one or more domains within the system.

Besides that, it looks to me that the user base passwords for the application itself is MD5 hashed, while the mailbox passwords have the ability of a much more powerful encryption. Can anyone clarify this for me? I'm trying to figure out if this application is featured and secure enough for my needs.

Thanks in advance!
Lennart

Originally created by @lweijl on GitHub (Jun 9, 2013). Original GitHub issue: https://github.com/opensolutions/ViMbAdmin/issues/42 Hi there, What's the reason for ViMbAdmin to have a separate user base for the application itself? I would like to be able to have a super admin account, which also has a mailbox within a domain and have that account be the domain admin of one or more domains within the system. Besides that, it looks to me that the user base passwords for the application itself is MD5 hashed, while the mailbox passwords have the ability of a much more powerful encryption. Can anyone clarify this for me? I'm trying to figure out if this application is featured and secure enough for my needs. Thanks in advance! Lennart

kerem closed this issue

2026-02-26 09:35:21 +03:00

kerem commented

2026-02-26 09:35:22 +03:00

Author

Owner

@barryo commented on GitHub (Jun 10, 2013):

What's the reason for ViMbAdmin to have a separate user base for the application itself?

Many deployments are service provider based where a separate userbase is required.

I would like to be able to have a super admin account, which also has a mailbox within a domain
and have that account be the domain admin of one or more domains within the system.

A super admin can edit any domain so this functionality is available. I don't see the issue here?

Besides that, it looks to me that the user base passwords for the application itself is MD5 hashed

MD5 hashed with salt. See securitysalt parameter in the configuration file. V3 will move to configurable password hashing for admins with bcrypt as the default.

@barryo commented on GitHub (Jun 10, 2013): > What's the reason for ViMbAdmin to have a separate user base for the application itself? Many deployments are service provider based where a separate userbase is required. > I would like to be able to have a super admin account, which also has a mailbox within a domain > and have that account be the domain admin of one or more domains within the system. A super admin can edit _any domain_ so this functionality is available. I don't see the issue here? > Besides that, it looks to me that the user base passwords for the application itself is MD5 hashed MD5 hashed with salt. See `securitysalt` parameter in the configuration file. V3 will move to configurable password hashing for admins with bcrypt as the default.

kerem commented

2026-02-26 09:35:22 +03:00

Author

Owner

@lweijl commented on GitHub (Jun 10, 2013):

Thanks, that clarified a lot. I am having trouble creating mailboxes though. The creation seems to go okay, but the actual mailbox is never created on the filesystem. I'm assuming the mail user that is configured within the configuration file is the one that is used for these actions? Syslog nor any other log file is telling why the creation is failing..

I guess the question is, how does ViMbAdmin create mailboxes and their users on the filesystem and which applications/commands are used in the process? I guess I could look at the source code but this way anyone with this question/problem can find it.

@lweijl commented on GitHub (Jun 10, 2013): Thanks, that clarified a lot. I am having trouble creating mailboxes though. The creation seems to go okay, but the actual mailbox is never created on the filesystem. I'm assuming the mail user that is configured within the configuration file is the one that is used for these actions? Syslog nor any other log file is telling why the creation is failing.. I guess the question is, how does ViMbAdmin create mailboxes and their users on the filesystem and which applications/commands are used in the process? I guess I could look at the source code but this way anyone with this question/problem can find it.

kerem commented

2026-02-26 09:35:22 +03:00

Author

Owner

@barryo commented on GitHub (Jun 10, 2013):

I guess the question is, how does ViMbAdmin create mailboxes and their users on the filesystem

ViMbAdmin doesn't - Dovecot deliver or whatever LDA (local delivery agent) you are using does this. V2 is poorly documented on this aspect (which is why we refer you to PostfixAdmin docs as it's the same type of thing). V3 will be better documented and much more flexible in this area.

@barryo commented on GitHub (Jun 10, 2013): > I guess the question is, how does ViMbAdmin create mailboxes and their users on the filesystem ViMbAdmin doesn't - Dovecot deliver or whatever LDA (local delivery agent) you are using does this. V2 is poorly documented on this aspect (which is why we refer you to PostfixAdmin docs as it's the same type of thing). V3 will be better documented and much more flexible in this area.

kerem referenced this issue

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

[GH-ISSUE #249] Default Quota not populated when mailbox is created #201

kerem referenced this issue

2026-02-26 10:30:30 +03:00

[PR #38] [MERGED] Setting the quota for a mailbox will consider a set maxquota of the domain #261