[Dovecot] DOVECOT 2.2.4 = 501 5.5.4 Unsupported options in LMTP
Hi,
Sorry for my english. My problem:
dspam-3.9.0 (dspam-3.10.2 all the time segmentation fault) dspam.conf .................... # DeliveryHost /var/run/dovecot/lmtp # same error as IP DeliveryHost 127.0.0.33 DeliveryPort 24 DeliveryProto LMTP .................... ServerHost 192.168.1.34 ServerPort 24 ServerQueueSize 32 ServerPID /var/run/dspam/dspam.pid
dovecot-2.2.4 10-master.conf service lmtp { # Create inet listener only if you can't use the above UNIX socket inet_listener lmtp { # Avoid making LMTP visible for the entire internet address = 127.0.0.33 port = 24 } }
quota is not included
telnet to dspam LMTP
# telnet 192.168.1.34 24 Trying 192.168.1.34... Connected to 192.168.1.34. Escape character is '^]'. 220 DSPAM LMTP 3.9.0 Ready LHLO test.com 250-localhost.localdomain 250-PIPELINING 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 SIZE MAIL FROM:<test@test.com> 250 2.1.0 OK RCPT TO:<user@test.com> 250 2.1.5 OK DATA 354 Enter mail, end with "." on a line by itself 1234567 qwertyu asdfghj
. 530 5.3.0 <user@test.com> Fatal: 501 5.5.4 Unsupported options QUIT 221 2.0.0 OK Connection closed by foreign host.
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:<test@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
after telnet to dovecot LMTP
# telnet 127.0.0.33 24 Trying 127.0.0.33... Connected to 127.0.0.33. Escape character is '^]'. 220 mail Dovecot ready. LHLO test.com 250-mail 250-8BITMIME 250-ENHANCEDSTATUSCODES 250 PIPELINING MAIL FROM:<test@test.com> 250 2.1.0 OK RCPT TO:<user@test.com> 250 2.1.5 OK DATA 354 OK 1234567 qwertyu asdfghj
. 250 2.0.0 <user@test.com> WVKvFEln1VEuFQAAZU03Dg Saved QUIT 221 2.0.0 OK
How can I persuade dovecot to deliver the mail?
And one more:
telnet to dovecot LMTP # telnet 127.0.0.33 24 .................... MAIL FROM: test@test.com 501 5.5.4 Invalid parameters MAIL FROM: <test@test.com> 501 5.5.4 Invalid parameters MAIL FROM:<test@test.com> 250 2.1.0 OK
telnet to dspam LMTP # telnet 192.168.1.34 24 .................... MAIL FROM: test@test.com 250 2.1.0 OK ....................
# telnet 192.168.1.34 24 .................... MAIL FROM: <test@test.com> 250 2.1.0 OK ....................
Thank you!
Regards, Dmitry
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:<test@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
participants (2)
-
Axel Luttgens
-
Dmitry