lists.apache.org

Archiving

To have PonEE archive emails, add the following alias to the subscriber list (should be done automatically when a list is created):

  1. for public lists: archive-asf-public@cust-asf.ponee.io
  2. for private lists: archive-asf-private@cust-asf.ponee.io

This should only be done for lists, Do not point aliases here, contact PonEE if you need to archive an alias.

Changes to lists (renames, public/private conversion etc)

Contact root@ponee.io with your request.


If an entire project is being renamed, please specify all the lists to be renamed, don't just say "foo.a.o -> bar.a.o". We may be able to see the private lists, but PonEE does not see them unless they snoop, and snooping is bad karma.


mail-relay.apache.org

Mail relay management

  1. Update https://github.com/apache/infrastructure-p6/blob/production/data/common/relayclients.yaml with the appropriate information.
  2. Ensure that the following configuration is in the nodefile:
postfix::server config
---
classes:
  - postfix::server

postfix::server::relayhost: '[mail-relay.apache.org]:587'
postfix::server::smtp_use_tls: true

...

hermes.apache.org

Mail relay management – Use of mail-relay.a.o preferred

add or remove IPs to hermes' relay allow list

  1. edit https://svn.apache.org/repos/infra/infrastructure/qpsmtpd/config/relayclients locally and commit.
  2. update https://github.com/apache/infrastructure-p6/blob/production/data/common/relayclients.yaml
  3. as root, svn up the following directories on hermes:
    1. /usr/home/smtpd/qpsmtpd-private/config
    2. /usr/home/smtpd/qpsmtpd/config/relayclients
  4. For the changes to take effect, restart qmail-smtpd and qmail-send:
Restart Qmail Services
as root:
svc -t /var/service/qmail-smtpd-private
svc -u /var/service/qmail-smtpd-private
svc -t /var/service/qmail-send
svc -u /var/service/qmail-send

Replacing Mail Relays

  1. Create a second mail relay using the above process.
  2. Make sure that mail-relay is not pointed at the mailrelay you're replacing.
  3. Turn off / rename (or delete) / disable networking for the mailrelay you're replacing – Currently (6/3/20 – dfoulks) it is easier to rename and re-ip the mailrelay servers due to how p6 is configured
  4. rename the new mailrelay host to assume the name of the replaced host. don't forget:
    1. hostnamectl set-hostname
    2. /etc/hosts
    3. virtualization provider rename
  5. Assign the private / provider IP of the replaced host to the new mailrelay server (this is hard referenced in many places)
  6. Test the mail relay server as its new identity (relay your mail through it (gmail instructions))
  7. Once you've renamed the host, clean up.
    1. remove the DNS entry for the host that assumed the role of mailrelay1
    2. ensure that you clean up the puppet cert
      1. puppet node clean <old certname> 
      2. puppet node deactivate <old certname>
      3. delete the /etc/puppetlabs/puppet/ssl directory
      4. delete the /opt/puppetlabs/puppet/cache directory
      5. re-register the puppet agent. 
    3. follow the above process to remove the relay from the configuration.