This is the mail archive of the cygwin-talk@cygwin.com mailing list for the cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: That aaaspam thing [was: Read the reports before you trade]


On Thu, Feb 10, 2005 at 10:03:39AM -0000, Dave Korn wrote:
>> -----Original Message-----
>> From: cygwin-talk-owner On Behalf Of Christopher Faylor
>> Sent: 09 February 2005 19:38
>
>> >  Oh, btw, here comes that terrible mailer misconfiguration 
>> problem of mine.  Oh
>> >no, not again.....
>> >
>> >
>> >Richard@usacablenews.com
>> >Richard@usacablenews.com
>> >Richard@usacablenews.com
>> >Richard@usacablenews.com
>> >Richard@usacablenews.com
>> >Richard@usacablenews.com
>> >Richard@usacablenews.com
>> >Richard@usacablenews.com
>> >Richard@usacablenews.com
>> >Richard@usacablenews.com
>> >Richard@usacablenews.com
>> >Richard@usacablenews.com
>> >Richard@usacablenews.com
>> >Richard@usacablenews.com
>> >Richard@usacablenews.com
>> >Richard@usacablenews.com
>> >Richard@usacablenews.com
>> >Richard@usacablenews.com
>> >
>> >
>> >  Heh.  Domain doesn't even have an MX yet, but should he 
>> try and set one up
>> >hopefully he won't find the incoming responses amongst the 
>> spam........
>> 
>> DaveK, you repeated that Richard@usacablenews.com many times? 
>>  Do you realize
>> that if you repeat an address like richard@usacablenews.com 
>> in a message like
>> this then it is possible that Richard@usacablenews.com might, 
>> himself, end
>> up getting a lot of spam due to spam scrapers pulling the 
>> Richard@usacablenews.com
>> name out of the archive?
>> 
>> This probably just slipped your mind.
>> 
>> Apologies to Richard@usacablenews.com in advance for DaveK's 
>> minor screwup.
>
>
>  Yes, you're absolutely right.  I too would like to apologise to
>Richard@usacablenews.com, and indeed to any other users at that domain, such as
>Lucas@usacablenews.com, Angel@usacablenews.com, Lucas@usacablenews.com,
>Angel@usacablenews.com, Lucas@usacablenews.com and Angel@usacablenews.com, not
>to mention the rather oddly named nothanks@usacablenews.com (don't you think
>that nothanks@usacablenews.com is a rather funny email address?  I certainly
>think that nothanks@usacablenews.com sounds a bit odd), and of course
>Angel@usacablenews.com, Lucas@usacablenews.com, and not least of all
>Richard@usacablenews.com, for any inconvenience caused by my accidental posting
>of Richard@usacablenews.com's email address.

Wow, Dave.  You're really slipping!  You included all of the above in a message
AGAIN.

And, you forgot to mention that Blake@usacablenews.com, Caroline@usacablenews.com,
Dakota@usacablenews.com, Dalton@usacablenews.com, Devin@usacablenews.com, Erin@usacablenews.com,
Jenna@usacablenews.com, Paige@usacablenews.com, Seth@usacablenews.com, Shelby@usacablenews.com,
Sophi@usacablenews.com, and Vanessa@usacablenews.com, could also be impacted by
your thoughtlessness.

OOPS!  I just realized that by including Blake@usacablenews.com, Caroline@usacablenews.com,
Dakota@usacablenews.com, Dalton@usacablenews.com, Devin@usacablenews.com, Erin@usacablenews.com,
Jenna@usacablenews.com, Paige@usacablenews.com, Seth@usacablenews.com, Shelby@usacablenews.com,
Sophi@usacablenews.com, and Vanessa@usacablenews.com, in *my* message, I could
be causing them some problems, too.

Oh well.  It's too late now.  I've already pressed the send key.

cgf


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]