Using AWS SES for marketing (EmailOctopus)?
I'm wondering if anyone here uses AWS SES for both their transactional and marketing emails, using something like EmailOctopus or MuxEmail on top of SES.
It seems great because it saves a lot of money over the traditional marketing mail services, and I only need something simple for now anyway. However, everything I read says don't mix your transactional and marketing senders or you'll impact your deliverability or get blocked or something else. My service heavily relies on transactional email so I can't risk that.
Thoughts?
Why not use different SES endpoints? e.g. US East for marketing and US Central for transactional. To be on the safe side I would be tempted to use a different domain for marketing.
I hadn't thought about using a different SES endpoint. I wonder if SES would allow it they already gave me grief during the account approval for this first endpoint because they know I had a separate SES account for a different side project, I don't know if theyd approve another new one so early.
I could definitely use a separate domain though, you mean send my transactional through mail@example.com and marketing through like mail@getexample.com?
A guy on here wrote a very good article about cold emailing and he recommends using two domains. Check it out https://www.indiehackers.com/post/cold-emailing-a-masterclass-5e67ef495f
Yeah exactly.
Given the popularity of email platforms like SES, Mailchimp and others, I would be surprised if the spam filters paid too much attention to the senders IP address. I imagine the domain itself is far more important.
I thought about using something like team@mydomain.com for transactional emails and team@mydomain-updates.com for marketing stuff.
Many services use Amazon SES, which allows them to offer competitive pricing. As you said, email octopus or https://mailpost.io/. I don.t see a problem to use these services.