• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Issue mail server not properly configured - leading to block

leopixelstudios

New Pleskian
Server operating system version
AlmaLinux 8.10 (Cerulean Leopard)
Plesk version and microupdate number
Plesk Obsidian 18.0.77 Update #2
Hello! I am going nuts on this issue.. I've had a mail server for a couple of years now without any issue.. last week I've added a new domain that needed mail services as well.. since then I've been blacklisted in spamhaus... Now, the part that I'm pulling my hair over... I wanted to dispute the blacklisting with spamhaus BUT, what they say is an error, is not something (or I think) I can fix..

The HELO points to the OVH server name
the IP address is of course the OVH server IP Address

the mail server is mail.xyz.com with ip address 1.2.3.4
the rDns point back to the domain mail.xyz.com

when I sumit my request to spamhaus.. that's what they give me ....

The A record for the HELO domain does not match the sending IP address.
Of course it won't!! I don't have the server name in my a record, I have the domain name

The reverse DNS domain does not match the HELO domain.
the reverse DNS points to the domain name, not the server name..

what can I do to fix this!
I have another domain with an email service with the same type of configuration (except it's their domain name) .. so I'm afraid they'll get blacklisted as well


thx.
 
Yeap, that seems to be an issue.. now the problem I have is that the ip addresss that the helo points to is an address I have in plesk, but no on my server host (ovh) .. how do I change this so that the server uses the "real" server ip address?

thx
 
Here's the result from spamhaus... so I understand about the server name HELO not being properly setup.. that's will be taken care of..
The issue I have is with the IPV4 record.. this is not an IP that originates from OVH, but one that has been created in Plesk..

but this address doesn't see to be working (it's a dedicated address with no submask..)

and the bottom part, the PTR will be changed to the same HELO value, and the PTR will resolve to this address 149.. but the HELO should also point to the 149 address and not the 51...


1777039014752.png
 
Back
Top