search for: ehlo

On 28/08/2020 01:11, Alec Moskvin wrote: > Hello, > > When connecting to Exim 4.94, dovecot submission logs this warning: > > dovecot[25235]: submission(alec)<25347><QNydV8+t+oMKAgAF>: Warning: smtp-client: conn localhost:25 ([::1]:25) [1]: Received invalid EHLO response line: Unexpected character in EHLO keyword > > Looks like it doesn't like the underscore in "X_PIPE_CONNECT", since > it's neither "isalnum" nor a dash [1]: > > 1598480923.401085 220 myhostname ESMTP Exim 4.94 Wed, 26 Aug 2020 18:28:43 -0400 &g...

...ved by intended recipient. > > in local dovecot logs I notice > > ==> /var/log/dovecot/dovecot.log <== > 2020-09-24 16:22:19 submission(recipient at example.com)<xxxxxxxxxxxxxxxx>: Warning: smtp-client: conn smtp.fastmail.com:465 (66.111.4.140:465) [1]: Received invalid EHLO response line: Unexpected character in EHLO keyword > > at debug level > > ==> /var/log/dovecot/dovecot-debug.log <== > 2020-09-24 16:22:19 submission(recipient at example.com)<xxxxxxxxxxxxxxxx>: Debug: smtp-client: conn smtp.fastmail.com:465 (66.111.4.140:465) [1]: com...

Hello, When connecting to Exim 4.94, dovecot submission logs this warning: dovecot[25235]: submission(alec)<25347><QNydV8+t+oMKAgAF>: Warning: smtp-client: conn localhost:25 ([::1]:25) [1]: Received invalid EHLO response line: Unexpected character in EHLO keyword Looks like it doesn't like the underscore in "X_PIPE_CONNECT", since it's neither "isalnum" nor a dash [1]: 1598480923.401085 220 myhostname ESMTP Exim 4.94 Wed, 26 Aug 2020 18:28:43 -0400 1598480923.401906 250-my...

...l's delivered/received by intended recipient. in local dovecot logs I notice ==> /var/log/dovecot/dovecot.log <== 2020-09-24 16:22:19 submission(recipient at example.com)<xxxxxxxxxxxxxxxx>: Warning: smtp-client: conn smtp.fastmail.com:465 (66.111.4.140:465) [1]: Received invalid EHLO response line: Unexpected character in EHLO keyword at debug level ==> /var/log/dovecot/dovecot-debug.log <== 2020-09-24 16:22:19 submission(recipient at example.com)<xxxxxxxxxxxxxxxx>: Debug: smtp-client: conn smtp.fastmail.com:465 (66.111.4.140:465) [1]: command EHLO: Got reply (1...

Log report is reporting a lot of these lately.. following is just a short snippet from the beginning on one server. WARNING!!!! Possible Attack: Attempt from 104.29.broadband2.iol.cz [83.208.29.104] with: command=HELO/EHLO, count=3 : 1 Time(s) Attempt from 106.7.broadband7.iol.cz [88.102.7.106] with: command=HELO/EHLO, count=3 : 1 Time(s) Attempt from 106.74.broadband5.iol.cz [88.100.74.106] with: command=HELO/EHLO, count=3 : 1 Time(s) Attempt from 126.239.broadband7.iol.cz [88.102.239.126] with:...

