What Happens To Bounced @Donotreply.com E-Mails 286
An anonymous reader writes "The Washington Post's Security Fix blog today features a funny but scary interview with a guy in Seattle who owns the domain name donotreply.com. Apparently, everyone from major US banks to the Transportation Security Administration to contractors in Iraq use some variation on the address in the "From:" field of all e-mails sent out, with the result that bounced e-mails go to the owner of donotreply.com.'With the exception of extreme cases like those mentioned above, Faliszek says he long ago stopped trying to alert companies about the e-mails he was receiving. It's just not worth it: Faliszek said he is constantly threatened with lawsuits from companies who for one reason or another have a difficult time grasping why he is in possession of their internal documents and e-mails.'"
*Cough* (Score:5, Insightful)
Re: (Score:3, Interesting)
Re: (Score:3, Funny)
Some of them are sad and pitiful, and read a lot like, "Please accept these plans to repay my credit so I can buy my children food this week! I am waiting anxiously to hear from you and your Reply Here link wasn't working so I sent this email instead."
Re:*Cough* (Score:5, Insightful)
In addition I'm pretty sure someone could probably find a way to use US copyright laws and make them pay money for using his domain name (Intellectual Property) without his permission.
WTF (Score:5, Insightful)
Re:WTF (Score:4, Interesting)
Re:WTF (Score:5, Informative)
http://tools.ietf.org/html/rfc2606 [ietf.org]
Re:WTF (Score:5, Funny)
I've also wondered if routing your mail using user%example.org@example.com notation still worked. Could one give out an address like user%example.com@spamfilter.example to run it through a spam filtering service and reject any mail that didn't come via spamfilter.example (if spamfilter.example allowed such relaying syntax)?
Sorry, first disclosure, I can't even patent it now.
Re:WTF (Score:4, Informative)
Re: (Score:2)
Re: (Score:2)
I was thinking that originally, but now I wonder if I could instead have an MX setup for donotreply.company.com that sends the mail to 127.0.0.1
Would there be any pitfalls to that? Worst case it would try to deliver the mail to localhost, which assuming the guy was actually running an smtp server, it would probably just reject it as an invalid recipient, ref
Re: (Score:3, Informative)
Thanks
Robert
Re:WTF (Score:5, Insightful)
Why even have a donotreply@company.com? How about customerservice@company.com? I guess that would make it too easy to get customer service.
Re:WTF (Score:5, Insightful)
If you're sending communication as email, you should expect communication as email back.
Re:WTF (Score:5, Funny)
Re:WTF (Score:4, Funny)
Re:WTF (Score:5, Funny)
Re:WTF (Score:5, Funny)
- Dylan O'Notreply
Re:WTF (Score:5, Funny)
Re:WTF (Score:5, Insightful)
Re:WTF (Score:5, Informative)
Surely they should use example.com (Documented in RFCs to never be a real domain). It has no MX and points to a simple web page that just says it's an example for documentation and gives a link to the relevant RFC.
example.com or invalid or donotreply.mydomain.com (Score:4, Informative)
Handing mail to example.com is more or less fine - originally there wasn't anything there, though the fine people at ICANN decided to put an explanatory web page there; AFAICT, telnet example.com 25 times out. And "invalid"'s even better, since it NXDOMAINs, and you can use addresses like donotreply@really.donotreply.invalid.
But you can also manage it yourself - use a subdomain like donotreply.mydomain.com, with some appropriate treatment like NXDOMAIN or a stub email server that replies "554 we told you donotreply, please use the URL in our email" or points to 127.0.0.86 or whatever. That way it's obvious who;s managing it.
Of course, if you're using donotreply.com because you're a spammer, none of these explanations matter to you, because you're a rude nyeculturny thug who doesn't mind bothering people. And some fraction of the people who reply to those will be including their credit card numbers, mother's maiden name, and postal address, so that they can collect the Microsoft Lottery or order their Nigerian Herbal Fake Viagra, and well, more power to the folks at donotreply.com for offering to educate those poor suckers
Re:WTF (Score:4, Funny)
Re: (Score:3, Funny)
Re: (Score:2)
Re:WTF (Score:5, Insightful)
Now that I have thought about it a bit more, this is about the money. If they put donotreply@companydomain.com, then the inevitable replies would eat up their bandwidth and processing power on their incoming mail servers.
By forging that information, which is not good policy, they are intentionally redirecting that reply to somewhere else. They may have thought that the sending mail server would simply give a permanent delivery failure notice to the sender, but in this case that forged information leads to an active mail server which accepts all of those emails.
Who is the bigger "butthead" here? The companies intentionally forging their emails or the guy who owns this domain and is exploiting this companies (after they have already harassed him) to save a couple of animals?
Re:WTF (Score:5, Insightful)
Anyone bright enough to -think- having the messages bounce to another domain would save them money should be able to think that maybe just maybe if they have the messages bounce to another domain that this other domain might actually exist, accept that bounced mail, and even read it.
If they really wanted to save money, and not take that risk they could blacklist an address at their mail gates front door. That would eliminate most, but not all the cost of handling the return mail.
And it would be a simple matter to simply have it go to "donotreplay@donotreplay.company.com" which wouldn't have an MX record configured, and would thus never get anywhere. And being a subdomain of your own, it wouldn't be incidently delivered to someone else either.
Re: (Score:3, Informative)
That statement works both ways
Nevertheless, your bring up a valid point. However, I have seen some rather malicious behavior coming from the Pointy Haired Ones that looks like incompetence at first glance. That's just their way.
As for the MX record, you are completely correct. The more elegant solution to be sure. The sending mail server will not even be able to resolve it, and no bandwidth is used at all.
Re: (Score:3, Insightful)
It does not. One is a general rule that holds true in the majority of situations, the reverse does not, which is why the original is recognized at all. It works in this specific case, or you would not even bring it up.
Re: (Score:2)
There are two reasons for everything corporations do. I suspect the first, greed, isn't the one here. It's the second: stupidity.
Re:WTF (Score:5, Insightful)
Re: (Score:3, Informative)
Re: (Score:2)
Re: (Score:2, Informative)
Re: (Score:2)
Re: (Score:3, Funny)
Business plan (Score:5, Informative)
Re: (Score:3, Interesting)
forgery? (Score:3, Interesting)
Re:forgery? (Score:5, Informative)
http://www.ftc.gov/bcp/conline/pubs/buspubs/canspam.shtm [ftc.gov]
"It bans false or misleading header information. Your email's "From," "To," and routing information - including the originating domain name and email address - must be accurate and identify the person who initiated the email."
Re: (Score:2)
Is he going to sell his domain now? (Score:2)
I wonder how long it's going to take for domain squatters or other people to attempt to approach this guy with an offer, and I wonder if he'll accept said offer. This might not bode well for the populace in general if companies don't wake up to their idiotic IT policies.
Stupid on both sides (Score:5, Insightful)
Sounds like he is the one being hurt here. Of course somebody has to own that domain (I guess) and he decided too. Terrible domain name, but still not his fault.
Which brings me to:
All of these organizations and companies are just being cute by forging their FROM headers. Technically that should not be allowed, but you can do it anyways. They don't want to deal with it and they create "one-way" traffic by inserting bogus information into that header.
The problem is that bogus information is an actual domain that is active and running a mail server. They are treating it like is a reserved word.
The lawsuits are funny, since the header information will show conclusively that those people intentionally redirected the traffic to this guy. If anything, he can counter-sue.
The only thing I can think of is that donotreply.com becomes a reserved word, which is probably easier than getting all those mail administrators to change their behavior, or to get smarter.
In any case, the domain owner is without fault on this one. Unless you count being stupid as a fault, which picking that domain is a little unwise.
Re: (Score:2)
Re:Stupid on both sides (Score:4, Interesting)
I operate an email servicing company. The costs of the bandwidth alone for millions of emails each week is NOT cheap. The server may not have to be that expensive, as it is only about 2 to 10 emails per second (approx. 2 per million), which is not that outrageous. Disk space is cheap these days and he can delete a lot of stuff coming in pretty fast.
However, that bandwidth is costing him money. A fair amount of it too. Hard to say, since he is in Seattle. I would think a couple hundred bucks a month all day long if not more.
So if he is spending that kind of money to keep it, it must be making him money. That's just my opinion....
This happened with PO boxes as well... (Score:3, Funny)
step 3 (Score:3, Insightful)
.invalid exists (Score:2)
".invalid" is already a reserved top-level domain. Thus "donotreply.invalid"
would produce the desired behavior.
>
> behavior, or to get smarter.
This guy seems to be dealing with it. Perhaps he could arrange for incoming emails to be automatically entered into a database searchable at www.donotreply.com. Should be easily doable by ha
Re: (Score:2)
He is a "douche". But he is also a technically correct douche, the best kind douche
The companies are douches for forging their headers, and he is a douche for deliberately exploiting those douches. So in fact, he may be a double-douche.
Re: (Score:2)
Cease and Desist Letters for legally owned domains (Score:4, Funny)
I find myself in a somewhat similar situation. I was supposed to do some work for a company who later ended up folding because of 'bad management', and I was left holding the bag on the domain I purchased at their instruction, that they never paid me for.(they didnt want to buy it, I dont know?).
Other than getting all the requests for 'why havent you paid us yet', the end result is that almost 2 years later these people are COMING AFTER ME WITH A CEASE AND DESIST LETTER and demanding that I turn over this domain and others to them for free because it 'infringes on their copyright'. Although, I honestly can say Im not suprised that Caton Commercial, the real estate company who is operating as the umbrella company for all these shell companies who eventually go under, doesnt know its ass from a whole in the ground.
Knowing full well that this sort of behavior is borderline as far as being professional, I posted the full contents of the Cease and Desist Letter sent by a Mr John Argoudelis [demystify.info] online so anyone thinking of working with this company may come across this sort of behavior and maybe think twice. Lawyers and Real Estate agents.... whew... what a combo of integrity!
The company is also involved in numerous court cases relating to other aspects of their business practices. Ive posted a short description of the Will County court cases that caton commercial is involved in [blackjackandhookers.org] at my blackjack and hookers site.
In fact, forget the blackjack!
Re: (Score:3, Funny)
Just a minute, my boss just walked up with a box.
Re:Cease and Desist Letters for legally owned doma (Score:4, Funny)
Re:Cease and Desist Letters for legally owned doma (Score:2)
Just re-direct all email and web for that domain to a collection agency. You might even be able to contract for finder's fees.
That or put up a zone file pointing to 127.0.0.1 for the A record.
Never thought of "donotreply.com" (Score:2)
Re:Never thought of "donotreply.com" (Score:5, Funny)
I always just use me@yourmomshouse.com.
Re: (Score:2)
Re: (Score:2)
*shrugs*
I have a suggestion: (Score:5, Funny)
2. Donotreply owner sets up an autoreply for companya@donotreply.com. This auto-reply should be inappropriate, goatse is definitely an option.
3. Company A loses customers in droves, problem solved.
Re: (Score:2)
Yeah you are... I got your number
Re:I have a suggestion: (Score:5, Funny)
He had a phone number for years.
Out of the blue, he started getting calls in the middle of the night from security guards checking in on their rounds.
Seems a security company had started up and had a number close to his and the guards were mistakenly calling his number instead of theirs.
He asked the company to change their number. They said no and told him to change his.
The next time he got a call in the middle of the night, he told the guard that he could go home for the night.
Company calls up the next day all upset that he sent the guard home and telling him he couldn't do that.
He says he could and would keep on as long as the calls continued.
Number changed. Calls stopped.
(This is from memory, the details may not be 100% accurate, the gist of the story is as he told me.)
all the best,
drew
http://packet-in.org/wiki/index.php?title=Main_Page [packet-in.org]
Packet In - net band. Libre music available gratis. Could be for a limited time only. Then again, it could last as long as copyrights...
Re: (Score:3, Interesting)
One night, very late, someone called and was quite upset that not only weren't we the pharmacy, but that we couldn't transfer their call to the pharmacist. This in the days when yoh could choose pluse or tone dial phones. My mom lost her cool and gave the caller quite a talking to.
The pharmacy owner called the next day and began to chew me out (I was home sick, she
Re:I have a suggestion: (Score:4, Funny)
I started telling the callers to tell "Leanne" that she was giving out the wrong number, and to let her friends know about it, but the calls kept coming.
One day at about 4AM, I got woken up with asking if "Leanne" was home. I had an epiphany, and told them "no, she died today." The caller was dumbstruck. I told him that she got hit by a bus on the way home. The caller asked the obligatory "is there anything I can do?" and I said "Yes - can you call all of her friends and let them know the funeral is on Tuesday?"
That was the last call for "Leanne" I ever got.
RFC 2606 (Score:5, Informative)
".invalid" is intended for use in online construction of domain
names that are sure to be invalid and which it is obvious at a
glance are invalid.
A possible use for example.com (Score:4, Informative)
For reply addresses, a more reasonable protocol would be to use the sender's actual domain but with an invalid username, as Poromenos1 suggests. A further problem of using a domain not your own as a sender address is that the recipient's email server may block it due to SPF records or other checks on sender domains.
I remember once getting an incensed missive from the owner of asdfg.com who complained about emails we were sending him regarding updates of our product. Turned out that a user had entered that domain when he registered the product in an attempt to not get our emails.
Re: (Score:2)
Good point, but just to nitpick:
SPF policies apply only to the envelope sender address, not the message's From: header.
Re: (Score:3, Insightful)
I usually just do admin@domain, where domain is the domain of the stupid website I'm trying to access which pointlessly requires me to register first. The solution is to not require registration, rather than trying to block all the bullshit a
My domain (Score:3, Insightful)
I got bored with replying (some guy in SanDiego is a real estate agent for ReMax, I don't think he ever got it), so I just limited what my mail server will accept.
Now it just bounces back to the sender and hopefully they think "oops, perhaps I shouldn't do that", which is what I believe this guy should do. Discourage the bad behavior, don't exploit it.
Sort of like copying to file... (Score:4, Interesting)
I did this once. (Score:5, Funny)
Re:I did this once. (Score:5, Interesting)
Sell captured emails (Score:4, Insightful)
(no I didn't RTFA)
Reminds me of my younger days (Score:5, Funny)
I learned my lesson, though. Now I never put my real phone number in the whois record for my domains.
Re: (Score:2)
Re: (Score:2)
I didn't learn any lessons. It just made me wonder why on earth someone named I. P. Freely would use his ini
donotreply.com (Score:2)
"I'll do a quick summery..." (Score:4, Funny)
Been there, done that (Score:2)
I used to host nospin.com. You wouldn't believe all of the bizarre crap that came in for Bill O'Reilly. I used to forward them on, but the sheer volume and, well, stupidity made me trash them instead.
Damn! I wish I had this domain! (Score:2)
Heh - Been there, done that (Score:5, Funny)
My favorites:
Sent: Sunday, July 04, 1999 8:12 AM
To: kai@hershey.com
Subject: From: Kim!!
Hi! grandma I am so thankful that you came all the
way from Florida to see me and by the way..... thanx
for the choc cookie!! and next time you come over
could you bring the extra pleasure condoms. I need
them for me and Ryan.
love you Grandma!!
Kim
Sent: Monday, July 05, 1999 12:09 PM
To: Kim
From: Kai
Subject: From: Kim!!
Kim:
We are not your grandmother.
Kai Ponte
Hershey Business Systems
Then there was this one from an AOL member (figures):
From: TrtleGrl69@aol.com
Sent: Wednesday, August 11, 1999 2:19 PM
Subject: no response to our email dealing with
dead bugs in my payday
I am extremely disappointed at the fact you have not
responded to this incident. I'm upset that I purchased a
payday and began eating it and ended up seeing a worm like
bug with bug carcasses and holes in and on the candy
bar.
I
Talk about extremely bad customer service.
Chad Weaver
I liked my response:
From: Ponte, Kai <kai@hershey.com>
Sent: Monday, August 30, 1999 7:20 AM
To: TrtleGrl69@aol.com
Subject: RE: no response to our email
dealing with dead bugs in my payday
The worm like creature you found - was it alive?
Did it taste good?
Kai Ponte
Information Technology Specialist
Hershey Business Systems
They should be using... (Score:5, Informative)
In a similar manner, people wanting fake IP addresses to use for documentation, training, etc., should use addresses in the 192.0.2.0/24 range, which is reserved by RFC 3330 [rfc-editor.org].
I use .... (Score:2)
How about nospam.com? (Score:4, Interesting)
At first I thought all this (domain hacks) was quite funny. However, it is unfortunate so many see the net as one big crime spree.
He's not just some guy in Seattle... (Score:5, Informative)
Incidentally, they never did send me a prize for winning that CrateMaster contest. Bastards!
Re:He's not just some guy in Seattle... (Score:5, Funny)
Foo@bar.com has been my secretary (Score:3, Interesting)
who@givesafuck.com (Score:4, Funny)
Harvest addresses, sell to spammers (Score:3, Insightful)
Anyone dumb enough to reply to "donotreply" is likely to buy products from spam emails!
He could probably filter into lists based on the mail initiator, and the contents of the original email (quoted in the reply). Plus, the harvested emails are from currently active, valid accounts. These targeted lists of high-quality chumps would be worth paying extra for.
node.com had similar problems. (Score:3, Interesting)
It first existed before canned sendmail configurations from vendors were common, when mail bounced from site to site much like Internet packets from router to router (rather than straight over the net to the target's Mail Transfer Agent), and most sites hacked up their own MTA configurations. A significant number of system administrators (especially at big companies and universities) got the bright idea that their users were likely to follow the manual too closely and send mail to "user@node.com". So they'd hotwire their MTA config such that mail to "@node.com" would bounce the mail with a friendly note to the user.
Of course that massively disrupted mail to node.com. So the sysadmin, from time to time, had to hunt down another "helpful" site's mail admin and educate him.
He also set up a "user"(@node.com) account and used the "vacation" program to send the "helpful letter", thus providing the service for the entire net. Vacation saves the incoming mail, too. It turns out the "problem" was essentially non-existent. "user@node.com" only got one or two mails per month - at least until some idiots used "user" and "node.com" as the default fields in their mailing list signup pages... And then the spammers got hold of it...
you can own the headline domain (Score:2, Informative)
Re:you can own the headline domain (Score:5, Funny)
Re: (Score:3, Insightful)
Re: (Score:3, Insightful)
Which makes us wonder, in turn, why YOU wanted to buy it...
Re:you can own the headline domain (Score:4, Interesting)
The guy has a gold mine, this is illegal... (Score:4, Interesting)
If I owned the domain, I'd be contacting every commercial enterprise who's email got bounced to me, and letting them know that for a nominal fee, they could avoid my getting the feds to take notice of their illegal activities.
Maybe... (Score:5, Insightful)
If by putting fake header in an email, you're filling my email inbox, you're causing me damage, both in terms of stolen resources (you are consuming both bandwidth and storage space, both of which I pay for), and my own time in sorting through the chaff. You owe me for my costs, both in actual dollars and in time and effort. You can choose pay me a reasonable fee to cover my costs and efforts, or I'll let the government show you why you shouldn't have done it in the first place.
BTW, don't assume that law is the same as ethics. There are a lot illegal actions which are perfectly ethical, and vice versa. I choose ethics over law (which, at least in the US, has little meaning).
Re:at least the US (Score:5, Insightful)
Re:at least the US (Score:4, Insightful)
In this whole Rev. Wright thing, it's become very very apparent how the media neglects their responsibility to a)elevate the dialog and b)at least show a 5-minute clip before condemning a man. People expect all of their leaders to be saints, and it's ridiculous.
The only thing that Rev. Wright said that was ridiculous was that the govt created the AIDS virus to kill black people. But then, he also believes in a homonid living in the sky, so I give him a free pass on that. Beyond that, he said:
1. God doesn't bless America for killing innocent people, he damns America for killing innocent people.
2. And he said that our violence in the world begets violence at home.
Which are both teachings straight from the motherfucking Bible, everybody. People are pissed because a preacher preaches from the Bible? Come the fuck on.
[/tangent]
oh, look at that. my captcha is "tedious".
Re: (Score:2)
It's each company's fault if they send him confidential information. They have no business setting up From: addresses to a domain that they do not control.
Re: (Score:2)
I haven't done that, but I used to do something much worse. At one point, for my sins, I served time on the helldesk of an ISP. Every now and then I'd make a note of the email address of a foul-mouthed, abusive caller who really didn't deserve the good service i tried to give everybody. For the next several weeks I'd have fun signing them up for mailing lists, newsletters and using their name on those stupid webforms that want your e