Install New hestiacp on hostinger after mails setup now we are getting lots of incoming emails blocked

Community Support Mail
1

SNI=mail.global-freight.co.in F=em rejected RCPT Rejected because Ip is in a black list at zen.spamhaus.org

2

Take a look to this post for a few options to fix that issue:

3

Thank you for the quick response. I have already removed Spamhaus from the DNSBL configuration, and after that the emails seem to be working properly. However, I will continue monitoring the situation.
Can you please explain point number 2. As I did research I have to replace current /etc/systemd/resolved.conf namerever to new one
nameserver 76.76.2.0 nameserver 76.76.10.0

is it correct?
after changing all emails will work fine? or any other change need to be done.

4

Maybe. It will depend on how your OS configure the name servers so changing them there could use them or maybe you should change them in /etc/netplan/50-cloud-init.yaml if your OS uses cloud-init. I don’t even know whether you are using Ubuntu or Debian.

Show the output of this command:

resolvectl status
5

I’m using a Ubuntu 24.04.4 LTS

root@srv1375894:~# resolvectl status

Global

     Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

resolv.conf mode: stub

Link 2 (eth0)

Current Scopes: DNS

     Protocols: +DefaultRoute -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Current DNS Server: 8.8.4.4

   DNS Servers: 153.92.2.6 1.1.1.1 8.8.4.4

root@srv1375894:~#

6

Show the output of these commands:

cat /etc/netplan/50-cloud-init.yaml
grep -rF 153.92.2.6
grep -rF 8.8.4.4
7

# This file is generated from information provided by the datasource. Changes

# to it will not persist across an instance reboot. To disable cloud-init’s

# network configuration capabilities, write a file

# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:

# network: {config: disabled}

network:

version: 2

ethernets:

    eth0:

        addresses:

        - 168.231.122.166/24

        - 2a02:4780:12:de::1/48

        match:

            macaddress: ea:e8:d4:ba:0e:96

        nameservers:

            addresses:

            - 153.92.2.6

            - 1.1.1.1

            - 8.8.4.4

            search:

            - localhost

        routes:

        -   to: default

            via: 168.231.122.254

        -   to: default

            via: 2a02:4780:12::1

        set-name: eth0

install.sh: sed -i “s/1.0.0.1 8.8.4.4 1.1.1.1 8.8.8.8/$resolver/g” /etc/nginx/nginx.conf

8

Edit /etc/netplan/50-cloud-init.yaml and replace:

- 153.92.2.6
- 1.1.1.1
- 8.8.4.4

with:

- 76.76.2.0
- 76.76.10.0

Save the file an execute this:

netplan apply

Once done, show again the output of:

resolvectl status
9

root@srv1375894:~# resolvectl status

Global

     Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

resolv.conf mode: stub

Link 2 (eth0)

Current Scopes: DNS

     Protocols: +DefaultRoute -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Current DNS Server: 76.76.2.0

   DNS Servers: 76.76.2.0 76.76.10.0
10

Ok, that’s good. Now enable again Spamhaus in Exim and check whether you receive mails.

11

Thank you
Just last Question:-
Is it required to enable Spamhaus again? What happens if I do not enable it?

12

No, you don’t need to enable it if you don’t want to, but Spamhaus blocks many spammers, so it’s up to you.