14 Commits

Author SHA1 Message Date
Amy Marrich (spotz)
0dac2f3f87 Retire the Women-of-OpenStack list
As WoO is now part of the D&I WG this list is not needed.

Change-Id: I6af5f537357d3523aaa2d4b2e673296687e33a7d
2019-09-16 12:00:45 -05:00
James E. Blair
3199e3b225 Enable SPF checking on lists
This requires an external program and only works on Debian hosts.

Newer versions of exim (4.91) have SPF functionality built-in, but
they are not yet available to us.

Change-Id: Idfe6bfa5a404b61c8761aa1bfa2212e4b4e32be9
2019-06-07 10:34:33 -07:00
Jeremy Stanley
74649101f8 Blackhole spam for airship-discuss-owner address
The airship-discuss-owner address for lists.airshipit.org is now
besieged with a flood of unsolicited messages. Reject anything sent
to it with an SMTP error explaining the situation.

Change-Id: I19fcea2a502c41cc9438f2710dae3cd686eecc05
2019-04-23 18:12:11 +00:00
James E. Blair
9e6db28ffb Save a copy of all messages to openstack-discuss
To debug DMARC issues, save a copy of every message sent to
openstack-discuss with as little manipulation as possible.

Change-Id: Ic1156849957bc326e9216c2aca0ab9d180e158e6
2019-01-23 11:19:00 -08:00
Jeremy Stanley
159f012d47 Reject messages to starlingx-discuss-owner
The owner address for the starlingx-discuss list on
lists.starlingx.io has started receiving large volumes of
unsolicited messages unrelated to its intended purpose. As there's
no easy way to discern them from legitimate messages, we'll do the
same as we've done for other owner addresses and reject them with a
brief error explaining the situation.

Change-Id: I95a910c2e6206098ca268a0e10e86b66455ad1bd
2019-01-02 19:40:15 +00:00
Jeremy Stanley
a507b6b401 Add lists.opendev.org to Mailman
Set up the initial boilerplate to enable addition of new
project-neutral Mailman mailing lists on lists.opendev.org.

Change-Id: I8cad4149bdd7b51d10f43b928cdb9362d4bde835
2018-12-13 20:36:08 +00:00
Jeremy Stanley
8017415779 Retire the interop-wg mailing list
This list's owners have asked for it to be shut down, as they will
be using an [interop-wg] tag on the new openstack-discuss ML for
future communication. Once this merges (so that Puppet won't
recreate it), the list can be removed with the `rmlist` utility
(this will still leave the archives available but will remove it
from the list index and no longer accept subscriptions/posts).

Set the old list address as an alias for the new openstack-discuss
ML so that replies to previous messages from the list will be routed
there for the foreseeable future.

Change-Id: Ib5fd5aece2465d569e0e7c180ee14ba94882f2b7
2018-11-30 18:39:16 +00:00
Jeremy Stanley
e9d49b4839 Shut down openstack general, dev, ops and sigs mls
The general openstack, openstack-dev, openstack-operators and
openstack-sigs mailing lists have been deprecated since November 19
and are slated to be removed on December 3. Merging this on that
date will ensure any further replies to messages from those lists
are rerouted to the new openstack-discuss mailing list for the
foreseeable future.

The openstack-tc list is included in this batch as it has already
been closed down with a recommendation to send further such
communications to the openstack-discuss ML.

Additionally remove the Puppet mailman resource for the
openstack-sigs ML so it won't be automatically recreated after it
gets deleted (the other lists predate our use of Puppet for this
purpose).

Clean up the corresponding -owner spam rejection aliases since these
addresses will no longer be accepting E-mail anyway.

Change-Id: I9a7fae465c3f6bdcf3ebbadb8926eb4feb8fad79
2018-11-30 18:22:00 +00:00
Ian Y. Choi
72781811aa Blackhole messages to openstack-ko-owner@l.o.o
The OpenStack Korean mailing list's owner address have
become overrun by the same mass spam we've seen hitting our other ML
owner addresses. Add a blackhole alias for it.

Change-Id: Ia6c7e6701a69ee56076062aa85f8699121648501
2018-11-29 02:23:35 +09:00
Jeremy Stanley
33ec337b42 Blackhole messages to openstack-sigs-owner@l.o.o
The OpenStack SIGS mailing list's owner address is starting to
become overrun by the same mass spam we've seen hitting our other ML
owner addresses. Add a blackhole alias for it.

Change-Id: Iefc5b5fa600c5d1de75d3302c8ddf0e1a03301e5
2018-11-19 16:16:33 +00:00
Jeremy Stanley
4fb2143f3c Blackhole messages to edge-computing-owner@l.o.o
The OpenStack edge-computing mailing list's owner address is
starting to become overrun by the same mass spam we've seen hitting
our other ML owner addresses. Add a blackhole alias for it.

Change-Id: I97a2db5d0565cc166604352e397f580ea2d9e767
2018-11-12 10:15:02 +00:00
James E. Blair
46a643f823 lists: run mailman verp router before dnslookup
The mailman verp router handles remote addresses like dnslookup.
It needs to run before dnslookup in order to be effective, so run
it first.  It's only for outgoing messages, not incoming, so won't
affect the blackhole aliases we have for incoming fake bounce
messages.

Note that the verp router hasn't been used in about a year due to
this oversight, so we should merge this change with caution.

Change-Id: I7d2a0f05f82485a54c1e7048f09b4edf6e0f0612
2018-10-16 13:04:13 -07:00
James E. Blair
40c6e6d7ad Template all exim routers
So that we can have complete control of the router order, always
template the full set of routers, including the "default" ones.
So that it's easy to use the defaults but put them in a different
order, define each router in its own variable which can be used
in host or group vars to "copy" that router in.

Apply this change to lists, firehose, and storyboard, all of which
have custom exim routers.  Note that firehose intentionally has
its localuser router last.

Change-Id: I737942b8c15f7020b54e350db885e968a93f806a
2018-08-16 13:49:55 -07:00
Monty Taylor
4cca3f8d2a
Add lists exim config to ansible
The mailing list servers have a more complex exim config. Put the
routers and transports into ansible variables.

While we're doing it, role variables with an exim_ prefix - since 'routers'
as a global variable might be a little broad.

iteritems isn't a thing in python3, only items.

We need to escape the exim config with ${if or{{ - because of the {{
which looks like jinja. Wrap it in a {% raw %} block.

Getting the yaml indentation right for things here is non-trivial. Make
them strings instead.

Add a README.rst file - and use the zuul:rolevar construct in it,
because it's nice.

Change-Id: Ieccfce99a1d278440c5baa207479a1887898298e
2018-08-15 15:11:48 -05:00