Changes between Version 22 and Version 23 of email-deliverability

Timestamp:

Sep 19, 2017, 4:21:00 PM (7 years ago)

Author:

Jamie McClelland

Comment:

--

email-deliverability

@@ -15 +15 @@
 == Use bulk.mayfirst.org ==
 
-All web sites that send bulk email (e.g. CiviCRM) should be configured to relay through bulk.mayfirst.org (assata) which will relay via our [wiki:bulk-email-relay bulk email relay servers].
+All web sites that send bulk email (e.g. CiviCRM) should be configured to relay through bulk.mayfirst.org (assata) which will relay via our [wiki:bulk-mail-relay bulk email relay servers].
 
 By using our bulk mail relay servers, we ensure a high volume of legitimate email which offsets bad email.
@@ -29 +29 @@
 Via Nagios, we currently monitor the following:
 
+=== spambox deliveries ===
+
+If our email ends up in the spam box of any of the three major corporate providers, we get an alert.
+
+==== What do to ====
+
+See [wiki:filter-check filter-check] for more information on how to debug the problem.
+
 === mailq ===
 
 If the mailq goes over 200 messages on any server we get a warning and if it goes over 500 we get an alert.
 
-**What to do**
+==== What to do ====
 
 Run `mailq` to review the messages in the queue.
@@ -43 +51 @@
 If we have more than 20 blocked messages that fit a possible pattern of spam we get a critical alert.
 
-**What do to**
+==== What do to ====
 
 Run `mf-check-blocklist -b` to get a human readable report of the blocked messages.
@@ -53 +61 @@
 If a single sasl username relays more than 100 messages in a 24 hour period we get an alert.
 
-**What do to**
+==== What do to ====
 
 Run `mf-check-relayers` to see who is being reported. Try to determine if they are sending illegimate email.