cdransf/coryd.dev-eleventy
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix: lint md files

Browse source
This commit is contained in:
Cory Dransfeldt 2023-03-27 18:12:49 -07:00
parent 7b21a5b384
commit 55b45b8305
No known key found for this signature in database
7 changed files with 43 additions and 36 deletions
Download patch file Download diff file Expand all files Collapse all files

10
src/posts/2022/migrating-to-fastmail.md
View file

@ -17,14 +17,14 @@ They also offer [extensive documentation](https://www.fastmail.com/help/domain_m
**MX:**
```
```text
example.com. IN MX 10 in1-smtp.messagingengine.com
example.com. IN MX 10 in1-smtp.messagingengine.com
```
**SPF:**
```
```text
@ TXT "v=spf1 include:spf.messagingengine.com -all"
```
@ -32,9 +32,9 @@ example.com. IN MX 10 in1-smtp.messagingengine.com
These will be specific to your domain and can be found and set as follows:
1. Login to your FastMail account and go to Options –> Virtual Domains (or Manage –> Domains for a family/business account).
2. Scroll to the bottom, and you’ll see a new "DKIM signing keys" section. For each domain you have, you’ll see a DKIM public key.
3. Login to your DNS provider, and create a new TXT record for each domain listed and use the value in the "Public Key" column as the TXT record data to publish.
1. Login to your FastMail account and go to Options –> Virtual Domains (or Manage –> Domains for a family/business account).
2. Scroll to the bottom, and you’ll see a new "DKIM signing keys" section. For each domain you have, you’ll see a DKIM public key.
3. Login to your DNS provider, and create a new TXT record for each domain listed and use the value in the "Public Key" column as the TXT record data to publish.
**Bonus points**