On Sat, 3 Feb 2001 02:54:10 -0800 (PST),
Howard Schwartz <[EMAIL PROTECTED]> wrote:
>
> My corporate ISP just installed what the level-1 techs call a ``spam
> filter'' for the SMTP mail server. As a result, this server refuses
> to send mail out to anyone not already in its domain, unless my
> mail transport software identifies me as a trusted user, presumably
> with a userid and password.
Does this mean that you will have to use SMTP auth all the time,
or just when you are a "roaming" user?
> I do not know too much about SMTP authentication, except that
> there are several ways to do it (e.g., CRAM-MD3, PLAIN, LOGIN methods),
> that some of them use MIME to encrypt your password, that some of them
> use a new STMP command called `auth' or `auth=<identity>'. I have
> not tried arachne's insight yet to see if it has SMTP authentication.
> Can any one help me figure out if I can tweak my old SMTP programs to
> provide some form of this authentication? I was hoping this might be
> done with some varient of the traditional `HELO' command, or by
> first logging in to the POP server, giving my identity, and then
> switching to SMTP.
I'm pretty sure it's your ISP that decides what athentication
protocol, if any, is required on its mailservers. SMTP auth is
not the same as POP-before-SMTP. DOS clients should be able to
handle the latter, but not the former. Since I've never had to
use SMTP auth, I don't even know which Linux clients support it.
> Any ideas? I hate to see my dos smtp days coming to an end.
Another factor you may have to consider is whether or not your
ISP blocks port 25, which forces you to use your ISP's smarthost.
If they don't, then you should be able to find another e-mail
service that will allow you to send mail using POP-before-SMTP,
or, as long as your ISP's dialups are not listed in the DUL,
you can send direct-to-MX (ka9q can do this).
If they do block port 25 and they also force SMTP auth, you may
be SOL.
Howard E.
--
DOS TCP/IP * <URL:http://www.ncf.ca/~ag221/dosppp.html>
