Mailing lists http and smtp

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Greetings. 

So, we are getting closer to rolling out some hyperkitty goodness for
production. Now we need to determine how we want to manage the rollout
from a techincal angle. 

First, some history/description of how our current lists work:

HTTP/HTTPS:

Requests to admin.fedoraproject.org/mailman are proxied from any proxy
to collab03 (located at osuosl).

lists.fedoraproject.org is just a A record directly pointing to
collab03, so requests go direct to it. 

SMTP:

incoming: 

lists.fedoraproject.org has MX for our 3 smtp-mm machines. They are
located in 3 places around the globe. They accept emails for lists and
relay them to collab03. If collab03 is down or they can't reach it,
they simply queue and wait. 

outgoing: 

collab03 relays everything to bastion01. bastion01 sends the emails
out. This I think is to make sure all *.fedoraproject.org emails come
from the same ip address and don't shift around. 

(Note that the path for non lists emails is a bit different). 

So, my hyperkitty migration plan: 

1 Figure out how to get http and smtp to it with NO disruption of
  existing urls and emails. 
2 Setup test list and do some testing.
3 Once that looks good, move on to migrating a list over (this list
  perhaps :) 
4 Then, migrate a bunch more opt-in. 
5 Then, set a sunset date on the old setup and migrate the rest. 

Options for item 1: 

1) Setup forwards on collab03 for any lists going to mm3 and setup
httpd redirects for admin.fedoraproject.org/mailman/*listname* and
lists.fedoraproject.org/mailman/*listname*.

This means a lot of monkeying with the config and apache redirects are
sometimes very fragile. 

2. Make a new 'mailman3.fedoraproject.org' hostname, set smtp-mm's to
accept for it and send on to mailman01/02. Setup proxies to proxy
mailman3 into mailman01/02. 

This makes it nice and seperate, but means list names change? 

3) Hybrid: Setup mailman3.fedoraproject.org for the web interface only,
use forwards for the smtp side. 

This means list names could stay the same, but web interface is
different. Might confuse people where a list web interface is. 

4) Your brilliant plan here. ;) 

Thoughts?

kevin

Attachment: signature.asc
Description: PGP signature

_______________________________________________
infrastructure mailing list
infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/infrastructure

[Index of Archives]     [Fedora Development]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]

  Powered by Linux