The mailman3 mail processing sub-system providing the various queue runners, etc.
- ops ›
This charm deploys and manages the "Mailman Core" component of mailman3. "Mailman Core" or "Core" is the main engine that is responsible for handling emails. It does all the tasks of managing users, subscriptions, mailing lists, email addresses, talking to the MTA etc. However, the things that it doesn't manage include user authorization & user authentication.
However, users can manage their settings using email based commands which includes subscribing, unsubscribing, changing a few basic settings for their accounts etc.
Most functionalities in Core can be accessed using an administrative REST API which provides full control over the Core. Core expects the clients that consume this API would take up the responsibility of authenticating and authorizing users and provide interfaces for them to manage their settings and subscriptions.
- (string) Map various aliases to existing mailing lists. e.g. firstname.lastname@example.org email@example.com
- (boolean) Enable Spamassassin mail filter
- (boolean) Enable Postfix SPF extensions
- (string) Enable strict hostname checks in smtpd_recipient_restrictions. Set to "true" to enable, or "test" to enable checks in test mode. Test mode will prefix the restrictions with warn_if_reject, so that potential rejections will appear in the server logs but won't actually reject messages.
- (string) Space separated list of extra deb packages to install.
- (string) Use specified hostname/mailname.
- (string) List of signing keys for install_sources package sources, per charmhelpers standard format (a yaml list of strings encoded as a string). The keys should be the full ASCII armoured GPG public keys. While GPG key ids are also supported and looked up on a keyserver, operators should be aware that this mechanism is insecure. null can be used if a standard package signing key is used that will already be installed on the machine, and for PPA sources where the package signing key is securely retrieved from Launchpad.
- (string) List of extra apt sources, per charm-helpers standard format (a yaml list of strings encoded as a string). Each source may be either a line that can be added directly to sources.list(5), or in the form ppa:<user>/<ppa-name> for adding Personal Package Archives, or a distribution component to enable.
- (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.
- (string) A comma-separated list of nagios servicegroups. If left empty, the nagios_context will be used as the servicegroup
- (string) The status of service-affecting packages will be set to this value in the dpkg database. Valid values are "install" and "hold".
- (string) Define a http(s) proxy in /etc/default/spamassassin This will add http_proxy and https_proxy environment variables in Spamassassin's /etc/default file and allow sa-update cronjob to update rulesets though a http(s)_proxy. A valid entry would be http://proxy.host.name:3128
- (string) E-mail used by mailman for e-mail verifications etc.
- (string) Custom Spamassassin policies
- (string) Custom SPF configuration
- debugLevel = 1 defaultSeedOnly = 1 HELO_reject = SPF_Not_Pass Mail_From_reject = Fail PermError_reject = False TempError_Defer = False skip_addresses = 127.0.0.0/8,::ffff:127.0.0.0/104,::1/128
- (string) Override SSL/TLS certificate, defaults to empty which uses the snakeoil
- (string) Override SSL/TLS key, defaults to empty which uses the snakeoil
- (string) Policy map to enforce TLS/SSL