Software

Ask something
Discussion Locked

Spammer using my domain

0 helpful
2 replies

by nsceml 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a domain registered that is not live (no home page) but is set up through a domain registrar simply to forward all emails to a web email account.

The problem is that some spammer is using my domain name to send spam, and my web account is catching all the delivery failure notices.

The spammer does not have control of the domain, but is simply making it appear that emails are coming from my domain.

I don't know how to stop this. The registrar is not any help and won't reply to my emails. Any ideas on how to proceed with stopping this action?

2 replies

by nsceml

Here are some headers of the delivery failure notices I have received. This might help someone help me. Anywhere a series of 4's are shown was changed by me.

X-Apparently-To: 44444444@yahoo.com via 209.73.178.76; Tue, 19 Jul 2005 08:43:16 -0700
X-Originating-IP: [216.52.184.242]
Return-Path: <>
Authentication-Results: mta183.mail.dcn.yahoo.com from=unknown; domainkeys=neutral (no sig)
Received: from 216.52.184.242 (EHLO eforward2.name-services.com) (216.52.184.242) by mta183.mail.dcn.yahoo.com with SMTP; Tue, 19 Jul 2005 08:43:16 -0700
Received: from mxsf18.cluster1.charter.net ([209.225.28.218]) by eforward2.name-services.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 19 Jul 2005 08:39:14 -0700
Received: from mxip01a.cluster1.charter.net (mxip01a.cluster1.charter.net [209.225.28.131]) by mxsf18.cluster1.charter.net (8.12.11/8.12.11) with ESMTP id j6JFgIeT017918 for ; Tue, 19 Jul 2005 11:42:18 -0400
Message-Id: <200507191542.j6JFgIeT017918@mxsf18.cluster1.charter.net>
Received: from unknown (0.0.0.0) by mxip01a.cluster1.charter.net with ; 19 Jul 2005 11:42:20 -0400
Date: 19 Jul 2005 11:42:20 -0400
To: ONNTDWAMAnderson@44444444(my domain).net
From: "Mail Delivery System" Add to Address Book
Subject: Delivery Status Notification (Failure)
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status; boundary="14064628460176352.unknown"
Return-Path: <>
X-OriginalArrivalTime: 19 Jul 2005 15:39:14.0234 (UTC) FILETIME=[041471A0:01C58C78]
Content-Length: 1135

by bfilmfan

There isn't much of anyway for you to stop them.

People recieving the email probably aren't saavy enough to be able to read the header for where a message truly originated.

The best you can do is point that out to them.

This discussion is closed to new replies.