summaryrefslogtreecommitdiff
path: root/source/blog/2022
diff options
context:
space:
mode:
authorPrefetch2022-10-27 20:40:09 +0200
committerPrefetch2022-10-27 20:40:09 +0200
commit6e70f28ccbd5afc1506f71f013278a9d157ef03a (patch)
treea8ca7113917f3e0040d6e5b446e4e41291fd9d3a /source/blog/2022
parentbcae81336764eb6c4cdf0f91e2fe632b625dd8b2 (diff)
Optimize last images, add proof template, improve CSS
Diffstat (limited to 'source/blog/2022')
-rw-r--r--source/blog/2022/email-server-revisited/index.md4
-rw-r--r--source/blog/2022/email-server-revisited/microsoft-bounce.avifbin0 -> 12188 bytes
2 files changed, 1 insertions, 3 deletions
diff --git a/source/blog/2022/email-server-revisited/index.md b/source/blog/2022/email-server-revisited/index.md
index 4519bae..eb3fc18 100644
--- a/source/blog/2022/email-server-revisited/index.md
+++ b/source/blog/2022/email-server-revisited/index.md
@@ -181,9 +181,7 @@ 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:
-<a href="microsoft-bounce.png">
-<img src="microsoft-bounce.png" class="darkinv" style="width:100%">
-</a>
+{% 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,
diff --git a/source/blog/2022/email-server-revisited/microsoft-bounce.avif b/source/blog/2022/email-server-revisited/microsoft-bounce.avif
new file mode 100644
index 0000000..bc1c4f5
--- /dev/null
+++ b/source/blog/2022/email-server-revisited/microsoft-bounce.avif
Binary files differ