It seems I can't create such DNS record as it's not part of mailman.wmcloud.org and I don't have access to create DNS records in the zone of wmcloud.org. It is possible to create this DNS record? I made a web proxy for this but it wouldn't work as it wouldn't be able to route mail to the host. Type A would be great and I don't think MX would be needed. Thanks!
|Resolved||Security||None||T181803 Stop storing Mailman passwords in plain text|
|Resolved||None||T118641 Implement proper AAA for lists.wikimedia.org (mailman)|
|Resolved||None||T190054 List archives on lists.wikimedia.org is not mobile friendly|
|Resolved||None||T115329 "From" at start of line becomes ">From" in pipermail|
|Resolved||None||T52864 Upgrade GNU Mailman from 2.1 to Mailman3|
|Resolved||Ladsgroup||T258365 Setup Mailman3 in Cloud VPS|
|Resolved||bd808||T259444 Request for creating a DNS record for lists.wmcloud.org to 184.108.40.206|
As I recall with the meet project the project itself in OpenStack was named meet, therefore you automatically got a meet.wmflabs.org designate zone. Could get one for lists created too I guess (similar to the beta zone in deployment-prep). This way you could administer it without going through more tickets in future
lists.mailman.wmcloud.org would actually be "nicer" in our current DNS management setup. I don't quite understand the need for this testing system to have a particular hostname. Can you explain how that is needed for your testing? This is not a long term service you are building correct? Instead it is just a proof of concept and test platform for the Puppet role correct?
Herald re-added it :D
I wish it was this simple. mailman2 is drastically different than mailman3, For example, mailman2 stores everything as files (mails, settings) and it's already 200GB in production but mailman3 stores them in two different databases and we need to know what the size would be (T256538: Create test databases for mailman3) so I need to migrate a couple of fully public mailing lists from two to three to see how the size change.
Other bits that are weird are django handling of the domains:
or exim4 LMTP mail routing (See docs):
(tests.lists.wmcloud.org is actually email@example.com)
If I knew it beforehand, I would have gone with lists.mailman.wmcloud.org but now, If I need to fix it, I need rip everything apart and start again :( It's fine if it's in any way some hassle for you and I do everything again.
I made the record. Let's try to remember that it exists when it comes time to decommission this project. The record itself lives in the cloudinfra project. Cloudinfra is the owner of the wmcloud.org TLD for Designate (OpenStack's DNS service).
[19:45] < Amir1> bd808: sorry but one thing, gmail gave me this: "DNS Error: 29726073 DNS type 'mx' lookup of lists.wmcloud.org responded with code NXDOMAIN Domain name not found: lists.wmcloud.org" I thought if no MX record exists, it would fallback to A type record but I might be wrong