soft-bounce determines how Archiveopteryx responds when a message cannot be delivered to Archiveopteryx, and the problem seems to be permanent.
If soft-bounce is enabled, Archiveopteryx assumes that the problem is a configuration issue, and sends a temporary error. The sender will retry in a little while, and perhaps the configuration has been fixed then. In practice, the sender is your local MTA, perhaps Postfix or Exim, and the undeliverable messages stay in your mail queue for you to discover.
If soft-bounce is disabled, Archiveopteryx assumes that the problem really is permanent, and sends a permanent error. The message's sender will receive a bounce.
The configuration file generated at installation time includes soft-bounce=enabled. We recommend disabling it only when you trust the configuration, user list, et cetera.
soft-bounce is a toggle. Its default value is true:
soft-bounce = false
You can see its current value with the command aox show cf soft-bounce.
Toggles are written as a single word. Yes, true, on, 1, and enabled all mean that the toggle is enabled, while no, false, off, 0, and disabled unsurprisingly mean disabled. Toggles are case-insensitive.
Spaces are allowed at the start of the line, before and after '=', and after the value. Comments extend from '#' to the end of the line.
In case of questions, please write to firstname.lastname@example.org.
Last modified: 2010-11-19