Also, what is the point of giving this service your AWS creds rather than them using AWS directly? Since they charge you anyway?
Presumably so that if/when the service gets abused and Amazon decides to ban the offending account, it doesn't take down absolutely everyone on their service.
So have the customer make the account, take advantage of the free 10k emails a month to claim a lower price.
I don’t see the point in it. I doubt there will be much customer service if problems happen. Maybe if you’re trying to launch a free newsletter or something but otherwise it’s worth paying for peace of mind and potential lost time. You don’t want to deal with emails not getting sent or issues with the service when you’re focused on growing your company.
For bigger businesses, the cost is solved - either by using their system, processes, and people, or the ROI is good enough to pay someone to do it for them.
You can make money if you can reliably deliver an email for < $x, which is not a trivial problem.
No details as to how. Am not sure this can be guaranteed.
Since that event, I've flipped the switch back to "snail mail" and will resist the constant nagging until they implement a paper fallback (i.e. notify by email first and if it's not paid within X weeks of deadline, fire off a paper notification).
Also, don't you check your spam folder? Or, do you just straight up delete everything once the "pile" gets too big?
Sounds like a "you" problem, not a delivery problem.
Mail Layer does seems to have a bit more features, so pick your tradeoff.
As for feedback on the page, the mobile design isn’t exactly broken but it does have a number of problems. It’s so squished at the top it reads:
Mail
Documentation
Layer
the legal system uses certified mail as a proxy for this and digitally there is nothing better
This is just a high markup for something you have open source equivalents of.
Where’s the high markup?
the web site makes you get down the page, then open up FAQs to really understand how the pricing works.
It tells you what you’ll pay to them, but you’ll also be charged by AWS at the AWS rate (this is stated later in the FAQ, but the blatant marketing lie really grinds my gears)
The solo tier lists $12, but would actually be $17.
One recommendation would be to use have customers create an IAM role and use cross-account role assumption to access SES on their behalf. That way you don’t have to deal with handling long-lived credentials
We use listmonk, extremely flexible and lightweight as well! I want to try to build a Hubspot integration to fetch contacts directly from Hubspot.