|
||
|
Hey, it's Pavel.
Every week I pick a topic, break down a problem, and send it to you. This week I want to present you something new I created.
For quite a while I wanted to build a place where I could collect all the email deliverability information I use myself.
Not just articles, but actual guides, technical references, explanations, common errors, checks, and things that I usually have to search for again when I am working on a problem.
So I built one.
It is still quite raw at the moment.
Some sections have much more information than others, there are things I want to restructure, and there are still a lot of topics which are missing completely. But I decided that there wasn't much point in waiting until everything was finished, because realistically it probably never will be.
Email deliverability changes all the time, and I am already updating the site almost every day.
At the moment I am adding more guides around Gmail, authentication, sender reputation, SMTP errors, infrastructure, complaints and troubleshooting, and I am also working on expanding it further into Outlook, Yahoo and other areas.
The idea is quite simple: if I come across something useful while working on a client problem, researching an issue, or testing something myself, I want to turn it into something that can also be useful to somebody else.
And this is where I would actually appreciate some help.
Search through it, open the guides, test the site, try the tools, and let me know when something doesn't make sense or doesn't work properly.
If you notice an error, an outdated explanation, a missing topic, or something which deserves a much deeper guide, tell me. At this stage that kind of feedback is probably more useful than anything else.
I would rather build this based on the actual questions people working with email have than simply keep adding articles because I think they might be useful.
Everything on the wiki is free and I intend to keep it that way.
There are still infrastructure and hosting costs behind it though, so I also added an option to support the project if you find it useful and want to help me continue developing it:
There is absolutely no requirement to do that. Using the wiki, sharing it, sending feedback or simply telling me what I should add next already helps.
This is still the first version.
There is a lot more I want to build into it.
Before You Go: Here's How I Can Help
Work with me directly — If you have a deliverability problem that needs fixing, I take on clients through Upwork. Audits, troubleshooting, ongoing support.
Start your newsletter on beehiiv — Send Point runs on beehiiv and I'm a beehiiv partner. If you're looking for a platform, get 20% off for 3 months with code PAVEL20OFF at beehiiv.com. I can help you with setup and migration, just reply to that email if interested.
Stay in the loop — Issues go out weekly. Each one covers a specific deliverability problem: concrete signals, concrete fixes. Forward this to someone who needs it.
— Pavel
