Tails

#2 Updated by intrigeri 2018-11-12 15:30:30

Some of these lists should be self-hosted while some others will be hosted at puscii.nl. Which ones exactly is under discussion.

Regarding email routing and DNS setup, initial rough draft:

• the MX for tails.b.o points to lizard
• the canonical address for lists hosted at lizard becomes tails.b.o * the canonical address for lists hosted at puscii becomes puscii.nl
• for backwards compatibility, the current @b.o addresses are redirected to the new ones; that would be set up wherever the b.o MX will point to, likely A/I; I’m not sure how best this would be implemented

#3 Updated by groente 2018-11-12 16:07:16

> * the MX for tails.b.o points to lizar
> * the canonical address for lists hosted at lizard becomes tails.b.o > * the canonical address for lists hosted at puscii becomes puscii.nl

migrating schleuder lists becomes a lot easier when you don’t change their name. that way, you won’t have to add identities to the PGP keys, which is probably going to be manual labour.

> * for backwards compatibility, the current @b.o addresses are redirected to the new ones; that would be set up wherever the b.o MX will point to, likely A/I; I’m not sure how best this would be implemented

instead of redirects, we can use transport maps to send the @b.o mail to the right server handling that particular list.

#4 Updated by intrigeri 2018-11-15 12:21:18

> migrating schleuder lists becomes a lot easier when you don’t change their name. that way, you won’t have to add identities to the PGP keys, which is probably going to be manual labour.

I’m not concerned about adding a few UIDs to a dozen keys or so.

>> * for backwards compatibility, the current @b.o addresses are redirected to the new ones; that would be set up wherever the b.o MX will point to, likely A/I; I’m not sure how best this would be implemented

> instead of redirects, we can use transport maps to send the @b.o mail to the right server handling that particular list.

Yeah, that was one of the options I had in mind when I wrote “redirected” :)

#5 Updated by intrigeri 2018-12-09 16:48:06

For now, we won’t change canonical addresses but will ensure the boum.org MX has aliases redirecting to the new hosting providers. Later on, if we get our own domain name or decide to postpone the topic for the foreseeable future, we might want to remove this layer of indirection in order to have one less point of failure (the boum.org MX): add UIDs to the GnuPG keys, make the new hosting location’s domain the canonical addres of the lists, and after a while drop the backwards compat aliases.

#6 Updated by groente 2018-12-09 17:04:07

intrigeri wrote:
> For now, we won’t change canonical addresses but will ensure the boum.org MX has aliases redirecting to the new hosting providers.

Just to be clear, we need transport maps, not aliases for hits.

The MTA where boum.org’s MX points to should have transport maps set for the schleuder lists which deliver (deliver, not forward) mail to the hosting provider. The hosting provider should accept mail for boum.org. Specifically, it should accept mail for the lists it hosts and have a transport map that delivers everything else to wherever boum.org’s MX points.

#7 Updated by intrigeri 2018-12-11 09:11:44

Thanks for the clarification. I’ve filed 2 subtasks to track the next steps :)