Am 31.01.2014 16:45, schrieb KT Walrus: > I only have one domain for my mail addresses, e.g. usern...@domain.com. > > When I create a new account, should the userid be set to username and a > single alias created for usern...@domain.com for this userid? Is this the > best way to set up new accounts?
yes, or use the cli-utils
dbmail-users -h
*** dbmail-users ***
Use this program to manage your DBMail users.
See the man page for more info. Modes of operation:
-a user add a user
-d user delete a user
-c user change details for a user
-e user empty all mailboxes for a user
-l uspec list information for matching users
-x alias create an external forwarding address
Summary of options for all modes:
-w passwd specify user's password on the command line
-W [file] read from a file or prompt for a user's password
-p pwtype password type may be one of the following:
plaintext, crypt, md5-hash, md5-digest, md5-base64,
whirlpool, sha512, sha256, sha1, tiger
each type may be given a '-raw' suffix to indicate
that the password argument has already been encoded.
-P [file] pull encrypted password from the shadow file
-u user new username (only useful for -c, change)
-g client assign the user to a client
-m max set the maximum mail quota in <bytes>B,
<kbytes>K, or <mbytes>M, default in bytes
specify 0 to remove any mail quota limits
-s alia.. adds a list of recipient aliases
-S alia.. removes a list of recipient aliases (wildcards supported)
-t fwds.. adds a list of deliver-to forwards
-T fwds.. removes a list of deliver-to forwards (wildcards supported)
Common options for all DBMail utilities:
-f file specify an alternative config file
-q quietly skip interactive prompts
use twice to suppress error messages
-n show the intended action but do not perform it, no to all
-y perform all proposed actions, as though yes to all
-v verbose details
-V show the version
-h show this help message
> I see the aliases table has a column called client_idnr. What is this column
> used for?
AFAIK that is not in the default scheme
the unuseable http://library.mobrien.com/dbmailadministrator/ is using it
and that is what i took as reference between aliases, users and domains
with a own metatable so that i can select users by that id to list the
one from a specfific domain with fast queries
but you need to hold that in sync in your own code
> I also want to set up IMAP/POP3 access to allow only IMAP/POP3 for a certain
> group of users, and deny IMAP/POP3 access to all others except from a
> Roundcube
> Mail installation on my website. I assume I can do this using Usermaps
> feature,
> but I’m having a little difficulty understanding the best way to set this up.
sorry, don't know
> Lastly, I want to have an admin IMAP user that can login (only from
> localhost) and access/update/create/delete
> mailboxes for any existing user using IMAP. What is the best way to set this
> up?
> I’ve been assuming I need to set up an ACL for each user mailbox to allow the
> admin user access, but I don’t
> think this will allow the admin user to create/delete mailboxes (and
> autosubscribe the user to them).
> Is there a way to set up a wildcard ACL (mailbox id 0?) to allow access to
> the admin user to all mailboxes?
do not setup such users, i don't know if it is possible
but even if don't do that - solve that in a admin backend
no reachable from the web by directly interact with the DB
i have implemented that, but it's deeply in our CMS/Library code burried
so i can't publish source codes :-(
signature.asc
Description: OpenPGP digital signature
_______________________________________________ DBmail mailing list DBmail@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
