-
Notifications
You must be signed in to change notification settings - Fork 28
Open
Description
I realized the static postfix map we were using locally hadn't been updated in a while, so I generated a new one from git and compared them and discovered that we had made some updates that weren't in the upstream map. I will list them below, but first I think we should consider if there are reasons to still maintain this file over using the SRV method.
- calyx.com moved to v3: kz4bswvhrqufq7e3ntwtco7jwgrpwwmh5j5kvlbonogt7xoipzwfedyd.onion (SRV record still points to the v2)
- calyxinstitute.org moved to v3: kz4bswvhrqufq7e3ntwtco7jwgrpwwmh5j5kvlbonogt7xoipzwfedyd.onion (SRV points to the v3)
- potager.org moved to v3: smsriptlensuwrolqrqp3sqhqpuovc4fg7n2q3l3b6dq3owgrv6c26yd.onion (but no SRV record)
- espora.org v2 record dropped (no SRV, no answer on v2)
- espiv.net moved to v3: jcifdulylocooyez2fh32i53kdo66d7tq7fotdc7lw6r2bgcb3rhjzqd.onion (SRV is CNAME for espiv.net? maybe a wildcard record? doesn't answer?)
- lists.espiv.net moved to v3: zo37k42zdy6n4lw22iamcy46rihir6t7d5imnrxcsyb7vmazvbjej2id.onion (no SRV, doesn't answer?)
- boum.org v2 record dropped (no SRV, no answer on v2)
If these domains want to keep doing onion-mx, make sure you are on v3 and publishing SRV records. Then we can either update the records in the map, or just drop them in the move to SRV only.
Metadata
Metadata
Assignees
Labels
No labels