home  bbs  files  messages ]

      ZZNE4431             news.groups             32000 messages      

[ previous | next | reply ]

[ list messages | list forums ]

  Msg # 401 of 32000 on ZZNE4431, Saturday 5-12-23, 2:29  
  From: REBECCA ORE  
  To: CHARLES  
  Subj: Re: RFC2822-compliant email addresses  
 From: spamtrapforore@NOHarvestverizon.net 
  
 In article <120920041211307597%fort@his.com.remove.invalid>, 
  Charles  wrote: 
  
 > In article , Bruce Murphy 
 >  wrote: 
 > 
 > > I wasn't aware gmail had had this sort of problem. Have you found the 
 > > gmail problem to have subsided? I'd be surprised if the google folks 
 > > weren't actively seeking ways to keep it to a dull roar. 
 > 
 > I have two Gmail addresses and have not recieved any spam there yet. 
  
 I think mine was from a dictionary attack based on people's tending to 
 accept gmail's default which is the account name that received the 
 invitation plus the gmail.com after the @ sign.  Changing the default 
 that Gmail offers to something that hasn't been used anywhere else and 
 isn't the same username as another email account that may have been 
 harvested is a good idea. 
  
 Since Gmail set the default that way, harvesting other addresses and 
 substituting gmail.com instead of isp.net probably gets a fair number of 
 hits.  Obviously, that was what happened with my address, and it matches 
 some other anecdotal evidence (a person getting spammed after joining a 
 mailing list with the gmail addy -- a lot of mailing lists are 
 web-searchable).  Gmail may not be enough of an ISP to have standing in 
 a SpamCan suit, but they probably have enough examples of harvested mail 
 that was falsely signed up for third part spam to do quite well in court 
 if they do have ISP standing in terms of that law. 
  
 --- SoupGate-Win32 v1.05 
  * Origin: you cannot sedate... all the things you hate (1:229/2) 

[ list messages | list forums | previous | next | reply ]

search for:

328,121 visits
(c) 1994,  bbs@darkrealms.ca