...submission_relay_port = 8587 submission_relay_rawlog_dir = /var/log/dovecot/ submission_relay_trusted = yes My main issue is that until I login, dovecot-submission won't connect to the backend and query the capabilities and so won't report the right capabilities. That mean that the first EHLO message don't get the right capabilities list. " EHLO example.com 250-smtp.example.com 250-8BITMIME 250-AUTH PLAIN LOGIN 250-BURL imap 250-CHUNKING 250-ENHANCEDSTATUSCODES 250-SIZE 250 PIPELINING " This list don't contains VRFY, DNS, and SIZE is not specified (all of these is p...

...y_rawlog_dir = /var/log/dovecot/ >> submission_relay_trusted = yes >> >> My main issue is that until I login, dovecot-submission won't connect to the backend and query the capabilities and so won't report the right capabilities. >> >> That mean that the first EHLO message don't get the right capabilities list. >> >> " >> EHLO example.com >> >> 250-smtp.example.com >> 250-8BITMIME >> 250-AUTH PLAIN LOGIN >> 250-BURL imap >> 250-CHUNKING >> 250-ENHANCEDSTATUSCODES >> 250-SIZE >>...

I couldn't find working solutions for this anomalie on the net. What does this mean and does someone know how to fix this? postfix/smtpd[18757]: improper command pipelining after EHLO from unknown[192.168.10.233]: QUIT\r\n Thanks Best Regards, Leander

...d Postfix master.cf: https://pastebin.com/W0nynZG6 dovecot.conf: https://pastebin.com/tMD90Znn This is what my server logs (mail.info, mail.warn) tell me: root at bgrsld-mail0:~# tail /var/log/mail.info Jul 17 18:22:08 bgrsld-mail0 postfix/submission/smtpd[8472]: improper command pipelining after EHLO from unknown[192.168.2.110]: QUIT\r\n Jul 17 18:22:08 bgrsld-mail0 postfix/submission/smtpd[8465]: disconnect from unknown[192.168.2.110] ehlo=1 quit=1 commands=2 Jul 17 18:22:08 bgrsld-mail0 postfix/submission/smtpd[8472]: disconnect from unknown[192.168.2.110] ehlo=1 quit=1 commands=2 Jul 17 18...

Hello folks, I have a CentOS 6.4 installation running Sendmail, and after some serious hair tear stare and compare I'm a bit stumped. When I connect to the server either with telnet or SSL, sendmail is not presenting the AUTH capability after an EHLO. Everything looks like it should be working, but no amount of tweaking is getting the AUTH capability advertised (and it doesn't work if you just try it anyway). Here's the config bits from sendmail.mc-- define(`confAUTH_OPTIONS', `A p')dnl define(`confAUTH_MECHANISMS', `EX...

Dear all, I am stuck on this issue for days, I am able to connect on my IMAP server using Apple mail client but thunderbird shows me this error: "improper command pipelining after EHLO" I have tried all the ports in manual config but it just is not working while Apple Mail is able to connect perfectly, here are my configuration details of "postconf -n" , "doveconf -n" and " master.cf" https://pastebin.com/M3XG9DXA Thanks in advance. ---------...

...submission_relay_trusted = yes >>> >>> My main issue is that until I login, dovecot-submission won't >>> connect to the backend and query the capabilities and so won't >>> report the right?capabilities. >>> >>> That mean that the first EHLO message don't get the right >>> capabilities list. >>> >>> " >>> EHLO example.com <http://example.com> >>> >>> 250-smtp.example.com <http://250-smtp.example.com> >>> 250-8BITMIME >>> 250-AUTH PLAIN LOGIN &...

Hi List, I have a postfix server based on CentOS 5 in which I have been trying to add TLS encryption support for SMTP. From the localhost when I do an EHLO, following is the output [root at xxxxxxx ~]# nc localhost 25 220 xxxxxxx.xxxx.xxx.xx ESMTP Postfix EHLO localhost 250-xxxxxxx.xxxx.xxx.xx 250-PIPELINING 250-SIZE 41943040 250-VRFY 250-ETRN 250-STARTTLS 250-AUTH PLAIN LOGIN 250-AUTH=PLAIN LOGIN 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN However...

