agriculture | asatru | copywrongs | humor | musings | politics | technology | index haxton.org  
   
MacRaven Logo
MacRaven
Dave Haxton's Weblog

Musings, Reflections, Rants and Comments from a Hoosier Heathen husband, father, grandfather, farmer and software engineer. There's really only one of me ...


Contact Me   


RSS Feed   


November
Sun Mon Tue Wed Thu Fri Sat
           
21 22
23 24 25 26 27 28 29
30            



The Blogroll
A Mindful Life The Accidental Smallholder Asahel's Search Austro-Athenian Empire Brad Spangler Cauldron Born DiRT Dispatches Garden of Thought Hardscrabble Creek Honk & Helen In Siberia Laudator Temporis Acti Left Libertarian Little Heathen Fox Lorrie's Livejournal Masson's Blog Mutualist Blog MyAppleMenu nobody asked, BUT NoNAIS Notes on Religion Numenous Thoughts OrangeGuru Overlawyered Prophet or Madman rogueclassicism Secular Blasphemy Sugar Mountain Farm TMN Thud Factor Wildhunt Blog within the crainium

Page Loaded at

Eastern Standard Time

Support Denmark!

No NAIS!

MLL


lunar phases
 


Click for Thorntown, Indiana Forecast

       

home :: Technology :: Google_Mail_Ser..._Spam.writeback

Wed, 09 Apr 2008

Google Mail Servers Enable Backscatter Spam

Does this account for the recent uptick in SPAM?

Google email servers are responsible for a large volume of backscatter spam. No recipient validation is being performed for the domains googlegroups.com and blogger.com — possibly for other Google domains as well, but these two have been confirmed. (You can test this by sending an email to a bogus address in either of the domains; you'll quickly get a Google-generated bounce message.) Consequently spammers are able to launch dictionary attacks against these domains using forged envelope sender addresses. The owners of these forged addresses are then inundated with the bounce messages generated by the Google mail servers. The proper behavior would be for the mail servers to reject email traffic to non-existent users during the initial SMTP transaction. Attempts at contacting them via abuse@google.com and postmaster@google.com have gone unanswered for quite some time. Only automated responses are received which say Google isn't doing anything wrong.

(link) [Slashdot]

/Technology | 0 writebacks | permanent link


writebacks...

comment...

 
Notes: If you put a <mailto:> link in the URL field your address will not be mangled: this could be a bad idea as your email address could be easily harvested by bots designed for SPAM. The comments field should now format correctly for line feeds and carriage returns: when you hit the 'Enter' or 'Return' keys in your comment it should break to a new line. The text should wrap cleanly. Please let me know if it doesn't. No HTML tags will pass through - entering links seems to be the main cause of comment SPAM. Also, please be sure that Javascript is enabled in your browser before attempting to post a writeback. Sorry for any inconvenience, but this really helps cut down on the amount of comment SPAM I have to deal with.
 
 Name:
 URL:(optional)
 Title: (optional)
 Comments:  
Save my Name and URL/Email for next time