Le 4 juil. 2013 à 15:41, Dmitry a écrit :
> [...]
>
> at the same time tcpflow LMTP
>
> # tcpflow -c -i any host 127.0.0.33
> 127.000.000.033.00024-127.000.000.001.41663: 220 mail Dovecot ready.
> 127.000.000.001.41663-127.000.000.033.00024: LHLO localhost
> 127.000.000.001.41663-127.000.000.033.00024:
> 127.000.000.033.00024-127.000.000.001.41663: 250-mail
> 250-8BITMIME
> 250-ENHANCEDSTATUSCODES
> 250 PIPELINING
> 127.000.000.001.41663-127.000.000.033.00024: MAIL FROM:<t...@test.com> SIZE=25
> 127.000.000.001.41663-127.000.000.033.00024:
> 127.000.000.033.00024-127.000.000.001.41663: 501 5.5.4 Unsupported options
> 127.000.000.001.41663-127.000.000.033.00024: QUIT
> 127.000.000.001.41663-127.000.000.033.00024:
> 127.000.000.033.00024-127.000.000.001.41663: 221 2.0.0 OK
> ^Ctcpflow[5411]: terminating
>
> ***************************************************
Hello Dmitry,
So, it seems that when getting an LMTP connection from dspam, dovecot doesn't
advertise a SIZE extension and that dspam anyway makes use of that extension.
Hmmm... from RFC5321:
In the absence of specific extensions offered by the
server and accepted by the client, clients MUST NOT send such
parameters and servers SHOULD reject commands containing them as
having invalid syntax.
I don't know anything about dspam (beside a quick look at their site) nor how
it integrates in your environment, but it looks like the behavior of dspam's
LMTP client is somewhat buggy.
Seems to be a question for some dspam mailing list...
On the other hand, the release notes for dspam Version 3.10.0 tend to imply
that the problem has been corrected.
HTH
Axel
