IIS and SMTP - Reading news over HTTP?

Author

Reading news over HTTP?

Eric Dan

2005-03-22, 2:51 am

Hi,

Is there any support in the news server (IIS 6) for reading news over HTTP?

If the above support does not exist and I know that many organizations use
this scenario (news over HTTP) is there a complementary product? any other
ideas?

--
Thanks
Eric

Jason Brown [MSFT]

2005-03-26, 2:47 am

There's no built-in support, no. There are numerous third-party products for
this though - you might want to take a look over at www.asp.net - they may
well have a community project open on this subject.

--
Jason Brown
Microsoft GTSC, IIS

This posting is provided "AS IS" with no warranties, and confers no rights.

"Eric Dan" <nospam@stopspamming.com> wrote in message
news:80591F8D-CAFD-4034-BA29-C3FFDDFC8D13@microsoft.com...
> Hi,
>
> Is there any support in the news server (IIS 6) for reading news over
> HTTP?
>
> If the above support does not exist and I know that many organizations use
> this scenario (news over HTTP) is there a complementary product? any other
> ideas?
>
> --
> Thanks
> Eric

Peter D. Hipson

2005-03-26, 6:04 pm

Another alternative is Exchange Server which does support HTTP
newsgroups. IMHO, the licensing issues are so convoluted and
non-understandable that it is unclear whether you can allow anomous
public access or not. I did ask Microsoft for a definative answer and
even they could (would?) not come up with one. Once MS gets its
license issues more sane and logical, Exchange Server is a viable too.
Right now, I'd say there are better, less complex (legally and
technically) solutions.

It would be nice if Exchange server didn't bother with client
licensing... IMHO (again) MS is missing the boat here: Exchange Server
client licenses are so expensive that it virtually eliminates the
product from serious consideration for many potential users. But then
again, it is MS's product, so they can do as they like. I just wish I
could give my consulting clients better news about costs using a MS
solution!

On Sat, 26 Mar 2005 14:47:25 +1100, "Jason Brown [MSFT]"
<i-brjaso@online.microsoft.com> wrote:

>There's no built-in support, no. There are numerous third-party products for
>this though - you might want to take a look over at www.asp.net - they may
>well have a community project open on this subject.

PeterD, the Darkstar Network
To email, fix my address!
ExpertZone!

Jason Brown [MSFT]

2005-03-27, 2:47 am

Well, it's not my department to comment on licencing and pricing but I will
note that Exchange Server as a standalone product is very much aimed at the
enterprise; medium to large businesses.

Small Business Server bundles Exchange at a very affordable rate, but you
are limited on the number of clients which can connect.

--
Jason Brown
Microsoft GTSC, IIS

This posting is provided "AS IS" with no warranties, and confers no rights.

"Peter D. Hipson" <mcn01 at hipson dot net> wrote in message
news:k6ua4115j0c8tv0sqra4ot4f7qu5glvuij@
4ax.com...
> Another alternative is Exchange Server which does support HTTP
> newsgroups. IMHO, the licensing issues are so convoluted and
> non-understandable that it is unclear whether you can allow anomous
> public access or not. I did ask Microsoft for a definative answer and
> even they could (would?) not come up with one. Once MS gets its
> license issues more sane and logical, Exchange Server is a viable too.
> Right now, I'd say there are better, less complex (legally and
> technically) solutions.
>
> It would be nice if Exchange server didn't bother with client
> licensing... IMHO (again) MS is missing the boat here: Exchange Server
> client licenses are so expensive that it virtually eliminates the
> product from serious consideration for many potential users. But then
> again, it is MS's product, so they can do as they like. I just wish I
> could give my consulting clients better news about costs using a MS
> solution!
>
>
>
> On Sat, 26 Mar 2005 14:47:25 +1100, "Jason Brown [MSFT]"
> <i-brjaso@online.microsoft.com> wrote:
>
>
> PeterD, the Darkstar Network
> To email, fix my address!
> ExpertZone!

Peter D. Hipson

2005-03-27, 5:54 pm

Jason, that describes Exchange quite well. However, for a solution for
many, Exchange's licensing model is not 'friendly'. I've had to
install other products with customers because of this, and that
translates to lost sales for MS. However, neither you, nor I, will be
able to change this...

For example, say I'm an ISP and offereing email to my customers. I can
charge, if I'm lucky maybe 14.95/month for the service. That's $180 a
year per client. Now, if I restrict each client to one email address
(that is unrealistic, however) and a client license costs me about $80
per client (street price, not list!) that means that of my gross
income, I spend almost 50% just for the client email license! That
leaves me with $100 to cover cost of services, hardware, and whatever
else there is. At those costs, it is not effective--I'm better off
with other solutions (which may not have all the functionality, but
"bang for buck" do blow Exchange out of the water...

---real case study:

I really think the most amazing thing is that MS was not able to
clarify how, if at all, when NNTP server parts of Exchange are
available to the public at large, what cleint licensing is needed, if
any! I asked, they could (or would?) not tell me. Where does that
leave me? Either I forget about client licensing and hope that MS
doesn't decide to sue me, or I find a solution that is more cost
effective.

Care to guess what solution was implemented?

--- end of case study!

This issues also affect many small businesses...

I'm not ragging on you, Jason, just trying to get my point across.

On Sun, 27 Mar 2005 14:37:13 +1000, "Jason Brown [MSFT]"
<i-brjaso@online.microsoft.com> wrote:

>Well, it's not my department to comment on licencing and pricing but I will
>note that Exchange Server as a standalone product is very much aimed at the
>enterprise; medium to large businesses.
>
>Small Business Server bundles Exchange at a very affordable rate, but you
>are limited on the number of clients which can connect.

PeterD, the Darkstar Network
To email, fix my address!
ExpertZone!

Eric Dan

2005-03-29, 7:50 am

Thanks a lot for all your responses Jason and Peter.
Eric

"Peter D. Hipson" wrote:

> Jason, that describes Exchange quite well. However, for a solution for
> many, Exchange's licensing model is not 'friendly'. I've had to
> install other products with customers because of this, and that
> translates to lost sales for MS. However, neither you, nor I, will be
> able to change this...
>
> For example, say I'm an ISP and offereing email to my customers. I can
> charge, if I'm lucky maybe 14.95/month for the service. That's $180 a
> year per client. Now, if I restrict each client to one email address
> (that is unrealistic, however) and a client license costs me about $80
> per client (street price, not list!) that means that of my gross
> income, I spend almost 50% just for the client email license! That
> leaves me with $100 to cover cost of services, hardware, and whatever
> else there is. At those costs, it is not effective--I'm better off
> with other solutions (which may not have all the functionality, but
> "bang for buck" do blow Exchange out of the water...
>
> ---real case study:
>
> I really think the most amazing thing is that MS was not able to
> clarify how, if at all, when NNTP server parts of Exchange are
> available to the public at large, what cleint licensing is needed, if
> any! I asked, they could (or would?) not tell me. Where does that
> leave me? Either I forget about client licensing and hope that MS
> doesn't decide to sue me, or I find a solution that is more cost
> effective.
>
> Care to guess what solution was implemented?
>
> --- end of case study!
>
> This issues also affect many small businesses...
>
> I'm not ragging on you, Jason, just trying to get my point across.
>
> On Sun, 27 Mar 2005 14:37:13 +1000, "Jason Brown [MSFT]"
> <i-brjaso@online.microsoft.com> wrote:
>
>
> PeterD, the Darkstar Network
> To email, fix my address!
> ExpertZone!
>