That is so true... Most developers who get an account with Mailgun (http://mailg...

robterrell · on Nov 21, 2011

Ironically, I just came across some potentially real email addresses in the Mailgun docs and sample code, i.e.:

You might want to edit those.

old-gregg · on Nov 22, 2011

We own profista.com and use it for testing ourselves. Using it in the docs helps us see how many people are trying out the samples.

I wish all our users would read the docs as carefully as you do! :)

gsiener · on Nov 22, 2011

Would love to read a post about how you measure sample engagement through this and other cleverness!

pyre · on Nov 21, 2011

Some should setup a MX on test.com and:

* post a public webpage with all email going to @test.com

* post a public webpage with all email addresses harvested from emails to @test.com

Or

* setup an auto responder asking people to stop sending there (bonus points: threaten to post emails of repeat offenders to spammer lists)

robin_reala · on Nov 22, 2011

See also donotreply.com:

http://blog.washingtonpost.com/securityfix/2008/03/they_told...

sneak · on Nov 22, 2011

Whenever you think the solution is to "setup an auto responder".... don't.

troethom · on Nov 21, 2011

You should probably set the example by avoid using "@farfaraway.uk" in your blog posts. It's invalid right now, but that could change too... ;-)

Sukotto · on Nov 22, 2011

Acme Labs has much the same problem. Jef's (2005) article about handling his mail is still a good read (though a bit dated now) http://acme.com/mail_filtering/

stickfigure · on Nov 21, 2011

I agree, test.com is an awful domain to use.

Whenever I fire up email testing tools, I use president@whitehouse.gov.

logn · on Nov 22, 2011

do you notice a lot of vans in your parking lot?