[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cobalt-users] POP before SMTP
- Subject: RE: [cobalt-users] POP before SMTP
- From: <rpaiz@xxxxxxxxxxxxxx>
- Date: Sat Mar 24 00:32:01 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
> Outlook may be stupid ...however it is also clever..
I'll debate that...
> As there is a simple solution...(forced authorisation)
SMTP authentication and POP-before-SMTP are *not* the same thing. What
you describe in your post is the correct way to use SMTP authentication
(identifying yourself to the SMTP server) rather than POP-before-SMTP (a
small application which remembers which IP address you POP'd from for 15
minutes and allows relaying to/from that IP address. The two are
entirely unrelated
While your server may have SMTP authentication configured (which will in
fact allow you to relay from anywhere if you successfully authenticate),
many servers don't have this setup (including mine). You have
implemented a second solution to the problem, but this is *not* related
to POP-before-SMTP and will not solve the original poster's problem if
his sendmail just happens not to know how to authenticate.
> Outlook can be a bit frustrating at times, however I don't know
> of a more flexible email program.
Eudora (my preference)
Pegasus.
Both substantially more flexible at email, both multi-platform, both
more stable, and both without the hassles and the bugs and the problems
and the memory hogging and the MS bull and the incompatible address
lists and the... never mind.
Outlook is the only mail client on Earth that can even *have* a damaged
contact record (something I've never seen anywhere else), and why such a
thing would break your ability to send mail to anyone is beyond me. Yet
the "No transport provider was available..." 'feature' is
well-documented, and I've seen it on dozens of systems.
I'm only stuck on Outlook for another two months or so, while I finish
migrating my old office away from that $#@!%$!!! Exchange Server. Sorry,
I very strongly disagree with you.
--
Rodolfo J. Paiz
rpaiz@xxxxxxxxxxxxxx <mailto:rpaiz@xxxxxxxxxxxxxx>