----- Original Message ----- > From: "Wietse Venema" <wie...@porcupine.org> > To: "Nguyen Nang Thang" <than...@iwayvietnam.com> > Cc: "Postfix users" <postfix-users@postfix.org> > Sent: Saturday, January 23, 2016 9:09:09 AM > Subject: Re: Postfix Postscreen Pregreet Test
> Nguyen Nang Thang: >> >> > domain zen.spamhaus.org as 127.0.0.4 >> >> > Jan 22 00:00:53 spike postfix/postscreen[44350]: PREGREET 16 after 0.69 >> >> > from >> >> > [177.231.207.212]:38026: HELO bryozoann\r\n >> > >> > That is a zombie that speaks before its turn. >> >> Ok, I'm clear about the operation of the parameter "postscreen_greet_wait". >> Log in our email system shows as below: >> Jan 22 00:57:59 gw postfix/postscreen[4837]: CONNECT from >> [201.139.132.41]:37245 >> to [192.168.100.79]:25 >> Jan 22 00:57:59 gw postfix/postscreen[4837]: PREGREET 50 after 0.52 from >> [201.139.132.41]:37245: HELO 201.139.132.41.cable.dyn.cableonline.com.mx\r\n >> => The IP 201.139.132.41 is monitored by Pregreeting test. >> >> But my current concern is that how to manually test the parameter >> "postscreen_greet_wait" by my own test? > > Postfix sends: > > 220-myhostname ESMTP > > Postfix waits $postscreen_greet_wait seconds. > Bad SMTP clients will greet before $postscreen_greet_wait seconds > have passed. > > 220 myhostname ESMTP > > Good SMTP clients will greet now. Wietse: Thanks for your detailed explain. Can you suggest me technical ways to manually test Bad SMTP clients that greet before $postscreen_greet_wait seconds have passed? It's true that we cannot use the "telnet" command to test because I'm thinking scripts/tools are suitable ways to test Bad SMTP client, right? Regards, Thang
