Roundcube webmail not receiving emails

isuru · July 15, 2024, 3:39pm

I can send emails but but not receving replys or emails to roundcube mail. I found tis same matter in this platform but it’s not working for me. when I type this command

dig 1.0.0.1.zen.spamhaus.org +short
it output shows 127.255.255.254
output for this code cat /etc/resolv.conf is

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.

nameserver 1.1.1.1
namesever 8.8.8.8
nameserver 127.0.0.53
search vcn04252228.oraclevcn.com

output of this command

systemctl status resolvconf.service

is

● resolvconf.service - Nameserver information manager
     Loaded: loaded (/lib/systemd/system/resolvconf.service; enabled; vendor pr>
     Active: active (exited) since Mon 2024-07-15 15:07:21 UTC; 30min ago
       Docs: man:resolvconf(8)
    Process: 366 ExecStart=/sbin/resolvconf --enable-updates (code=exited, stat>
   Main PID: 366 (code=exited, status=0/SUCCESS)

How can I fix it?

maurice · July 15, 2024, 4:11pm

Check the path that an incoming mail should follow to end up in your mailbox.
Do the MX records point to the right server?
Does the email arrive at your server? Check exim’s log for that.
Is exim rejecting the mail? Check exim’s log for that.
In your message, you are referring to spamhaus and dns and you show you are using public dns servers which spamhaus does not want you to do. See their explanation at Help for Spamhaus Public Mirror Users - Spamhaus Technology

isuru · July 19, 2024, 5:56am

yes, MX records point to the right server . I can send emails and it delevered successfuly. but not reseving any emails. after few houres this email comes to sender’s email |550 Rejected because 209.85.222.182 is in a black list at zen.spamhaus.org Error: open resolver; https://check.spamhaus.org/returnc/pub/172.69.21.23/|

sahsanu · July 19, 2024, 6:26am

If you can’t receive any mails because all ips are being rejected and you are using public dns resolvers like 1.1.1.1,9.9.9.9, etc. you have 4 options:

1.- Replace the dns resolver that is using your server to one not blocked by Spamhaus like 76.76.2.0
2.- Install and use your own dns resolver (like Unbound or PowerDNS).
3.- Create a free query key from spamhaus and use it in Exim. To do so, check this link
4.- Remove zen.spamhaus.org from /etc/exim4/dnsbl.conf and restart exim (I don’t recommend this option).

isuru · July 19, 2024, 7:01am

Please Can you explain how to do this step 1. Replace the dns resolver that is using your server to one not blocked by Spamhaus like 76.76.2.0.
I am using cloudflare for dns records and oraclecloud vps for hosting. is it oraclecloud firewall setting or can I fix it with cloudflare.

sahsanu · July 19, 2024, 7:20am

It is not related to your domain dns records hosted on Cloudflare. It is related to use a public dns resolver not allowed by Spamhaus, I don’t really know whether you are using 1.1.1.1 and 1.0.0.1 or any other public resolver.

I don’t know if you are using systemd-resolved, if that is the case, you can check it with this command:

resolvectl status

You should edit this file /etc/systemd/resolved.conf and uncomment, add/modify these lines:

[Resolve]
DNS=76.76.2.0 76.76.10.0

Edit: I separated the ips with comma and it should be a space.

Once done, save the file, restart the service and test it.

systemctl restart systemd-resolved
systemctl status
curl -sSL https://7j.gg/chksph2 | bash -s --

isuru · July 19, 2024, 7:34am

I modified DNS=76.76.2.0,76.76.10.0 record like this. also restarted and when I run this command curl -sSL https://7j.gg/chksph2 | bash -s -- it shows this result.

Test 01: Request ignored by Spamhaus or DNS Resolver timed out
Test 02: Request ignored by Spamhaus or DNS Resolver timed out
Test 03: Request ignored by Spamhaus or DNS Resolver timed out
Test 04: Request ignored by Spamhaus or DNS Resolver timed out
Test 05: Request ignored by Spamhaus or DNS Resolver timed out
Test 06: Request ignored by Spamhaus or DNS Resolver timed out
Test 07: Request ignored by Spamhaus or DNS Resolver timed out
Test 08: Request ignored by Spamhaus or DNS Resolver timed out
Test 09: Request ignored by Spamhaus or DNS Resolver timed out
Test 10: Request ignored by Spamhaus or DNS Resolver timed out

Result is bad, Spamhaus is blocking/ignoring your current DNS Resolver 127.0.0.53{}

sahsanu · July 19, 2024, 7:40am

Did you restart the service or the server?

If you restarted the server, maybe you are using cloud-init and it is modifying the dns on every boot.

Show the output of these commands

resolvectl status
cat /etc/netplan/50-cloud-init.yaml

isuru · July 19, 2024, 7:44am

results of resolvectl status cat /etc/netplan/50-cloud-init.yaml

Global
       Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: foreign

Link 2 (ens3)
    Current Scopes: DNS
         Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 169.254.169.254
       DNS Servers: 169.254.169.254
        DNS Domain: vcn04252228.oraclevcn.com
# 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:
        ens3:
            dhcp4: true
            match:
                macaddress: 02:00:17:02:03:87
            set-name: ens3
ubuntu@hcp:~$

isuru · July 19, 2024, 7:51am

I just run this command
curl -sSL https://7j.gg/chksph2 | bash -s -- and it shows this result.

 sudo curl -sSL https://7j.gg/chksph2 | bash -s --

Test 01: Error: open resolver; https://check.spamhaus.org/returnc/pub/2400:cb00:                          467:1024::ac47:9d80/
Test 02: Error: open resolver; https://check.spamhaus.org/returnc/pub/172.71.157                          .6/
Test 03: Error: open resolver; https://check.spamhaus.org/returnc/pub/172.69.133                          .7/
Test 04: Error: open resolver; https://check.spamhaus.org/returnc/pub/2400:cb00:                          465:1024::ac45:8506/
Test 05: Error: open resolver; https://check.spamhaus.org/returnc/pub/172.69.133                          .7/
Test 06: Error: open resolver; https://check.spamhaus.org/returnc/pub/172.71.157                          .6/
Test 07: Error: open resolver; https://check.spamhaus.org/returnc/pub/172.71.157                          .6/
Test 08: Error: open resolver; https://check.spamhaus.org/returnc/pub/172.69.21.                          122/
Test 09: Error: open resolver; https://check.spamhaus.org/returnc/pub/172.69.21.                          23/
Test 10: Error: open resolver; https://check.spamhaus.org/returnc/pub/162.158.16                          5.4/

Result is bad, Spamhaus is blocking/ignoring your current DNS Resolver 1.1.1.1{}

sahsanu · July 19, 2024, 7:54am

It has no sense that in the first command it showed 127.0.0.53 as your main dns resolver and now it shows 1.1.1.1. Did you add 1.1.1.1 to some conf file?

sahsanu · July 19, 2024, 7:59am

Sorry I separated the ips with comma and it should be a space.

Edit again the file /etc/systemd/resolved.conf

[Resolve]
DNS=76.76.2.0 76.76.10.0

And restart the service:

systemctl restart systemd-resolved

isuru · July 19, 2024, 8:14am

done.but same result when I run this command curl -sSL https://7j.gg/chksph2 | bash -s --

Test 01: Error: open resolver; https://check.spamhaus.org/returnc/pub/2400:cb00:466:1024::ac47:9980/
Test 02: Error: open resolver; https://check.spamhaus.org/returnc/pub/2400:cb00:467:1024::ac47:9d80/
Test 03: Error: open resolver; https://check.spamhaus.org/returnc/pub/2400:cb00:467:1024::ac47:9d80/
Test 04: Error: open resolver; https://check.spamhaus.org/returnc/pub/2400:cb00:465:1024::ac45:8561/
Test 05: Error: open resolver; https://check.spamhaus.org/returnc/pub/172.69.133.7/
Test 06: Error: open resolver; https://check.spamhaus.org/returnc/pub/172.69.133.6/
Test 07: Error: open resolver; https://check.spamhaus.org/returnc/pub/162.158.165.4/
Test 08: Error: open resolver; https://check.spamhaus.org/returnc/pub/162.158.165.4/
Test 09: Error: open resolver; https://check.spamhaus.org/returnc/pub/172.69.133.7/
Test 10: Error: open resolver; https://check.spamhaus.org/returnc/pub/172.69.21.122/

Result is bad, Spamhaus is blocking/ignoring your current DNS Resolver 1.1.1.1{}

sahsanu · July 19, 2024, 8:16am

ls -l /etc/resolv.conf
grep -v '^#' /etc/resolv.conf
grep -v '^#' /etc/systemd/resolved.conf

isuru · July 19, 2024, 8:18am

result `nameserver 1.1.1.1
namesever 8.8.8.8
nameserver 127.0.0.53
search vcn04252228.oraclevcn.com

[Resolve]
DNS=76.76.2.0 76.76.10.0`

sahsanu · July 19, 2024, 8:20am

I need the first command. Did you manually edit /etc/resolv.conf?

isuru · July 19, 2024, 8:22am

that file contains nameserver 1.1.1.1 namesever 8.8.8.8 nameserver 127.0.0.53 search vcn04252228.oraclevcn.com

sahsanu · July 19, 2024, 8:24am

Yes I saw it in your previous post, I need the output of this command:

ls -l /etc/resolv.conf

isuru · July 19, 2024, 8:27am

this is the result for that code lrwxrwxrwx 1 root root 29 Jul 15 12:35 /etc/resolv.conf -> ../run/resolvconf/resolv.conf

sahsanu · July 19, 2024, 8:32am

And how you configured those name servers?

grep -r '1\.1\.1\.1\|8\.8\.8\.8' /etc/

I’ll be out for a while.