If I am enough lucky there’s a smart guy at Kamatera Support desk enough skilled to distinguish the real culprit between a real IP address (usually belonging to this house of retarded spamming monkeys called Cloudwm) and a fake server name associated to that IP in a Received: line
X-Google-Smtp-Source: AGHT+IGfo2k+5mAQTSmY0ZdqTifH9fJvECpzoq7IQoGxBhJCO9J6o249irgQd0c3NjPuxzarvzFiVg==
X-Received: by 2002:a17:907:d5a6:b0:ade:3eb6:3c6 with SMTP id a640c23a62f3a-ae9cddf1163mr2051293866b.15.1753111599210;
Mon, 21 Jul 2025 08:26:39 -0700 (PDT)
Return-Path: bjgdeommlnhud@gmail.com
Received: from mail.michlans.me ([81.28.6.28])
by smtp.gmail.com with ESMTPSA id a640c23a62f3a-aec6c7dcf56sm701185466b.67.2025.07.21.08.26.38
for xxsjfgkj@gmail.com
(version=TLS1 cipher=ECDHE-ECDSA-AES128-SHA bits=128/128);
Mon, 21 Jul 2025 08:26:38 -0700 (PDT)
Date: Mon, 21 Jul 2025 08:26:38 -0700 (PDT)
X-Google-Original-Date: [smtp_date]
From: “Gwen C. Scott” bjgdeommlnhud@gmail.com
Whether I am not enough lucky I may happen to crash on a wall of stupidity of some wanker kid who usually replies with
Hello, There is no server assigned to this IP anymore. Please remove this IP from your records just because the server is fake
~$ host mail.michlans.me
;; communications error to 172.18.144.1#53: timed out
;; communications error to 172.18.144.1#53: timed out
;; no servers could be reached
and he hasn’t enough brains to point the IP address which is real not a fake server name
where the server name is always fake, made of some random chars or anyways some non existent server such as
mail.michlans.me ([81.28.6.28])
Any suggestions about how to stop these spamming monkeys who are molesting me since months?
One quick question: when I was using the old dslreports site I could use some sort of email to report phishing email, such as
phish+1367969_8dba@dslreports.com
Is there anything similar on broadbandbulletin?