summaryrefslogtreecommitdiff
path: root/source/blog/2022/email-server-revisited
diff options
context:
space:
mode:
authorPrefetch2023-01-01 16:40:56 +0100
committerPrefetch2023-01-01 17:02:29 +0100
commitb1a9b1b9b2f04efd6dc39bd2a02c544d34d1259c (patch)
tree1fd87919deee17e58f8ad19c09abd54bd4a70886 /source/blog/2022/email-server-revisited
parent1d700ab734aa9b6711eb31796beb25cb7659d8e0 (diff)
Change license, add Makefile, add image caching control
Diffstat (limited to 'source/blog/2022/email-server-revisited')
-rw-r--r--source/blog/2022/email-server-revisited/index.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/source/blog/2022/email-server-revisited/index.md b/source/blog/2022/email-server-revisited/index.md
index eb3fc18..20eff24 100644
--- a/source/blog/2022/email-server-revisited/index.md
+++ b/source/blog/2022/email-server-revisited/index.md
@@ -181,7 +181,8 @@ One day, I tried to send an email to an Outlook-based account,
and OpenSMTPD reported it had been unable to make the delivery,
because Microsoft had thrown an error:
-{% include image.html file="microsoft-bounce.png" width="100%" class="darkinv" alt="Bounce message due to error from Microsoft" %}
+{% include image.html file="microsoft-bounce.png" width="100%" class="darkinv"
+ alt="Bounce message due to error from Microsoft" %}
To their credit, they seem to be offering a way out.
This approach is reasonable: preventively ban high-risk IP ranges,