2.3.13 broken submission relay smtp parser

[Aki Tuomi]

> On 09/06/2021 08:57 Tony Hain <tony at tndh.net> wrote:
> 
>  
> I have a new install of dovecot 2.3.13, along with exim 4.94, in an Azure
> hosted FreeBSD 12.2 VM. I have been running exim on local hardware with
> FreeBSD for 15+ years, but dovecot and Azure are a new "learning
> experience". I am getting an error response in dovecot.log when trying to
> use the submission relay function, which is apparently new in 2.3...  It
> would appear the parser is either broken or has a character set limitation
> that no other smtp implementation has. I finally gave up trying to figure
> out what I might have done wrong in setting up exim and pointed dovecot at
> mailjet and got the same error. 
> 
> Jun 08 19:39:42
> submission(testing at dispatch.tndh.net)<89538><lOfAL0zEFNmsOCrh>: Warning:
> smtp-client: conn in-v3.mailjet.com:587 (104.199.96.85:587) [1]: Received
> invalid EHLO response line: Unexpected character in EHLO keyword
> Jun 08 19:39:42
> submission(testing at dispatch.tndh.net)<89538><lOfAL0zEFNmsOCrh>: Warning:
> smtp-client: conn in-v3.mailjet.com:587 (104.199.96.85:587) [1]: Received
> invalid EHLO response line: Unexpected character in EHLO keyword
> 
> I didn't try the mailjet path with telnet, but I had done that earlier with
> the local exim server and I can't see any invalid characters, even in the
> tcpdump pcap file.
> 
> Jun 08 10:49:42
> submission(testing at dispatch.tndh.net)<29791><j8NnyETEqV2sOCq3>: Warning:
> smtp-client: conn 127.0.0.1:58 [1]: Received invalid EHLO response line:
> Unexpected character in EHLO keyword
> # telnet localhost 58
> Trying 127.0.0.1...
> Connected to localhost.
> Escape character is '^]'.
> 220 secure smtp server
> ehlo dovecot.tndh.net
> 250-exim.tndh.net Hello dovecot.tndh.net [127.0.0.1]
> 250-SIZE 536870912
> 250-8BITMIME
> 250-VRFY
> 250-PIPELINING
> 250-X_PIPE_CONNECT
> 250-AUTH CRAM-MD5
> 250-CHUNKING
> 250-SMTPUTF8
> 250 HELP
> 
> This might be some confusion about starttls on the mailjet path, but if that
> is true the error message is wrong; and it wouldn't be true for the local
> exim open smtp port. If it really is smtp, it would be most helpful if the
> error message actually reported what string it is taking issue with. 
> 

Hi!

Can you provide the rawlogs?

Aki