As the team is in the very early stages of this project, we want to get some initial technical thoughts on what is easy and what is difficult around sending emails. We know that Mediawiki already sends emails in a few ways, and we should get a sense of whether we would be changing an existing service, adding a new one, or something else.
Here are the very basic existing requirements around emails, which will change in the future, as the project becomes better defined:
- Include rich content.
- Be sent based on rules that incorporate welcome survey responses, edit history, and time.
- Allow people to unsubscribe - see T215743 and T215672
- Allow us to track opens and clicks.
- Allow us to track when they are replied to
- Have a noreply@ from address
For some examples of emails that we might want to send, see these slides (images to published on wiki during January 2019).
Completing this specific task means writing down thoughts either here or in some other document.
- Other standard metrics that are tracked by ESPs
- Sent - Number of emails that moved through the Email Service Provider’s sending mail server
- Delivered - Number of Sent emails that were not rejected by a receiving server
- Bounced - Sent emails that were rejected. There are two types of bounces:
- (a) Hard bounces are permanently rejected emails (e.g., due to invalid email address or the sender’s server has been blocked);
- (b) Soft bounces are temporarily rejected emails (e.g., due to recipient mailbox being full, server being down, message exceeding size limits. Repeated soft bounces → hard bounces.)
- Marked as Spam/Abuse rate - Number of recipients who reported the email as spam, divided by delivered emails