SOLVED Debian 10 - Not sending emails

[Starburst]

So I switch to the dark side just for Incredible PBX 2021 on Debian 10.

Checked, sendmail is installed and running. But no emails are going out.

Mail Queue has Explanation Mark and says, "4 are queued on this machine, and have not been delivered"

3 are VM notifications and 1 so far is from AvantFax.

Port 25 is open at 1&1.
Also have added it to rules.v4

 

[wardmundy]

Add the Gmail piece as covered in the tutorial. Script to do it is in /root folder.

 

[kenn10]

Add the Gmail piece as covered in the tutorial.

AKA RTFM

 

[Starburst]

Add the Gmail piece as covered in the tutorial. Script to do it is in /root folder.

Was trying to send it to our main email like before on CentOS.
Upstream port 25 is open.
Didn't have to use Gmail.

 

[Starburst]

AKA RTFM

That's only a last resort...
If you ever see someone reading a manual, you know it's fubar...

 

[Starburst]

Found the fix.
Had to run dpkg-reconfigure exim4-config

Apparently on Debian, it only does local mail by default, you have to reconfigure it to allow remote mail.

Everything seems like it's working, except iptables looses it mind and forgets some rules I added.

 

[wardmundy]

Everything seems like it's working, except iptables looses it mind and forgets some rules I added.

Where and how did you add them??

 

[Starburst]

First did the normal:
(e.g.) sudo iptables -A OUTPUT -p icmp --icmp-type echo-reply -j ACCEPT

But then when I rebooted it wasn't saved, it was only a couple up arrows and enter, but then I edited /etc/iptables/rules.v4

PBX crashed last night around 10p, and I noticed the IP Phone was blinking because it couldn't reconnect.
Rules are still there in the file.

Debian is weird...

 

[ostridge]

edited /etc/iptables/rules.v4

Have a look in

 cat /usr/local/sbin/iptables-custom

that is where the custom additions reside.
There other custom scripts there also

ls -l /usr/local/sbin/iptables

so you may need to consider which is appropriate depending what you trying to do.

dont forget to restart this one includes the call for /usr/local/sbin/iptables-custom

/usr/local/sbin/iptables-restart

Regards

 

[wardmundy]

You’re really playing with fire by tinkering with the Incredible PBX security profile. Once you break it, you own it. It’s your phone bill.

 

[wardmundy]

Found the fix.
Had to run dpkg-reconfigure exim4-config

Apparently on Debian, it only does local mail by default, you have to reconfigure it to allow remote mail.

Everything seems like it's working, except iptables looses it mind and forgets some rules I added.

Actually, we don't support exim4 with Incredible PBX except on the Raspberry Pi platform. So... you've apparently wandered off the reservation. And that's perfectly fine unless, as here, you're seeking support for a product that doesn't work and that nobody knows you're using.

By the way, port 25 does NOT have to be open on your Incredible PBX firewall to send emails. That opens a potential attack surface on your PBX!

 

[ostridge]

port 25 does NOT have to be open on your Incredible PBX firewall to send emails

By the way you don't need any ports to be open on your router, except maybe if you actually want to open the 3 Knockd ports for port knocker; although that too is deemed insecure.

 

[Starburst]

Actually, we don't support exim4 with Incredible PBX except on the Raspberry Pi platform. So... you've apparently wandered off the reservation. And that's perfectly fine unless, as here, you're seeking support for a product that doesn't work and that nobody knows you're using.

By the way, port 25 does NOT have to be open on your Incredible PBX firewall to send emails. That opens a potential attack surface on your PBX!

I've been off the reservation for years...

In iptables I only enabled ICMP for Monitoring and and IP so the phones can connect.

This is being hosted in the cloud behind a firewall, so ports are locked down that way.
I prefer csf to fail2ban, but that's a whole other story and not relevant to the PBX.