I 100% agree, but the servers connecting to our relay are in some cases
badly configured, out of date with patching and just plain old.
We have had no choice but to implement this as we have no control of the
remote servers and in a lot of cases the administration of them has been
sub-contracted out so there is no local knowledge at the end site.
This patch was to provide a cleaner fix rather than the less elegant bogus
authenticator with a name of "\r\n250-AUTH="
-Andy-
> -----Original Message-----
> From: Jakob Hirsch [mailto:jh@plonk.de]
> Sent: 07 December 2005 15:17
> To: andrew.johnson@???
> Cc: exim-dev@???
> Subject: Re: [exim-dev] FW: Legacy EHLO AUTH responses (patch) 4.52
>
> Andrew Johnson wrote:
>
> > related to the AUTH= line (which seems to be deprecated now
> ?!). With
> > help from this list last week, I managed to fix most of my broken
> > users by adding a bogus authenticator to do the AUTH=LOGIN line I
> > needed. This broke some other servers. It seems I need to put the
> > AUTH=LOGIN line BEFORE my AUTH PLAIN LOGIN line - harder to do with
> > the bogus
>
> What server stumbles over a "AUTH=LOGIN" line (especially one
> that comes after "AUTH LOGIN...")? That sounds really broken
> (even though AUTH=LOGIN is not valid in a ESMTP greeting).
>
> And I wonder who needs this, more than six years after RFC
> 2554. But that's a different story...
>
>
>
