I have given this some thought and conclude that most of Postfix
isn't architected to report a hard error for an 'impossible' database
request. It assumes that database errors can be fixed by human
intervention (for example, fixing a 'device full' problem, fixing
database corruption, fixing a database schema, etc.).
Perhaps a more practical solution is for the memcache client to
replace an over-size key with its SHA256 value (formatted as 64
hexadecimal characters), and to accept the vanishingly small
possibility of a false match (to eliminate that possibility one
would have to go overboard and prepend the full key to the stored
data).
Wietse
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
