This allows side-effects to open a different mailbox than what is allocated
initially in act_store_start().

lib-sieve: store action: Allow side-effects to change the mailbox identifier used in action logging.

lib-sieve: plugins: mailbox: tag-mailbox-create - Add variable for trans->box in seff_mailbox_create_pre_execute().

Use mailbox_get_last_error() shorthand rather than
mail_storage_get_last_error().

This way, the mailbox does not need to be opened until result execution.

By setting the MAILBOX_FLAG_POST_SESSION flag, this  makes sure the result of
this test closely matches what would happen for a real delivery action using
"fileinto".

This way, the execution order can be made explicit.

plugins: imap-filter-sieve: Fix mixup between tag and problem part of the FILTER response for compile error.

plugins: imap-filter-sieve: Perform main initialization of Sieve script execution environment only once.

This way, any configuration errors can be reported as a single FILTER ERRORS
response, rather than a FILTERED ERRORS response for each filtered message.

plugins: imap-filter-sieve: Make sure user gets to see at least one error when script execution fails.

The previous commit should already prevent this, but this makes sure it
can't become broken in the future either. It makes the performance a tiny
bit worse, but that's not practically noticeable.

ManageSieve doesn't allow NULs in strings.

This fixes a bug with unescaping a string with NULs: str_unescape() could
have been called for memory that points outside the allocated string,
causing heap corruption. This could cause crashes or theoretically even
result in remote code execution exploit.

Found by Nick Roessler and Rafi Rubin

Before, it only compared the handles, which would cause duplicate tests with
different values to be cached as the same duplicate test.

Also explicitly initialize login_binary->anonymous_login_acceptable to FALSE to
make clear that anonymous logins are intentionally not allowed for ManageSieve.

Addresses a Coverity report.

The action name can be determined from the sieve_action_name field that existed
before.

It is no longer used.

Avoid using a Sieve error handler directly.