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.
How is Mail.Baby after no MailChannels use?
nqservices
Member
in General
Hi all,
It's now been some time since Mail.Baby stopped using Mailchannels as relay.
For people that are using, how do you rate the service since then? Any diference on terms of reliability and of course, delivery quality?
Thanks
Comments
It sucks, frankly. Baby just can't deliver that well. I'm sure in time it will get better, but it definitely needs something to lift it up.
Does Mail.baby offer insights into mail delivery reports similar to the Insights Console Mailchannels has?
@interservermike
Things are working out pretty well here. We do have reports in the dashboard including a deliverability report.
Isnt @labze using mail.baby?
I think some providers here also using it, maybe they can give some insights
I did try it out, and meant to share some feedback with @interservermike . Definitely easy to setup and use, however I did have mail landing in spam in gmail.
Could you please share a screenshot of the dashboard and an example deliverability report? Additionally, is this dashboard and report also accessible to customers of web hosts that use Mail.baby as their SMTP relay for shared web hosting packages?
PS. In my opinion, the Mail.baby website could benefit from some polishing.
I think dashboard and report is just available for the web host. I think Mailchannels also works that way. And maybe is for the best this way.
I think @jar uses mail.baby for MXRoute. Perhaps he can share his recent experiences.
It has been working great since the switch over. I highly recommend mail.baby
I had a cPanel Reseller Account at my previous host and had access to the MailChannels Insights dashboard for my domains. This was really helpful during troubleshooting, as cPanel's Mail Delivery Troubleshooter itself would always say 'Delivered' (yes, delivered/handed over to the SMTP relay...)
@jar runs his own servers afaik.
I do indeed. According to the stats around 45K mails are sent each month across all nodes and I rarely, if ever, receive any complaints with delivery issues.
I am not a commercial user. Have no idea how many of my sent messages end up in spam. the couple of bounces are probably when I was testing mail server. For me mailbably works good for the money
mailbaby works just fine.
works fine, but most of mail.baby emails going into spam folder of gmail
what benefit would it get?
You probably don't have spf or dmarc set up correctly.
That's been my experience. Gmail hasn't ever been an issue if SPF and whatnot is configured correctly.
Biggest pain point for me, having dealt with most of our mail tickets, was Outlook/O365 emails just getting blackholed. Shows delivered/accepted, and then it just never shows up in an inbox or spam box or anything.
There were a couple painful weeks, but things have been fairly chill.
The remaining mail tickets are mostly technical issues, or complaining that their outreach spam isn't going through when they BCC 30 addresses on every sales pitch.
Just curious what volume are we talking about?
~600-750k emails/mo
More customers. For example, the dashboard @jperkins shared looks very nice. Thanks for sharing
Hi,
Noticed on their website https://www.mail.baby/tips/spf/ that they have change the SPF record from the old one “relay.maybaby.net” to the new “spf-c.mailbaby.net”.
I’m still using the “old”. Does anyone knows if is equal to use any of them or if there is one that is recommended?
@interservermike
Thanks
No worries, both will work.
https://digwebinterface.com/?hostnames=relay.mailbaby.net spf-c.mailbaby.net&type=TXT&ns=resolver&useresolver=9.9.9.10&nameservers=
And it seems there is another SPF, that shows on their website homepage: "_spf-c.mailbaby.net"
So 3 different SPF in total:
relay.mailbaby.net
spf-c.mailbaby.net
_spf-c.mailbaby.net
The original spf will work, and continue to work.> @nqservices said:
The old one will still work you do not need to update to the new one.
What I would recommend for new set ups is using your own domain in an spf record, and including the mailbaby spf. That way there is one record to update if a change is ever needed rather than needing to update all domains.
For the spf record, is it possible to do any white labels? Such as using send.mixwp.com as spf for my customers.
You could copy and paste the contents of the Mail Baby SPF record into your own, but that's messy as you would need to check it constantly to see if Mail Baby has added any new IP's to the record.
Alternatively, you could setup a TXT record of send.mixwp.com with it's value of the Mail Baby SPF record and your customers then use send.mixwp.com as the SPF include. It's not completely white label because if someone looks up the record then they can see its value.
Actually, I don't need it to be fully white label, but it's always good to make customers see our own brand more