Ralf Hildebrandt:
> * Wietse Venema <[email protected]>:
>
> > > What's odd here, is that the host always makes two parallel TLS
> > > connections (you must have some "late" tests enabled to get all
> > > the way to STARTTLS), with the first connection logging tempfailed
> > > recipients and logging "PASS NEW", and soon after the second seems
> > > to just disconnect without logging either. Don't know what if
> > > anything that second connection does to the cached state.
> >
> > First the client passes all tests in the session from
> > [106.10.151.33]:58305, and postscreen caches that result.
> >
> > However, the other session ends without passing deep protocol
> > tests, and when that session ends, postscreen caches only the tests
> > that were passed in that session, i.e. no deep protocol tests.
> >
> > I'll see if it is possible to handle this without keeping too much
> > state in postscreen for too much time.
>
> Thanks
Short answer: disable the after-220 tests:
postscreen_bare_newline_enable = no
postscreen_non_smtp_command_enable = no
postscreen_pipelining_enable = no
Long answer: fixing this requires changing the book-keeping of
passed tests, from per-session state into shared per-client state.
With my current availability, that is likely to take longer than
most clients are willing to retry. Hence the "short answer" suggestion.
Wietse