Re: [exim] Upgrade blues...

Startseite
Nachricht löschen
Nachricht beantworten
Autor: Marc Haber
Datum:  
To: exim-users
Betreff: Re: [exim] Upgrade blues...
On Thu, 29 Sep 2005 18:10:29 +0800, Niclas Hedhman
<niclas@???> wrote:
>Well, that depends on which combo of encryption and authentication that is
>tried from the client. Minimum expected was SSL + PLAIN which gives the
>following...
>
>2005-09-29 09:43:06 no host name found for IP address 219.94.56.25
>2005-09-29 09:43:06 SMTP protocol violation: synchronization error (input sent
>without waiting for greeting): rejected connection from H=[219.94.56.25]
>input="\200g\001\003"


That looks, as it has already been said, that your client is directly
starting the SSL negotiation, which is inappropriate for connections
to the server's port 25/TCP.

>If I set No Encryption + PLAIN I get;
>2005-09-29 09:44:44 no host name found for IP address 219.94.56.25
>and the client says the server doesn't support PLAIN authentication
>(expected).


Debian's exim doesn't advertise SMTP AUTH over unencrypted
connections. And since your serverf doesn't advertise STARTTLS, it
looks like you didn't enable TLS, probably by not having read the
chapter "Using TLS" in README.Debian.gz.

>see below. That is the 'compiled output' from the "update-exim4.conf" tool,
>which I don't know whether it is Exim or Debian related.


Not knowing this is probably a sure sign of not having read the
copious amount of Debian specific documentation.

>support_broken_outlook_express_4_server:
> driver = plaintext
> public_name = "\r\n250-AUTH=PLAIN LOGIN"
> server_prompts = User Name : Password
> server_condition = no
>
>which I enabled (didn't make any difference for the KMail case).


If it would help for Kmail, that would have been documented. Actually,
Kmail is pretty good in protocol compliance and doesn't need any hand
holding to work.

Please note that this hack is only needed for Outlook _Express_ _4_,
and not for any later version of Outlook Express, nor for any version
of Outlook (without Express) that I am aware of.

>Well, I thought I can't have been the only one who use 'stock Debian'
>configurations, which stopped working after an upgrade. I expected a "Oh,
>that is because we have introduce XYZ, and you will need to enable/disable
>the parameter ABC" or something like that.


If you used any Debian exim4 package before, then the failure is a
surprise to me. If you used exim 3 before, then please note that you
didn't do an upgrade, but you installed an entirely different package.
There is a chapter "Updating from exim 3" in README.Debian.gz, and the
very first sentence in that README file says that exim4 is an entirely
different package which does not offer a smooth upgrade path from exim
3.

>No, but I don't expect to be a programmer and a 6 RFCs expert to set up the
>most basic outgoing mailserver either. Perhaps too much to ask for.


People running a mail server are widely expected to know their
protocols and basic debugging techniques.

Greetings
Marc

-- 
-------------------------------------- !! No courtesy copies, please !! -----
Marc Haber         |   " Questions are the         | Mailadresse im Header
Mannheim, Germany  |     Beginning of Wisdom "     | http://www.zugschlus.de/
Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834