Re: [Evolution] HELO respose error: (again)

[Dave Rigby <drigby opaltelecom co uk>]

Hi Guys

I've worked out what it is - We have a firewall / NAT box that
translates our private IPs to public IPs. It would appear that this acts
as a transparent firewall, and it is this box that doesn't understand
the EHLO, and responds with the 502.

However, this is still a bug in Evolution, as it should handle this much
more gracefully.

In Summary:

During an SMTP conversation, if an EHLO fails, then evolution should
drop to HELO, and not report any errors.

People can argue about whether or not this follows the specs, but from
an enduser's point of view, if Outlook/Mozilla/Kmail/etc works, then so
should Evo.

I think that people are under the impression this bug is fixed, but it
isn't! (I'm using the latest devel snapshot RPMS btw)


Regards

Dave 


On Fri, 2002-08-23 at 15:13, Tony Earnshaw wrote:
> fre, 2002-08-23 kl. 14:22 skrev Dave Rigby:
>
> > OK, I work with the guys who configure the mail server, so do you know
> > specifically what needs to be setup in the config? I'm vaguely familar
> > with exim.
>
> Dave,
>
> I've checked out a *very* old Exim server (Exim v2.12 at Oslo University
> - the present version is v4.10 with v4.11 coming along), looked through
> the Makefile and configs of my present 4.10 and my cat Billy's checked
> out Opaltelecom's Exim mail server.
>
> There's nothing wrong with any of them - all of them accept EHLOs, but
> some with many more ESMTP possibilities than others.
>
> So my conclusion is that you've configured your Evo client to do
> something your MTA's not capable of. Reason for this are the 502 message
> possibilities in RFC1869 and RFC1982.
>
> What could you be doing (bearing in mind that others have not reported
> suchlike)?
>
> There are 2 possibilities, for which Exim (at least the latest versions)
> can be configured, and which my present version supports, but which
> Opaltelecom's doesn't support:
>
> 1: SSL, but Evo 1.0.x and 1.1.x send different commands for this, as far
> as I've gathered and Opalcom's ESMTP does not support SSL;
> 2: AUTH and AUTH method, but Opalcom's ESMTP does not support AUTH at
> all.
>
> The fact that there are no faults with your other mail clients (MUAs)
> and mail to the same server, would suggest that either they aren't
> trying either of the above, or they don't register 5xx messages from the
> MTA.
>
> Precisely what you are doing you can see in Exim's mail log (normally
> called "mainlog", but you might be using Debian which differs in many
> config options), which should log all faults.
>
> The rest is definitely OT, but if you want you can mail me privately
> (Billy da Kat answers mail at the same address too!).
>
> Best,
>
> Tony
>
> -- 
>
> Tony Earnshaw
>
> The usefulness of RTFM is vastly overrated.
>
> e-post:               tonni billy demon nl
> www:          http://www.billy.demon.nl
> gpg public key:       http://www.billy.demon.nl/tonni.armor
>
> Telefoon:     (+31) (0)172 530428
> Mobiel:               (+31) (0)6 51153356
>
> GPG Fingerprint = 3924 6BF8 A755 DE1A 4AD6 FA2B F7D7 6051 3BE7 B981
> 3BE7B981
-- 
Regards

Dave Rigby <drigby opaltelecom co uk>
IP Services Team

Opal Telecom