From 6e70f28ccbd5afc1506f71f013278a9d157ef03a Mon Sep 17 00:00:00 2001 From: Prefetch Date: Thu, 27 Oct 2022 20:40:09 +0200 Subject: Optimize last images, add proof template, improve CSS --- source/blog/2022/email-server-revisited/index.md | 4 +--- .../2022/email-server-revisited/microsoft-bounce.avif | Bin 0 -> 12188 bytes 2 files changed, 1 insertion(+), 3 deletions(-) create mode 100644 source/blog/2022/email-server-revisited/microsoft-bounce.avif (limited to 'source/blog/2022/email-server-revisited') 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: - - - +{% 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 Binary files /dev/null and b/source/blog/2022/email-server-revisited/microsoft-bounce.avif differ -- cgit v1.2.3