From: Colin W. <co...@la...> - 2013-11-05 12:36:07
|
Hi Andras, I have looked back through my emails and confirmed that I saw the exact same behaviour which I reported on the list on 30/09/2013. I'm not sure what sparked the issue off, whether it was an ASSP update, a perl or perl module update or an OS update. Either way, disabling OCR resolved the issue for me. I thought Thomas released an updated module that address the issue but I haven't turned it back on as all the requirements for OCR are a pain to install on Ubuntu. I can't risk turning it back on to see if the problem is still there at the moment, we've had a few too many issues lately (not specifically ASSP, other issues like datacentre outages etc). All the best, Colin Waring. -----Original Message----- From: Virag Andras [mailto:sno...@sn...] Sent: 05 November 2013 11:55 To: ASSP development mailing list Subject: Re: [Assp-test] assp/postfix 5.2.2 command not recognized Hi, I can't say I understand the last passage, but the rest makes sense. Still, why would the clients from several hosts would start sending unrecognized commands for 3 weeks now (after the assp upgrade), when they never did it in the past, I'm still perplexed. What I did after Colins suggestion, I did a check on the file versions and it was consistent, but a couple of perl modules were outdated. I updated them, installed the latest assp, disabled OCR (somehow in most of the "faulty" mails I could check, had image parts). So far so good, I don't see the error. Wish me luck. Thanks guys Andras On Tue, 5 Nov 2013 07:11:28 +0100, Thomas Eckardt <Tho...@th...> wrote: >>Nov 4 10:45:47 mail.server/smtpd[18910]: match_string: >> gIl2eY22EOu8Yx6 > ~? CONNECT >>Nov 4 10:45:47 mail.server/smtpd[18910]: match_string: >> gIl2eY22EOu8Yx6 > ~? GET >>Nov 4 10:45:47 mail.server/smtpd[18910]: match_string: >> gIl2eY22EOu8Yx6 > ~? POST > > This is HTTP stuff. ASSP never does this in SMTP workers - so the > commands > are submitted from the client or server. > Because assp is a proxy, these commands are processed transparent. > > The mail is delivered because assp saw >>Nov 4 10:45:47 mail.server/smtpd[18910]: > > localhost.localdomain[127.0.0.1]: 250 2.0.0 Ok: queued as 1C08E5303D9 > after that a QUIT, RSET, NOOP, or MAIL FROM is expected. How ever, > postfix > answers with 502, which is right - assp counts the protocol mistakes > and > drops the connection with > Date 84504-01966 [Worker_2] [MaxErrors] > > There is nothing you can do - except if the connected host is one of > your > locals. > > One possible cause for this behavior would be, if assp/Perl/system > scrambles connection (socket) data between the threads. In this case, > there must be a HTTP request at exact the same time via the GUI. > > Thomas > > > > > Von: "Andras Virag" <sno...@sn...> > An: "'ASSP development mailing list'" > <ass...@li...>, > Datum: 04.11.2013 21:13 > Betreff: Re: [Assp-test] assp/postfix 5.2.2 command not > recognized > > > > No, I really loved it. :) Especially that I was/am a support engineer > myself, and Thomas was so right! I really was dumb. > > So: > This is perl 5, version 14, subversion 1 (v5.14.1) built for > x86_64-linux-thread-multi > and ASSP version 2.3.4(13303) > Yes, the kernel is old, but it's not that easy to upgrade now.... > > > Aaaaand, the error message from assp: > Date 84504-01966 [Worker_2] IP <from@email> to: to@email [SMTP Error] > 502 > 5.5.2 Error: command not recognized > Date 84504-01966 [Worker_2] [MaxErrors] 91.239.66.136 > <ad...@vz...> to: to@email max errors (MaxErrors=5) > exceeded > -- dropping connection - after reply: 502 5.5.2 Error: command not > recognized from 127.0.0.1 > > Postfix: > Nov 4 10:45:46 mail.server/smtpd [18910]: input attribute name: > (end) > Nov 4 10:45:46 mail.server/smtpd [18910]: send attr flags = 178 > Nov 4 10:45:46 mail.server/smtpd [18910]: 1C08E5303D9: > client=localhost.localdomain[127.0.0.1] > Nov 4 10:45:46 mail.server/smtpd [18910]: > > localhost.localdomain[127.0.0.1]: 250 2.1.5 Ok > Nov 4 10:45:46 mail.server/smtpd [18910]: watchdog_pat: > 0x7f7a3f5abcd0 > Nov 4 10:45:46 mail.server/smtpd [18910]: < > localhost.localdomain[127.0.0.1]: DATA > Nov 4 10:45:46 mail.server/smtpd [18910]: match_string: DATA ~? NOOP > Nov 4 10:45:46 mail.server/smtpd [18910]: match_list_match: DATA: no > match > Nov 4 10:45:46 mail.server/smtpd [18910]: > > localhost.localdomain[127.0.0.1]: 354 End data with <CR><LF>.<CR><LF> > Nov 4 10:45:47 mail.server/smtpd [18910]: public/cleanup socket: > wanted > attribute: status > Nov 4 10:45:47 mail.server/smtpd [18910]: input attribute name: > status > Nov 4 10:45:47 mail.server/smtpd [18910]: input attribute value: 0 > Nov 4 10:45:47 mail.server/smtpd [18910]: public/cleanup socket: > wanted > attribute: reason > Nov 4 10:45:47 mail.server/smtpd [18910]: input attribute name: > reason > Nov 4 10:45:47 mail.server/smtpd [18910]: input attribute value: > (end) > Nov 4 10:45:47 mail.server/smtpd [18910]: public/cleanup socket: > wanted > attribute: (list terminator) > Nov 4 10:45:47 mail.server/smtpd [18910]: input attribute name: > (end) > Nov 4 10:45:47 mail.server/smtpd[18910]: > > localhost.localdomain[127.0.0.1]: 250 2.0.0 Ok: queued as 1C08E5303D9 > Nov 4 10:45:47 mail.server/smtpd[18910]: watchdog_pat: > 0x7f7a3f5abcd0 > Nov 4 10:45:47 mail.server/smtpd[18910]: < > localhost.localdomain[127.0.0.1]: gIl2eY22EOu8Yx6 > Nov 4 10:45:47 mail.server/smtpd[18910]: match_string: > gIl2eY22EOu8Yx6 ~? > NOOP > Nov 4 10:45:47 mail.server/smtpd[18910]: match_list_match: > gIl2eY22EOu8Yx6: no match > Nov 4 10:45:47 mail.server/smtpd[18910]: match_string: > gIl2eY22EOu8Yx6 ~? > CONNECT > Nov 4 10:45:47 mail.server/smtpd[18910]: match_string: > gIl2eY22EOu8Yx6 ~? > GET > Nov 4 10:45:47 mail.server/smtpd[18910]: match_string: > gIl2eY22EOu8Yx6 ~? > POST > Nov 4 10:45:47 mail.server/smtpd[18910]: match_list_match: > gIl2eY22EOu8Yx6: no match > Nov 4 10:45:47 mail.server/smtpd[18910]: > > localhost.localdomain[127.0.0.1]: 502 5.5.2 Error: command not > recognized > Nov 4 10:45:47 mail.server/smtpd[18910]: watchdog_pat: > 0x7f7a3f5abcd0 > Nov 4 10:45:47 mail.server/smtpd[18910]: < > localhost.localdomain[127.0.0.1]: > > c0+1mItYt+4rghGUZG/PJ+ntTcbx+8G5Ia7edPEZrdbeN8guZOWz/IHH/wCunXCCOfEcgPlptKhe > Nov 4 10:45:47 mail.server/smtpd[18910]: match_string: > > c0+1mItYt+4rghGUZG/PJ+ntTcbx+8G5Ia7edPEZrdbeN8guZOWz/IHH/wCunXCCOfEcgPlptKhe > ~? NOOP > Nov 4 10:45:47 mail.server/smtpd[18910]: match_list_match: > > c0+1mItYt+4rghGUZG/PJ+ntTcbx+8G5Ia7edPEZrdbeN8guZOWz/IHH/wCunXCCOfEcgPlptKhe: > > no match > Nov 4 10:45:47 mail.server/smtpd[18910]: match_string: > > c0+1mItYt+4rghGUZG/PJ+ntTcbx+8G5Ia7edPEZrdbeN8guZOWz/IHH/wCunXCCOfEcgPlptKhe > ~? CONNECT > Nov 4 10:45:47 mail.server/smtpd[18910]: match_string: > > c0+1mItYt+4rghGUZG/PJ+ntTcbx+8G5Ia7edPEZrdbeN8guZOWz/IHH/wCunXCCOfEcgPlptKhe > ~? GET > Nov 4 10:45:47 mail.server/smtpd[18910]: match_string: > > c0+1mItYt+4rghGUZG/PJ+ntTcbx+8G5Ia7edPEZrdbeN8guZOWz/IHH/wCunXCCOfEcgPlptKhe > ~? POST > Nov 4 10:45:47 mail.server/smtpd[18910]: match_list_match: > > c0+1mItYt+4rghGUZG/PJ+ntTcbx+8G5Ia7edPEZrdbeN8guZOWz/IHH/wCunXCCOfEcgPlptKhe: > > no match > Nov 4 10:45:47 mail.server/smtpd[18910]: > > localhost.localdomain[127.0.0.1]: 502 5.5.2 Error: command not > recognized > Nov 4 10:45:47 mail.server/smtpd[18910]: watchdog_pat: > 0x7f7a3f5abcd0 > > Etc....etc.... > Andras > > > -----Eredeti üzenet----- > Feladó: Robert K Coffman Jr. -Info From Data Corp. > [mailto:bco...@in...] > Küldve: Monday, November 4, 2013 6:54 PM > Címzett: ASSP development mailing list > Tárgy: Re: [Assp-test] assp/postfix 5.2.2 command not recognized > >> I am so embarassed by my stupidity. I have no excuse. :) Yes it is > Linux, >> with the latest assp and I promise I will send all the relevant info > once >> I am home. >> > > András, > > Don't feel so bad. Thomas' post was good for a laugh, which we all > need! > > - Bob > > > ------------------------------------------------------------------------------ > Android is increasing in popularity, but the open development > platform > that > developers love is also attractive to malware creators. Download this > white > paper to learn more about secure code signing practices that can help > keep > > Android apps secure. > > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk > > _______________________________________________ > Assp-test mailing list > Ass...@li... > https://lists.sourceforge.net/lists/listinfo/assp-test > > > > ------------------------------------------------------------------------------ > Android is increasing in popularity, but the open development > platform > that > developers love is also attractive to malware creators. Download this > white > paper to learn more about secure code signing practices that can help > keep > Android apps secure. > > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk > > _______________________________________________ > Assp-test mailing list > Ass...@li... > https://lists.sourceforge.net/lists/listinfo/assp-test > > > > DISCLAIMER: > ******************************************************* > This email and any files transmitted with it may be confidential, > legally > privileged and protected in law and are intended solely for the use > of the > > individual to whom it is addressed. > This email was multiple times scanned for viruses. There should be no > known virus in this email! > ******************************************************* ------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk _______________________________________________ Assp-test mailing list Ass...@li... https://lists.sourceforge.net/lists/listinfo/assp-test |