Deutsch English Français Italiano |
<9c036674340a558c742c864a95764304@www.novabbs.com> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!weretis.net!feeder9.news.weretis.net!i2pn.org!i2pn2.org!.POSTED!not-for-mail From: hquest@hquest.pro.br (HQuest) Newsgroups: comp.mail.sendmail Subject: Re: [client] did not issue MAIL/EXPN/VRFY/ETRN during connection Date: Fri, 26 Apr 2024 21:19:20 +0000 Organization: novaBBS Message-ID: <9c036674340a558c742c864a95764304@www.novabbs.com> References: <5c620d24d884ece84a12b62e2a4cbf45@www.novabbs.com> <v0h2fl$c0c$1@news.misty.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Info: i2pn2.org; logging-data="2463463"; mail-complaints-to="usenet@i2pn2.org"; posting-account="2XJ8hjIEUuziWBqN+XBS7yv7yfwqQ5GdIjLva+fAx2c"; User-Agent: Rocksolid Light X-Rslight-Site: $2y$10$M0z3TCB8rQSnsxj3Vwo3M.OHaorp7eP0NU9qCm8t4I8q8DfIRb/cS X-Spam-Checker-Version: SpamAssassin 4.0.0 X-Rslight-Posting-User: 3d3517e5dd24387fdf8da64199401ea731577ab2 Bytes: 2309 Lines: 20 Claus Aßmann wrote: > Do you get any mail from them or does this always happen? From Proofpoint I used to get, but they began consistently failing in the past 2-3 weeks. From Cisco, it is a hit or miss. From a few other providers, we only recently started doing business with them, so never found in my log archives (went back to about 2y of past logs to confirm). >> define(`confTO_COMMAND', `1m')dnl > Why did you choose this? I believe this was recommendation from a 3rd party. >> Kcheck_client dns -R a -T T -q > Where/how is this used? It came as part of DNSBL setup, but judging by your reaction, seems not required, and I'm more than happy to clear it out. Less is more (except timeout, it seems). >> Apr 26 13:16:01 mxhost sm-mta[126129]: NOQUEUE: connect from >> mx0a-0017d901.pphosted.com [208.84.65.218] >> Apr 26 13:17:01 mxhost sm-mta[126129]: 43QHG1xY126129: timeout waiting >> for input from mx0a-0017d901.pphosted.com during server cmd read > Maybe 1m is too short, esp. if DNS lookups take a while. > The default is much longer - see the docs. It is interesting that these timeout changes occurred over a year ago. I can see a DNS query and response for these incoming systems happening in under 2 seconds. Will change those back to their default and see how it behaves. More to come.