#12037 Disable posts on mailman01.stg
Closed: Fixed 6 months ago by zlopez. Opened 6 months ago by kevin.

We should disable incoming email and web posts to lists.stg.fedoraproject.org.

Right now it's able to send to subscribers, but those subscriber lists may be out of date... ie, someone might have unsibscribed in prod but didn't know there was a staging version of that list.
Also it can be confusing to get a post from a stg list and not see it in prod, users may not know they need a seperate staging account, etc.

So, I think we should just comment the access for incoming emails on mm-smtp ansible and do something to disable auth on the archive side to prevent people from logging in/posting.

Then, if we need to test something we can re-enable it.

Or perhaps we could just send all outgoing emails to /dev/null... but then that could result in spam on the web side...


Metadata Update from @zlopez:
- Issue assigned to zlopez
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: low-trouble, medium-gain, ops

6 months ago

There are multiple ways, how we can do that:

  • Set the hyperkitty to DEBUG mode, which will disable sending e-mails from web UI
  • We can switch the whole mailman to devmode and not set any e-mail address to recipient, it should then just drop all the messages
  • We can create a firewall entry for bastion to just drop any incoming SMTP packet from mailman staging machine

I will do the first two and hopefully it will stop sending e-mails (I'm not sure if not setting the e-mail will work as it's not documented). I will test that.

Here is the PR for the change. I tested it locally on the machine and I wasn't able to sent message to and from the machine, so that should be enough.

Ah ha. I didn't know about debug. That sounds good... does that also prevent web posts via hyperkitty?

Both of them have debug settings that prevents them from sending actual e-mails. The PR addresses hyperkitty and mailman as well.

The change was merged and deployed now.

Metadata Update from @zlopez:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

6 months ago

Log in to comment on this ticket.

Metadata
Boards 1
ops Status: Backlog