New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
So you are using Cloudflare Email Routing too?
Yeah. Cloudflare for in, Mailjet for out.
Cool. Did you have to wait for a review of your Mailjet account?
No. Just signed up with my custom email as I thought otherwise it could lead to verification delay.
Similarly, SendinBlue gives 300/day. I've had issues with these platforms landing emails under "Promotions" in Gmail though. (at least it's better than spam!)
Though, if you have any shared hosting provider, they probably have pretty decent deliverability -- many use MailChannels, mail.baby, etc.
The best deal of all is probably to get the cheapest lifetime plan from MikePT and send from that. I think it's like $15 one time or something.
The free-with-domain OVH email is also popular. Though, it lacks dkim. The free email with gandi does have it. That's pretty decent. It has sieve support too.
Same, my mails either went as spam or marketing. That's why I stopped using the third party bulk mail providers.
pobox.com didn't have this issue but it is $20/year.
If you need send, you could use mutant mail, their ltd is on appsumo.
Does a shared hosting with MailChannels have same issues with SendinBlue or worse?
I am planning to make simple queue to avoid abuse when using Mxroute to send my transaction email.
Mxroute limits 300 mails per hour so it seems to be much better than the above services.
Is there any self-hosted mail system that can limit send per hour and use Mxroute as actually mail service?
After searching LET, look like ZeptoMail is a much better choice. $2.5 for 10k mail, valid for 6 months. Cheaper than a Mxroute 10GB promo
This conversation is about personal email. Transactional mail providers are a sensible choice for transactional mail.
Yeah, we have quite a few customers using MyW for that, which is OK, we're currently delivering over 200k emails/mo.
I am using WP Mail SMTP plugin and my mailer is Google / Gmail.
Automated WordPress email now goes through Gmail. Suppose, If anyone
register on my website, login info sent from [email protected]
Now, if I follow this tutorial https://improvmx.com/guides/send-emails-using-gmail/ , will these automated WordPress email send from
[email protected]?
Seems like they are just selling selfhosted AnonAddy?
For ~20 years, I sent and received email from my own domain, but used the local ISP for SMTP send and POP3 receive.
My email addresses in the domain were forwarders with two levels of indirection. The first level of inbound email went to a common forwarder in the domain, and that forwarder sent the email to the email address at the local ISP. When I moved or otherwise changed ISPs, all I had to do was change the one forwarder to point to the new ISP account. It was simple, fast, and elegant.
Sending email was a matter of sending from the domain-email address, but authenticating to the SMTP server using the local ISP email account username and password. It just worked ... for a long time. The email looked like it came from my domain, and replies were properly addressed to my domain, but outbound email was sent from my local ISP.
I started doing it that way at a time when ISPs did not let you keep your email address when you moved, switched ISPs, or otherwise cancelled their services. Many friends used to complain bitterly about the hassles of switching email addresses with their family, friends, banks, etc. I would urge them to get their own domains and eliminate the problem, but for many, the idea was too much to grasp.
The problem with my method was that it is the same one used by spammers to pretend that an email is coming from your bank when it is actually comes from somewhere else. Over time, I started to get warnings from ISPs and hosting providers that the practice may not last and it was time to move to host email directly from my domains.
Despite the warnings, I kept up the practice for a long time. Eventually it became enough of a problem that I switched to sending and receiving email from my domain itself using shared hosting and now also MXroute. It was mostly inertia that kept me from moving to that better system.