Difference between revisions of "Network/Procedures/Maintain a listserv"
From Makers Local 256
< Network
(initial commit) |
m (moar moar resources) |
||
| (3 intermediate revisions by one user not shown) | |||
| Line 8: | Line 8: | ||
*** Someone does something vaguely spammy and some service has an overly quick trigger finger. | *** Someone does something vaguely spammy and some service has an overly quick trigger finger. | ||
** Possible solutions: | ** Possible solutions: | ||
| + | *** Heavily restrict the machines that can send mail from the shop. | ||
| + | *** Make it so random shop Internet traffic leaves on a different Internet address. | ||
*** [http://en.wikipedia.org/wiki/Sender_Policy_Framework SPF records]. This is implemented by the shop right now. | *** [http://en.wikipedia.org/wiki/Sender_Policy_Framework SPF records]. This is implemented by the shop right now. | ||
*** [http://www.dkim.org/ DKIM]. I believe this is finished implementation, but more testing is needed. | *** [http://www.dkim.org/ DKIM]. I believe this is finished implementation, but more testing is needed. | ||
| Line 16: | Line 18: | ||
* Other resources. | * Other resources. | ||
** [https://support.google.com/mail/answer/81126 How to not be sent to spam on gmail] | ** [https://support.google.com/mail/answer/81126 How to not be sent to spam on gmail] | ||
| + | ** Many links in [https://news.ycombinator.com/item?id=9231808 this thread] | ||
| + | ** [http://rfc-clueless.org/pages/listing_policy This dnsbl] is asinine but perhaps we should try not to be on it anyway. | ||
| + | ** [http://www.spamhaus.org/news/article/719/a-survival-guide-for-the-small-mail-server A Survival Guide for the Small Mail Server] | ||
Latest revision as of 01:02, 20 March 2015
This is more of an FYI than a howto or anything. Basically, it turns out that mail providers are becoming more and more paranoid as mail gets less and less usable due to spam. As a result, ML256 has had some trouble actually delivering mail to people who are members of its lists. I'll try to summarize possible problems and solutions here.
- We get onto spam blacklists.
- For the shop, this can be checked here: http://bgp.he.net/ip/24.96.165.230#_rbl
- This could happen for several reasons.
- Mail spoofed as from the shop.
- Someone's machine at the shop actually sends spam (because it has malware or some other reason).
- Someone does something vaguely spammy and some service has an overly quick trigger finger.
- Possible solutions:
- Heavily restrict the machines that can send mail from the shop.
- Make it so random shop Internet traffic leaves on a different Internet address.
- SPF records. This is implemented by the shop right now.
- DKIM. I believe this is finished implementation, but more testing is needed.
- DMARC. We're not here yet.
- People click that we are spam and then their mail provider starts to believe it.
- Possible solutions:
- List-Unsubscribe header. This may actually redirect the "Report spam" button in Gmail to an automatic unsubscribe process! This would be ideal.
- Possible solutions:
- Other resources.
- How to not be sent to spam on gmail
- Many links in this thread
- This dnsbl is asinine but perhaps we should try not to be on it anyway.
- A Survival Guide for the Small Mail Server
