olin_piclist@embedinc.com"OlinLathrop" wrote:

> Gerhard Fiedler wrote:
>> Have you tried the SMTP server that comes with Win2k? AFAIK fits all
>> your reqs, and it's already there.
> 
> I wasn't aware Windows 2000 came with a outgoing SMTP server.  I'll
> look into that.  Would you happen to have pointers on where in the
> overwhelming pile of Microsoft documentation to start looking?

See Adam's message; this should you get started. Then go to Control
Panel > Administrative Tools > Internet Information Services, where you
might have an FTP server, a web server and an SMTP server. Stop the ones
you don't want; right-click on the ones you want to configure and check
out their Properties dialogs.

Help is available for most dialogs; this should get you somewhere. If
not, searching for specific terms usually helps me. This is a standard
tool, out there for a long time.


>> There's also http://www.postcastserver.com/ (no experience, but looks
>> like it is what you want, if you can't get the Win2k server going).
> 
> That is one of the ones I tried and gave up on.  It's a mess.  The
> interface is fine and it supposedly does what I want, but it just
> doesn't quite work right.  It's very slow and eats up a lot of CPU
> for no apparent reason, can't deliver some messages for no apparent
> reason, and there wasn't a obvious way to have it give up on messages
> after a certain number of tries, clear them out of the queue, and
> send a error reply.

Wow... I wonder why somebody bothers to publish something like this.

> I have meanwhile found something called QK SMTP server.  It is
> supposedly configurable to do exactly what I want.  It even has the
> additional nice feature that after a configurable number of failed
> attempts to send a message directly it can fall back on delivering it
> to other outgoing SMTP servers.  That's what I have installed at this
> point.  The current problem with it is that although the GUI
> interface has a checkbox for "Run at Windows startup", it doesn't, or
> perhaps it tries and then craps out for some reason without leaving
> any trace.  It seems to work well when I run it manually after
> logging in to Windows, but that's no good long term. 

There are tools to run normal applications as Windows services. If their
built-in mechanism doesn't work, you could try this.

Gerhard
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist