mention upstreaming of my mailman patch

diff --git a/personal/_posts/2018-06-10-mailman-subscription-spam-continued.md b/personal/_posts/2018-06-10-mailman-subscription-spam-continued.md
index 4b92caf8a19952657da3de54207f5321c5013d1f..9809180d4362ca60ad4384a859af510d302df8da 100644 (file)
--- a/personal/_posts/2018-06-10-mailman-subscription-spam-continued.md
+++ b/personal/_posts/2018-06-10-mailman-subscription-spam-continued.md
@@ -178,3 +178,6 @@ successfully subscribe someone.  It is still a good idea to monitor the logs
 (`/var/log/mailman/subscribe` on Debian) to see if any illegitimate requests
 still make it through, but unless you site is really big I'd be rather surprised
 to see bots being able to answer site-specific questions.
 (`/var/log/mailman/subscribe` on Debian) to see if any illegitimate requests
 still make it through, but unless you site is really big I'd be rather surprised
 to see bots being able to answer site-specific questions.

+
+**Update:** With Mailman 2.1.30, this patch is now included upstream.
+The `CAPTCHAS` format is slightly different than above to support multiple languages; consult the Mailman documentation for further details. **/Update**