Having the client dump straight to the ISP via SMTP is my top
choice at the moment. The fact that the client machine couldn't
just dump the mail and then be able to log-off isn't going over very
well, though. Sending a large file at the end of the day would keep
the person from logging off for a while.
We have a static IP and a dedicated phone line at the ISP, but I'm
using diald because the telco doesn't have flat rates for
businesses. I'll talk to my ISP, but I kinda doubt they'll go for it. It's
worth a shot. My preference would be ISDN to make the problem
moot, but it's too pricey for management's taste at the moment.
We're a pretty small company. We have RoadRunner in the area,
but it's for personal accounts only right now. Hmmm....maybe set-
up an old 486 on my new RR account and run QMQP from there.
My personal machine is dual-boot with W95, so that one wouldn't
be up all the time, but I could have the 486 masquerade.
Thanks for the ideas!
Mark
> In those situations in which you're sending big files to someone, you could
> point your mail program straight at your ISP's SMTP server (assuming you're
> injecting these messages with SMTP).
>
> Do you have a full-time connection and a static IP address? If so, you might
> get some nice person (like your ISP) to accept mail from you by QMQP. They'd
> have to install qmail, but it wouldn't interfere with sendmail or whatever
> they're using. This would let you supply a single message and as many
> recipients as you like, and queue the whole thing remotely.
>
> Chris
>
