Hello so I have started planning my 2.3 to 2.4 migration and finished the lab work today for that process. Does anyone know of any tools to migrate the configs from 2.3 to 2.4?
Also if you are running 2.4 I would like to hear from you as to how well it is working out.
Thanks.
Hello so I have started planning my 2.3 to 2.4 migration and finished the lab work today for that process. Does anyone know of any tools to migrate the configs from 2.3 to 2.4? Also if you are running 2.4 I would like to hear from you as to how well it is working out. Thanks.
On Sun, May 03, 2026 at 07:30:17PM -0700, Gregory Carter via dovecot wrote:
Hello so I have started planning my 2.3 to 2.4 migration and finished the lab work today for that process. Does anyone know of any tools to migrate the configs from 2.3 to 2.4? Also if you are running 2.4 I would like to hear from you as to how well it is working out. Thanks.
Try something like Google Gemini or CHATGPT.
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
-- Member - Liberal International This is doctor@nk.ca Ici doctor@nk.ca Yahweh, King & country!Never Satan President Republic!Beware AntiChrist rising! Look at Psalms 14 and 53 on Atheism ; All I want to hear from Jesus is WEll Done Good and Faithful Servant.
Hi,
This is my DokuWiki, made for me, but it's Public available, so feel free to take a look on it:
https://dokuwiki.tachtler.net/doku.php?id=tachtler:dovecot_archlinux#dovecot...
It's in German language and made for/with Archlinux, but you can find a way to translate the relevant parts.
Greetings Klaus.
--
e-Mail : klaus@tachtler.net Homepage: https://www.tachtler.net DokuWiki: https://dokuwiki.tachtler.net
On 04/05/2026 05:42 EEST The Doctor via dovecot <dovecot@dovecot.org> wrote:
On Sun, May 03, 2026 at 07:30:17PM -0700, Gregory Carter via dovecot wrote:
Hello so I have started planning my 2.3 to 2.4 migration and finished the lab work today for that process. Does anyone know of any tools to migrate the configs from 2.3 to 2.4? Also if you are running 2.4 I would like to hear from you as to how well it is working out. Thanks.
Try something like Google Gemini or CHATGPT.
We provide an actual tool for this, so I would recommend using it first.
Aki
On Mon, 4 May 2026 07:40:16 +0300 (EEST) Aki Tuomi via dovecot <dovecot@dovecot.org> wrote:
On 04/05/2026 05:42 EEST The Doctor via dovecot <dovecot@dovecot.org> wrote:
On Sun, May 03, 2026 at 07:30:17PM -0700, Gregory Carter via dovecot wrote:
Hello so I have started planning my 2.3 to 2.4 migration and finished the lab work today for that process. Does anyone know of any tools to migrate the configs from 2.3 to 2.4? Also if you are running 2.4 I would like to hear from you as to how well it is working out. Thanks.
Try something like Google Gemini or CHATGPT.
We provide an actual tool for this, so I would recommend using it first.
Halo Aki, thanks a lot for this tool! Just a small question (it's not specified on the converter page) - what should be inserted as "dovecot.conf" is the output from 'doveconf -n' - is that right?
Thanks, Franta Hanzlík
On 04/05/2026 13:33 EEST Franta Hanzlík via dovecot <dovecot@dovecot.org> wrote:
On Mon, 4 May 2026 07:40:16 +0300 (EEST) Aki Tuomi via dovecot <dovecot@dovecot.org> wrote:
On 04/05/2026 05:42 EEST The Doctor via dovecot <dovecot@dovecot.org> wrote:
On Sun, May 03, 2026 at 07:30:17PM -0700, Gregory Carter via dovecot wrote:
Hello so I have started planning my 2.3 to 2.4 migration and finished the lab work today for that process. Does anyone know of any tools to migrate the configs from 2.3 to 2.4? Also if you are running 2.4 I would like to hear from you as to how well it is working out. Thanks.
Try something like Google Gemini or CHATGPT.
We provide an actual tool for this, so I would recommend using it first.
Halo Aki, thanks a lot for this tool! Just a small question (it's not specified on the converter page) - what should be inserted as "dovecot.conf" is the output from 'doveconf -n' - is that right?
Thanks, Franta Hanzlík
Yes, that's right.
Aki
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 }
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.
Aki
"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: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...
"Gregory" == Gregory Carter <gjcarter2@gmail.com> writes:
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.
Done, playing with it now.
- Performance. Test various things, like indexing, download speed and connection performance.
Not as worried, it's a small personal system.
These are the two I will be raked over the coals with if I screw it up.
Users are such testy creatures. :-)
Since I'm the main user... I get to beat myself up.
So here's a question. The 2.3 to 2.4 converter suggests this small snippet of proposed configuration:
mail_driver = maildir
mail_path = /var/mail/%{user | domain}/%{user | username}/Maildir
managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress compar
protocols = imap lmtp sieve
sieve_script personal {
driver = file
path = ~/sieve
}Will the 'sieve_script personal { ... } ' block work ok with it's path being ~/ and will it inherit the mail_path defined farther up? Right now under 2.3 it creates the following:
/var/mail/stoffel.org/john/sieve/
/var/mail/stoffel.org/john/Maildir/directories, but I think I need to add in for 2.4 the following:
mail_home = /var/mail%{user | domain}/%{user | username}/And then the sieve_script_personal will work properly. Is this correct? And no, I haven't tried it yet, working on deploying my new test VM.
Now my old system is configured to use sqlite3 as the backend mechanism, and I see that it does define the following queries:
driver = sqlite
password_query = SELECT email as user, password FROM virtual_users WHERE email='%u';
user_query = SELECT '/var/mail/%d/%n' as home, 'maildir:/var/mail/%d/%n/Maildir' as mail, 'mail' AS uid, 'mail' AS gid FROM virtual_users WHERE email = '%u';
iterate_query = SELECT email AS user from virtual_users;
and I think the 'user_query' returning the 'home' value and the correct directory would do the right thing and mean I don't need to explicitly define mail_home.
Is this true?
Thanks, John
There wasn't any "antispam" plugin in Dovecot 2.3, so you are on your own there.
The sieve_spamtest settings are discussed in the upgrading page: https://doc.dovecot.org/2.4.3/installation/upgrade/2.3-to-2.4.html
michael
On 05/04/2026 10:53 AM MDT 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
Does anyone know of any tools to migrate the configs from 2.3 to 2.4?
participants (8)
-
Aki Tuomi
-
dovecot＠ptld.com
-
Franta Hanzlík
-
Gregory Carter
-
John Stoffel
-
Klaus Tachtler
-
Michael Slusarz
-
The Doctor