classycraft3r
A static ip is of course a step in the right direction. Just make sure it’s not listed on any RBL’s.
And also sort out the PTR.

      Why was the IP already blocked even though it had never been used in your service or for spam bots?

        piperino What do you mean by “sort out the PTR” ?
        As for the RBL’s we are blocked on 3 of them, we don’t know why as we never performed any spam or mail service before.

            Hestia
            don’t know. maybe it was abused by the previous owner.
            there is also a chance the whole subnet is blocked.

                classycraft3r
                ideal PTR should point to you mailserver.
                But at this point just start us google. there might be a basic guide installing and operate a mailserver😉

                    is there a way to unlock it?

                    It would be stupid if we suffered from it when we are not the cause of this problem

                    piperino As you can see on the screenshots, it should be pointing to it.

                    184.80.65.82.in-addr.arpa.project-hestia.me -> mail.project-hestia.me -> Mailserver IP
                    And mailcow resolves it as 82-65-80-184.subs.proxad.net

                    Also requests to gmail (outgoing emails) can’t seem to go through the Modem for some reason.
                    sudo traceroute -n -T -p 25 gmail-smtp-in.l.google.com gives me this:

                    traceroute to gmail-smtp-in.l.google.com (64.233.167.26), 30 hops max, 60 byte packets
 1  192.168.0.254  1.797 ms  2.515 ms  3.312 ms
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
...

                    Also requests to gmail (outgoing emails) can’t seem to go through the Modem for some reason.
                    sudo traceroute -n -T -p 25 gmail-smtp-in.l.google.com gives me this:

                    traceroute to gmail-smtp-in.l.google.com (64.233.167.26), 30 hops max, 60 byte packets
 1  192.168.0.254  1.797 ms  2.515 ms  3.312 ms
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
...

                    (sorry for the doubling, something went wrong on my side and it edited it two times).

                        classycraft3r I fixed the firewall issue, but now it sends emails, but I never recieve them. They appears and disappears from the queue and I still don’t get them.

                        EDIT: This is because of the PTR record. Now I really need to fix this.
                        EDIT 2: The weird this about the PTR record happens because the reverse DNS bring out the domain associated with our address. I’ll find a way to change this on their forum.

                            classycraft3r
                            PTR Records are only added in the in-addr.arpa. zones of the IP owner. But the A and PTR records should match.

                            Means you can put whatever PTR you want in cloudflare DNS, since they don’t own the IP Block it has no affect.

                              No one is typing