This page explains who publishes the MailTester blog, how its articles are produced, and how to tell us when something is wrong. It applies to every article on this blog.
Who publishes this blog
Articles here are published by the MailTester Editorial Team — the editorial group behind MailTester. That is a collective byline, not an individual writer. We use it because these articles are produced by a team process rather than written by one named person, and we would rather say so than attach a personal name to work a single person did not do.
Editorial responsibility for this blog rests with Achraf, the operator of MailTester, reachable at [email protected].
How articles are produced
Articles covering inbox placement, spam-score testing and SPF, DKIM and DMARC are researched and drafted with AI assistance, then checked against published sources — vendor documentation, published standards and specifications, and primary reference material — and edited before they go live. Where an article depends on a specific standard, vendor document or dataset, we link to it from the article so you can check it yourself rather than take our word for it.
We publish at volume. AI assistance is what makes that possible, and we would rather disclose it plainly here than let you discover it.
Older articles
This blog has a large archive, and some of it predates the process described above. We do not claim that every older article was produced or reviewed the way a new one is. Older articles are reviewed when we materially revise them and when a reader reports a problem with one.
Corrections
If you find an error — a broken example, an out-of-date figure, a misread specification, a recommendation that no longer holds — tell us and we will correct it or take it down. Email [email protected] with the article URL and what is wrong. We correct the article in place, and where a correction changes what the article actually concludes, we say so in the article rather than editing it silently.
What we do not claim
These articles are general technical and practical guidance. They are not legal, compliance or professional advice, and they are not a substitute for the official documentation of any product or standard we describe. Where we are uncertain, we try to say so in the article instead of writing around it.
Disclosure
This blog is published by MailTester, which sells a product in the field it writes about. Articles may mention or link to MailTester products. We are telling you that up front so you can weigh it.