ipng/ipng.ch
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Replace all post_url with Hugo ref blocks

Browse Source
This commit is contained in:
Pim van Pelt
2024-08-05 01:43:55 +02:00
parent c1f1775c91
commit a2f10236a3
56 changed files with 221 additions and 241 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
content/articles/2024-05-17-smtp.md
View File

@ -105,8 +105,7 @@ themselves will not need to do any DNSBL lookups, which is convenient because it
them behind a loadbalancer and serve them entirely within IPng Site Local. If you're curious as to
what this site local thing means, basically it's an internal network spanning all IPng's points of
presence, with an IPv4, IPv6 and MPLS backbone that is disconnected from the internet. For more
details on the design goals, take a look at the [[article]({% post_url 2023-03-11-mpls-core
%})] I wrote about it last year.
details on the design goals, take a look at the [[article]({{< ref "2023-03-11-mpls-core" >}})] I wrote about it last year.
#### Debian VMs
@ -259,7 +258,7 @@ this case for `chrma0` in R&uuml;mlang, Switzerland. However, when clients conne
let the server present itself as simply `smtp-out.ipng.ch`, which will also be its public DNS name
later, but put the internal FQDN for debugging purposes between parenthesis. See the `smtpd_banner`
and `myhostname` for the destinction. I'll load up the `*.ipng.ch` wildcard certificate which I
described in my Let's Encrypt [[DNS-01]({% post_url 2023-03-24-lego-dns01 %})] article.
described in my Let's Encrypt [[DNS-01]({{< ref "2023-03-24-lego-dns01" >}})] article.
***Authorization***: I will make Postfix accept relaying for those users that are either in the
@ -364,7 +363,7 @@ This allows OpenDKIM to sign messages for any number of domains, using the corre
Now that I have three of these identical VMs, I am ready to hook them up to the internet. On the way
in, I will point `smtp-out.ipng.ch` to our NGINX cluster. I wrote about that cluster in a [[previous
article]({% post_url 2023-03-17-ipng-frontends %})]. I will add a snippet there, that exposes these
article]({{< ref "2023-03-17-ipng-frontends" >}})]. I will add a snippet there, that exposes these
VMs behind a TCP loadbalancer like so:
```
@ -394,7 +393,7 @@ spot within IPng Site Local (which, you will remember, is not connected directly
There are three redundant gateways in IPng Site Local (in Geneva, Br&uuml;ttisellen and Amsterdam).
If any of these were to go down for maintenance or fail, the network will use OSPF E1 to find the
next closest default gateway. I wrote about how this entire european network is connected via three
gateways that are self-repairing in this [[article]({% post_url 2023-03-11-mpls-core %})], in case
gateways that are self-repairing in this [[article]({{< ref "2023-03-11-mpls-core" >}})], in case
you're curious.
But, for the purposes of SMTP, it means that each of the internal `smtp-out` VMs will be seen by