I manage several PBX systems and some of them the email works fine and some don’t/ After quite a bit of comparing settings and troubleshooting, I am unable to come up with a definite answer.
Does anyone have a solid solution using internal or external server for email with FreePBX?
We could end up going down all sorts of rabbit holes when it comes to email deliverability. Are the systems all using Outlook? What’s different and what’s the same about them?
System Admin > Notification Settings > From Address
Voicemail Admin > Settings > Email Config
Advanced Settings > Email “From:” Address
When I have come up against issues such as this, the first thing I do is use a known good email account to establish whether it’s the PBX or the way I’ve set things up.
Some providers are more fiddly than others. Getting email to just work will never not be satisfying! It seems that whenever it gets easier, recipient standards get harder to meet. MxToolbox is very useful.
Lastly, check you’re allowed to send mail over typical SMTP ports like 25, 465, 587. These ports are blocked by DigitalOcean, for example, and nothing you try will get round it. You need to use a mail relay service such as SMTP2GO, sending on port 2525 with TLS encryption and SASL authentication.
In the example you’ve posted, the PBX is successfully connecting on port 25 and the message is being accepted upstream, so that isn’t the problem on this system. For any of the others where email is failing, it’s still worth checking whether your hosting provider blocks outbound SMTP.
On the systems that work I have it set ot use an internal mail server and have the FQDN of hte pbx set adnd in DNS I have created a A ricord for the fqdn that points to the pbx. Several of those seem to work.
On a recent one that does not, I have been trying to get it to work with our iRedMail server we ue for notifications from several systems.
This is the sender and it’s being rejected. Ensure that’s a real mailbox or at least a forwarder, and change the Sender/From in all three places mentioned.
When you say the email does not work. What exactly are you referring to ?
the system never sends the email out ?
or the email is sent but the receiver never gets it ?
I looked up your email addresses on MXTOOLBOX (you really should not put peoples email in public view, fyi, this is not a secure site) The FROM address datacareadvanced.net was blacklisted
“If you are on the UCEPROTECTL2/L3, you have an IP address from your ISP that falls into a poor reputation range (i.e., the entire range of IP addresses is blocked as a result of the provider hosting spammers)”
We had a client that I set up their FreePBX System, and Microsoft just flat out refused to accept the emails from them from that system. We run our own email server at our place and what I ended up doing was creating accounts on our server for their 5 staff (dummy accounts), then forwarding everything that comes in directly to their email account hosted with microsoft. Basically creating a relay service, then auto deleting everything we forwarded.
Not the ideal way to do it, but it was a quick fix that worked.
So first thing I would do is test and verify emails to yourself from their server to see if you get them. You can verify they are going out and that “someone” can receive them. Verify the server you are using to send from is still not blacklisted someplace,
One thing worth adding to the checklist above: if the systems that fail are on different hosts/IPs, check the reverse DNS (PTR) record for each sending IP and make sure SPF/DKIM actually align with the domain in the From address. Postfix will happily accept and relay the message locally (which is why the log looks fine), but the receiving mail server can silently drop it later in its own filtering if the PTR doesn’t resolve or SPF fails, with no bounce ever coming back to the PBX. Comparing “dig -x ” output between a working box and a failing one is usually a quick way to spot the difference.