Also you must have a
tls_advertise_hosts = *
to publicise TLS capabilities.
This is not your problem though, as the telnet session to your
mailserver seems to indicate.
When you telnet localhost 25 (if you are on the server), you should
get a line like:
220 mail.nisus.com ESMTP Exim 4.11 Thu, 02 Jan 2003 15:00:59 +0000
with the appropriate hostname/version/date. After that you can try a normal:
HELO localhost
that should work. Then you can again try an EHLO localhost. If that
does not work (and you are telnetting from the server itself) then I
have no idea of what is going on..
But it looks like the problem is only for remote connections and that
Nico's might have given you the solution?
Giuliano
At 6:25 -0800 2003/01/02, <dave@???> wrote:
> > On Thu, 2 Jan 2003, dave@??? wrote:
>>
>>> My client is sendin that command, I was not using telnet.
>>
>> Well, if your client really sends such crap, your should look out for
>> another one :)
>>
>>> When I get back into the office, I will run the exim -d -bh 10.0.1.2.
>>
>> check auth_advertise_hosts in your configfile, in the most cases, it
>> should be
>>
> > auth_advertise_hosts = *
>>
>> or at least
>>
> > auth_advertise_hosts = !+relay_hosts
>>
>> the first one will advertise AUTH to ALL connecting clients, the other
>> one will restrict the announcement to clients not in your relay_hosts
>> hostlist (which prevents some problems with broken clients, that want to
>> authenticate in any case if AUTH is published).
>>
>> ciao
>
>I don't have auth_advertise_hosts in my configfile at all.
>
>Here is my configfile:
>
--
H U M P H
|| |||
software
Java & C++ Server/Client/Human Interface applications on MacOS - MacOS X
http://www.humph.com/
