* Wietse Venema via Postfix-users:

>> I prefer Postfix returning an error when asked to perform an operation
>> which is not possible, nonsensical or otherwise indicates that there are
>> misconfigurations or misunderstandings about Postfix's inner workings
>> involved. [...]
>
> I think that there are different degrees of 'impossible', and that
> they can correspond to different levels of severity.

That's why I included "nonsensical" above. Postfix currently treats the
attempt to create an index for a table type which does not use/need an
index as an error, which I like. It signals that the requested operation
cannot be executed, and does so in a way which can be detected
programmatically by means of the exit code. That, to me, is preferrable
to a mere human-readable warning message, which can be ignored or
overlooked by accident.

In a broad sense, Postfix's current behaviour permits me to both learn
from a mistake, and to also detect that mistake in scripts etc. I would
not like to see this go away.

Of course there are different levels of mistakes, and running postmap on
a texthash table is not harmful. However, in the realm of traditional
interpretation of zero/nonzero exit codes, I think this invocation of
postmap needs to land on the nonzero side.

-Ralph
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to