Re: MSN Messenger 6.0 and win 98 SE
- From: Jeanie Vejil <proud2have-tsedog@xxxxxxxxxxxxx>
- To: jfw@xxxxxxxxxxxxx
- Date: Sun, 13 Feb 2005 23:43:04 -0600
Chris, I found the correct MSN 6.2 for win 98 SE and Millennium. At first,
I thought when it began to install, it said it was only for Millennium, and
started to write a note back to let you know, but then I went back and
looked at it again, and got it downloaded and installed.
Thanks for your help. Now all I have to do is figure out what is going on
with my MSN passport and/or password.
Jeanie
At 10:15 PM 2/13/05, you wrote:
>Thanks Chris. I'll give it a try.
>
>Jeanie
>
>At 07:53 PM 2/13/05, you wrote:
> >Hi Jeanie,
> >According to the MSN web site, there are two versions of MSN 6.2. There is
> >a MSN 6.2 for XP, and a MSN 6.2 for windows 98 & ME. The link below should
> >take you directly to the download page for MSN 6.2 for windows 98 & ME. If
> >something does not work out, I downloaded the setup file myself, and will be
> >glad to send it to you. Once you get to the web page, hit insert f7 for a
> >links list, hit the letter D, and it should say, download and install later.
> >Hit enter on that link to download the setup file.
> >
> >http://messenger.msn.com/download/?dlos=1
> >
> >Hope this helps,
> >Chris Chaffin
> >
> >----- Original Message -----
> >From: "Jeanie Vejil" <proud2have-tsedog@xxxxxxxxxxxxx>
> >To: <jfw@xxxxxxxxxxxxx>
> >Sent: Sunday, February 13, 2005 7:58 PM
> >Subject: Re: MSN Messenger 6.0 and win 98 SE
> >
> >
> > > Yes, I did, but I'll try it again and maybe get lucky, smile! Thanks.
> > >
> > > Jeanie
> > >
> > >
> > >
> > > At 06:02 PM 2/13/05, you wrote:
> > >>Hi Jeannie, no you can't use the msn 6.2. It is for windows xp only. Did
> > >>you
> > >>try going to msn.com, and in the edit field type in msn 6.0? That is what
> > >>I
> > >>did to find 6.2, and it found it for me.
> > >>----- Original Message -----
> > >>From: "Jeanie Vejil" <proud2have-tsedog@xxxxxxxxxxxxx>
> > >>To: <jfw@xxxxxxxxxxxxx>
> > >>Sent: Sunday, February 13, 2005 6:50 PM
> > >>Subject: RE: MSN Messenger 6.0 and win 98 SE
> > >>
> > >>
> > >> > Hi all. I'm leaving all of this long series of messages intact since
> > >> > they
> > >> > deal with MSN, which is what I'm going to ask about.
> > >> >
> > >> > Many months ago, I'm sure those of you who were on the JFWLite list
> > >> > before
> > >> > it was shut down, remember getting notices that if we were using MSN
> > >> > 4.6,
> > >> > we needed to upgrade to at least MSN 5.0, which I did, and I hated it
> > >> > with
> > >> > a passion. It was a pain in the neck to get signed into, and I had
> > >> > lost
> > >> > all of my contact due to needing a hard drive replacement.
> > >> >
> > >> > Last week, I had to uninstall and reinstall Norton System Works 2003,
> > >> > and
> > >> > after it was installed, it informed me that it wouldn't be able to
> > >> > protect
> > >> > me against anything downloaded from MSN 5.0 and that I would need to
> > >> > upgrade to at least version 6.0.
> > >> >
> > >> > Here's where the problem lies. I can't find MSN 6.0 anywhere. I've
> > >> > been
> > >> > to the JFWLite programs page, and there is MSN 5.0 which won't do me
> > >> > any
> > >> > good as far as Norton's autoprotection is concerned, and there is also
> > >> > MSN
> > >> > 6.2, but it says it's for XP and I'm using win 98 SE.
> > >> >
> > >> > I also went to msn.com and microsoft.com, and I couldn't find MSN 6.0
> > >> > there
> > >> > either.
> > >> >
> > >> > Since I'm running win 98 SE, I'm not going to be able to use MSN 6.2,
> > >> > am
> > >> > I?
> > >> >
> > >> > I had already read the article David posted at the end of this long
> > >> > thread,
> > >> > and that's why I'm asking for advice. I'm also using JFW 5.1.
> > >> >
> > >> > Hope someone has an answer.
> > >> >
> > >> > Jeanie Vejil
> > >> >
> > >> > At 12:16 AM 2/13/05, you wrote:
> > >> >>anyone know where to get windows messenger?
> > >> >>That was always so much better!
> > >> >>Thanks,
> > >> >>Jed
> > >> >>
> > >> >>-----Original Message-----
> > >> >>From: John Miller [mailto:n1umj@xxxxxxxxxxx]
> > >> >>Sent: Saturday, February 12, 2005 7:04 PM
> > >> >>To: jfw@xxxxxxxxxxxxx
> > >> >>Subject: Re: MSN Messenger Users Be Sure To Read This
> > >> >>
> > >> >>
> > >> >>that's why I use windows messenger, that way I don't get the updates
> > >> >>all
> > >> >>the
> > >> >>time and all. I don't miss MSN messenger at all.
> > >> >>----- Original Message -----
> > >> >>From: "Rose Combs" <rosecombs@xxxxxxxxx>
> > >> >>To: <jfw@xxxxxxxxxxxxx>
> > >> >>Sent: Saturday, February 12, 2005 6:01 PM
> > >> >>Subject: RE: MSN Messenger Users Be Sure To Read This
> > >> >>
> > >> >>
> > >> >> > Well, I turned on my computer at nine this morning and it was OK,
> > >> >> > needed
> > >> >> > to perform a reboot at two this afternoon trying to fix another
> > >> >> > problem
> > >> >> > and was getting MSN messenger messages all in my face when I was
> > >> >> > trying
> > >> >> > to do something different, then when I went to check my local
> > >> >> > weather,
> > >> >> > my home page was changed and more than anything that annoys me,
> tell
> > >> >> > me
> > >> >> > to update, do it automatically, bug me if you must but don't switch
> > >> >> > my
> > >> >> > home page to MSN every time I do an update.
> > >> >> >
> > >> >> > I never really use the service, installed it a few weeks ago
> when my
> > >> >> > husband did his for a class he was taking, have no real contacts to
> > >> >> > speak of and don't have a clue how to get them, providing I have
> > >> >> > time.
> > >> >> >
> > >> >> >
> > >> >> >
> > >> >> > Rose Combs
> > >> >> > rosecombs@xxxxxxxxx
> > >> >> > rmcombs@xxxxxxxxxxx
> > >> >> > -----Original Message-----
> > >> >> > From: jfw-bounce@xxxxxxxxxxxxx [mailto:jfw-bounce@xxxxxxxxxxxxx] On
> > >> >> > Behalf Of Jack Lowe
> > >> >> > Sent: Saturday, February 12, 2005 6:08 AM
> > >> >> > To: jfw@xxxxxxxxxxxxx
> > >> >> > Subject: Re: MSN Messenger Users Be Sure To Read This
> > >> >> >
> > >> >> >
> > >> >> > Thanks David, this was interesting. What's even more
> interesting is
> > >> >> > that
> > >> >> > I've not had to upgrade anything with MSN. It's Saturday morning,
> > >> >> > and
> > >> >> > I've
> > >> >> > been able to log in to MSN without being asked to upgrade to
> another
> > >> >> > version. So, where's this alleged MSN upgrade that we all
> > >> >> > supposedly
> > >> >> > must
> > >> >> > do before we can log on? Jack
> > >> >> > ----- Original Message -----
> > >> >> > From: "david the wild-thing" <d.h.whitehead@xxxxxxxxxxxx>
> > >> >> > To: "jfw-list" <jfw@xxxxxxxxxxxxx>
> > >> >> > Sent: Saturday, February 12, 2005 7:51 AM
> > >> >> > Subject: MSN Messenger Users Be Sure To Read This
> > >> >> >
> > >> >> >
> > >> >> >> Hi, I no this is off topic, however, I think some people may find
> > >> >> >> this
> > >> >> >
> > >> >> >> interesting.
> > >> >> >>
> > >> >> >>
> > >> >> >>>>> If you've been having problems logging on to MSN Messenger, be
> > >> >> >>>>> sure
> > >> >> >
> > >> >> >>>>> to read this article. Ryan Naraine - eWEEK
> > >> >> >>>>> Microsoft Corp. on Friday lashed out at two security research
> > >> >> >>>>> firms
> > >> >> > for
> > >> >> >>>>> publishing
> > >> >> >>>>> proof-of-concept exploit code for MSN Messenger hours after
> > >> >> > Microsoft
> > >> >> >>>>> for
> > >> >> >>>>> the product.
> > >> >> >>>>> In one instance, the software giant said malicious hackers have
> > >> >> >>>>> modified
> > >> >> >>>>> the
> > >> >> >>>>> proof-of-concept
> > >> >> >>>>> code into an exploit that puts millions of users at risk of
> code
> > >> >> >>>>> execution
> > >> >> >>>>> attacks
> > >> >> >>>>> that require no user interaction.
> > >> >> >>>>> Moving swiftly to blunt an attack, Microsoft has decided to
> push
> > >> >> > out
> > >> >> >>>>> patched
> > >> >> >>>>> versions
> > >> >> >>>>> of MSN Messenger as a mandatory update. As of Thursday evening,
> > >> >> > users
> > >> >> >>>>> of
> > >> >> >>>>> the
> > >> >> >>>>> popular
> > >> >> >>>>> instant messaging client must update to MSN Messenger version
> > >> >> > 6.2.0205
> > >> >> >>>>> or
> > >> >> >>>>> the MSN
> > >> >> >>>>> Messenger 7.0 beta before they are allowed to log on.
> > >> >> >>>>> "When the vulnerability was announced this week we initially
> > >> >> > introduced
> > >> >> >>>>> an
> > >> >> >>>>> optional
> > >> >> >>>>> upgrade and had plans to make the upgrade mandatory," a
> > >> >> >>>>> Microsoft
> > >> >> >>>>> spokesperson said.
> > >> >> >>>>> "But when we learned that detailed exploit code had been
> > >> >> >>>>> published
> > >> >> > on
> > >> >> >>>>> the
> > >> >> >>>>> Internet
> > >> >> >>>>> we felt the need to take decisive action."
> > >> >> >>>>> According to the exploit code seen by eWEEK.com, an attacker
> > >> >> >>>>> need
> > >> >> > only
> > >> >> >>>>> load
> > >> >> >>>>> a malicious
> > >> >> >>>>> PNG (Portable Network Graphics) file as a buddy icon to launch
> > >> >> >>>>> an
> > >> >> >>>>> attack
> > >> >> >>>>> against
> > >> >> >>>>> every MSN Messenger user on a buddy list.
> > >> >> >>>>> Core Security Technologies, the research company that found and
> > >> >> >>>>> reported
> > >> >> >>>>> the
> > >> >> >>>>> flaw,
> > >> >> >>>>> confirmed that the published exploit code could be used to
> > >> >> >>>>> launch
> > >> >> > blind
> > >> >> >>>>> attacks.
> > >> >> >>>>> "The target doesn't even have to communicate with the attacker.
> > >> >> > Once
> > >> >> >>>>> the
> > >> >> >>>>> attacker
> > >> >> >>>>> has the target's MSN Messenger contact on his contact list, he
> > >> >> >>>>> can
> > >> >> >>>>> launch an
> > >> >> >>>>> attack
> > >> >> >>>>> without the target even knowing," said Max Caceres, director of
> > >> >> > product
> > >> >> >>>>> management
> > >> >> >>>>> at Core Security.
> > >> >> >>>>> Even worse, Caceres told eWEEK.com that the attacker could take
> > >> >> > control
> > >> >> >>>>> of
> > >> >> >>>>> the infected
> > >> >> >>>>> machine and change the target's display to replicate the attack
> > >> >> > against
> > >> >> >>>>> everyone
> > >> >> >>>>> on that buddy list.
> > >> >> >>>>> "This could lead to a massive, widespread attack unless all MSN
> > >> >> >>>>> Messenger
> > >> >> >>>>> users apply
> > >> >> >>>>> the upgrades," he said.
> > >> >> >>>>> Microsoft late Thursday released a to warn customers of the
> > >> >> >>>>> risk.
> > >> >> > The
> > >> >> >>>>> company also
> > >> >> >>>>> provided in a separate notice for both consumer and enterprise
> > >> >> >>>>> MSN
> > >> >> >>>>> Messenger
> > >> >> >>>>> users.
> > >> >> >>>>> Microsoft pinned the blame for the exploit code squarely on the
> > >> >> >>>>> shoulders of
> > >> >> >>>>> Core
> > >> >> >>>>> Security, alleging that the public exploit is based on
> > >> >> > proof-of-concept
> > >> >> >>>>> code
> > >> >> >>>>> released
> > >> >> >>>>> by the Mass.-based information security firm.
> > >> >> >>>>> [Core Security] published proof-of-concept code on the Internet
> > >> >> >>>>> the
> > >> >> >
> > >> >> >>>>> same
> > >> >> >>>>> day
> > >> >> >>>>> Microsoft
> > >> >> >>>>> issued Security Bulletin MS05-009 to resolve the issue. Since
> > >> >> >>>>> then,
> > >> >> > a
> > >> >> >>>>> separate individual
> > >> >> >>>>> has modified the posted code into exploit code," Microsoft said
> > >> >> >>>>> in
> > >> >> > a
> > >> >> >>>>> strongly worded
> > >> >> >>>>> statement.
> > >> >> >>>>> "[T]he publishing of proof-of-concept code within hours of the
> > >> >> > security
> > >> >> >>>>> updates being
> > >> >> >>>>> made available has put customers at increased risk."
> > >> >> >>>>> Caceres dismissed the Microsoft accusation and pointed out that
> > >> >> >>>>> engineers at
> > >> >> >>>>> Core
> > >> >> >>>>> Security worked closely with Microsoft since reporting the
> > >> >> >>>>> vulnerability
> > >> >> >>>>> in
> > >> >> >>>>> August
> > >> >> >>>>> 2003.
> > >> >> >>>>> "We worked with Microsoft for six months to develop this patch.
> > >> >> >>>>> We
> > >> >> >>>>> waited
> > >> >> >>>>> until they
> > >> >> >>>>> released the fix before we published our advisory," Caceres
> > >> >> >>>>> said,
> > >> >> >>>>> arguing
> > >> >> >>>>> that it
> > >> >> >>>>> is common procedure to provide proof-of-concept code to let
> > >> >> > businesses
> > >> >> >>>>> determine
> > >> >> >>>>> whether their systems are secure.
> > >> >> >>>>> Core Security's contained a ZIP-compressed image of a malformed
> > >> >> >>>>> PNG
> > >> >> >
> > >> >> >>>>> file
> > >> >> >>>>> that was
> > >> >> >>>>> intended to allow MSN Messenger users to check to see if they
> > >> >> >>>>> were
> > >> >> >>>>> vulnerable.
> > >> >> >>>>> "We're in the business of getting people to understand how
> > >> >> >>>>> secure
> > >> >> > their
> > >> >> >>>>> systems are
> > >> >> >>>>> and to help them test to see if they are vulnerable. Our
> > >> >> >>>>> proof-of-concept is
> > >> >> >>>>> used
> > >> >> >>>>> for those tests. It is not to be used by an attacker to
> > >> >> >>>>> arbitrarily
> > >> >> >>>>> control
> > >> >> >>>>> a target,"
> > >> >> >>>>> Caceres said.
> > >> >> >>>>> But Microsoft isn't buying that explanation. "A common practice
> > >> >> > among
> > >> >> >>>>> responsible
> > >> >> >>>>> researchers is to wait a reasonable period of time before
> > >> >> > publishing
> > >> >> >>>>> such
> > >> >> >>>>> code .
> > >> >> >>>>> Microsoft is disappointed computer users were not given a
> > >> >> > reasonable
> > >> >> >>>>> opportunity
> > >> >> >>>>> to safeguard their computing environments."
> > >> >> >>>>> As part of the new plan to make the upgrade mandatory, all MSN
> > >> >> >>>>> Messenger
> > >> >> >>>>> users who
> > >> >> >>>>> attempt to log into the system with a vulnerable version of the
> > >> >> > client
> > >> >> >>>>> will
> > >> >> >>>>> be told
> > >> >> >>>>> they need to upgrade in the coming days or they will no longer
> > >> >> >>>>> be
> > >> >> > able
> > >> >> >>>>> to
> > >> >> >>>>> use the
> > >> >> >>>>> service with that vulnerable client.
> > >> >> >>>>> MSN Messenger users running vulnerable clients will receive
> > >> >> >>>>> "toast"
> > >> >> >>>>> warnings
> > >> >> >>>>> about
> > >> >> >>>>> the vulnerability and directed to a They will not be able
> to log
> > >> >> > into
> > >> >> >>>>> the
> > >> >> >>>>> Messenger
> > >> >> >>>>> service until they accept that upgrade. MSN also plans to
> > >> >> > communicate
> > >> >> >>>>> with
> > >> >> >>>>> users
> > >> >> >>>>> via security update via links on MSN properties and Web sites.
> > >> >> >>>>> How to Protect Against an Exploit:
> > >> >> >>>>> MSN Messenger users should make sure their Windows and MSN
> > >> >> > Messenger
> > >> >> >>>>> software is
> > >> >> >>>>> current with the released on Feb. 8. The latest versions of MSN
> > >> >> >>>>> Messenger
> > >> >> >>>>> can be
> > >> >> >>>>> Alternatively, users can install an evaluation copy (beta
> > >> >> >>>>> release)
> > >> >> > of
> > >> >> >>>>> the
> > >> >> >>>>> new MSN
> > >> >> >>>>> Messenger 7.0, which is not targeted by the exploit code.
> > >> >> >>>>> Enterprise businesses should consider removing and blocking MSN
> > >> >> >>>>> Messenger
> > >> >> >>>>> from their
> > >> >> >>>>> environments. If this is not feasible, they should make sure
> > >> >> >>>>> every
> > >> >> >>>>> installed
> > >> >> >>>>> version
> > >> >> >>>>> of Windows and MSN Messenger is current with the latest
> security
> > >> >> >>>>> updates.
> > >> >> >>>>> MSN Messenger is not intended for corporate environments and
> > >> >> > Microsoft
> > >> >> >>>>> recommends
> > >> >> >>>>> uninstalling the client from a business network. Corporate
> > >> >> >>>>> clients
> > >> >> >>>>> should
> > >> >> >>>>> switch
> > >> >> >>>>> to Windows Messenger, which is included with Windows.
> > >> >> >>>>> Corporate users should also consider This can be done by
> > >> >> >>>>> blocking
> > >> >> >>>>> outbound
> > >> >> >>>>> access
> > >> >> >>>>> to TCP port 1863 and blocking HTTP access to
> > >> >> >>>>> messenger.hotmail.com.
> > >> >> >>>>> Check out eWEEK.com's for the latest security news, reviews and
> > >> >> >>>>> analysis.
> > >> >> >>>>> And for
> > >> >> >>>>> insights on security coverage around the Web, take a look at
> > >> >> > eWEEK.com
> > >> >> >>>>> Security Center
> > >> >> >>>>> Editor
> > >> >> >>
> > >> >> >>
> > >> >> >> --
> > >> >> >> To post a message to the list, send it to jfw@xxxxxxxxxxxxx To
> > >> >> >> unsubscribe from this mailing list, send a message to
> > >> >> >> jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject
> > >> >> >> line. Archives located at: //www.freelists.org/archives/jfw
> > >> >> >>
> > >> >> >> If you have any concerns about the list, post received from the
> > >> >> >> list,
> > >> >> >> or
> > >> >> >> the way the list is being run, do not post them to the list.
> Rather
> > >> >> >> contact the list owner at jfw-admins@xxxxxxxxxxxxxx
> > >> >> >
> > >> >> > --
> > >> >> > To post a message to the list, send it to jfw@xxxxxxxxxxxxx
> > >> >> > To unsubscribe from this mailing list, send a message to
> > >> >> > jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject
> > >> >> > line.
> > >> >> > Archives located at: //www.freelists.org/archives/jfw
> > >> >> >
> > >> >> > If you have any concerns about the list, post received from the
> > >> >> > list,
> > >> >> > or
> > >> >> > the way the list is being run, do not post them to the list. Rather
> > >> >> > contact the list owner at jfw-admins@xxxxxxxxxxxxxx
> > >> >> >
> > >> >> >
> > >> >> >
> > >> >> > --
> > >> >> > To post a message to the list, send it to jfw@xxxxxxxxxxxxx
> > >> >> > To unsubscribe from this mailing list, send a message to
> > >> >> > jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject
> > >> >> > line.
> > >> >> > Archives located at: //www.freelists.org/archives/jfw
> > >> >> >
> > >> >> > If you have any concerns about the list, post received from the
> > >> >> > list,
> > >> >> > or
> > >> >> > the way the list is being run, do not post them to the list. Rather
> > >> >> > contact the list owner at jfw-admins@xxxxxxxxxxxxxx
> > >> >> >
> > >> >>
> > >> >>
> > >> >>--
> > >> >>To post a message to the list, send it to jfw@xxxxxxxxxxxxx
> > >> >>To unsubscribe from this mailing list, send a message to
> > >> >>jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject
> > >> >>line.
> > >> >>Archives located at: //www.freelists.org/archives/jfw
> > >> >>
> > >> >>If you have any concerns about the list, post received from the list,
> > >> >>or
> > >> >>the
> > >> >>way the list is being run, do not post them to the list. Rather
> contact
> > >> >>the
> > >> >>list owner at jfw-admins@xxxxxxxxxxxxxx
> > >> >>
> > >> >>
> > >> >>
> > >> >>
> > >> >>--
> > >> >>To post a message to the list, send it to jfw@xxxxxxxxxxxxx
> > >> >>To unsubscribe from this mailing list, send a message to
> > >> >>jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject
> > >> >>line.
> > >> >>Archives located at: //www.freelists.org/archives/jfw
> > >> >>
> > >> >>If you have any concerns about the list, post received from the list,
> > >> >>or
> > >> >>the way the list is being run, do not post them to the list. Rather
> > >> >>contact the list owner at jfw-admins@xxxxxxxxxxxxxx
> > >> >
> > >> > --
> > >> > To post a message to the list, send it to jfw@xxxxxxxxxxxxx
> > >> > To unsubscribe from this mailing list, send a message to
> > >> > jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject
> > >> > line.
> > >> > Archives located at: //www.freelists.org/archives/jfw
> > >> >
> > >> > If you have any concerns about the list, post received from the list,
> > >> > or
> > >> > the way the list is being run, do not post them to the list. Rather
> > >> > contact the list owner at jfw-admins@xxxxxxxxxxxxxx
> > >>
> > >>--
> > >>To post a message to the list, send it to jfw@xxxxxxxxxxxxx
> > >>To unsubscribe from this mailing list, send a message to
> > >>jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line.
> > >>Archives located at: //www.freelists.org/archives/jfw
> > >>
> > >>If you have any concerns about the list, post received from the list, or
> > >>the way the list is being run, do not post them to the list. Rather
> > >>contact the list owner at jfw-admins@xxxxxxxxxxxxxx
> > >
> > > --
> > > To post a message to the list, send it to jfw@xxxxxxxxxxxxx
> > > To unsubscribe from this mailing list, send a message to
> > > jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line.
> > > Archives located at: //www.freelists.org/archives/jfw
> > >
> > > If you have any concerns about the list, post received from the list, or
> > > the way the list is being run, do not post them to the list. Rather
> > > contact the list owner at jfw-admins@xxxxxxxxxxxxxx
> >
> >--
> >To post a message to the list, send it to jfw@xxxxxxxxxxxxx
> >To unsubscribe from this mailing list, send a message to
> >jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line.
> >Archives located at: //www.freelists.org/archives/jfw
> >
> >If you have any concerns about the list, post received from the list, or
> >the way the list is being run, do not post them to the list. Rather
> >contact the list owner at jfw-admins@xxxxxxxxxxxxxx
>
>--
>To post a message to the list, send it to jfw@xxxxxxxxxxxxx
>To unsubscribe from this mailing list, send a message to
>jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line.
>Archives located at: //www.freelists.org/archives/jfw
>
>If you have any concerns about the list, post received from the list, or
>the way the list is being run, do not post them to the list. Rather
>contact the list owner at jfw-admins@xxxxxxxxxxxxxx
--
To post a message to the list, send it to jfw@xxxxxxxxxxxxx
To unsubscribe from this mailing list, send a message to
jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line.
Archives located at: //www.freelists.org/archives/jfw
If you have any concerns about the list, post received from the list, or the
way the list is being run, do not post them to the list. Rather contact the
list owner at jfw-admins@xxxxxxxxxxxxxx
Other related posts:
