2017-11-02 21:05:12 +02:00
Mailu command line
==================
Managing users and aliases can be done from CLI using commands:
* alias
* alias_delete
* user
* user_import
* user_delete
* config_update
alias
-----
.. code-block :: bash
2018-11-08 22:35:41 +02:00
docker-compose exec admin flask mailu alias foo example.net "mail1@example.com,mail2@example.com"
2017-11-02 21:05:12 +02:00
alias_delete
------------
.. code-block :: bash
2018-11-08 22:35:41 +02:00
docker-compose exec admin flask mailu alias_delete foo@example.net
2017-11-02 21:05:12 +02:00
user
----
.. code-block :: bash
2018-11-08 22:35:41 +02:00
docker-compose exec admin flask mailu user --hash_scheme='SHA512-CRYPT' myuser example.net 'password123'
2017-11-02 21:05:12 +02:00
user_import
-----------
primary difference with simple `user` command is that password is being imported as a hash - very useful when migrating users from other systems where only hash is known.
.. code-block :: bash
2018-11-08 22:43:05 +02:00
docker-compose run --rm admin python manage.py user --hash_scheme='SHA512-CRYPT' myuser example.net '$6$51ebe0cb9f1dab48effa2a0ad8660cb489b445936b9ffd812a0b8f46bca66dd549fea530ce'
2017-11-02 21:05:12 +02:00
user_delete
------------
.. code-block :: bash
2018-11-08 22:35:41 +02:00
docker-compose exec admin flask mailu user_delete foo@example.net
2017-11-02 21:05:12 +02:00
config_update
-------------
2018-03-01 18:49:30 +02:00
The sole purpose of this command is for importing users/aliases in bulk and synchronizing DB entries with external YAML template:
2017-11-02 21:05:12 +02:00
.. code-block :: bash
2018-11-08 22:35:41 +02:00
cat mail-config.yml | docker-compose exec admin flask mailu config_update --delete_objects
2017-11-02 21:05:12 +02:00
where mail-config.yml looks like:
.. code-block :: bash
users:
- localpart: foo
domain: example.com
password_hash: klkjhumnzxcjkajahsdqweqqwr
hash_scheme: MD5-CRYPT
aliases:
- localpart: alias1
domain: example.com
destination: "user1@example.com,user2@example.com"
without `` --delete_object `` option config_update will only add/update new values but will *not* remove any entries missing in provided YAML input.
Users
-----
following are additional parameters that could be defined for users:
* comment
* quota_bytes
* global_admin
* enable_imap
* enable_pop
* forward_enabled
* forward_destination
* reply_enabled
* reply_subject
* reply_body
* displayed_name
* spam_enabled
* spam_threshold
Alias
-----
additional fields:
* wildcard