mailman3 core #12

  • By hloeung
  • Latest version (#12)
  • bionic
  • Stable

Description

The mailman3 mail processing sub-system providing the various queue runners, etc.


Overview

Describe the intended usage of this charm and anything unique about how this
charm relates to others here.

This README will be displayed in the Charm Store, it should be either Markdown
or RST. Ideal READMEs include instructions on how to use the charm, expected
usage, and charm features that your audience might be interested in. For an
example of a well written README check out Hadoop:
http://jujucharms.com/charms/precise/hadoop

Use this as a Markdown reference if you need help with the formatting of this
README: http://askubuntu.com/editing-help

This charm provides service. Add a description here of what the service
itself actually does.

Also remember to check the icon guidelines so that your charm looks good
in the Juju GUI.

Usage

Step by step instructions on using the charm:

juju deploy servicename

and so on. If you're providing a web service or something that the end user
needs to go to, tell them here, especially if you're deploying a service that
might listen to a non-default port.

You can then browse to http://ip-address to configure the service.

Scale out Usage

If the charm has any recommendations for running at scale, outline them in
examples here. For example if you have a memcached relation that improves
performance, mention it here.

Known Limitations and Issues

This not only helps users but gives people a place to start if they want to help
you add features to your charm.

Configuration

The configuration options will be listed on the charm store, however If you're
making assumptions or opinionated decisions in the charm (like setting a default
administrator password), you should detail that here so the user knows how to
change it immediately, etc.

Contact Information

Though this will be listed in the charm store itself don't assume a user will
know that, so include that information here:

Upstream Project Name

  • Upstream website
  • Upstream bug tracker
  • Upstream mailing list or contact information
  • Feel free to add things if it's useful for users

Configuration

ssl_key
(string) Override SSL/TLS key, defaults to empty which uses the snakeoil
ssl_cert
(string) Override SSL/TLS certificate, defaults to empty which uses the snakeoil
nagios_servicegroups
(string) A comma-separated list of nagios servicegroups. If left empty, the nagios_context will be used as the servicegroup
nagios_context
(string) Used by the nrpe subordinate charms. A string that will be prepended to instance name to set the host name in nagios. So for instance the hostname would be something like: juju-myservice-0 If you're running multiple environments with the same services in them this allows you to differentiate between them.
juju
ssl_policy_map
(string) Policy map to enforce TLS/SSL
site_owner
(string) E-mail used by mailman for e-mail verifications etc.
admin@changeme.internal
hostname
(string) Use specified hostname/mailname.