Build a lab first, lots of things to consider:
- copy a mailbox from your existing production system and test it against a client to insure it doesn't screw up peoples folder views.
- Performance. Test various things, like indexing, download speed and connection performance.
These are the two I will be raked over the coals with if I screw it up.
Users are such testy creatures. :-)
On Mon, May 4, 2026 at 11:53 AM John Stoffel <john@stoffel.org> wrote:
"Aki" == Aki Tuomi <aki.tuomi@open-xchange.com> writes:
On 04/05/2026 19:53 EEST John Stoffel via dovecot <dovecot@dovecot.org> wrote:
When I try this in my currently working 2.3 config, I see the following warnings:
Warnings during conversion:
- <memory>:45: no converter for 'plugin/@1/antispam_backend'
- <memory>:46: no converter for 'plugin/@1/antispam_debug_target'
- <memory>:47: no converter for 'plugin/@1/antispam_pipe_program'
- <memory>:48: no converter for 'plugin/@1/antispam_pipe_program_args'
- <memory>:49: no converter for
'plugin/@1/antispam_pipe_program_notspam_arg'
- <memory>:50: no converter for
'plugin/@1/antispam_pipe_program_spam_arg'
- <memory>:51: no converter for 'plugin/@1/antispam_pipe_tmpdir'
- <memory>:52: no converter for 'plugin/@1/antispam_signature'
- <memory>:53: no converter for 'plugin/@1/antispam_signature_missing'
- <memory>:54: no converter for 'plugin/@1/antispam_spam'
- <memory>:55: no converter for 'plugin/@1/antispam_trash'
- <memory>:62: no converter for 'plugin/@1/sieve_spamtest_max_header'
- <memory>:63: no converter for
'plugin/@1/sieve_spamtest_status_header'
- <memory>:64: no converter for 'plugin/@1/sieve_spamtest_status_type'
And my configuration is this. My question is how do I replace this feature moving forward to scan incomming emails with spamassassin (handled in postfix) but then filed into dovecot so they get put into the correct folders?
plugin { antispam_backend = pipe antispam_debug_target = syslog antispam_pipe_program = /usr/bin/spamc antispam_pipe_program_args = --username;debian-spamd antispam_pipe_program_notspam_arg = --learntype=ham antispam_pipe_program_spam_arg = --learntype=spam antispam_pipe_tmpdir = /var/tmp antispam_signature = X-Spam-Flag antispam_signature_missing = move antispam_spam = Junk antispam_trash = Trash sieve = ~/.dovecot.sieve sieve_after = /etc/dovecot/sieve-after sieve_before = /var/lib/dovecot/sieve/before.d sieve_dir = ~/sieve sieve_extensions = +spamtest +spamtestplus sieve_global_dir = sieve_spamtest_max_header = X-Spamd-Result: default: [[:alnum:]]+ \[-?[[:digit:]]+\.[[:digit:]]+ / (-?[[:digit:]]+\.[[:digit:]]+)\] sieve_spamtest_status_header = X-Spamd-Result: default: [[:alnum:]]+ \[(-?[[:digit:]]+\.[[:digit:]]+) / -?[[:digit:]]+\.[[:digit:]]+\] sieve_spamtest_status_type = score }
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
https://doc.dovecot.org/2.4.3/core/config/sieve/extensions/spamtest_virustes...
We haven't yet written every possible converter to the tool.
Ok. It would be nice if the tool instead just said "No converter, please read docs for upgrading instructions.
But overall, do you think if these are the only warnings, I should be ok to migrate?
Thanks, John
Build a lab first, lots of things to consider:
- copy a mailbox from your existing production system and test it against a client to insure it doesn't screw up peoples folder views.
- Performance. Test various things, like indexing, download speed and connection performance. These are the two I will be raked over the coals with if I screw it up. Users are such testy creatures. :-) On Mon, May 4, 2026 at 11:53AM John Stoffel <[1]john@stoffel.org> wrote:
>>>>> "Aki" == Aki Tuomi <[2]aki.tuomi@open-xchange.com> writes:
>> On 04/05/2026 19:53 EEST John Stoffel via dovecot
<[3]dovecot@dovecot.org> wrote:
>>
>>
>> When I try this in my currently working 2.3 config, I see the
>> following warnings:
>>
>> # Warnings during conversion:
>> # - <memory>:45: no converter for 'plugin/@1/antispam_backend'
>> # - <memory>:46: no converter for 'plugin/@1/antispam_debug_target'
>> # - <memory>:47: no converter for 'plugin/@1/antispam_pipe_program'
>> # - <memory>:48: no converter for
'plugin/@1/antispam_pipe_program_args'
>> # - <memory>:49: no converter for
'plugin/@1/antispam_pipe_program_notspam_arg'
>> # - <memory>:50: no converter for
'plugin/@1/antispam_pipe_program_spam_arg'
>> # - <memory>:51: no converter for 'plugin/@1/antispam_pipe_tmpdir'
>> # - <memory>:52: no converter for 'plugin/@1/antispam_signature'
>> # - <memory>:53: no converter for
'plugin/@1/antispam_signature_missing'
>> # - <memory>:54: no converter for 'plugin/@1/antispam_spam'
>> # - <memory>:55: no converter for 'plugin/@1/antispam_trash'
>> # - <memory>:62: no converter for
'plugin/@1/sieve_spamtest_max_header'
>> # - <memory>:63: no converter for
'plugin/@1/sieve_spamtest_status_header'
>> # - <memory>:64: no converter for
'plugin/@1/sieve_spamtest_status_type'
>>
>>
>> And my configuration is this. My question is how do I replace this
>> feature moving forward to scan incomming emails with spamassassin
>> (handled in postfix) but then filed into dovecot so they get put into
>> the correct folders?
>>
>>
>> plugin {
>> antispam_backend = pipe
>> antispam_debug_target = syslog
>> antispam_pipe_program = /usr/bin/spamc
>> antispam_pipe_program_args = --username;debian-spamd
>> antispam_pipe_program_notspam_arg = --learntype=ham
>> antispam_pipe_program_spam_arg = --learntype=spam
>> antispam_pipe_tmpdir = /var/tmp
>> antispam_signature = X-Spam-Flag
>> antispam_signature_missing = move
>> antispam_spam = Junk
>> antispam_trash = Trash
>> sieve = ~/.dovecot.sieve
>> sieve_after = /etc/dovecot/sieve-after
>> sieve_before = /var/lib/dovecot/sieve/before.d
>> sieve_dir = ~/sieve
>> sieve_extensions = +spamtest +spamtestplus
>> sieve_global_dir =
>> sieve_spamtest_max_header = X-Spamd-Result: default: [[:alnum:]]+
\[-?[[:digit:]]+\.[[:digit:]]+ / (-?[[:digit:]]+\.[[:digit:]]+)\]
>> sieve_spamtest_status_header = X-Spamd-Result: default: [[:alnum:]]+
\[(-?[[:digit:]]+\.[[:digit:]]+) / -?[[:digit:]]+\.[[:digit:]]+\]
>> sieve_spamtest_status_type = score
>> }
>> _______________________________________________
>> dovecot mailing list -- [4]dovecot@dovecot.org
>> To unsubscribe send an email to [5]dovecot-leave@dovecot.org
>
[6]https://doc.dovecot.org/2.4.3/core/config/sieve/extensions/spamtest_virustest.html#sieve_spamtest_score_max_header
> We haven't yet written every possible converter to the tool.
Ok. It would be nice if the tool instead just said "No converter,
please read docs for upgrading instructions.
But overall, do you think if these are the only warnings, I should be
ok to migrate?
Thanks,
JohnReferences
Visible links
- mailto:john@stoffel.org
- mailto:aki.tuomi@open-xchange.com
- mailto:dovecot@dovecot.org
- mailto:dovecot@dovecot.org
- mailto:dovecot-leave@dovecot.org
- https://doc.dovecot.org/2.4.3/core/config/sieve/extensions/spamtest_virustes...