Hi Twileg,
how do you manage to break the thread always?
Anyway…
Twilek <twilek@???> (Di 20 Dez 2016 21:04:52 CET):
> I sent a Test message with your logging parameters and the output was
> (sanitized for peronal data):
…
> 17155 Process 17155 is handling incoming connection from [127.0.0.1]
> 17155 SMTP>> 220 www.mydomain.de ESMTP Exim 4.88 Tue, 20 Dec 2016 20:56:34 +0100
> 17155 Process 17155 is ready for new message
…
> 17155 DSN: orcpt: NULL flags: 0
> 17155 SMTP<< BDAT 1048576
> 17155 chunking state 1
> 17155 >>Headers received:
> 17155 Received: from ip-x-x-x-x.x.x.de
> 17155 (ip-x-x-x-x.x.x.de [x.x.x.x]) by
> 17155 www.mydomain.de (Horde Framework) with HTTPS; Tue, 20 Dec 2016
> 19:56:34 +0000
…
> 17155 Data file name: /var/spool/exim4//input//1cJQWY-0004Sh-L1-D
> 17155 SMTP>> 250 1048576 byte chunk received
Exim responds after 1048576 bytes - the end of the current chung.
> 17155 SMTP<<
> 17155 LOG: smtp_protocol_error MAIN
But they (Horde) don't stop sending.
> 17155 SMTP protocol error in "" H=localhost (mydomain.de) [127.0.0.1]
> only BDAT permissible after non-LAST BDAT
> 17155 SMTP>> 503 only BDAT permissible after non-LAST BDAT
> 17155 SMTP<< BDAT 1048576
But the next BDAT seems to announce come as the very next item, I'd say,
there is just a "off by one" error, on Exim's or Horde's side.
> 17155 LOG: smtp_protocol_error MAIN
> 17155 SMTP protocol error in "BDAT 1048576" H=localhost (mydomain.de)
> [127.0.0.1] only RSET accepted now
> 17155 SMTP>> 503 only RSET accepted now
> 17155 SMTP<< 3dUFxtO0/wzyT2yLntnW6mtiIUQj5Vr8SfEHjv4d+D/hX0LzB0
And additionally they do not seem to be interested in the responses to
the data they send.
--
Heiko
