> -Original Message-
> From: Stephen Carville [mailto:[EMAIL PROTECTED]]
> Sent: Sun, January 26, 2003 5:48 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Messenger Poppups
>
>
> On Saturday 25 January 2003 08:50 pm, Buck wrote:
> > Hmm, you may have something
-
> From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
> On Behalf Of Stephen Carville
> Sent: Saturday, January 25, 2003 11:34 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Messenger Poppups
>
> On Saturday 25 January 2003 01:49 pm, Jay Crews wrote:
> > Buck writes
> >
PROTECTED]
Subject: Re: Messenger Poppups
On Saturday 25 January 2003 01:49 pm, Jay Crews wrote:
> Buck writes
> >
> > It is obvious from the replies that I am getting that the Linux
crowd is
> > not familiar with the problem. This isn't a put-down, just the
bliss of
&g
On Saturday 25 January 2003 01:49 pm, Jay Crews wrote:
> Buck writes
> >
> > It is obvious from the replies that I am getting that the Linux
crowd is
> > not familiar with the problem. This isn't a put-down, just the
bliss of
> > not having to experience the problem.
>
> That's probably
On Sat, 2003-01-25 at 15:00, Buck wrote:
> I do have a firewall. I learned really quick how to stop the problem.
> My original question was whether or not Redhat had a similar problem. I
> have learned that the problem is unique to "windoz".
>
It occurred to me later that a useful piece of ad
nds.
Of course, I have a bit of a learning curve to get past my windoz
habits.
Thanks
Buck
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
On Behalf Of Jay Crews
Sent: Saturday, January 25, 2003 4:49 PM
To: [EMAIL PROTECTED]
Subject: Re: Messenger Poppups
Buck wri
Buck writes
>
> It is obvious from the replies that I am getting that the Linux crowd is
> not familiar with the problem. This isn't a put-down, just the bliss of
> not having to experience the problem.
That's probably because this is a RedHat Linux mailing list.
We know what M$ is. Some
It is obvious from the replies that I am getting that the Linux crowd is
not familiar with the problem. This isn't a put-down, just the bliss of
not having to experience the problem.
A new form of spam has emerged through a service automatically installed
and enabled on Microsoft Windows produc