Skip to content
Snippets Groups Projects
Select Git revision
  • main default
1 result
You can move around the graph by using the arrow keys.
Created with Raphaël 2.2.026Jul251917927Jun1831May3028171615963130Apr261118Mar13Feb16Jan12Dec117429Nov26Sep20630Aug29151095118Jul228Jun1312128May27261294228Apr27252416131229Mar13107653215Feb13110Jan4125Dec23181615131211326Nov252318732130Oct292321654330Sep2213730Aug282218178Jul628Jun222016141228Apr242112522Mar16926Feb2221191412830Jan141311130Dec2613Nov873229Oct2120191715131110765429Sep212028Aug262423201914131110215Jul147628Jun272321201310931May30181615964228Apr2619181410976528Mar27252321191898229Feb272214131227Jan2619lib-sieve: plugins: enotify: mailto: Use event API to handle the "mailto URI" log prefix.lib-sieve: plugins: enotify: Use event API to handle the notify command/action log prefix.lib-sieve: plugins: enotify: mailto: uri-mailto - Restructure error handling.lib-sieve: sieve-result - Handle action log prefix at a central location using the event.lib-sieve: sieve-error - Compose both the event and the error handler log message once using the event API.lib-sieve: sieve-error - Change error handler log function to accept direct message string.plugins: lda-sieve: Drop custom action error handler.sieve-tools: sieve-test - Use the new result message amendment callback rather than the prefix error handler.sieve-tools: sieve-filter - Use the new result message amendment callback rather than the prefix error handler.plugins: lda-sieve: Use the new result message amendment callback rather than a special error handler.lib-sieve: sieve-result - Add support for amending result log messages.lib-sieve: sieve-result - Allow specifying an explicit name for actions added to the result.lib-sieve: sieve-result - Add sieve_result_event_log*().lib-sieve: sieve-error - Add sieve_event_log().lib-sieve: sieve-error - Make enum sieve_error_flags public.lib-sieve: sieve-result - Define "sieve-action" event category.lib-sieve: sieve-interpreter - Define "sieve-runtime" event category.lib-sieve: sieve-execute - Define "sieve-execute" event category.lib-sieve: Define "sieve" event category.lib-sieve: sieve-result - Use action event for all action execution log messages.lib-sieve: sieve-result - Add event support for individual actions.lib-sieve: sieve-interpreter - Use runtime event for all runtime log messages.lib-sieve: sieve-error - Add support for logging through events other than the main instance event.lib-sieve: sieve-result - Add event support to action execute environment.lib-sieve: sieve-runtime - Add event support to runtime environment.lib-sieve: sieve-execute - Add event support to execute environment.lib-sieve: Add username field to main instance event.lib-sieve: sieve-actions - Remove action argument from action and side-effect definition functions.lib-sieve: sieve-actions - Add current action to action execution environment.lib-sieve: Handle init/deinit of execute context in separate functions.lib-sieve: sieve-action - Add sieve_action_name() macro.lib-sieve: sieve-interpreter - Turn bools in struct sieve_interpreter into bit fields.lib-sieve: sieve-result - Make direct result pointer avalable as local variable in sieve_result_unref().lib-sieve: sieve-erorr - Add sieve_internal_error_params() and use it.lib-sieve: sieve-error - Compose message prefixes in a single place for all error handler variants.lib-sieve: sieve-error - Remove varexpand error handler.testsuite: testsuite-log - Change error message structure to match rest of Pigeonhole.testsuite: testsuite-log - Uninstall testsuite error handler upon deinit.doveadm-sieve: Shared attribute iteration shouldn't list Sieve scriptslib-sieve: plugins: vnd.dovecot: report: cmd-report - Fix resource leak occurring when the SMTP submission fails.
Loading

Consent

On this website, we use the web analytics service Matomo to analyze and review the use of our website. Through the collected statistics, we can improve our offerings and make them more appealing for you. Here, you can decide whether to allow us to process your data and set corresponding cookies for these purposes, in addition to technically necessary cookies. Further information on data protection—especially regarding "cookies" and "Matomo"—can be found in our privacy policy. You can withdraw your consent at any time.