Merge remote-tracking branch 'wiki/master'

howto/rt.md

@@ -294,11 +294,8 @@ Or like this:
 
 In this case, it means a RT admin disabled the user in the web
 interface, presumably to block off a repeated spammer. The bounce is
-harmless, but noise can be reduced by adding it to the server-level
-block list, in the `senderaccess` map in `profile::rt`. Beware that
-the map only checks the "envelope from" (the email provided in the
-`MAIL FROM` line during the SMTP session, visible as the `Return-Path`
-header, typically), not the `From`.
+harmless, but noise can be reduced by adding the sender to the denylist
+in the `profile::rspamd::denylist` array in `data/common/mail.yaml`.
 
 See Also [issue 33314](https://gitlab.torproject.org/tpo/tpa/team/-/issues/33314) for more information.
 

service/email.md

@@ -503,6 +503,17 @@ run the timer by hand:
 Note that the normal value is `1`, not `0`, as the script counts
 `/var/mail` itself as a file.
 
+## Deal with blocklists
+
+Sometimes we end up on blocklists. That always sucks. What to do depends on
+who's blocking. Sometimes there'll be a contact address in the bounce message.
+Let's try to collect our experiences per provider here:
+
+### Microsoft
+
+You can request delisting here: https://olcsupport.office.com/ , you need a microsoft account to do so.
+They should get back to you soon to resolve the situation, if needed you can contact them on outlooksupport@microsoftsupport.com
+
 ## Disaster recovery
 
 N/A. The server should be rebuildable from scratch using the Puppet