Changes between Version 22 and Version 23 of email-deliverability


Ignore:
Timestamp:
Sep 19, 2017, 12:21:00 PM (2 years ago)
Author:
Jamie McClelland
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • email-deliverability

    v22 v23  
    1515== Use bulk.mayfirst.org ==
    1616
    17 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].
     17All 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].
    1818
    1919By using our bulk mail relay servers, we ensure a high volume of legitimate email which offsets bad email.
     
    2929Via Nagios, we currently monitor the following:
    3030
     31=== spambox deliveries ===
     32
     33If our email ends up in the spam box of any of the three major corporate providers, we get an alert.
     34
     35==== What do to ====
     36
     37See [wiki:filter-check filter-check] for more information on how to debug the problem.
     38
    3139=== mailq ===
    3240
    3341If the mailq goes over 200 messages on any server we get a warning and if it goes over 500 we get an alert.
    3442
    35 **What to do**
     43==== What to do ====
    3644
    3745Run `mailq` to review the messages in the queue.
     
    4351If we have more than 20 blocked messages that fit a possible pattern of spam we get a critical alert.
    4452
    45 **What do to**
     53==== What do to ====
    4654
    4755Run `mf-check-blocklist -b` to get a human readable report of the blocked messages.
     
    5361If a single sasl username relays more than 100 messages in a 24 hour period we get an alert.
    5462
    55 **What do to**
     63==== What do to ====
    5664
    5765Run `mf-check-relayers` to see who is being reported. Try to determine if they are sending illegimate email.