When did commercial ESPs appear?

Still have a question, spotted an error, or have a better explanation or a source we should cite?

Commercial Email Service Providers (ESPs) appeared in the mid-to-late 1990s. Constant Contact launched in 1995, followed by AWeber in 1998, Mailchimp in 2001, and ExactTarget in 2000 (now part of Salesforce Marketing Cloud).

But before ESPs existed, companies sent marketing email from their own mail servers. That meant hiring engineers to manage infrastructure, manually handling bounce processing, and dealing with IP reputation directly. It worked fine at small scale, but when you needed to send to tens of thousands of people, you were on your own if something broke.

The first ESPs solved this by renting shared infrastructure. You uploaded your list, built your campaign in their interface, and they handled delivery. The trade-off: you shared IP reputation with every other customer on that platform. Shared IP sending meant your deliverability could tank if another customer on the same IP sent spam, but it also meant you didn't need a team of engineers to send email.

By the early 2000s, the ESP model had split into two tracks: marketing platforms (newsletters, campaigns, automation) and transactional ESPs (receipts, password resets, notifications). That's still the structure today.

Curious how ESPs evolved into the platforms we use now? Check out how email moved from local servers to the cloud.

Contributors

Who worked on this answer

Every name links to their profile. Every company links to their site. Real people, real accountability.

Ask an AI · tailored to your setup

Ask the AI: Should I run my own mail server or use an ESP?

I read this on the Email Almanac about "When did commercial ESPs appear": "Commercial Email Service Providers (ESPs) appeared in the mid-to-late 1990s. Constant Contact launched in 1995, followed by AWeber in 1998, Mailchimp in 2001, and ExactTarget in 2000 (now part of Salesforce Marketing Cloud). Before ESPs existed, companies sent marketing email from their own mail servers. That meant hiring engineers to manage infrastructure, manually handling bounce processing, and dealing with IP reputation directly. It worked fine at small scale, but when you needed to send to tens of thousands of people, you were on your own if something broke. The first ESPs solved this by renting shared infrastructure. You uploaded your list, built your campaign in their interface, and they handled delivery. The trade-off: you shared IP reputation with every other customer on that platform." Help me understand what this means for MY situation: 1. Should I be running my own mail server or using an ESP? 2. What are the real trade-offs between shared IP (cheaper, easier) and dedicated IP (more control, more responsibility)? 3. If I'm migrating from one ESP to another, what historical baggage should I be aware of? 4. What's the next step for me? --- My details (fill in what applies): - Current ESP or mail server setup: e.g. self-hosted Postfix, Mailchimp, SendGrid - Sending volume: e.g. 1,000/month or 50,000/month - Type of email: marketing campaigns, transactional, both - Technical resources: have in-house engineers / outsourced / no tech team - Current pain point: describe what prompted this question

Edit the yellow boxes, then send to the AI of your choice.