On Mon, 2004-04-19 at 14:12 +0100, Philip Hazel wrote:
> On Mon, 19 Apr 2004, Brent Russell Langille wrote:
>
> > > Because it has not followed the RFC. Exim looks for what the RFC says it
> > > should look for, namely
> > >
> > > 250-AUTH LOGIN
> > >
> > > Note the crucial difference.
>
> > i would never have found that. thank you very much. is there any thing i
> > can do about this?
>
> The output you showed contained
>
> 250-AUTH
> 250-AUTH=LOGIN
>
> I know that some MTAs output sequences like
>
> 250-AUTH PLAIN LOGIN ...
> 250-AUTH=LOGIN
>
> in order to support both standard-conforming and some non-standard
> clients. (The = format was used by some clients at one time; perhaps
> this MTA is trying to support such clients.) Maybe the MTA you are
> dealing with is trying to do that, but is misconfigured? You could try
> contacting its administrator.
>
> Philip
>
> --
> Philip Hazel University of Cambridge Computing Service,
> ph10@??? Cambridge, England. Phone: +44 1223 334714.
> Get the Exim 4 book: http://www.uit.co.uk/exim-book
thanks for the advice. i will try to contact the administrator. the only
problem being that i am currently living in korea and i think that
communication will be difficult.
so there is no way to override exim4's strict adherence to the RFC
standard? as i mentioned before i can connect with and submit
authorization with ximian evolution so somehow it it dealing with the
servers' misconfiguration.
thanks again for any advice
