Провайдер заблокировал отправку по smtp по жалобе.

360 нету, email там были сделаны еще когда это был сервис бесплатный Почта для домена, после как сделали платно ящики там только работают на примем, а сейчас настроил(вернее в движке форума уже предусмотрено было) просто отправку через smtp почту site@yandex.ru

Да не суть это, проблема скорее в первом посте

Это не важно что они пишут. Абсолютно. Это такая контора, с мнением которой вынуждены считаться все провайдеры и регистраторы. Ведь они могут в свою базу закинуть айпи хостера! 

Дискуссии с вами вести никто не будет. Получили письмо от спамхауса - меняйте хостера. 

Сейчас вроде с ip сняли пометку, но остались какие-то ограничения и предложения 

Most recent historical listing - CSS Blocklist
Warning Icon
Historical Listing
This IP is not currently listed. Here is the most recent information provided regarding the listing of **.***.***.***

Date Listed: November 30, 2025 14:38:55

Date Removed: December 03, 2025 13:55:29

Less Info
Why was this IP listed?
CSS listings are based on a wide range of inputs and are always the result of multiple events and heuristics. In this case:

**.***.**.*** is sending emails of an unsolicited nature AND the configuration requires attention. This can be for several reasons, but the most common are:

Data collection/list hygiene issues - our FAQ.
A malware infection, insecure installation or misconfigured server. Please see our FAQ for help.
What should be done about it?
If this is a shared server, please call your hosting company or ISP!

To solve this ALL of these must be done before requesting removal:

The unsolicited email problem needs to be addressed and resolved, or
The malware needs to be found and removed, or
The misconfiguration must be corrected. Its HELO value has no relationship with the rDNS (PTR) of the IP. The IP it resolves to is not even in the same ASN, and this causes it to appear to be spoofing.
Or both!
HELO/EHLO & DNS CHECKS:

Check your DNS (A record and rDNS), email authentication and HELO values.
Ensure they are realistic for their intended use, and resolvable in external DNS.
If this is a Plesk, cPanel or DirectAdmin host, please read the FAQ.
You can test a server's HELO configuration by visiting AboutMyEmail. From there, send an email from the machine in question to the provided email address, and then examine the results. This tool will give a lot of detail about the email. To check HELO/EHLO, navigate to "Delivery" -> "SMTP" and look for the EHLO line.

If the HELO value does NOT exist in DNS, that must be corrected
If the HELO value is NOT correct, that must be fixed
If the HELO is using a domain that does NOT exist, that must be corrected
Make sure your SPF record is current, accurate AND published!

If the HELO/EHLO IS what you expect it to be AND it exists in DNS, then there is very probably a spambot or some other kind of malware! This needs to be found and removed.

MALWARE CHECKS:

Secure your firewall to not allow any packets outbound on port 25, except those coming from any email server(s) on your local network. Remote sending of email to servers or printers on the Internet will still work if web-based, or correctly configured to use port 587 using SMTP-AUTH.
Guest networks should also be secured - infected personal devices are a big issue!
NOTE: limiting port 25 outbound will only prevent the abusive connections from leaving your network and will not find or remove the malware. In order to do that, we suggest setting up network logging/packet logging to monitor anomalous traffic. This will help identify sources of malware if the scans do not find anything.

Perform complete scans with an up to date anti-virus/malware on all devices behind this IP on a scheduled basis.
Remember to check personal devices such as laptops, phones, tablets, as well as routers, etc. Malware can be on almost anything that is connected to the internet, including a smart doorbell.
Consider the router or firewall as a source of the problem if scans find no other devices.
Logging at the router or firewall can reveal unusual traffic and help find the compromised device(s). (For example: What is trying to connect out on port 25 that should not?)
This FAQ can be helpful.

For more details about CSS, listing criteria and removal please see our FAQ.

Requesting removal
If the problem on **.***.**.*** has been addressed, you can request a review and removal.

Типа нормально теперь все? Можно хотера включить отправку почты?