AdminSysGNULinux

Vérif avec https://www.mail-tester.com/

Diagnostic-Code: smtp; 550 5.7.1 Service unavailable; client [xxx.xxx.xxx.xxx]
    blocked using all.spamrats.com

Alert: Your IP is part of a network listed as a Worst Offender

This is a Worst Offender Alert and this means that not only this IP address, but the whole class 'C' is also on the indicated SpamRATS List. Usually this means the whole range has the same issue of naming conventions or no reverse DNS AND that many IP's from this Class C have been used in Spam Attacks, Dictionary attacks or other forms of attacks, as detected by Mail Servers in the Data Collection Grid. You will NOT be able to use the removal form to remove your IP Addresses. If you have recently been assigned the IP Addresses, or have changed what these IP Addresses are used for, you can use the contact form and ask for a reclassification, but you will have to provide full disclosure, including whois for the ip addresses, your affiliation with the company that owns them, and a description of what the IP's were previously used for, and what they will be used for, in order for a Spam Auditor to consider reclassification. Remember, the majority of the IP's in this space WERE detected as being involved in some form of attack or abusive behaviour, so you had better have a good reason to ask for removal, and you need to own or control the IP addresses, as evidenced by ARIN whois.

Alerte : votre adresse IP fait partie d'un réseau répertorié comme étant le pire contrevenant

Il s'agit d'une alerte de pire infraction , ce qui signifie que non seulement cette adresse IP, mais toute la classe « C », figure également sur la liste SpamRATS indiquée. Cela signifie généralement que toute la plage présente le même problème de conventions de nommage ou l'absence de DNS inversé, et que de nombreuses adresses IP de cette classe C ont été utilisées dans des attaques de spam, des attaques par dictionnaire ou d'autres formes d'attaques, comme détecté par les serveurs de messagerie dans la grille de collecte de données. Vous ne pourrez PAS utiliser le formulaire de suppression pour supprimer vos adresses IP. Si ces adresses IP vous ont été récemment attribuées ou si vous en avez modifié l'utilisation, vous pouvez utiliser le formulaire de contact et demander une reclassification. Vous devrez toutefois fournir des informations complètes, notamment le Whois des adresses IP, votre affiliation avec l'entreprise qui les possède et une description de leur utilisation antérieure et future, afin qu'un auditeur de spam puisse envisager une reclassification. N'oubliez pas que la majorité des adresses IP de cet espace ont été détectées comme étant impliquées dans une forme d'attaque ou de comportement abusif. Vous feriez donc mieux d'avoir une bonne raison de demander la suppression, et vous devez posséder ou contrôler les adresses IP, comme en témoigne le whois d'ARIN.

Cette espèce de rat me discrimine est assume faire des punitions collective.

Encore une fois !

Why is 2001:41d0:404:200::/64 listed?

CSS lists IPv6 addresses by (/64). CSS listings are influenced by:

    Email showing indications that it is of an unsolicited nature;
    Poor email list hygiene;
    Sending out bad email due to a compromise, insecure installation or misconfigured server;
    Other indicators of low reputation or abuse.

CSS listings are based on a wide range of inputs and are always the result of multiple events and heuristics.
What should be done about it?

According to current agreed upon standards, any given /64 is intended to be one single entity.
CSS and IPv6:

    CSS lists /64 subnets (or larger) of IPv6 addresses as dictated by industry standards.
    The industry standard for the smallest IPv6 allocation to individual customers, even for home-uses like cable, DSL or wireless is a /64.
    Some providers choose to not follow the industry standard, and allocate smaller subnets. As a result, you are sharing the same network segment as other customers, which can include problematic ones.
    This non-standard allocation practice can result in IPv6 IPs being listed in CSS because of neighboring IPs that share the same /64 - contrary to industry standard.

NOTE: If your allocation is smaller than /64, we cannot remove it from CSS, and the situation needs to be corrected with the provider prior to requesting removal. For more information about IPv6, IP allocation, and industry standards, please see our FAQ. A spammer can cycle through IPv6 addresses every 5 seconds (or even faster, with custom kernels). Since an IPv6 /64 is twice the size of the entire IPv4 mask, lots of spam can be produced with very minimal effort. Thus, listing the whole /64 is warranted.
Removal from CSS

If the problem on 2001:41d0:404:200::/64 has been addressed, you can start the delisting process.

There is no spam from 2001:41d0:404:200::16c9.
I checked logs, and outgoing network flow.
The is no evidence of spam (inside or outside)

The message says "2001:41d0:404:200::/64" but my server is not 2001:41d0:404:200::/64 (the range) , but 2001:41d0:404:200::16c9.

Some peoples use to apply collective punishment, 

Is this exact IP yours? Do you control the full /64 or larger?
------------------------------------------
IP: 2001:41d0:404:200::4c57
------------------------------------------
If the answer is no, please contact your service provider.

CSS/XBL lists IPv6 with /64 granularity, and one or more IPs within the /64 in question are sending spam. 

A /64 is the industry standard for the smallest IPv6 allocation to individual customers, even for home-uses like cable, DSL or wireless. The /64 choice has RFC4291 as its origin and it is further discussed in RFC6177.

As a spammer can cycle through IPv6 addresses every 5 seconds or less and an IPv6 /64 is twice the size of the entire IPv4 internet, a lot of spam can be sent with minimal effort. Thus, listing the whole /64 is warranted.

For more detailed information, the below URL should help:

https://www.spamhaus.org/faqs/combined-spam-sources-css/#css-how-handle-ipv6
https://www.spamhaus.org/faqs/exploits-blocklist-xbl/#how-does-xbl-handle-ipv6-addresses


To resolve this issue, contact your service provider and request the assignment of a /64 range together with DNS/rDNS appropriate for email service.

These links may be helpful when having the conversation with your ISP:

https://slash64.net/

https://www.m3aawg.org/sites/default/files/document/M3AAWG_Inbound_IPv6_Policy_Issues-2014-09.pdf