> The address verify feature DOES NOT create its own connection cache.
>
> If you disagree, show actual evidence from the Postfix logfile,
> and explain what part of this evidence means that Postfix
> verification creates its own connection cache.
>
> Wietse
Sorry, it's all about my bad english. I don't mean "it's create own
cache". I mean, "I think verify create new connections against using
scache."
It's looks this way due:
There is no mails in queue, which fail to delivered. Messages to already
known/verified addreses delivered normal to backend servers.
But verify often fails with error "Recipient address rejected: unverified
address: lost connection with mail.xxx[x.x.x.x] while receiving the
initial server greeting."
[r...@mx1 /]# mailq
Mail queue is empty
[r...@mx1 /]# grep accepted /var/log/maillog | wc -l
146
[r...@mx1 /]# grep 'unverified address' /var/log/maillog | wc -l
34
On netstat I see ESTABLISHED connections(1-3) from frontend postfix to
backend CGP.
