public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Todd "Waxahachiefortudinouslyexportitionismistically" Hartman <thartman@austin.ibm.com>
To: gnu-win32@cygnus.com (gnuwin32)
Subject: Re: FLORIDA FIRE VICTIMS - NEWS-GROUP-NEWS
Date: Thu, 09 Jul 1998 19:48:00 -0000	[thread overview]
Message-ID: <199807091334.IAA22826@fredthecat.austin.ibm.com> (raw)

> >Is this for real?  I tried the URL here and got nothing (404--Not Found).
> >Is there some way I can ensure that the address above has anything to
> >do with the Better Business Beareau?
> >
> >-- 
> >Todd Hartman           thartman@austin.ibm.com      (512)838-8789
> 
> 
> Todd,
> 
> Checking the URL was the first thing I did too, although I was already 
> highly suspicious.  I find it hard to believe that any reputable organization
> that wanted to help the fire victims would send some blanket email message
> on the net soliciting money.  I suppose there is the possibility that this
> is a real solicitation but I think a better bet is that it is spam.  If you
> or anyone else is interested in helping out victims of the fire in Florida,
> I suggest you contact authorities in Florida directly.  I'm sure they can
> direct you to completely reputable and valid organizations that will make
> sure your donations get to the right places and people.  Sending money to 
> the above address is quite likely going to line someone's pocket in my
> estimation...
> 
> 
> Larry Hall                              lhall@rfk.com


Well, naturally I was a bit suspicious because it looked like bulk e-mail.
Also, the URL had nothing to do with the "Better Business Council"
(whatever that is).  Also, when I sent a message to the sender
(hurricaine@mpinet.net--complete with misspelling), I got an automatic
reply saying that the person had been expelled for bulk e-mailing.  What
I was really hoping for with my original reply to the list was that the
person who sent it would respond to attempt to defend what appeared to
be a rather suspicious request for dough.  Thanks for the replies, though.


todd.

-- 
Todd Hartman           thartman@austin.ibm.com      (512)838-8789
The opinions which may or may not be explicitly expressed or implied in this
document are completely my own and are not necessarily those of my employer.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

             reply	other threads:[~1998-07-09 19:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-07-09 19:48 Todd Waxahachiefortudinouslyexportitionismistically Hartman [this message]
1998-07-10 12:03 ` tjoen
  -- strict thread matches above, loose matches on Subject: below --
1998-07-09 19:48 Craig Ganoe
1998-07-09 13:22 Larry Hall
1998-07-09 10:49 Earnie Boyd
1998-07-08 10:01 Todd Waxahachiefortudinouslyexportitionismistically Hartman
1998-07-09 13:22 ` Michael H. Warfield
1998-07-09 19:48 ` Larry Hall
1998-07-10  5:51 ` Stipe Tolj
1998-07-07  2:37 hurricaine

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199807091334.IAA22826@fredthecat.austin.ibm.com \
    --to=thartman@austin.ibm.com \
    --cc=gnu-win32@cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).