...sieve file and shows the actual values that are used for the tests. However, it pointed out my problem quite clearly. > Thank you for this. Actually, after many hours of head-bashing, I discovered the problem. sieve doesn't work when you're just using telnet port 25 ! I was doing : ehlo test mail from:sender at example.com rcpt to:recip at example.com data Subject: hello world Hello World ! . With the above, sieve was simply sending everything to INBOX When I changed my methodology : ehlo test mail from:sender at example.com rcpt to:recip at example.com data From:<sender at e...

...= /var/log/dovecot.log > submission_relay_trusted = yes > verbose_ssl = yes > > > Logging: > Dec 18 16:36:39 submission-login: Debug: smtp-server: conn [0]: > Connection created > Dec 18 16:36:39 submission-login: Debug: smtp-server: conn [0]: Received > new command: EHLO [10.225.11.41] > Dec 18 16:36:39 submission-login: Debug: smtp-server: conn [0]: command > EHLO; 250 reply: Submitted > Dec 18 16:36:39 submission-login: Debug: smtp-server: conn [0]: command > EHLO: Ready to reply > Dec 18 16:36:39 submission-login: Debug: smtp-server: conn [0...

...ple.org[192.168.1.1], sasl_method=PLAIN, sasl_username=test at example.org postfix/submission/smtpd[19509]: *warning: non-SMTP command from example.org <http://example.org>[192.168.1.1]: Content-Transfer-Encoding: 7bit* postfix/submission/smtpd[19509]: disconnect from example.org[192.168.1.1] ehlo=1 auth=1 mail=1 rcpt=1 unknown=0/2 commands=4/6 postfix/submission/smtpd[19509]: connect from example.org[192.168.1.1] postfix/submission/smtpd[19509]: client=example.org[192.168.1.1], sasl_method=PLAIN, sasl_username=test at example.org postfix/submission/smtpd[19509]: *warning: non-SMTP command f...

Am 26.01.2015 um 15:22 schrieb Leander Sch?fer: > I couldn't find working solutions for this anomalie on the net. What > does this mean and does someone know how to fix this? > > postfix/smtpd[18757]: improper command pipelining after EHLO from > unknown[192.168.10.233]: QUIT\r\n that's hardly a dovecot topic and without "postconf -n", in doubt with content of "master.cf" and more informations nobody can help you at all -------------- next part -------------- A non-text attachment was scrubbed... Name: s...

...t a submission server with questions in regards to how Dovecot handles the backend hosts capabilities. To my understanding, Dovecot will connect to the host specified in either submission_host or submission_relay_host, and gather a list of capabilities. Once gathered, after the client sends the EHLO greeting Dovecot will respond back with capabilities that the backend host is capable of. My question is, When does this occur? Running a tcpdump with the filter set to the relay host IP, I don't see any traffic until after I send the EHLO command. Dovecot states that CHUNKING is available...

...t = XX.XX.XX.XX submission_relay_rawlog_dir = /var/log/dovecot.log submission_relay_trusted = yes verbose_ssl = yes Logging: Dec 18 16:36:39 submission-login: Debug: smtp-server: conn [0]: Connection created Dec 18 16:36:39 submission-login: Debug: smtp-server: conn [0]: Received new command: EHLO [10.225.11.41] Dec 18 16:36:39 submission-login: Debug: smtp-server: conn [0]: command EHLO; 250 reply: Submitted Dec 18 16:36:39 submission-login: Debug: smtp-server: conn [0]: command EHLO: Ready to reply Dec 18 16:36:39 submission-login: Debug: smtp-server: conn [0]: Trigger output Dec 18...

...I was setting up mail client on PC of my customer and standardily checked boxes, that I want to use SSL for POP3 and SMTP. Next I wanted to check configuration (by sending email from this mailbox to this mailbox) but it does not work. So I have opened telnet, connected via port 25 and writed "ehlo hostname" and then finded out, that there is missing STARTTLS. Is possible, that some bad configuration on client side (firewall, etc...) can cause this error including that this function is missing in printout of ehlo? POP3S working good. >From Sendmail log (/var/log/maillog): Nov 28 19:...