Can Outlook 2003 handle newsgroups?

V

_Vanguard_

JM said:
Can Outlook 2003 handle newsgroups or must I use Outlook Express?


Outlook does not support NNTP (network news transfer protocol). It
calls Outlook Express to do that.
 
J

JM

Thanks...

_Vanguard_ said:
Outlook does not support NNTP (network news transfer protocol). It
calls Outlook Express to do that.

--
____________________________________________________________
*** Post your replies to the newsgroup. Share with others.
*** For e-mail, you must append "#NEWS#" to the Subject.
____________________________________________________________
 
D

Don Caton

JM said:
Can Outlook 2003 handle newsgroups or must I use Outlook Express?

Outlook can handle newsgroups directly with a 3rd party add-in.
Otherwise, it just runs Outlook Express to view newsgroups.

If you're interested in an add-in to view newsgroups, my company sells
one http://www.shorelinesoftware.com

There are a couple of others as well.
http://www.slipstick.com/outlook/olexpr.htm has a listing, as well as
lots of other Outlook-related resources.
 
L

Leythos

Can Outlook 2003 handle newsgroups or must I use Outlook Express?

I would strongly suggest that you get a Usenet reader and not use OE as
your method to access Usenet. There are many applications, many free
ones, designed specifically for Usenet access that don't cause the
problems that OE does when posting or reading usenet posts.
 
L

Lanwench [MVP - Exchange]

Leythos said:
I would strongly suggest that you get a Usenet reader and not use OE
as your method to access Usenet. There are many applications, many
free ones, designed specifically for Usenet access that don't cause
the problems that OE does when posting or reading usenet posts.

Forte Agent is a nice one.
That said, I've used OE as my news client for years (with a couple of
add-ins - OETools and OE-Quotefix) and have never had any problems or
complaints to speak of.
 
B

Brian Tillman

Lanwench [MVP - Exchange]
That said, I've used OE as my news client for years (with a couple of
add-ins - OETools and OE-Quotefix) and have never had any problems or
complaints to speak of.

As have I. My only complaint with OE as a newsreader is that yEnc requires
an add-in.
 
L

Leythos

Forte Agent is a nice one.
That said, I've used OE as my news client for years (with a couple of
add-ins - OETools and OE-Quotefix) and have never had any problems or
complaints to speak of.

I guess I should have said, that for the typical home user or other non-
security aware persons, they should not be using OE for Usenet. While I
know that it CAN be setup to properly quote, most people don't have a
clue about the updates, let alone how to properly post to groups. A
typical Usenet reader (rather than an email client) would make life much
simpler for those types of people.
 
L

Lanwench [MVP - Exchange]

Leythos said:
I guess I should have said, that for the typical home user or other
non- security aware persons, they should not be using OE for Usenet.
While I know that it CAN be setup to properly quote, most people
don't have a clue about the updates, let alone how to properly post
to groups. A typical Usenet reader (rather than an email client)
would make life much simpler for those types of people.

I disagree -

1. Outlook Express is a mail *and news* client. In fact, it used to be
called Internet Mail & News.
2. The web interface to the newsgroups is incredibly clunky , often results
in multiple identical posts, and since people already have OE, it's pretty
easy to switch. Even without addins, it's easy to use & will quote by
default - and top-posting is often the norm in these groups anyway.

However, this is really off topic for this group, so I'll shut up now. :)
 
V

Vanguard

"Lanwench [MVP - Exchange]"
message
I disagree -

1. Outlook Express is a mail *and news* client. In fact, it used to be
called Internet Mail & News.

Too bad they changed the name. Lots of posts in here are from Outlook
Express users because they think it's related to Outlook (and they're
often just trying to find something called "Outlook" when navigating the
webnews interface). That stupidity is the same as Symantec buying
Powerquest, dumping their old Ghost product, and renaming DriveImage to
Ghost, so users discussing Ghost might be talking about different
products.
2. The web interface to the newsgroups is incredibly clunky , often
results
in multiple identical posts, and since people already have OE, it's
pretty
easy to switch.

Webnews-for-dummies interface is what it should be called. It's
horrific. Once you use any NNTP (network news transfer protocol)
client, you won't want to use that god awful webnews-for-dummies
interface. No way to watch threads. No way to killfile certain senders
or topics. No way to color code messages of interest based on your own
criteria. No way to ... yadda yadda, the list goes on. Those are the
disadvantages of using webnews. I suppose if you're travelling without
your laptop, if you have one, and getting stuck with using the webnews
interface on someone else's computer, like at the resort or an Internet
cafe, does let you get in your usenet fix, but it's not a real
satisfying fix, sort of like putting creamer powder in your coffee
instead of real cream.
Even without addins, it's easy to use & will quote by
default - and top-posting is often the norm in these groups anyway.

