Changes between Version 9 and Version 10 of email-deliverability


Ignore:
Timestamp:
Nov 18, 2012, 11:37:14 PM (11 years ago)
Author:
Jamie McClelland
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • email-deliverability

    v9 v10  
    2828
    2929We should add:
    30  * Monitor for known mail.log strings that indicate blocking (I have a list already)
    31  * Checking for signs that a web site is compromised (not sure how to do this)
    32  * Check for signs on mail.mayfirst.org that a relay mail account has been compromised (e.g. certain number of messages sent per hour)
     30 * Monitor for known mail.log strings that indicate blocking (I have a list already): #831
     31 * Checking for signs that a web site is compromised (not sure how to do this): not assigned a ticket
     32 * Check for signs on mail.mayfirst.org that a relay mail account has been compromised (e.g. certain number of messages sent per hour): not assigned a ticket
     33 * Use [http://exchange.nagios.org/directory/Plugins/Security/check_dnsbl/details the check_dnsbl Nagios plugin]: #5736
    3334
    34 Jon says:
    35  * Perhaps use [http://exchange.nagios.org/directory/Plugins/Security/check_dnsbl/details the check_dnsbl Nagios plugin] ([ticket:5736 I suggested this before] but folks didn't want to because it wasn't in a Debian repo)
    36 
    37 == Pursue bulk mailer status for our email list servers ==
     35== Pursue bulk mailer status and apply for feedback loops for our email list servers with major mail providers ==
    3836
    3937Many providers allow us to apply for bulk mailer status. We should pursue this for assata.mayfirst.org and leslie.mayfirst.org, our two mailing list servers.
    4038
    41 == sign up for feedback loop with major providers ==
     39See [wiki:email-deliverability-status] for current status of our bulk mail and feedback loop applications.
    4240
    43  * #6314
     41Followed up in: #6314
    4442
    4543== Provide tools for release mailq back log ==
    … …  
    4745Although this runs the risk of getting more IP addresses blocked, it would nonetheless be useful if we had easy method for swapping out IP addresses easily to relieve a big mailq backlog. That could happen either by having multiple IP addresses assigned to each bulk mail server that could be swapped around with a command line tool and/or by temporarily relaying mail to a server in another cabinet (e.g. chun or femi or fela).
    4846
    49 == Current Status ==
     47== open deliverability tickets ==
    5048
    51 see [wiki:email-deliverability-status] for current status of these proposals.
     49=== Open Tickets tagged `blocklist` ===
     50[[TicketQuery(format=table,status=new|assigned,keywords=~blocklist)]]
     51