So I hope I’m not wrong here… but I was under the impression from reading around that Amazon SES was the less expensive transaction email service.
Well, there was this cheaper option which is to rape Mxroute, but… @Jarland and @Miguel don’t really like that flavor.
So with was with a bit of surprise that I noticed that Elastic Mail is actually cheaper when in volume.
I think you got it all wrong. We were never meant to be the cheapest; we provide not only SMTP Relay Service as Outbound SPAM Filtering. Our offer is completely different than Amazon SES / Elastic Email which use SES anyway. Plus $7 USD per day for Premium Support, and $1 USD per GB of attachments, we dont do that. We provide 24/7 support and we dont bill extra for support or attachments.
Ahhhh I see what you mean. Yeah, dunno if they have some sort of custom setup though but the network is the same. I have read that they are indeed using SES.
Btw come to Leiria right now. I’ll pay you a few beers.
But the emails would go through Elastic Email’s system first and then through Amazon SES to be delivered, no? I can’t imagine they’ll just give you the SES credentials directly. And this is where reliability changes, it won’t be the same for (1) privacy and (2) perhaps uptime.
They won’t give the SES credentials, nor shoudl they need to.
In order to use their server you need to configure dkim and spf.
I think you using their systems as the relay to SES makes no difference in regards to what SES will be doing for your email. Because (do correct me if I’m wrong), with SPF and DKIM properly configured, their service acts like your email server.
If I use their system to send out emails, and those emails go through their system first before being delivered by SES, then it is a problem, as I’ve mentioned above due to privacy and uptime concerns.
Now, I haven’t used their service, so I can’t say how they really have it set up, but it’s hard to imagine that when sending out emails, those emails don’t go through their system first, cause how else would they even track your stats/quotas.
They may use something like mxroute uses, to deliver emails to gmail, outlook, … they use SES. For email addresses on custom domains, they may use ovh??
Thats most likely how it works yeah. But, not sure. I have never used their service so I should not even be commenting it, or say that they use SES or not. Speaking from what I have heard, not what I have tested. Nevertheless, its indeed cheap, but has cons too. Just like any other service.
In regards to what could be the setup, their MTA can provide the auth etc and manage the smarthosts. Eg, if its a Gmail address it gets delivered using SES, if not, it can be delivered from OVH IPs etc etc.
I actually work for Elastic Email so I can give you some information straight from the source.
Elastic Email is one of the few companies that have their own MTA (Mail Transfer Agent). So we don’t use Amazon or any other provider. Almost everything is done by us. We use several anti-spam systems. Deliverability rate is quite high when comparing to competitors. 8 years on the market gave us lot of experience. We are stable and reliable email service provider.
I don’t want to promote us, but you actually can create a free account, verify your domain and do some tests.
Heya Marcin, I hope you don’t mind me naging you a bit.
I’ve had an account with Mail Channels for quite a long time, never really used it to be honest.
One thing I don’t get is why the main account verified domains are visible to all sub accounts. The subaccounts seem to have all the features for your clients to resell your service, but then that odd thing…
To me what would make sense is for the main account (which would be your client) to be able to verify domains and assign them to subaccounts (as well as allow the subaccounts to verify their own domains).
What’s the thinking behind having the main account verified domains available to subaccounts?
Also, why not allow subaccounts to get access to your promo? (maybe tied them to different user accounts to avoid abuse, as in name, email, address details)
…why do you always inject the unsubscribe link/name/address? Why not give the option to the account admin to disable it?
