What is important in e-mail testing - 10 points:
Sie sind hier
Some numbers you should know, when sending out e-mails:
When an e-mail template is used, the behaviour is monitored and the behaviour of all existing e-mails in our system.
There are such details like the opening and click numbers, or if the email was able to reach the recipient at all.
One useful information is the status code of the receiving mailserver:
For that we need to know how the way of the e-mail does look like:
When I know the e-mail itself looks ok, I go to a complete testing system and try to trigger the e-mail from there, with real data and think about special cases, like what happens if some optional data is there or not.
There I look into the logs, if some errors happened, because of some naming mismatch in the payload that should trigger the e-mail, or if some expected non optional data is missing.
When this is all ok, the e-mail is put to the live system and sometimes ramped up just to a part of users for some time in these stages:
We have 2 types of e-mails at the social business network company I current work with:
Why bother, it is just simple HTML, isn't it? What can possibly go wrong?
The best reason I heard, when starting working with e-mails, was from a colleague:
'You can not change an e-mail once it is sent out!'
You know the problem: You crafted a new shiny email for your customers and do not know how to test and what to look out for.
Send an email to email.mind.map at gmail.com and you get the newest copy;
If you have some additional points, feel free to comment
There exists a tutorial how to use the RePhone http://wiki.seeed.cc/RePhone/ with Mac OS X, but its lacking some comfort, lets push this a little further, but not to the end
Existing tutorial: https://github.com/Seeed-Studio/CodeLite_for_RePhone/wiki/building-RePho...
What is it missing?