You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Patrick Beard <pa...@scotcomms.co.uk> on 2004/07/05 10:42:58 UTC
Domain Hijack
Hi,
Sorry if this is off topic, but I need some help.
It would appear that our domain has been hijacked by some spammers. I've
started to get a lot of mail rejections from mail we have not sent, mainly
its the typical online prescriptions.
Is there anything I can do to stop this? Is our domain in danger of getting
blacklisted? We use a number of anti-spam measures on our mailserver, is
this some kind of 'punishment' by the spammers?
My main problem with it, is it brings our name into disrepute.
Below is the headers for one of the messages.
Return-Path: <pm...@scotcomms.co.uk>
Received: (qmail 18876 invoked from network); 4 Jul 2004 15:09:55 -0000
Received: from i043135.ppp.dion.ne.jp (HELO scotcomms.co.uk)
(210.196.43.135)
by int-resources.com with SMTP; 4 Jul 2004 15:09:55 -0000
Message-ID: <51...@suJJ>
From: "Alissa Venanzi" <pm...@scotcomms.co.uk>
To: XXXXXXXXXXX
Subject: Real meds. Get it by tomorrow 0213
Date: Sun, 4 Jul 2004 10:12:25 -0500
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_855_78F7_630E78F7.630E78F7"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
This is a multi-part message in MIME format.
------=_NextPart_855_78F7_630E78F7.630E78F7
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Any advice would be appreciated.
--
Patrick
Re: Domain Hijack
Posted by Patrick Beard <pa...@scotcomms.co.uk>.
Thanks to all who replied.
I've now taken the following steps;
Put info on our website
Informed our provider.
Complained to the company that hosts the website featured in the spam (For
all the good that'll do - hananet.net ***sigh***)
Upgraded to the latest version of our relay MTA. This allows for LDAP
queries at smtp time. The version we used before would only ask the
destination if the recipient was acceptable and as the destination server is
an Exchange server everything with the correct domain was accepted - now its
not.
Thanks again.
Patrick
Re: Domain Hijack
Posted by Bob Proulx <bo...@proulx.com>.
Patrick Beard wrote:
> It would appear that our domain has been hijacked by some spammers. I've
> started to get a lot of mail rejections from mail we have not sent, mainly
> its the typical online prescriptions.
Unfortunately those are very common these days.
> Is there anything I can do to stop this?
This is a hot topic of debate because of the latest proposal to stop
forgeries.
http://spf.pobox.com/
> Is our domain in danger of getting blacklisted? We use a number of
> anti-spam measures on our mailserver, is this some kind of
> 'punishment' by the spammers?
No. You are just seeing the latest nastiness from spammers. Everyone
else is seeing the same thing.
> My main problem with it, is it brings our name into disrepute.
It is a joe-job.
Bob
Re: Domain Hijack
Posted by Matthew Cline <ma...@nightrealms.com>.
On Monday 05 July 2004 08:42 am, Patrick Beard wrote:
> Hi,
>
> Sorry if this is off topic, but I need some help.
> It would appear that our domain has been hijacked by some spammers. I've
> started to get a lot of mail rejections from mail we have not sent, mainly
> its the typical online prescriptions.
Technically, this isn't a domain hijack, but a "Joe Job". See
http://catb.org/~esr/jargon/html/J/joe-job.html
--
Give a man a match, and he'll be warm for a minute, but set him on
fire, and he'll be warm for the rest of his life.
Advanced SPAM filtering software: http://spamassassin.org
Re: Domain Hijack
Posted by Andy Jezierski <aj...@stepan.com>.
Kelson Vibber <ke...@speed.net> wrote on 07/06/2004 12:08:42 PM:
[snip]
>
> That said, I actually had someone reply to me once and tell me she didn't
> care if it was forged, we had to protect ourselves and it "should not be
> [her] responsibility to figure out if it is fake or not," and please make
> sure she didn't get any more spam from our domain name.
>
You should have forged her E-mail address and sent her a bunch of Spam. ;-)
What would she do then, E-mail herself telling herself not to spam
herself????
Andy
Re: Domain Hijack
Posted by Kelson Vibber <ke...@speed.net>.
At 09:33 AM 7/5/2004, Matt Kettler wrote:
>At 09:42 AM 7/5/04 +0100, Patrick Beard wrote:
>> Is our domain in danger of getting blacklisted?
>
>Only by idiots who believe you really sent it.
Unfortunately there are plenty of those. We get several complaints a week
to our abuse contact address, all from spam that's forged our domain
name. (Generally something obviously fake like
iufewkfbo@speed.net) Actually, last week we got a complaint about
speed.net.tw, so it's not *all* from forgeries - sometimes it's mistaken
identity! (It's been a *long* time since we've had to kick someone off or
make someone close a relay.)
>Unfortunately all you can do here is educate. Most people have encountered
>forged-from email by now, particularly with all the viruses about that
>forge From: lines. Education shouldn't be all that hard, since most people
>have encountered similar things before.
Exactly. The problem isn't really idiocy so much as it is ignorance. Most
people don't know about full headers, don't know how easy it is to forge
the From address, etc. My form response includes information on reading
the full headers, a link to our website's statement on joe-jobs, a
reference to SPF (or, Sender-ID, or whatever the new name is), and an
analogy to postal mail: You can write whatever you want as the return
address on an envelope, but the postmark will reveal whether it was really
sent from, say, Redmond, Washington, or whether it actually came from
somewhere in Arkansas.
For the most part it works. Most people leave it at that, and I've never
seen a repeat complaint, and some people have even written back thanking me
for the info and for looking into it (and occasionally apologizing for
sending the complaint to the wrong people).
That said, I actually had someone reply to me once and tell me she didn't
care if it was forged, we had to protect ourselves and it "should not be
[her] responsibility to figure out if it is fake or not," and please make
sure she didn't get any more spam from our domain name.
*sigh*
Kelson Vibber
SpeedGate Communications <www.speed.net>
Re: Domain Hijack
Posted by Matt Kettler <mk...@comcast.net>.
At 09:42 AM 7/5/04 +0100, Patrick Beard wrote:
>Sorry if this is off topic, but I need some help.
>It would appear that our domain has been hijacked by some spammers. I've
>started to get a lot of mail rejections from mail we have not sent, mainly
>its the typical online prescriptions.
>Is there anything I can do to stop this?
Not much. You can publish SPF records in your DNS entries, but very few
sites check SPF at the moment.
You can also try to contact the administrators responsible for the machines
that are originating the messages. In this case that's
i043135.ppp.dion.ne.jp, a Japanese dialup node, but that may not be so easy
given language barriers.
> Is our domain in danger of getting blacklisted?
Only by idiots who believe you really sent it.
>We use a number of anti-spam measures on our mailserver, is
>this some kind of 'punishment' by the spammers?
Possibly, but unless you're very vocal you're more likely to just be a
random selection from a list. Usualy spammers intentionally target those
who have been causing them lots of irritation by calling their ISPs to
detect them, writing spamfilters, etc.
>My main problem with it, is it brings our name into disrepute.
Unfortunately all you can do here is educate. Most people have encountered
forged-from email by now, particularly with all the viruses about that
forge From: lines. Education shouldn't be all that hard, since most people
have encountered similar things before.
Quite frankly, anyone who believes the From: line on any email is
hopelessly clueless... Do you know my name is really "Matt Kettler"? Do I
know yours is "Patrick Beard"? Do I even know for sure
patrick@scotcomms.co.uk is your address, and not merely a forgery of a
co-worker's address?
I for one certainly don't trust any of the above (except my own name) to be
fact, because I know how easy it is to lie about such things. Odds are they
are true, but I don't know for sure.
>Below is the headers for one of the messages.