- Jun 20, 2017
-
-
Stephan Bosch authored
-
Stephan Bosch authored
For accounts that perform many redirects, the lda-dupes database could grow to impractical sizes. Changed the default retention period from 24 to 12 hours.
-
Stephan Bosch authored
-
- Jun 16, 2017
-
-
Timo Sirainen authored
-
- Jun 14, 2017
-
-
Timo Sirainen authored
-
Timo Sirainen authored
-
- Jun 12, 2017
-
-
Timo Sirainen authored
-
- Apr 27, 2017
-
-
Stephan Bosch authored
Upon continuing the deferred implicit keep, the implicit side-effects (such as imap flags) were not applied.
-
- Apr 24, 2017
-
-
Timo Sirainen authored
-
- Apr 21, 2017
-
-
Timo Sirainen authored
-
- Apr 12, 2017
-
-
Stephan Bosch authored
Implicit keep was deferred for the source message, which discards all flags.
-
- Apr 05, 2017
-
-
Timo Sirainen authored
-
- Mar 22, 2017
-
-
Stephan Bosch authored
When this is enabled for a mailbox rule, the specified Sieve script is executed for the message in the source mailbox during a "COPY" event. This happens only after the Sieve script that is executed for the corresponding message in the destination mailbox finishes running successfully.
-
Stephan Bosch authored
This already has the imapsieve transaction context associated with it before the sieve scripts are executed. This currently cannot occur, but it will become relevant in subsequent commits.
-
Stephan Bosch authored
-
- Mar 21, 2017
-
-
Stephan Bosch authored
imapsieve plugin: Don't open the user's personal script storage if no personal script is configured.
-
Stephan Bosch authored
-
- Mar 16, 2017
-
-
Stephan Bosch authored
lib-sieve: multiscript: The execution of the discard script had an implicit "keep", rather than an implicit "discard".
-
- Mar 09, 2017
-
-
Timo Sirainen authored
-
Timo Sirainen authored
-
- Feb 26, 2017
-
-
Stephan Bosch authored
lib-sieve: store action: Made static analyzer happier about tr_context argument for sieve_act_store_add_flags(). Added an assert ensuring it is not NULL.
-
Stephan Bosch authored
This used strftime() directly and allocated memory from the heap before i_fatal(). It also used printf() to send the BYE message, which will only work right when the service is running stand-alone.
-
- Feb 22, 2017
-
-
Timo Sirainen authored
-
- Feb 20, 2017
-
-
Stephan Bosch authored
-
Stephan Bosch authored
This adds a new callback to the Sieve script execution environment.
-
- Feb 18, 2017
-
-
Timo Sirainen authored
-
- Feb 14, 2017
-
-
Timo Sirainen authored
-
Timo Sirainen authored
It can never be NULL after the "lib-storage: Always create mail_save_context.dest_mail" core change.
-
- Feb 12, 2017
-
-
Stephan Bosch authored
lib-sieve: file storage: Amended the up-to-date timestamp comparison for on-disk binaries to include nanoseconds. This will fix problems occurring when both binary and script are saved within the same second. On older systems that have no support for nanoseconds in the stat() time stamps, this has no effect.
-
Stephan Bosch authored
-
Stephan Bosch authored
Otherwise, the mailbox name would never match, since matching is performed case-sensitively and Dovecot only returns the upper-cased "INBOX". This change prevents confusing administrators that for some reason choose to use a different capitalization of that mailbox name.
-
Stephan Bosch authored
Use eacces_error_get(), rather than just printing "Permission denied".
-
- Feb 08, 2017
-
-
Stephan Bosch authored
Use eacces_error_get(), rather than just printing "Permission denied".
-
- Jan 30, 2017
-
-
Martti Rannanjärvi authored
path-util is a merge of realpath from Pigeonhole and abspath from core.
-
- Jan 14, 2017
-
-
Stephan Bosch authored
This is not currently used anywhere, so nothing actually broke. This bug was exposed by the previous commit, causing a compiler error/warning on some compilers.
-
- Jan 13, 2017
-
-
Stephan Bosch authored
Applies to LDA/LMTP context in general, not only when sieve_before/sieve_after are used. Action side-effects and the message snapshot would be lost at the final stage where the implicit keep is evaluated. This happened because the keep action itself is not actually executed, but rather its presence is noted to determine whether more scripts need to be executed. So, when finally execution of the actual keep action is due, i.e. when there are no more scripts in the sequence, it overrides the explicit keep from the last script. This didn't take the side-effects and message snapshot into account.
-
- Jan 11, 2017
-
-
Stephan Bosch authored
-
Stephan Bosch authored
The situation where no headers are found was not always handled correctly.
-
Stephan Bosch authored
-
- Jan 01, 2017
-
-
Stephan Bosch authored
-