250-AUTH=LOGIN CRAM-MD5 PLAIN
250-AUTH LOGIN CRAM-MD5 PLAIN
250-PIPELINING
250 8BITMIME

Where RFC2554? Sorry, but i'm don't have this RFC...


> [arith@foo arith]$ telnet foo.com 25
> Trying 192.0.0.1...
> Connected to foo.com
> Escape character is '^]'.
> 220 foo.com ESMTP
> ehlo foo.com
> 250-foo.com
> 250-PIPELINING
> 250 8BITMIME
>
> qmail don't support RFC2554
>
> -----Original Message-----
> From: Michail A.Baikov [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 08, 2001 4:31 PM
> To: Matt Simonsen; Enrique Vadillo
> Cc: [EMAIL PROTECTED]
> Subject: Re: SMTP authentication
>
>
> Qmail support SMTP Authorization (RFC2554) ?
>
>
> ----- Original Message -----
> From: "Enrique Vadillo" <[EMAIL PROTECTED]>
> To: "Matt Simonsen" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Wednesday, February 07, 2001 10:40 PM
> Subject: Re: SMTP authentication
>
>
> > I got exactly the same problem, the only thing i could do for now is
> > to give them a webmail frontend but most people are very used to sending
> > mail using their favorite mail programs.
> >
> > anyone here know any way this can be done? i use qmail on solaris,
> > i'm open to any ideas.
> >
> > iPass has no information on this even though it's very related to their
> > business.
> >
> > Enrique-
> >
> > |o| ---- Matt Simonsen escribió ----
> > |o| Is it possible/adviseable to run a Qmail server to authenticate all
> relay
> > |o| SMTP traffic so that we can leave the relay open but not allow
> spammers
> > |o| access? I have Qmail running with Courier IMAP server, my problem is
> that we
> > |o| have some users with laptops who travel and use different ISPs out
of
> the
> > |o| office and would not be able to get email through out SMTP server.
To
> ask
> > |o| them to change settings may be too much. I have thought of setting
up
> 2
> > |o| Outlook profiles for them with different outgoing mail servers, but
I
> am
> > |o| hoping there is a way to allow their traffic through via a username
> and
> > |o| password combo.
> > |o|
> > |o| Thanks
> > |o| Matt

Reply via email to