4c4e27cb3a
This converts our existing puppeted mailman configuration into a set of ansible roles and a new playbook. We don't try to do anything new and instead do our best to map from puppet to ansible as closely as possible. This helps reduce churn and will help us find problems more quickly if they happen. Followups will further cleanup the puppetry. Change-Id: If8cdb1164c9000438d1977d8965a92ca8eebe4df
23 lines
903 B
Plaintext
23 lines
903 B
Plaintext
Mailing list subscription confirmation notice for mailing list %(listname)s
|
|
|
|
We have received a request%(remote)s for subscription of your email
|
|
address, "%(email)s", to the %(listaddr)s mailing list. To confirm
|
|
that you want to be added to this mailing list, simply reply to this
|
|
message, keeping the Subject: header intact. Or visit this web page:
|
|
|
|
%(confirmurl)s
|
|
|
|
Or include the following line -- and only the following line -- in a
|
|
message to %(requestaddr)s:
|
|
|
|
confirm %(cookie)s
|
|
|
|
Note that simply sending a `reply' to this message should work from
|
|
most mail readers, since that usually leaves the Subject: line in
|
|
the right form (additional "Re:" text in the Subject: is okay).
|
|
|
|
If you do not wish to be subscribed to this list, please simply
|
|
disregard this message. If you think you are being maliciously
|
|
subscribed to the list, or have any other questions, send them to
|
|
%(listadmin)s.
|