On 11/14/24 15:13, Matt Saladna via Postfix-users wrote:
In situations where either a server has run out of storage, a btree
database can become corrupted. I see this evidenced in the following
manner, specifically "no cursor":
Removing the .db cache in /var/lib/postfix followed by a restart
On Thu, Nov 14, 2024 at 02:13:11PM -0600, Matt Saladna via Postfix-users wrote:
> In situations where either a server has run out of storage, a btree database
> can become corrupted. I see this evidenced in the following manner,
> specifically "no cursor":
>
> Nov 14 20:10:44 web2 postfix/postscr
Matt Saladna via Postfix-users:
> Nov 14 20:10:45 web2 postfix/proxymap[1378875]: panic: dict_db_sequence: no
> cursor
> Nov 14 20:10:46 web2 postfix/postscreen[1377623]: warning: dict_proxy_lookup:
> service proxywrite: Connection reset by peer
I do not recommend using postscreen with a proxied