Well, yeah, top-posting is the norm if most users posting in the
newsgroup are using OE unmodified. I've had several arguments regarding
which way is best (I personally prefer top-posting, in the same order as
you see replies in e-mail) and eventually decided to use OE-QuoteFix to
bottom-post instead of the *default* behavior of OE to topmost. I'm
known to be obstinate (i.e., you need to well prove your point) so
switching from top- to bottom-posting was a choice I made in my style to
suit the community rather than myself (i.e., bend a little to fit in,
which is what we all do in a society to establish norms of behavior).

Before Windows XP SP-2, I used OE-Quotefix with Outlook Express to get
my reply at the end of my post. With Windows XP SP-2, there is now a
registry hack to make OE bottompost, so I thought I didn't need
OE-QuoteFix anymore (fixing to bottom-post was the major reason I used
it). However, I've noticed OE cannot figure out how to quote some posts
when it is configured via registry hack to bottompost. I haven't
narrowed it down as to when OE with the bottom-post registry hack
forgets to quote but have seen it screw up on quoted-printable posts.
The quote characters are sometimes missing from the quoted portion. So
I may have to go back to using OE-QuoteFix but which itself has a bug of
melding the first line in the reply portion of a post as the last line
of the quoted portion (i.e., the first line of the reply gets indented
with the quote character). It looks like this happens when a blank line
used as whitespace is absent between the last line of the quoted portion
and the first line of the reply section. Oh well, fix one thing, break
another.
 
L

Lanwench [MVP - Exchange]

Vanguard said:
"Lanwench [MVP - Exchange]"
message
I disagree -

1. Outlook Express is a mail *and news* client. In fact, it used to
be called Internet Mail & News.

Too bad they changed the name. Lots of posts in here are from Outlook
Express users because they think it's related to Outlook (and they're
often just trying to find something called "Outlook" when navigating
the webnews interface).

I totally agree, as I suspect all the Outlook MVPs do as well.
That stupidity is the same as Symantec buying
Powerquest, dumping their old Ghost product, and renaming DriveImage
to Ghost, so users discussing Ghost might be talking about different
products.

What will they rename BackupExec? said:
Webnews-for-dummies interface is what it should be called. It's
horrific. Once you use any NNTP (network news transfer protocol)
client, you won't want to use that god awful webnews-for-dummies
interface. No way to watch threads. No way to killfile certain
senders or topics. No way to color code messages of interest based
on your own criteria. No way to ... yadda yadda, the list goes on.
Those are the disadvantages of using webnews. I suppose if you're
travelling without your laptop, if you have one, and getting stuck
with using the webnews interface on someone else's computer, like at
the resort or an Internet cafe, does let you get in your usenet fix,
but it's not a real satisfying fix, sort of like putting creamer
powder in your coffee instead of real cream.


Well, yeah, top-posting is the norm if most users posting in the
newsgroup are using OE unmodified. I've had several arguments
regarding which way is best (I personally prefer top-posting, in the
same order as you see replies in e-mail) and eventually decided to
use OE-QuoteFix to bottom-post instead of the *default* behavior of
OE to topmost. I'm known to be obstinate (i.e., you need to well
prove your point) so switching from top- to bottom-posting was a
choice I made in my style to suit the community rather than myself
(i.e., bend a little to fit in, which is what we all do in a society
to establish norms of behavior).

I don't really have a preference; I just hate it when flamewars are started
on the topic, and am tempted to suggest that people side-post.
Before Windows XP SP-2, I used OE-Quotefix with Outlook Express to get
my reply at the end of my post. With Windows XP SP-2, there is now a
registry hack to make OE bottompost, so I thought I didn't need
OE-QuoteFix anymore (fixing to bottom-post was the major reason I used
it).

It also does a number of other things & I like it.

However, I've noticed OE cannot figure out how to quote some
posts when it is configured via registry hack to bottompost. I
haven't narrowed it down as to when OE with the bottom-post registry
hack forgets to quote but have seen it screw up on quoted-printable
posts. The quote characters are sometimes missing from the quoted
portion. So I may have to go back to using OE-QuoteFix but which
itself has a bug of melding the first line in the reply portion of a
post as the last line of the quoted portion (i.e., the first line of
the reply gets indented with the quote character).

Usually a problem in the original post, I think...
It looks like
this happens when a blank line used as whitespace is absent between
the last line of the quoted portion and the first line of the reply
section. Oh well, fix one thing, break another.

:)
 
Top