- dovecot - dovecot.org

2.4.0 on MacOS
by John Muccigrosso 01 Feb '25

01 Feb '25

I got bitten by the upgrade from 2.3 to 2.4 on my MacOS laptop. I know enough to be dangerous here and had a set-up that was working fine, but now I can't quite figure out how to modify my conf file to work correctly. The current error I'm getting is that there is no group "dovecot" even though I've created one and made the default user a member: > Fatal: service(dict) Group doesn't exist: dovecot More broadly I find the documentation hard to follow, as others seem to have noted in the past. Any help appreciated. Jackie

2 3

Help understanding doveadm-sync stateful
by Bruno MATEU 01 Feb '25

01 Feb '25

Hello, With the removal of the replication plugin in next releases, i'm trying to setup automatic synchronization using doveadm sync between my master and my replica. I managed to make the full sync work from my replica using the following comamnd `sync -A -N -R -f tcp:master-fqdn:12345` However i'd like to do stateful synchronization to avoid doing the full replication each time, and i haven't managed to do that. I tried the following: `doveadm sync -A -N -R -s "$(</var/lib/dovecot/sync-state)" tcp:master-fqdn:12345 > /var/lib/dovecot/sync-state`. However this output a `doveadm(username): Error: Saved sync state is invalid, falling back to full sync: Invalid base64 data` for every user. After looking at the state in /var/lib/dovecot/sync-state, i noticed that there is one line for every user with an associated state, plus one line with only a state. For some reason, the state is the same for every user, except one where the state is much longer. Do i need to run the command for each user, and give as an argument the corresponding state ? Is it enough to run the doveadm sync command with -A argument if i give the state in the last line outputted by doveadm sync ? Is this the right way to do it ? Best regards, Bruno MATEU

1 1

Different Replicator Crash??
by Kent Borg 31 Jan '25

31 Jan '25

I added the suggested "count--" and recompiled, and it now appears to work, the replication goes both ways, eyeballing the e-mail on the two servers they look the same. Good. But part of the time I am still getting what looks very much like the same crash, is there another "count--" I need to add to that file? > Jan 28 10:53:08 la dovecot[96175]: replicator: Panic: data stack: Out > of memory when allocating 268435496 bytes > Jan 28 10:53:08 la dovecot[96175]: replicator: Error: Raw backtrace: > #0 t_askpass[0x7fb404b0c0] -> #1 backtrace_append[0x7fb404b374] -> #2 > backtr\ > ace_get[0x7fb404b510] -> #3 execvp_const[0x7fb4057ba4] -> #4 > i_syslog_fatal_handler[0x7fb4058510] -> #5 i_panic[0x7fb3fa6808] -> #6 > t_pop_pass_st\ > r[0x7fb4050eb4] -> #7 connection_deinit[0x7fb4056430] -> #8 > pool_datastack_create[0x7fb407e7b0] -> #9 > array_bsearch_insert_pos_i[0x7fb40446d0] ->\ > #10 t_base64_scheme_decode[0x7fb404cb24] -> #11 > buffer_append[0x7fb404d3d0] -> #12 replicator_queue_push[0x558c4b4f40] > -> #13 replicator_brain_i\ > nit[0x558c4b53e4] -> #14 _start[0x558c4b3d70] -> #15 > _start[0x558c4b3f04] -> #16 io_loop_call_io[0x7fb4072f20] -> #17 > io_loop_handler_run_interna\ > l[0x7fb4075450] -> #18 io_loop_handler_run[0x7fb4075680] -> #19 > io_loop_run[0x7fb4075944] -> #20 master_service_run[0x7fb3fd84b0] -> > #21 main[0x5\ > 58c4b3930] -> #22 __libc_init_first[0x7fb3dd76d0] -> #23 > __libc_start_main[0x7fb3dd7780] -> #24 _start[0x558c4b3b80] > Jan 28 10:53:08 la dovecot[96175]: replicator: Fatal: master: > service(replicator): child 96714 killed with signal 6 (core dumps > disabled - https:\ > //dovecot.org/bugreport.html#coredumps) Thanks, -kb

1 0

Replication Question: Who Initiates?
by Kent Borg 31 Jan '25

31 Jan '25

As I understand it, if I am doing replication between a pair of servers, I run the replicator on just one and it makes all the two way changes necessary to make the two machines match. But this only happens when some change happens on that machine that runs the replicator. First, is this correct? If so, is there a way to have that other machine give the first machine poke, to get it to run a replication? Thanks, -kb

2 1

Writing to a Dictionary Using Lua
by Andrea Gabellini 31 Jan '25

31 Jan '25

Hello, I am using the push_notification_lua plugin and would like to modify my script to write data into a dictionary configured as follows: dict_server { dict proxy { idle_timeout = 300s name = sql slow_warn = 1s } dict sql { sql_driver = mysql mysql localhost { dbname = xxx password = xxx user = xxx } dict_map "shared/dsync/$user" { sql_table = dsync dict_map_value_field last_event { type = uint } dict_map_key_field userid { value = $user } } } } I am not very familiar with Lua, and I couldn't find any relevant examples in the documentation or online. Would it be possible to provide a sample code snippet demonstrating how to write to this dictionary using Lua? Thank you! -- TIM San Marino S.p.A. Andrea Gabellini Engineering R&D TIM San Marino S.p.A. - https://www.telecomitalia.sm Via Ventotto Luglio, 212 - Piano -2 47893 - Borgo Maggiore - Republic of San Marino Tel: (+378) 0549 886237 Fax: (+378) 0549 886188 -- Informativa Privacy Questa email ha per destinatari dei contatti presenti negli archivi di TIM San Marino S.p.A.. Tutte le informazioni vengono trattate e tutelate nel rispetto della normativa vigente sulla protezione dei dati personali (Reg. EU 2016/679). Per richiedere informazioni e/o variazioni e/o la cancellazione dei vostri dati presenti nei nostri archivi potete inviare una email a privacy(a)telecomitalia.sm. Avviso di Riservatezza Il contenuto di questa e-mail e degli eventuali allegati e' strettamente confidenziale e destinato alla/e persona/e a cui e' indirizzato. Se avete ricevuto per errore questa e-mail, vi preghiamo di segnalarcelo immediatamente e di cancellarla dal vostro computer. E' fatto divieto di copiare e divulgare il contenuto di questa e-mail. Ogni utilizzo abusivo delle informazioni qui contenute da parte di persone terze o comunque non indicate nella presente e-mail potra' essere perseguito ai sensi di legge.

2 3

"Modseq 34839 no longer in transaction log"
by Kent Borg 29 Jan '25

29 Jan '25

My new custom-built .deb packages seem to work, or at least work better! When new e-mails come in, it quickly attempts a sync, but says it fails: > Jan 29 10:31:49 la dovecot[1199]: doveadm: Error: > doveadm(kentborg)<2465><gL2eARV0mmehCQAAA3PmQQ>: Warning: Failed to do > incremental sync for mai\ > lbox INBOX, retry with a full sync (Modseq 34839 no longer in > transaction log (highest=37557, last_common_uid=12476, nextuid=12614)) Is this a leftover problem from my earlier crashes? I tried a full sync ("doveadm replicator replicate -f kentborg") and rebooting both machines, but I still get the error when new e-mails come in. The number in the error increments by three the several times I have seen this so far. Is there a way to make this happy? Thanks, -kb P.S. I am only doing one-way syncing so far.

1 0

Why does metrics exporter not work anymore?
by Christian Rößner 29 Jan '25

29 Jan '25

Hi, I am trying to get the metrics exporter to work in 2.4.0, but for some reason, I do not see any connection attempts to the named http server nor do I get any errors: $ doveconf -n # 2.4.0 (daeb6bc59c): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.0 (1b2d5bb9) # OS: Linux 6.10.14-linuxkit x86_64 Debian 12.9 # Hostname: b7638a15bee0 dovecot_config_version = 2.4.0 auth_allow_cleartext = yes auth_cache_verify_password_with_worker = yes auth_failure_delay = 0 secs auth_mechanisms = auth_mechanisms { plain = yes login = yes } auth_username_format = %{user | username | lower} debug_log_path = /dev/stdout default_internal_group = vmail default_internal_user = vmail default_login_user = vmail dovecot_storage_version = 2.4.0 first_valid_uid = 1000 imap_id_retain = yes info_log_path = /dev/stdout last_valid_uid = 1000 listen = listen { * = yes } lmtp_proxy = yes log_path = /dev/stdout mail_debug = yes mail_driver = sdbox mail_gid = vmail mail_home = /srv/mail/%Ln mail_path = ~/Mail mail_uid = vmail protocols { imap = yes pop3 = yes lmtp = yes } ssl = no verbose_proctitle = yes namespace inbox { inbox = yes separator = / } service lmtp { inet_listener lmtp { port = 24 ssl = no } } service imap-login { client_limit = 100 process_min_avail = 1 restart_request_count = unlimited inet_listener imap { port = 143 } } service pop3-login { client_limit = 100 process_min_avail = 1 restart_request_count = unlimited inet_listener pop3 { port = 110 } } event_exporter log { driver = log format = json time_format = rfc3339 } event_exporter conn_state { driver = http-post format = json http_post_url = http://nauthilus:8080/api/v1/custom/dovecot-session-cleaner time_format = rfc3339 http_client_request_absolute_timeout = 5sec } metric client_disconnect_http { exporter = conn_state exporter_include = exporter_include { name = yes hostname = yes timestamps = yes categories = yes fields = yes } filter = event=mail_user_session_finished AND (category=imap OR category=pop3 OR category=lmtp OR category=sieve) } metric imap_noop { exporter = conn_state exporter_include = exporter_include { name = yes hostname = yes timestamps = yes categories = yes fields = yes } filter = event=imap_command_finished AND cmd_name=NOOP } passdb lua { lua_file = /etc/dovecot/auth.lua } userdb prefetch { } userdb lua { auth_verbose = no lua_file = /etc/dovecot/auth.lua result_failure = return-fail result_internalfail = return-fail result_success = continue-ok skip = never } It is an example Docker setup found here: https://github.com/croessner/nauthilus-demo There are no error logs in dovecot. Thanks in advance Christian Rößner -- Rößner-Network-Solutions Zertifizierter ITSiBe / CISO Marburger Str. 70a, 36304 Alsfeld Fax: +49 6631 78823409, Mobil: +49 171 9905345 USt-IdNr.: DE225643613, https://roessner.website PGP fingerprint: 658D 1342 B762 F484 2DDF 1E88 38A5 4346 D727 94E5

4 16

Fwd: dovecot: master: Warning: service(imap-login): process_limit (100) reached, client connections are being dropped
by Stephane De Greef 28 Jan '25

28 Jan '25

-------- Message transféré -------- Sujet : Re: dovecot: master: Warning: service(imap-login): process_limit (100) reached, client connections are being dropped Date : Tue, 28 Jan 2025 11:22:35 +0100 De : Stephane De Greef <stephane.degreef(a)pacapime.be> Pour : dovecot-owner(a)dovecot.org doveconf -n # 2.3.19.1 (9b53102964): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.19 (4eae2f79) # OS: Linux 6.1.0-30-amd64 x86_64 Debian 12.9 ext4 # Hostname: pacapime.ovh auth_mechanisms = plain login mail_gid = 8 mail_home = /var/mail/%n mail_location = maildir:/var/mail/%n mail_plugins = " quota notify push_notification" mail_uid = 500 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext namespace inbox { inbox = yes location = mailbox Archive { auto = subscribe special_use = \Archive } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } passdb { args = /etc/dovecot/app-senders-passwd driver = passwd-file } plugin { antispam_backend = pipe antispam_debug_target = syslog antispam_pipe_program = /usr/bin/rspamc antispam_pipe_program_args = -h;localhost:11334;-P;q1 antispam_pipe_program_notspam_arg = learn_ham antispam_pipe_program_spam_arg = learn_spam antispam_spam_pattern_ignorecase = junk;spam antispam_trash_pattern_ignorecase = trash;papierkorb;deleted messages antispam_verbose_debug = 0 quota = maildir:User quota quota_rule2 = SPAM:ignore quota_rule3 = Trash:ignore quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u quota_warning3 = -storage=100%% quota-warning below %u sieve = /var/mail/sievescript/%n/.dovecot.sieve sieve_before = /etc/dovecot/global_script/ sieve_dir = /var/mail/sievescript/%n/scripts/ } protocols = imap sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-master { group = mail mode = 0660 user = vmail } } service quota-warning { executable = script /usr/bin/quota-warning.sh user = vmail } service stats { unix_listener stats-reader { group = mail mode = 0660 user = vmail } unix_listener stats-writer { group = mail mode = 0660 user = vmail } } ssl = required ssl_cert = </etc/yunohost/certs/pacapime.ovh/crt.pem ssl_cipher_list = ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-CHACHA20-POLY1305 ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } userdb { args = username_format=%n /etc/dovecot/app-senders-passwd driver = passwd-file } protocol imap { imap_client_workarounds = mail_plugins = " quota notify push_notification imap_quota antispam" } protocol lda { auth_socket_path = /var/run/dovecot/auth-master mail_plugins = quota sieve postmaster_address = postmaster(a)pacapime.ovh } local_name pacapime.be { ssl_cert = </etc/yunohost/certs/pacapime.be/crt.pem ssl_key = # hidden, use -P to show it } local_name auth.pacapime.be { ssl_cert = </etc/yunohost/certs/auth.pacapime.be/crt.pem ssl_key = # hidden, use -P to show it } local_name ftp.pacapime.be { ssl_cert = </etc/yunohost/certs/ftp.pacapime.be/crt.pem ssl_key = # hidden, use -P to show it } local_name www.pacapime.be { ssl_cert = </etc/yunohost/certs/www.pacapime.be/crt.pem ssl_key = # hidden, use -P to show it } local_name adm.pacapime.ovh { ssl_cert = </etc/yunohost/certs/adm.pacapime.ovh/crt.pem ssl_key = # hidden, use -P to show it } local_name coturn.pacapime.ovh { ssl_cert = </etc/yunohost/certs/coturn.pacapime.ovh/crt.pem ssl_key = # hidden, use -P to show it } local_name doc.pacapime.ovh { ssl_cert = </etc/yunohost/certs/doc.pacapime.ovh/crt.pem ssl_key = # hidden, use -P to show it } local_name drive.pacapime.ovh { ssl_cert = </etc/yunohost/certs/drive.pacapime.ovh/crt.pem ssl_key = # hidden, use -P to show it } local_name exc.pacapime.ovh { ssl_cert = </etc/yunohost/certs/exc.pacapime.ovh/crt.pem ssl_key = # hidden, use -P to show it } local_name graph.pacapime.ovh { ssl_cert = </etc/yunohost/certs/graph.pacapime.ovh/crt.pem ssl_key = # hidden, use -P to show it } local_name mail.pacapime.ovh { ssl_cert = </etc/yunohost/certs/mail.pacapime.ovh/crt.pem ssl_key = # hidden, use -P to show it } local_name mattermost.pacapime.ovh { ssl_cert = </etc/yunohost/certs/mattermost.pacapime.ovh/crt.pem ssl_key = # hidden, use -P to show it } local_name paper.pacapime.ovh { ssl_cert = </etc/yunohost/certs/paper.pacapime.ovh/crt.pem ssl_key = # hidden, use -P to show it } local_name pdf.pacapime.ovh { ssl_cert = </etc/yunohost/certs/pdf.pacapime.ovh/crt.pem ssl_key = # hidden, use -P to show it } local_name pictures.pacapime.ovh { ssl_cert = </etc/yunohost/certs/pictures.pacapime.ovh/crt.pem ssl_key = # hidden, use -P to show it } local_name qr.pacapime.ovh { ssl_cert = </etc/yunohost/certs/qr.pacapime.ovh/crt.pem ssl_key = # hidden, use -P to show it } local_name round.pacapime.ovh { ssl_cert = </etc/yunohost/certs/round.pacapime.ovh/crt.pem ssl_key = # hidden, use -P to show it } local_name rust.pacapime.ovh { ssl_cert = </etc/yunohost/certs/rust.pacapime.ovh/crt.pem ssl_key = # hidden, use -P to show it } local_name sql.pacapime.ovh { ssl_cert = </etc/yunohost/certs/sql.pacapime.ovh/crt.pem ssl_key = # hidden, use -P to show it } local_name stat.pacapime.ovh { ssl_cert = </etc/yunohost/certs/stat.pacapime.ovh/crt.pem ssl_key = # hidden, use -P to show it } local_name talk.pacapime.ovh { ssl_cert = </etc/yunohost/certs/talk.pacapime.ovh/crt.pem ssl_key = # hidden, use -P to show it } local_name test.pacapime.ovh { ssl_cert = </etc/yunohost/certs/test.pacapime.ovh/crt.pem ssl_key = # hidden, use -P to show it } local_name tools.pacapime.ovh { ssl_cert = </etc/yunohost/certs/tools.pacapime.ovh/crt.pem ssl_key = # hidden, use -P to show it } local_name video.pacapime.ovh { ssl_cert = </etc/yunohost/certs/video.pacapime.ovh/crt.pem ssl_key = # hidden, use -P to show it } local_name webmin.pacapime.ovh { ssl_cert = </etc/yunohost/certs/webmin.pacapime.ovh/crt.pem ssl_key = # hidden, use -P to show it } local_name www.pacapime.ovh { ssl_cert = </etc/yunohost/certs/www.pacapime.ovh/crt.pem ssl_key = # hidden, use -P to show it }

2 2

Example configs and packaging scripts
by Aki Tuomi 28 Jan '25

28 Jan '25

Hi! To make the transition from 2.3 to 2.4 easier, especially for package maintainers, we have prepared one-time conversion of 2.3 example configurations to 2.4. Please find them at https://github.com/dovecot/tools/blob/main/dovecot-2.4.0-example-config.tar… Please review release notes and changelogs for needed changes in future releases. Also, would like to remind that https://repo.dovecot.org/ce-2.4-latest/debian/bookworm/pool/main/ contains the debian.tar.xz used to build our packages, and similarly for rhel based https://repo.dovecot.org/ce-2.4-latest/rhel/9/SRPMS/ has the source RPMs. Kind regards, Aki Tuomi

3 3

dovecot: master: Warning: service(imap-login): process_limit (100) reached, client connections are being dropped
by Stephane De Greef 28 Jan '25

28 Jan '25

Hello, I would need a little help. I have the following message in the logs dovecot: master: Warning: service(imap-login): process_limit (100) reached, client connections are being dropped I have already modified the file /etc/dovecot/conf.d/10-master.conf The first 2 lines are default_process_limit = 200 default_client_limit = 1250 and if i make: grep -r process_limit /etc/ he found that: /etc/dovecot/conf.d/10-master.conf:default_process_limit = 200 /etc/dovecot/conf.d/10-master.conf: process_limit = 1024 /etc/dovecot/conf.d/10-master.conf: #process_limit = 1024 /etc/dovecot/conf.d/10-master.conf: process_limit = 1024 /etc/dovecot/conf.d/10-master.conf.original:default_process_limit = 150 /etc/dovecot/conf.d/10-master.conf.original: #process_limit = 1024 /etc/dovecot/conf.d/10-master.conf.original: #process_limit = 1024 /etc/dovecot/conf.d/10-master.conf.original: #process_limit = 1024 /etc/dovecot/conf.d/20-managesieve.conf: #process_limit = 1024 And so I don’t really understand why this error message remains at 100, I specify that the postfix and dovecot services were restarted after the modification,

2 1

doveadm backup and sieve scripts
by Maksim Rodin 28 Jan '25

28 Jan '25

Hello, What is the best way to backup (migrate) sieve rules? I tried: "doveadm backup -u somebox@somedomain maildir:/backup_dir" "doveadm backup -u somebox@somedomain remote:newmailserver.somedomain" Messages are copied but sieve rules are not. dovecot --version: 2.3.21.1 doveconf -n: # 2.3.21.1 (d492236fa0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.21.1 (49005e73) # OS: OpenBSD 7.5 amd64 # Hostname: mail first_valid_uid = 1000 mail_attachment_dir = /work/vmail/attaches mail_attachment_min_size = 10 k mail_gid = 2000 mail_home = /work/vmail/%n mail_location = sdbox:~/dbox mail_plugins = " zlib acl" mail_uid = 2000 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational r mbox_write_locks = fcntl mmap_disable = yes namespace { list = children location = sdbox:/work/vmail/%%d/%%n/dbox:INDEXPVT=~/dbox/shared/%%u prefix = shared/%%u/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / type = private } passdb { driver = bsdauth } passdb { args = /etc/dovecot/dovecot-shared.conf.ext driver = ldap } passdb { args = /etc/dovecot/dovecot-ldap_somedomain.conf.ext driver = ldap } plugin { acl = vfile acl_shared_dict = file:/var/db/dovecot/db/shared-mailboxes.db sieve = file:~/sieve;active=~/.dovecot.sieve zlib_save = lz4 zlib_save_level = 9 } protocols = imap lmtp submission sieve service decode2text { executable = script /usr/local/libexec/dovecot/decode2text.sh unix_listener decode2text { mode = 0666 } user = _dovecot } service lmtp { user = vmail } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } ssl_cert = </etc/letsencrypt/live/somedomain/fullchain.pem ssl_key = # hidden, use -P to show it submission_relay_host = localhost submission_relay_trusted = yes userdb { driver = passwd } userdb { args = /etc/dovecot/dovecot-shared.conf.ext default_fields = uid=vmail gid=vmail home=/work/vmail/%n_%{domain_first} driver = ldap } userdb { args = uid=vmail gid=vmail driver = static } verbose_proctitle = yes protocol lmtp { mail_plugins = " zlib acl sieve" } protocol imap { mail_max_userip_connections = 100 mail_plugins = " zlib acl imap_acl" } protocol submission { mail_max_userip_connections = 100 } -- Best regards Maksim Rodin

1 0

Tests failed in 2.4.0 (Possibly time-zone-related?)
by Peter 27 Jan '25

27 Jan '25

I'm getting the following failed test: test-var-expand.c:464: Assert failed: labs(t0 - t1) < 10 3600 < 10 is not true var_expand(providers) ................................................ : FAILED This test appears to be a timestamp comparison as per this comment: /* Ensure the time is within 10 seconds */ being exactly one hour off makes me suspect a time-zone issue on the build machine. This machine is in NZDT which is currently in daylight savings time which makes me suspect that this is an issue that is specific to dovecot being built in a timezone in the southern hemisphere. Shouldn't the comparison be done on UTC time instead of localtime to avoid these issues? Peter

2 3

2.4 , error with virtual plugin
by Luigi Trovato 26 Jan '25

26 Jan '25

Hello, even with updated config for virtual plugin: mail_plugins { virtual = yes } namespace virtual { prefix = virtual. separator = . mail_driver = virtual mail_path = ~/virtual } I get this error: imap(lonestar(a)lonestar.it)<2991><64ab1o8sDJl/AAAB>: Error: Namespace virtual: Unknown mail storage driver virtual imap(lonestar(a)lonestar.it)<2991><64ab1o8sDJl/AAAB>: Info: Disconnected: Namespace virtual: Unknown mail storage driver virtual in=0 out=442 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 What could it be? -- Ciao, Luigi

2 2

Errors using dovecot 2.4 container image
by Andreas Achtzehn 26 Jan '25

26 Jan '25

Dear Dovecot team, I ran into troubles using the newly released 2.4 docker image. The dovecot/dovenull users are apparently not part of the image -- hence the dovecot server fails to start up with a fatal error. I'm using a vanilla configuration, default_login_user, etc. are not set. Thanks for having a look! Best regards, Andreas

3 2

Latest docker image broken
by Stephen Benjamin 26 Jan '25

26 Jan '25

I use watchtower to keep my docker images up to date and the image pushed to latest tag yesterday broke everything - I can’t find any docs saying anything about mail_location being removed or replaced…. Any idea? I’m unfortunately away from my laptop for a few days so I can’t do any deep debugging but I’d appreciate any pointer. doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 1: mail_location: Unknown setting: mail_location Sent from my iPhone

2 2

Help with migration of Quota config to 2.4.0?
by dovecot.org＠schildbach.de 25 Jan '25

25 Jan '25

I've converted most of my config to 2.4.0, but one thing I don't get from the docs: ``` mail_plugins = $mail_plugins quota protocol imap { mail_plugins = $mail_plugins imap_quota } plugin { quota = maildir:User quota:noenforcing quota_rule = *:storage=7GB quota_rule2 = Trash:storage=+10%% } ``` How would this translate?

2 1

Dovecot 2.4.0 compilation issues (Linux, GCC 8.3.1)
by Andreas M. Kirchwitz 25 Jan '25

25 Jan '25

Hello users of Dovecot! Currently, Dovecot 2.3.21.1 compiles and runs fine on a Red Hat Linux clone with GCC 8.3.1. Now tried the brandnew sources of Dovecot 2.4.0, but to my surprise it doesn't even compile and I have no clue where to begin my debugging. Besides some minor things (new OpenSSL version check not working, maybe because not using proper include files; and one library is missing -lrt to use clock_gettime), I'm totally stuck at compiling the new "src/lib-http/http-server-settings.c". It fails while including "src/lib/macros.h" with the message "error: size of unnamed array is negative" Dovecot 2.3.21.1 has no http-server-settings.c but a very similar macros.h which everbody seems to be happy about. So what is it that happens while compiling http-server-settings.c to make GCC fail? I ran "./configure" with just LDFLAGS="-lrt -Wl,--no-as-needed" added, and then simply "make". Nothing special here. I'm happy with all the default settings and auto-detected options. Full log of compilation messages is appended at the end of this message. Any help is highly appreciated. Currently I have no idea where to even start my search for a workaround or even a solution. Never had such problems with compiling Dovecot so far. Thanks a lot in advance ... Andreas ====================================================================== Compilation messages where the error occurs: ====================================================================== Making all in lib-http make[3]: Entering directory '/usr/local/src/dovecot-2.4.0/src/lib-http' CC http-server-settings.lo In file included from ../../src/lib/lib.h:37, from http-server-settings.c:3: ../../src/lib/lib.h: In function ‘time_to_uint32’: ../../src/lib/lib.h:145:14: warning: comparison of integer expressions of different signedness: ‘time_t’ {aka ‘long int’} and ‘unsigned int’ [-Wsign-compare] i_assert(ts <= UINT32_MAX); ^~ ../../src/lib/macros.h:198:45: note: in definition of macro ‘unlikely’ # define unlikely(expr) (__builtin_expect((expr) ? 1 : 0, 0) != 0) ^~~~ ../../src/lib/lib.h:145:2: note: in expansion of macro ‘i_assert’ i_assert(ts <= UINT32_MAX); ^~~~~~~~ In file included from http-server-settings.c:3: ../../src/lib/lib.h: In function ‘time_to_uint32_trunc’: ../../src/lib/lib.h:153:9: warning: comparison of integer expressions of different signedness: ‘time_t’ {aka ‘long int’} and ‘unsigned int’ [-Wsign-compare] if (ts > UINT32_MAX) ^ In file included from ../../src/lib/lib.h:37, from http-server-settings.c:3: http-server-settings.c: At top level: ../../src/lib/macros.h:173:14: error: size of unnamed array is negative (sizeof(char[1 - 2 * ((condition) ? 1 : 0)]) > 0 ? FALSE : FALSE) ^ ../../src/lib/macros.h:182:2: note: in expansion of macro ‘COMPILE_ERROR_IF_TRUE’ COMPILE_ERROR_IF_TRUE( \ ^~~~~~~~~~~~~~~~~~~~~ ../../src/lib-settings/settings-parser.h:78:27: note: in expansion of macro ‘COMPILE_ERROR_IF_TYPES_NOT_COMPATIBLE’ { .type = (_enum_type) + COMPILE_ERROR_IF_TYPES_NOT_COMPATIBLE( \ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../../src/lib-settings/settings-parser.h:125:2: note: in expansion of macro ‘SETTING_DEFINE_STRUCT_TYPE’ SETTING_DEFINE_STRUCT_TYPE(SET_SIZE, SET_FLAG_HIDDEN, uoff_t, key, name, struct_name) ^~~~~~~~~~~~~~~~~~~~~~~~~~ http-server-settings.c:13:2: note: in expansion of macro ‘SETTING_DEFINE_STRUCT_SIZE_HIDDEN’ SETTING_DEFINE_STRUCT_##type("http_server_"#name, name, struct http_server_settings) ^~~~~~~~~~~~~~~~~~~~~~ http-server-settings.c:34:2: note: in expansion of macro ‘DEF’ DEF(SIZE_HIDDEN, socket_send_buffer_size), ^~~ ../../src/lib/macros.h:173:14: error: size of unnamed array is negative (sizeof(char[1 - 2 * ((condition) ? 1 : 0)]) > 0 ? FALSE : FALSE) ^ ../../src/lib/macros.h:182:2: note: in expansion of macro ‘COMPILE_ERROR_IF_TRUE’ COMPILE_ERROR_IF_TRUE( \ ^~~~~~~~~~~~~~~~~~~~~ ../../src/lib-settings/settings-parser.h:78:27: note: in expansion of macro ‘COMPILE_ERROR_IF_TYPES_NOT_COMPATIBLE’ { .type = (_enum_type) + COMPILE_ERROR_IF_TYPES_NOT_COMPATIBLE( \ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../../src/lib-settings/settings-parser.h:125:2: note: in expansion of macro ‘SETTING_DEFINE_STRUCT_TYPE’ SETTING_DEFINE_STRUCT_TYPE(SET_SIZE, SET_FLAG_HIDDEN, uoff_t, key, name, struct_name) ^~~~~~~~~~~~~~~~~~~~~~~~~~ http-server-settings.c:13:2: note: in expansion of macro ‘SETTING_DEFINE_STRUCT_SIZE_HIDDEN’ SETTING_DEFINE_STRUCT_##type("http_server_"#name, name, struct http_server_settings) ^~~~~~~~~~~~~~~~~~~~~~ http-server-settings.c:35:2: note: in expansion of macro ‘DEF’ DEF(SIZE_HIDDEN, socket_recv_buffer_size), ^~~ make[3]: *** [Makefile:1007: http-server-settings.lo] Error 1 make[3]: Leaving directory '/usr/local/src/dovecot-2.4.0/src/lib-http' make[2]: *** [Makefile:587: all-recursive] Error 1 make[2]: Leaving directory '/usr/local/src/dovecot-2.4.0/src' make[1]: *** [Makefile:725: all-recursive] Error 1 make[1]: Leaving directory '/usr/local/src/dovecot-2.4.0' make: *** [Makefile:567: all] Error 2

3 3

newbie dsync problems
by Kent Borg 25 Jan '25

25 Jan '25

I have a very basic postfix/dovecot server, with just a few users, and it works. But in the past I have had hardware failures…so I would like use dsync to a nearly matching server for some extra safety, and I have not yet been successful. I am trying to do this as root over ssh, with a private key for authentication. I do not managed to get the whole replicator thing working, so as part of simplifying things I am trying to run dsync manually, just on one user (myself). I hope this isn't a silly approach. What would the manual command look like? The closest example on the man page is: > $ doveadm sync -u username(a)example.com ssh -i id_dsa.dovecot \ > mailuser(a)example.com doveadm dsync-server -u username(a)example.com I try to change that to match my case and it has never heard of me: > root@la:/etc/dovecot# doveadm sync -1 -u kentborg(a)mail.borg.org ssh -i > /root/.ssh/id_rsa_rc.borg.org.dsync kentborg(a)mail.borg.org doveadm > dsync-server -u kentborg(a)mail.borg.org > doveadm(kentborg(a)mail.borg.org): Error: User doesn't exist > root@la:/etc/dovecot# I drop the machine part of the name and it knows who I am on this end but can't get to the other end: > root@la:/etc/dovecot# doveadm sync -1 -u kentborg ssh -i > /root/.ssh/id_rsa_rc.borg.org.dsync kentborg(a)mail.borg.org doveadm > dsync-server -u kent\ > borg(a)mail.borg.org > kentborg(a)mail.borg.org's password: I think I have root's ssh keys set up correctly, I can run this: > root@la:/etc/dovecot# ssh -i /root/.ssh/id_rsa_rc.borg.org.dsync > mail.borg.org > PTY allocation request failed on channel 0 > C-c C-croot@la:/etc/dovecot# …and on the remote end I see some debugging output I put in the remote script, outputting an empty username. Makes sense. If I try to put that in this (incomplete) dsync command: > root@la:/etc/dovecot# doveadm sync -u kentborg -1 ssh -i > /root/.ssh/id_rsa_rc.borg.org.dsync mail.borg.org > Error: Extraneous arguments found: 3 5 > doveadm(kentborg)<1029674><QvOnDPmKkmcqtg8AA8+vgQ>: Error: > read(remote) failed: EOF (version not received) > doveadm(kentborg)<1029674><QvOnDPmKkmcqtg8AA8+vgQ>: Error: Remote > command returned error 64: ssh -i /root/.ssh/id_rsa_rc.borg.org.dsync > mail.borg\ > .org dsync-server > root@la:/etc/dovecot# And the remote end outputs the username as "VERSION dsync 3 5", okay, maybe progress. But when I try to make the command more complete and send a username to the remote end, and now I am no longer talking to the remote end: > root@la:/etc/dovecot# doveadm sync -u kentborg -1 ssh -i > /root/.ssh/id_rsa_rc.borg.org.dsync remoteprefix(a)mail.borg.org > remoteprefix(a)mail.borg.org's password: Suggestions? Thanks, -kb

2 8

TLS Connections Between Dovecot & MariaDB
by duluxoz 25 Jan '25

25 Jan '25

Hi All, I'm using a MariaDB backend to a Dovecot server, with TLS required by the MariaDB server for connections. My sql_dovecot.conf.ext file is using the following connection line: `connect = host=mariadb.example.com dbname=mail_server user=vmail password={REDACTED} ssl_ca=/etc/pki/tls/certs/root_ca.crt`. I can't work out from the doco or Google what else I need in that line, but I suspect it'll be something like: `ssl_cert=/etc/pki/tls/certs/vmail_rsa.pem ssl_key=/etc/pki/tls/certs/vmail_rsa.key`. Could someone please confirm this and let me know the actual extra commands/options - thanks Cheers Dulux-Oz

2 3

Virtual folders in top level hierarchy
by Robert Sanchez 25 Jan '25

25 Jan '25

Hi, I've got a virtual "Flagged" folder but it appears as a subfolder of "virtual" instead of being alongside Inbox, Sent, etc. I've seen some previous messages where this was asked, but they didn't really seem to achieve what I want. My expectation was that calling the defined "virtual.Flagged" folder in the inbox namespace would link it there, but either that is not the expected behavior or I'm doing something wrong. This is my current config: namespace virtual { location = virtual:/etc/dovecot/virtual:INDEX=~/virtual:CONTROL=~/virtual:VOLATILEDIR=~/virtual/ prefix = virtual. separator = . list = yes hidden = no } namespace inbox { # (...) default Drafts, Junk, etc. # If you have a virtual "Flagged" mailbox: mailbox virtual.Flagged { special_use = \Flagged auto = subscribe comment = All my flagged messages } } I've also tried "hidden = yes" and "list = no", but I don't see any differences in the client. This is Dovecot 2.3.21 (47349e2482) on Ubuntu 24.04, btw. Thanks.

1 0

Proper syntax for using `allow_nets` with dovecot passdb sql
by Kevin Farley 24 Jan '25

24 Jan '25

Hi there, I posted this question in ServerFault (https://serverfault.com/questions/1170095/proper-syntax-for-using-allow-net…) but haven't gotten an answer after 10 days so thought I'd try here, I appreciate any help you can offer! I want to allow for two auth methods in dovecot via SQL. First, the traditional route where the password is hashed with |SHA512-CRYPT| and compared to the DB response. Second, where the request is coming from a user already authenticated by a different part of the local system, and the hash itself is passed and compared as |PLAIN|. It works perfectly with the following |auth-sql.conf.ext| and associated sql files... |# Passdb for traditional method passdb { driver = sql args = /etc/dovecot/conf.d/dovecot-sql.conf.ext } # Passdb for hybrid method (direct hash comparison) passdb { driver = sql args = /etc/dovecot/conf.d/dovecot-sql-hybrid.conf.ext } # Userdb prefetch to use attributes from the passdb query userdb { driver = prefetch } # Userdb static as fallback for default attributes userdb { driver = static args = uid=vmail gid=vmail home=/srv/mail/%d/%n } | The problem I'm having is that I want to secure the second hybrid |PLAIN| method so that it can only be used by the local host using the |allow_nets| argument. In the documentation <https://doc.dovecot.org/2.3/configuration_manual/authentication/allow_nets/…> it shows that I should simply add it to the |args| like this... |args = /etc/dovecot/conf.d/dovecot-sql-hybrid.conf.ext allow_nets=local,127.0.0.1/32 | But as soon as I do this, the logs show that it's trying to open the entire string as if the |allow_nets...| argument is part of the path, and fails to find the file. I've tried moving the |allow_nets| argument to the beginning, but that had the same result. What is the correct syntax for using |allow_nets| with |passdb sql|? # 2.3.16 (7e2e900c1a): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.16 (09c29328) # OS: Linux 5.14.0-503.21.1.el9_5.x86_64 x86_64 Rocky Linux release 9.5 (Blue Onyx) xfs Thanks, Kevin.

1 0

doveadm mailbox list permission failure for virtual user
by leo1subscr＠zudiewiener.com 24 Jan '25

24 Jan '25

I'm using Dovecot 2.3.21 (47349e2482) on Ubuntu and have convigured virtual mail users. Everything is working finem but a few doevadm commands fail sudo doveadm mailbox list returns doveadm(root): Error: chdir(/root/) failed: Permission denied (euid=1001(vmail) egid=1001(vmail) missing +x perm: /root, dir owned by 0:0 mode=0700)

3 2

Fwd: Fwd: [OFFLIST] Re: connection refused, no error anywhere
by Marco Fioretti 23 Jan '25

23 Jan '25

Hi Robert, I corrected the service imap-login section of both dovecot.conf AND conf.d/10-master.conf as you suggested, The files in ssl_cert and ssl_key exist and are readable by dovecot. I have even changed for testing the permission of /etc/letsencrypt/live /etc/letsencrypt/archive to 0755 and restarted dovecot. However, the output of ss -tuln | grep 993 is still null. What next? Thanks ---------- Forwarded message --------- Da: Robert Nowotny <rnowotny(a)rotek.at> Date: mar 21 gen 2025 alle ore 23:47 Subject: RE: Fwd: [OFFLIST] Re: connection refused, no error anywhere To: Marco Fioretti <marco.fioretti(a)gmail.com> To resolve the connection refused error when accessing Dovecot on the new server, you need to adjust the Dovecot configuration to enable the appropriate IMAP service ports. 1. Enable IMAPS (Port 993) for Secure Connections: - Modify the `service imap-login` section in your Dovecot configuration (likely in `/etc/dovecot/conf.d/10-master.conf`) to include an `imaps` listener: ```conf service imap-login { inet_listener imap { port = 0 # Disables plain IMAP (port 143) } inet_listener imaps { port = 993 ssl = yes } } ``` - This configuration disables plaintext IMAP on port 143 and enables IMAPS on port 993 with SSL. 2. Ensure SSL Certificates Are Correct: - Verify the paths to your SSL certificate and key in `/etc/dovecot/conf.d/10-ssl.conf`: ```conf ssl_cert = </etc/letsencrypt/live/example.com/fullchain.pem ssl_key = </etc/letsencrypt/live/example.com/privkey.pem ``` - Confirm the files exist and have proper permissions (readable by Dovecot). 3. Restart Dovecot: ```bash sudo systemctl restart dovecot ``` 4. Verify Dovecot is Listening: ```bash sudo ss -tuln | grep 993 ``` - You should see Dovecot listening on port 993. 5. Test the Connection Using SSL: ```bash openssl s_client -connect example.com:993 ``` - This should establish a secure connection to the IMAPS port. Additional Recommendations: - Disable Plaintext IMAP: Keeping `port = 0` for the `imap` listener ensures unencrypted IMAP is disabled, enhancing security. - Firewall Configuration: Confirm UFW allows port 993: ```bash sudo ufw allow 993/tcp ``` By enabling IMAPS on port 993 and ensuring SSL is properly configured, secure email access will be restored. If you must use port 143 (not recommended), set `port = 143` in the `imap` listener and enforce STARTTLS by adding `ssl = required` in your SSL configuration. *Von:* Marco Fioretti via dovecot <dovecot(a)dovecot.org> <dovecot(a)dovecot.org> *Gesendet:* Dienstag, 21. Januar 2025 um 23:22 MEZ *An:* Dovecot <dovecot(a)dovecot.org> <dovecot(a)dovecot.org> *Betreff:* FW: [OFFLIST] Re: connection refused, no error anywhere ---------- Forwarded message --------- Da: Marco Fioretti <marco.fioretti(a)gmail.com> <marco.fioretti(a)gmail.com> Date: mar 21 gen 2025 alle ore 19:33 Subject: Re: [OFFLIST] Re: connection refused, no error anywhere To: Michael Peddemors <michael(a)linuxmagic.com> <michael(a)linuxmagic.com> Hi Michel, I cannot say which NGO it is. What I know is that everything with that configuration was working fine, as far as they know, on the old server. So, any help to change the configuration to make it work with the current version of dovecot on Ubuntu 24.04LTS is very welcome... Il giorno mar 21 gen 2025 alle ore 19:11 Michael Peddemors <michael(a)linuxmagic.com> ha scritto: Which NGO? Don't listen on port 143 any more, make sure to only listen on 587/465/993/995 with TLS/SSL.. NGO's are often targeted.. On 2025-01-21 09:50, Marco Fioretti via dovecot wrote: Greetings, I was just tasked with rebuilding from scratch the mail server of an NGO, on a brand new Ubuntu 24.04 LTS VPS. I have copied the whole dovecot configuration to the new server, and now am stuck because: - dovecot IS running, dovecot service status shows no errors, but: - if I try to connect with mutt from my desktop I get "connection refused" - the ufw firewall does allow imap/imaps connections, and there are no errors in its log - even "telnet localhost 143" fails: Trying ::1... Connection failed: Connection refused Trying 127.0.0.1... telnet: Unable to connect to remote host: Connection refused - I see no related errors in /var/log/mail.log or /var/log/syslog. output of dovecot -n is pasted below, I only changed the actual domain name to "example.com" TIA for any pointer, I really need to get this server back online as soon as possible... Marco # 2.3.21 (47349e2482): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.21 (f6cd4b8e) doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -Pn > dovecot-new.conf doveconf: Warning: Obsolete setting in /etc/dovecot/conf.d/10-ssl.conf:9: ssl_dh_parameters_length is no longer needed # OS: Linux 6.8.0-51-generic x86_64 Ubuntu 24.04.1 LTS ext4 # Hostname: example.com auth_debug = yes auth_verbose = yes auth_verbose_passwords = plain mail_location = maildir:/var/mail/mymail_storage/base/ mbox_write_locks = fcntl passdb { args = /etc/imap.v_users driver = passwd-file } passdb { driver = pam } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imap { port = 0 } } ssl_cert = </etc/letsencrypt/live/example.com/fullchain.pem ssl_cipher_list = ALL ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = /etc/imap.v_users driver = passwd-file } userdb { driver = passwd } verbose_ssl = yes _______________________________________________ dovecot mailing list -- dovecot(a)dovecot.org To unsubscribe send an email to dovecot-leave(a)dovecot.org -- "Catch the Magic of Linux..." ------------------------------------------------------------------------ Michael Peddemors, President/CEO LinuxMagic Inc. Visit us at http://www.linuxmagic.com @linuxmagic A Wizard IT Company - For More Info http://www.wizard.ca "LinuxMagic" a Reg. TradeMark of Wizard Tower TechnoServices Ltd. ------------------------------------------------------------------------ 604-682-0300 Beautiful British Columbia, Canada _______________________________________________ dovecot mailing list -- dovecot(a)dovecot.org To unsubscribe send an email to dovecot-leave(a)dovecot.org

6 13

dovecot not listening, but doing passw checks? Was: connection refused, no error anywhere
by Marco Fioretti 22 Jan '25

22 Jan '25

Greetings, I just woke up and went back to try to diagnose the problem I first reported in my other thread, and noticed something weird. After your suggestions, the situation is as follow: 0) FTR, postfix is working, if I open the local mailboxes with mutt running on the server I do see email coming in as expected, from mailing lists and our correspondents 1) output of dovecot -n is below 2) both "ss -tuln | grep 993" and "netstat -tanp" show NO activity /presence on port 993 3) BUT, running "service dovecot status" (see output below, I only changed server and user name) I noticed a failed authentication attempt from SOMEUSER2, happened ~15/20 minutes before I checked, where "SOMEUSER" (without the trailing "2") is an ACTUAL user of the old server, and 200.89.159.59 an IP address I don't know (not my desktop's for sure, and AFAIK no legitimate user is trying to use the server at this time, they know I'm rebuilding it...) Now the question is, OK, that attempt may be some attacker trying to get in, this happens but... HOW is he succeeding to TRY to connect, if dovecot doesn't appear to be listening at all??? And of course, does this help in any way to figure out what is wrong with my configuration? Thanks, Marco ######################################### OUTPUT of dovecot -n (actual domain name changed to example.com) # 2.3.21 (47349e2482): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.21 (f6cd4b8e) doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -Pn > dovecot-new.conf doveconf: Warning: Obsolete setting in /etc/dovecot/conf.d/10-ssl.conf:9: ssl_dh_parameters_length is no longer needed # OS: Linux 6.8.0-51-generic x86_64 Ubuntu 24.04.1 LTS ext4 # Hostname: nexaima auth_debug = yes auth_verbose = yes auth_verbose_passwords = plain mail_debug = yes mail_location = maildir:/var/mail/mymail_storage/base/ mbox_write_locks = fcntl passdb { args = /etc/imap.v_users driver = passwd-file } passdb { driver = pam } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } } ssl_cert = </etc/letsencrypt/live/example.com/fullchain.pem ssl_cipher_list = ALL ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = /etc/imap.v_users driver = passwd-file } userdb { driver = passwd } verbose_ssl = yes ###################################################### FULL OUTPUT OF "service dovecot status": root@example:/# service dovecot status ● dovecot.service - Dovecot IMAP/POP3 email server Loaded: loaded (/usr/lib/systemd/system/dovecot.service; enabled; preset: enabled) Active: active (running) since Tue 2025-01-21 23:41:45 UTC; 5h 24min ago Docs: man:dovecot(1) https://doc.dovecot.org/ Main PID: 35241 (dovecot) Status: "v2.3.21 (47349e2482) running" Tasks: 5 (limit: 4543) Memory: 3.6M (peak: 5.5M) CPU: 503ms CGroup: /system.slice/dovecot.service ├─35241 /usr/sbin/dovecot -F ├─35242 dovecot/anvil ├─35243 dovecot/log ├─35246 dovecot/config └─35323 dovecot/stats Jan 22 04:49:06 example dovecot[35243]: auth-worker(37492): Debug: conn unix:auth-worker (pid=37491,uid=111): auth-worker<2>: pam(SOMEUSER2,200.89.159.59): #1/1 style=1 > Jan 22 04:49:06 example auth[37492]: pam_unix(dovecot:auth): check pass; user unknown Jan 22 04:49:06 example auth[37492]: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot ruser=SOMEUSER2 rhost=200.89.159.59 Jan 22 04:49:08 example dovecot[35243]: auth-worker(37492): conn unix:auth-worker (pid=37491,uid=111): auth-worker<2>: pam(SOMEUSER2,200.89.159.59): pam_authenticate() f> Jan 22 04:49:08 example dovecot[35243]: auth-worker(37492): Debug: conn unix:auth-worker (pid=37491,uid=111): auth-worker<2>: pam(SOMEUSER2,200.89.159.59): Finished pass> Jan 22 04:49:08 example dovecot[35243]: auth-worker(37492): Debug: conn unix:auth-worker (pid=37491,uid=111): auth-worker<2>: Finished: password_mismatch Jan 22 04:49:08 example dovecot[35243]: auth: Debug: pam(SOMEUSER2,200.89.159.59): Finished passdb lookup Jan 22 04:49:08 example dovecot[35243]: auth: Debug: auth(SOMEUSER2,200.89.159.59): Auth request finished Jan 22 04:49:10 example dovecot[35243]: auth: Debug: client passdb out: FAIL 2 user=SOMEUSER2 Jan 22 04:50:06 example dovecot[35243]: auth-worker(37492): Debug: conn unix:auth-worker (pid=37491,uid=111): Disconnected: Connection closed (fd=-1) lines 1-27/27 (END)

3 5

Fwd: [OFFLIST] Re: connection refused, no error anywhere
by Marco Fioretti 22 Jan '25

22 Jan '25

---------- Forwarded message --------- Da: Marco Fioretti <marco.fioretti(a)gmail.com> Date: mar 21 gen 2025 alle ore 19:33 Subject: Re: [OFFLIST] Re: connection refused, no error anywhere To: Michael Peddemors <michael(a)linuxmagic.com> Hi Michel, I cannot say which NGO it is. What I know is that everything with that configuration was working fine, as far as they know, on the old server. So, any help to change the configuration to make it work with the current version of dovecot on Ubuntu 24.04LTS is very welcome... Il giorno mar 21 gen 2025 alle ore 19:11 Michael Peddemors < michael(a)linuxmagic.com> ha scritto: > Which NGO? > > Don't listen on port 143 any more, make sure to only listen on > 587/465/993/995 with TLS/SSL.. > > NGO's are often targeted.. > > > > On 2025-01-21 09:50, Marco Fioretti via dovecot wrote: > > Greetings, > > > > I was just tasked with rebuilding from scratch the mail server of an NGO, > > on a brand new Ubuntu 24.04 LTS VPS. > > > > I have copied the whole dovecot configuration to the new server, and now > am > > stuck because: > > > > - dovecot IS running, dovecot service status shows no errors, but: > > > > - if I try to connect with mutt from my desktop I get "connection > refused" > > > > - the ufw firewall does allow imap/imaps connections, and there are no > > errors in its log > > > > - even "telnet localhost 143" fails: > > Trying ::1... > > Connection failed: Connection refused > > Trying 127.0.0.1... > > telnet: Unable to connect to remote host: Connection refused > > > > - I see no related errors in /var/log/mail.log or /var/log/syslog. > > > > > > output of dovecot -n is pasted below, I only changed the actual domain > name > > to "example.com" > > > > TIA for any pointer, I really need to get this server back online as soon > > as possible... > > > > Marco > > > > # 2.3.21 (47349e2482): /etc/dovecot/dovecot.conf > > # Pigeonhole version 0.5.21 (f6cd4b8e) > > doveconf: Warning: NOTE: You can get a new clean config file with: > doveconf > > -Pn > dovecot-new.conf > > doveconf: Warning: Obsolete setting in /etc/dovecot/conf.d/10-ssl.conf:9: > > ssl_dh_parameters_length is no longer needed > > # OS: Linux 6.8.0-51-generic x86_64 Ubuntu 24.04.1 LTS ext4 > > # Hostname: example.com > > auth_debug = yes > > auth_verbose = yes > > auth_verbose_passwords = plain > > mail_location = maildir:/var/mail/mymail_storage/base/ > > mbox_write_locks = fcntl > > passdb { > > args = /etc/imap.v_users > > driver = passwd-file > > } > > passdb { > > driver = pam > > } > > service auth { > > unix_listener /var/spool/postfix/private/auth { > > group = postfix > > mode = 0660 > > user = postfix > > } > > } > > service imap-login { > > inet_listener imap { > > port = 0 > > } > > } > > ssl_cert = </etc/letsencrypt/live/example.com/fullchain.pem > > ssl_cipher_list = ALL > > ssl_key = # hidden, use -P to show it > > ssl_prefer_server_ciphers = yes > > userdb { > > args = /etc/imap.v_users > > driver = passwd-file > > } > > userdb { > > driver = passwd > > } > > verbose_ssl = yes > > _______________________________________________ > > dovecot mailing list -- dovecot(a)dovecot.org > > To unsubscribe send an email to dovecot-leave(a)dovecot.org > > > -- > "Catch the Magic of Linux..." > ------------------------------------------------------------------------ > Michael Peddemors, President/CEO LinuxMagic Inc. > Visit us at http://www.linuxmagic.com @linuxmagic > A Wizard IT Company - For More Info http://www.wizard.ca > "LinuxMagic" a Reg. TradeMark of Wizard Tower TechnoServices Ltd. > ------------------------------------------------------------------------ > 604-682-0300 Beautiful British Columbia, Canada > >

1 0

Fwd: connection refused, no error anywhere
by Marco Fioretti 22 Jan '25

22 Jan '25

Hi Nick, honestly, I don't know why that port was set to 0, I just inherited the whole server... however, even changing that number to 143 and restarting dovecot makes no difference in the output of netstat I just pasted in another reply.... Il giorno mar 21 gen 2025 alle ore 19:00 Nick Howitt via dovecot < dovecot(a)dovecot.org> ha scritto: > Any reason why the imap-listener port is set to 0 and not 143 or > commented out? > > Have you checked if dovecot is listening on 143? > > > On 21/01/2025 17:50, Marco Fioretti via dovecot wrote: > > Greetings, > > > > I was just tasked with rebuilding from scratch the mail server of an NGO, > > on a brand new Ubuntu 24.04 LTS VPS. > > > > I have copied the whole dovecot configuration to the new server, and now > am > > stuck because: > > > > - dovecot IS running, dovecot service status shows no errors, but: > > > > - if I try to connect with mutt from my desktop I get "connection > refused" > > > > - the ufw firewall does allow imap/imaps connections, and there are no > > errors in its log > > > > - even "telnet localhost 143" fails: > > Trying ::1... > > Connection failed: Connection refused > > Trying 127.0.0.1... > > telnet: Unable to connect to remote host: Connection refused > > > > - I see no related errors in /var/log/mail.log or /var/log/syslog. > > > > > > output of dovecot -n is pasted below, I only changed the actual domain > name > > to "example.com" > > > > TIA for any pointer, I really need to get this server back online as soon > > as possible... > > > > Marco > > > > # 2.3.21 (47349e2482): /etc/dovecot/dovecot.conf > > # Pigeonhole version 0.5.21 (f6cd4b8e) > > doveconf: Warning: NOTE: You can get a new clean config file with: > doveconf > > -Pn > dovecot-new.conf > > doveconf: Warning: Obsolete setting in /etc/dovecot/conf.d/10-ssl.conf:9: > > ssl_dh_parameters_length is no longer needed > > # OS: Linux 6.8.0-51-generic x86_64 Ubuntu 24.04.1 LTS ext4 > > # Hostname: example.com > > auth_debug = yes > > auth_verbose = yes > > auth_verbose_passwords = plain > > mail_location = maildir:/var/mail/mymail_storage/base/ > > mbox_write_locks = fcntl > > passdb { > > args = /etc/imap.v_users > > driver = passwd-file > > } > > passdb { > > driver = pam > > } > > service auth { > > unix_listener /var/spool/postfix/private/auth { > > group = postfix > > mode = 0660 > > user = postfix > > } > > } > > service imap-login { > > inet_listener imap { > > port = 0 > > } > > } > > ssl_cert = </etc/letsencrypt/live/example.com/fullchain.pem > > ssl_cipher_list = ALL > > ssl_key = # hidden, use -P to show it > > ssl_prefer_server_ciphers = yes > > userdb { > > args = /etc/imap.v_users > > driver = passwd-file > > } > > userdb { > > driver = passwd > > } > > verbose_ssl = yes > > _______________________________________________ > > dovecot mailing list --dovecot(a)dovecot.org > > To unsubscribe send an email todovecot-leave(a)dovecot.org > _______________________________________________ > dovecot mailing list -- dovecot(a)dovecot.org > To unsubscribe send an email to dovecot-leave(a)dovecot.org >

1 0

Fwd: connection refused, no error anywhere
by Marco Fioretti 22 Jan '25

22 Jan '25

---------- Forwarded message --------- Da: Marco Fioretti <marco.fioretti(a)gmail.com> Date: mar 21 gen 2025 alle ore 19:27 Subject: Re: connection refused, no error anywhere To: Marc <Marc(a)f1-outsourcing.eu> Hi Marc, this is the output of netstat -tanp (I only removed the line showing the details of my ssh connection): Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 516/systemd-resolve tcp 0 0 127.0.0.54:53 0.0.0.0:* LISTEN 516/systemd-resolve tcp 0 0 127.0.0.1:10023 0.0.0.0:* LISTEN 28575/postgrey --in tcp6 0 0 :::80 :::* LISTEN 26990/apache2 tcp6 0 0 ::1:10023 :::* LISTEN 28575/postgrey --in and indeed it there is no tracce of dovecot there, but what should I do then? "service dovecot status" says the service IS active... Thanks! Il giorno mar 21 gen 2025 alle ore 19:00 Marc <Marc(a)f1-outsourcing.eu> ha scritto: > You are sure dovecot is running on the ports (netstat -tanp). You are sure > this firewall is ok? Maybe flush it, just to be sure. > > > Greetings, > > > > I was just tasked with rebuilding from scratch the mail server of an > > NGO, > > on a brand new Ubuntu 24.04 LTS VPS. > > > > I have copied the whole dovecot configuration to the new server, and now > > am > > stuck because: > > > > - dovecot IS running, dovecot service status shows no errors, but: > > > > - if I try to connect with mutt from my desktop I get "connection > > refused" > > > > - the ufw firewall does allow imap/imaps connections, and there are no > > errors in its log > > > > - even "telnet localhost 143" fails: > > Trying ::1... > > Connection failed: Connection refused > > Trying 127.0.0.1... > > telnet: Unable to connect to remote host: Connection refused > > > > - I see no related errors in /var/log/mail.log or /var/log/syslog. > > > > > > output of dovecot -n is pasted below, I only changed the actual domain > > name > > to "example.com" > > > > TIA for any pointer, I really need to get this server back online as > > soon > > as possible... > > > > Marco > > > > # 2.3.21 (47349e2482): /etc/dovecot/dovecot.conf > > # Pigeonhole version 0.5.21 (f6cd4b8e) > > doveconf: Warning: NOTE: You can get a new clean config file with: > > doveconf > > -Pn > dovecot-new.conf > > doveconf: Warning: Obsolete setting in /etc/dovecot/conf.d/10- > > ssl.conf:9: > > ssl_dh_parameters_length is no longer needed > > # OS: Linux 6.8.0-51-generic x86_64 Ubuntu 24.04.1 LTS ext4 > > # Hostname: example.com > > auth_debug = yes > > auth_verbose = yes > > auth_verbose_passwords = plain > > mail_location = maildir:/var/mail/mymail_storage/base/ > > mbox_write_locks = fcntl > > passdb { > > args = /etc/imap.v_users > > driver = passwd-file > > } > > passdb { > > driver = pam > > } > > service auth { > > unix_listener /var/spool/postfix/private/auth { > > group = postfix > > mode = 0660 > > user = postfix > > } > > } > > service imap-login { > > inet_listener imap { > > port = 0 > > } > > } > > ssl_cert = </etc/letsencrypt/live/example.com/fullchain.pem > > ssl_cipher_list = ALL > > ssl_key = # hidden, use -P to show it > > ssl_prefer_server_ciphers = yes > > userdb { > > args = /etc/imap.v_users > > driver = passwd-file > > } > > userdb { > > driver = passwd > > } > > verbose_ssl = yes >

1 0

connection refused, no error anywhere
by Marco Fioretti 21 Jan '25

21 Jan '25

Greetings, I was just tasked with rebuilding from scratch the mail server of an NGO, on a brand new Ubuntu 24.04 LTS VPS. I have copied the whole dovecot configuration to the new server, and now am stuck because: - dovecot IS running, dovecot service status shows no errors, but: - if I try to connect with mutt from my desktop I get "connection refused" - the ufw firewall does allow imap/imaps connections, and there are no errors in its log - even "telnet localhost 143" fails: Trying ::1... Connection failed: Connection refused Trying 127.0.0.1... telnet: Unable to connect to remote host: Connection refused - I see no related errors in /var/log/mail.log or /var/log/syslog. output of dovecot -n is pasted below, I only changed the actual domain name to "example.com" TIA for any pointer, I really need to get this server back online as soon as possible... Marco # 2.3.21 (47349e2482): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.21 (f6cd4b8e) doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -Pn > dovecot-new.conf doveconf: Warning: Obsolete setting in /etc/dovecot/conf.d/10-ssl.conf:9: ssl_dh_parameters_length is no longer needed # OS: Linux 6.8.0-51-generic x86_64 Ubuntu 24.04.1 LTS ext4 # Hostname: example.com auth_debug = yes auth_verbose = yes auth_verbose_passwords = plain mail_location = maildir:/var/mail/mymail_storage/base/ mbox_write_locks = fcntl passdb { args = /etc/imap.v_users driver = passwd-file } passdb { driver = pam } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imap { port = 0 } } ssl_cert = </etc/letsencrypt/live/example.com/fullchain.pem ssl_cipher_list = ALL ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = /etc/imap.v_users driver = passwd-file } userdb { driver = passwd } verbose_ssl = yes

3 2

Mail with single \r, partial fetch, error "Broken virtual size in mailbox"
by Ewald Dieterich 17 Jan '25

17 Jan '25

I run Dovecot 2.3.21 with the mdbox mailbox format. If I do a certain partial fetch on a mail with a single carriage return \r Dovecot closes the connection and logs the following error: Error: Mailbox INBOX: Deleting corrupted cache record uid=1: UID 1: Broken virtual size in mailbox INBOX: read(/var/spool/dovecot/user/storage/m.1): FETCH BODY[]<18.100> got too little data: 5 vs 6 This happens every time, doveadm force-resync doesn't help. Here's how to reproduce the issue: Deliver a mail with a single carriage return \r (here after the header/body separator, but that's not important): echo -ne "Subject: Test\r\n\r\n\rBody\r\n" | doveadm save -u user Then do a partial fetch from a specific offset: . fetch 1 body[]<18.100> * 1 FETCH (BODY[]<18> {6} ody Connection closed by foreign host. Offset 18 with length 6 should "Body\r\n", that's why the response is 1 byte short ("got too little data: 5 vs 6" in the error message), by why is \r causing this? Other offsets seem to work.

4 5

find mailbox (path) of message
by Marc 13 Jan '25

13 Jan '25

How should I use 'doveadm search -u' to get the mailbox path where the message is stored?

4 4

Bug report on attachment search in dovecot fts plugin
by h.murakami＠lab8.co.jp 10 Jan '25

10 Jan '25

Hi. I am using dovecot's fts plugin and have found a bug-like behavior. I have confirmed that dovecot by itself with fts plugin disabled works fine. dovecot --version 2.3.19.1 (9b53102964) The pattern we found is as follows 1. search with `with attachments` condition from RoundCube linked to dovecot 2. dovecot fts plugin executes the following query to solr but no document is found hdr:application%5c%2f+OR+hdr:multipart%5c%2fm+OR+hdr:multipart%5c%2fsigned+OR+hdr:multipart%5c%2freport 3. roundcube search results also show no items found That's all I have to report. If there is any way to improve the situation, we would like to receive it.

3 2

Re: Problem email client iPhone ios18.2
by Michael Slusarz 09 Jan '25

09 Jan '25

> On 01/08/2025 11:06 AM MST Len Padilla via dovecot <dovecot(a)dovecot.org> wrote: > > Details: > https://github.com/st3fan/dovecot-xaps-daemon > https://github.com/st3fan/dovecot-xaps-plugin Discussion of Apple Push Notifications is kind of irrelevant, since Apple doesn't support this anymore (more accurately: it has been deprecated, and existing users will eventually lose the functionality). See, e.g., https://blog.mxroute.com/important-update-regarding-ios-push-notifications/ michael

2 2

repo.dovecot.org status
by Jasper Spaans 06 Jan '25

06 Jan '25

Hello list, We're using the packages from repo.dovecot.org to run the latest version of dovecot on our systems running ubuntu focal (20.04). We'd like to upgrade these to a more recent ubuntu version[1], but those builds are not available on repo.dovecot.org. Is that repo still supported? If so, what would it take to get builds for ubuntu 22.04 and/or 24.04 on there? I can spend some time on that, but I also have the impression that the build infra (including the scripts) that generate the packages for this repo is not very public. Cheers, Jasper [1] for reasons that are out of scope for this message, using a dockerized build or upgrading to 24.04 (which does come with 2.3.21) is not an option at this moment, so we are currently looking at 22.04. unfortunately that also comes with a dovecot from 2022

2 1

SCRAM-SHA -PLUS variants and Dovecot (Channel Binding)
by * Neustradamus * 04 Jan '25

04 Jan '25

Dear all, In first, I wish you a Happy New Year 2025! In the past, I have requested SCRAM support in Dovecot, etc. I would like to know the situation with -PLUS variants (Channel Binding)? This feature for more security is always missing. RFC 9266: Channel Bindings for TLS 1.3: - https://datatracker.ietf.org/doc/html/rfc9266 Little details, to know easily: - tls-unique for TLS =< 1.2 - tls-server-end-point - tls-exporter for TLS = 1.3 Can you add tls-unique, tls-server-end-point and tls-exporter to be perfect? Stephan Bosch has started but no news since one year: - https://github.com/dovecot/core/compare/main...stephanbosch:dovecot-core:sa… Other links: SASL2 I-D: Extensible Simple Authentication and Security Layer (SASL): - https://datatracker.ietf.org/doc/html/draft-melnikov-sasl2 It is in several XEPs too: - XEP-0388: Extensible SASL Profile: https://xmpp.org/extensions/xep-0388.html - XEP-0440: SASL Channel-Binding Type Capability: https://xmpp.org/extensions/xep-0440.html - XEP-0474: SASL SCRAM Downgrade Protection: https://xmpp.org/extensions/xep-0474.html - XEP-0480: SASL Upgrade Tasks: https://xmpp.org/extensions/xep-0480.html Thanks in advance. Regards, Neustradamus

1 0

Possible SSL Related Issue
by bcs＠nanomail.net 02 Jan '25

02 Jan '25

Need some help in resolving the issue described below and would greatly appreciate any assistance. Please let me know if any additional information is required. Thank you. Updated Postfix with signed certificates from self signed and am experiencing several new log entries that I am unable to identify. See history that follows. * Self signed certificate in Postfix with pop3. Has worked this way since original install. Dec 29 00:12:41 mail dovecot: pop3-login: Login: user=<usr1>, method=PLAIN, rip=209.197.77.67, lip=10.0.1.211, mpid=15448, TLS, session=<CuXLvmEqzM/RxU1D> Dec 29 00:12:41 mail dovecot: pop3(usr1): Disconnected: Logged out top=0/0, retr=0/0, del=0/2825, size=204691614 * Updated log entry for signed certificate in Postfix. Original self signed certificate still used in Dovecot. Note new disconnect record with information such as <136791><t3CWAKwqpieu9RkM> before the Disconnected message. Unable to find anything about these codes. Jan 1 16:48:12 mail dovecot: pop3-login: Login: user=<usr1>, method=PLAIN, rip=174.245.25.12, lip=10.0.1.211, mpid=136791, TLS, session=<t3CWAKwqpieu9RkM> Jan 1 16:48:13 mail dovecot: pop3(usr1)<136791><t3CWAKwqpieu9RkM>: Disconnected: Logged out top=0/0, retr=0/0, del=0/2867, size=206803370 * Self signed certificate in Postfix with imap. Dec 29 00:06:30 mail dovecot: imap-login: Login: user=<usr2>, method=PLAIN, rip=10.0.1.101, lip=10.0.1.211, mpid=15104, TLS, session=<bZezqGEqBMMKAAFl> Dec 29 00:06:31 mail dovecot: imap(usr2): Connection closed (SELECT finished 0.177 secs ago) in=102 out=952 * Updated non self signed certificate in Postfix. Original self signed certificate still used in Dovecot. Similar information before Disconnect message. Jan 1 16:55:00 mail dovecot: imap-login: Login: user=<usr2>, method=PLAIN, rip=10.0.1.4, lip=10.0.1.211, mpid=136855, TLS, session=<Z/7hGKwqntEKAAEE> Jan 1 16:55:00 mail dovecot: imap(usr2)<136855><Z/7hGKwqntEKAAEE>: Connection closed (SELECT finished 0.117 secs ago) in=106 out=1012 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 Issue persists and appears worse when attempting to access the mail server with the Rainloop web application. Rainloop log messages before signed certificate update appeared as the following: Dec 29 07:09:17 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=20215, TLS, session=<xTGtkGcqKNgKAAHT> Dec 29 07:09:17 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=20216, TLS, session=<azKtkGcqMtgKAAHT> Dec 29 07:09:17 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=20217, TLS, session=<Qz2tkGcqOtgKAAHT> Dec 29 07:09:17 mail dovecot: imap(usr): Logged out in=211 out=2047 Dec 29 07:09:17 mail dovecot: imap(usr): Logged out in=28 out=787 Dec 29 07:09:17 mail dovecot: imap(usr): Logged out in=80 out=1449 Dec 29 07:09:17 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=20218, TLS, session=<0EetkGcqRNgKAAHT> Dec 29 07:09:17 mail dovecot: imap(usr): Logged out in=350 out=1381 Dec 29 07:09:17 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=20220, TLS, session=<U8+vkGcqVNgKAAHT> Dec 29 07:09:17 mail dovecot: imap(usr): Logged out in=713 out=66680 Dec 29 07:09:24 mail dovecot: imap(usr): Connection closed (SELECT finished 0.176 secs ago) in=110 out=970 But now contain the same type of <141032><n0r2ZbAqLLMKAAHT> entries before Logged out and seems to be completing significantly more logins and logouts. Note the web interface is working. Jan 1 22:02:53 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141032, TLS, session=<n0r2ZbAqLLMKAAHT> Jan 1 22:02:53 mail dovecot: imap(usr)<141032><n0r2ZbAqLLMKAAHT>: Logged out in=11 out=457 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 Jan 1 22:02:53 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141034, TLS, session=<4OP7ZbAqOLMKAAHT> Jan 1 22:02:53 mail dovecot: imap(usr)<141034><4OP7ZbAqOLMKAAHT>: Logged out in=80 out=1470 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 Jan 1 22:02:54 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141038, TLS, session=<Grz9ZbAqSLMKAAHT> Jan 1 22:02:54 mail dovecot: imap(usr)<141038><Grz9ZbAqSLMKAAHT>: Logged out in=342 out=1473 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 Jan 1 22:02:54 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141039, TLS, session=<+Mf9ZbAqVLMKAAHT> Jan 1 22:02:54 mail dovecot: imap(usr)<141039><+Mf9ZbAqVLMKAAHT>: Logged out in=693 out=37481 deleted=0 expunged=0 trashed=0 hdr_count=20 hdr_bytes=20978 body_count=0 body_bytes=0 Jan 1 22:02:59 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141041, TLS, session=<MxRKZrAq6IcKAAHT> Jan 1 22:02:59 mail dovecot: imap(usr)<141041><MxRKZrAq6IcKAAHT>: Logged out in=28 out=881 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 Jan 1 22:03:07 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141043, TLS, session=<SsLKZrAq7ocKAAHT> Jan 1 22:03:07 mail dovecot: imap(usr)<141043><SsLKZrAq7ocKAAHT>: Logged out in=525 out=10554 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=3522 body_count=1 body_bytes=4807 Jan 1 22:03:08 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141045, TLS, session=<b2/bZrAq/IcKAAHT> Jan 1 22:03:08 mail dovecot: imap(usr)<141045><b2/bZrAq/IcKAAHT>: Logged out in=523 out=15895 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=947 body_count=1 body_bytes=13215 Jan 1 22:03:09 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141047, TLS, session=<P3XrZrAqsJYKAAHT> Jan 1 22:03:09 mail dovecot: imap(usr)<141047><P3XrZrAqsJYKAAHT>: Logged out in=523 out=8719 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=779 body_count=1 body_bytes=6300 Jan 1 22:03:10 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141049, TLS, session=<JmD7ZrAqwJYKAAHT> Jan 1 22:03:10 mail dovecot: imap(usr)<141049><JmD7ZrAqwJYKAAHT>: Logged out in=523 out=13125 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=780 body_count=1 body_bytes=10700 Jan 1 22:03:11 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141051, TLS, session=<kkoLZ7Aq0JYKAAHT> Jan 1 22:03:11 mail dovecot: imap(usr)<141051><kkoLZ7Aq0JYKAAHT>: Logged out in=523 out=8022 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=800 body_count=1 body_bytes=5582 Jan 1 22:03:12 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141055, TLS, session=<7ywbZ7Aq4JYKAAHT> Jan 1 22:03:12 mail dovecot: imap(usr)<141055><7ywbZ7Aq4JYKAAHT>: Logged out in=523 out=13955 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=1113 body_count=1 body_bytes=11104 Jan 1 22:03:13 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141057, TLS, session=<JAMrZ7Aq6JYKAAHT> Jan 1 22:03:13 mail dovecot: imap(usr)<141057><JAMrZ7Aq6JYKAAHT>: Logged out in=523 out=14232 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=774 body_count=1 body_bytes=11814 Jan 1 22:03:14 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141059, TLS, session=<lvE6Z7Aq9JYKAAHT> Jan 1 22:03:14 mail dovecot: imap(usr)<141059><lvE6Z7Aq9JYKAAHT>: Logged out in=523 out=6987 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=749 body_count=1 body_bytes=4599 Jan 1 22:03:15 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141061, TLS, session=<6NdKZ7AqBJcKAAHT> Jan 1 22:03:15 mail dovecot: imap(usr)<141061><6NdKZ7AqBJcKAAHT>: Logged out in=523 out=7126 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=812 body_count=1 body_bytes=4676 Jan 1 22:03:16 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141063, TLS, session=<ebpaZ7AqCJcKAAHT> Jan 1 22:03:16 mail dovecot: imap(usr)<141063><ebpaZ7AqCJcKAAHT>: Logged out in=523 out=26116 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=861 body_count=1 body_bytes=23498 Jan 1 22:03:17 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141065, TLS, session=<2aRqZ7AqDJcKAAHT> Jan 1 22:03:17 mail dovecot: imap(usr)<141065><2aRqZ7AqDJcKAAHT>: Logged out in=523 out=8776 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=775 body_count=1 body_bytes=6374 Jan 1 22:03:18 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141067, TLS, session=<b4d6Z7AqAOIKAAHT> Jan 1 22:03:18 mail dovecot: imap(usr)<141067><b4d6Z7AqAOIKAAHT>: Logged out in=523 out=9875 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=749 body_count=1 body_bytes=7498 Jan 1 22:03:20 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141069, TLS, session=<a3GKZ7AqCuIKAAHT> Jan 1 22:03:20 mail dovecot: imap(usr)<141069><a3GKZ7AqCuIKAAHT>: Logged out in=523 out=61311 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=1153 body_count=1 body_bytes=58591 Jan 1 22:03:21 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141071, TLS, session=<AHuaZ7AqDuIKAAHT> Jan 1 22:03:21 mail dovecot: imap(usr)<141071><AHuaZ7AqDuIKAAHT>: Logged out in=523 out=9458 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=1150 body_count=1 body_bytes=6745 Jan 1 22:03:22 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141073, TLS, session=<X2WqZ7AqGuIKAAHT> Jan 1 22:03:22 mail dovecot: imap(usr)<141073><X2WqZ7AqGuIKAAHT>: Logged out in=523 out=11885 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=772 body_count=1 body_bytes=9482 Jan 1 22:03:23 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141075, TLS, session=<eEu6Z7AqKOIKAAHT> Jan 1 22:03:23 mail dovecot: imap(usr)<141075><eEu6Z7AqKOIKAAHT>: Logged out in=523 out=8665 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=777 body_count=1 body_bytes=6326 Jan 1 22:03:24 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141077, TLS, session=</i3KZ7AqOOIKAAHT> Jan 1 22:03:24 mail dovecot: imap(usr)<141077></i3KZ7AqOOIKAAHT>: Logged out in=523 out=42692 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=778 body_count=1 body_bytes=40360 Jan 1 22:03:25 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141079, TLS, session=<NCDaZ7AqOuIKAAHT> Jan 1 22:03:25 mail dovecot: imap(usr)<141079><NCDaZ7AqOuIKAAHT>: Logged out in=523 out=19469 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=1641 body_count=1 body_bytes=16070 Jan 1 22:03:26 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141081, TLS, session=<QAfqZ7AqPuIKAAHT> Jan 1 22:03:26 mail dovecot: imap(usr)<141081><QAfqZ7AqPuIKAAHT>: Logged out in=523 out=9596 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=858 body_count=1 body_bytes=7098 Jan 1 22:03:29 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141083, TLS, session=<AgEYaLAqgLUKAAHT> Jan 1 22:03:29 mail dovecot: imap(usr)<141083><AgEYaLAqgLUKAAHT>: Logged out in=523 out=11342 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=1188 body_count=1 body_bytes=8581 Jan 1 22:10:40 mail dovecot: imap(usr)<141310><rUXLgbAqGq8KAAE8>: Connection closed (SELECT finished 0.074 secs ago) in=101 out=966 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0

2 1

Hard-coded upper limit for sieve_max_redirects ?
by Maciej Polewczynski 02 Jan '25

02 Jan '25

Hello, After upgrading Dovecot from version 2.3.4 to 2.3.19 i noticed errors for some users having sieve redirects. Before upgrade all worked fine. In sieve plugin i have two limits: sieve_max_actions = 500 sieve_max_redirects = 150 If user have up to 100 redirects all works fine but if there are 101 or more none of them works and there is error: dovecot: lmtp(test2.mbox) Error: sieve: msgid=<***l>: redirect action: failed to check for duplicate forward to <101th.email.address> It seams that there is another limit but cant find where. When checked "dovecot -n|grep 100" there was only "default_process_limit". Increasing this changed nothing. Still the same error. File ".dovecot.sieve.log" in user home dir don't have any additional information. There is only: redirect action: failed to check for duplicate forward: internal error occurred: refer to server log for more information. Do you have any ideas how to fix it? -- Best regards, Maciej Polewczyński Do or do not. There is no try.

3 4

Moving all mail from one user to another
by Peter Reinhold 29 Dec '24

29 Dec '24

Hi all I have a user that has changed domain, and I am looking to move all her mail from her old account into her new one, but I am really unsure about how to go about it I would think that I am should use https://doc.dovecot.org/main/core/man/doveadm-move.1.html to do it, but the example supplied and all discussion about that tool I can find online is only about moving a users mail across folders on their account, and not the entire accounts content to another account. Has anyone tried to do something like this? -- Peter Reinhold

3 2

993 SSL 143 No encryption
by Dino Edwards 26 Dec '24

26 Dec '24

Hello, I have a dovecot server that listens on both 143 and 993 using SSL. I'm trying to get the 143 port to be unencrypted while 993 to remain encrypted. Is there any way to accomplish this? Thanks

2 3

vacation auto reply mail line endings CR LF
by tobias.niethammer＠projektb.net 21 Dec '24

21 Dec '24

Hi all, I tried to setup dovecot 2.3.21.1 (d492236fa0) (dovecot-pigeonhole-0.5.21.1) with the sieve vacation function. I'm getting here a bit into trouble. if I sent an e-mail to an receipient dovecot does via dma and the local mailserver an mail reply but the mail does only have the header inside. After a bit research my conclusion is that the reply mail which gets generated has line endings CR LF. I have to remove this manualy and set it to \LF to get the mail correcly transfered. I Setup the sieve rule with roundcube. I tried to manualy change the .dovecot.sieve file endings and comipled with sievec .dovecot.sieve .dovecot.svbin the binary again, with no change in the behavior. I guess i missed somewhere an variable to fix this issue? here the sieve file: #################################################### require ["vacation"];^M # rule:[Urlaub]^M if true^M {^M vacation :addresses "test02(a)projektb-mail.net" :subject "test Urlaub" text:^M test 1 test 2 test 3^M .^M ;^M }^M #################################################### thank you for your Support Tobias

4 5

Sekt
by Michael Grimm 20 Dec '24

20 Dec '24

.

1 1

COPY vs MOVE
by Scott Q. 19 Dec '24

19 Dec '24

Anyone that knows a bit about the dovecot internals. is move in any way faster than copy / set deleted flag / expunge ? Thanks! Scott

1 0

failed: error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown: SSL alert number 46, session=
by Marc 19 Dec '24

19 Dec '24

What is the best way to get rid of this message? I think clients start generating after ssl crt update.

3 8

ACL propagation with acl_defaults_from_inbox
by Francois Lesueur 19 Dec '24

19 Dec '24

Hello, When dovecot is configured with "acl_defaults_from_inbox = yes", ACL propagation when creating folders seems a bit strange to us. The current behavior is : - INBOX has some ACLs defined in its dovecot-acl file - This ACL is the default for subfolders without a dovecot-acl file inside ("acl_defaults_from_inbox = yes") - When creating a folder, a dovecot-acl file is created inside this folder with a copy of the contents of the dovecot-acl from the INBOX The behavior we expected was : - INBOX has some ACLs defined in its dovecot-acl file - This ACL is the default for subfolders without a dovecot-acl file inside - When creating a folder directly under INBOX, a dovecot-acl file should not be created, as the default from INBOX is already enforced. For subfolders, defaults from INBOX should not be propagated either in the dovecot-acl files. Although dovecot-acl files in subfolders allow to have exceptions, most usage of "acl_defaults_from_inbox = yes" is probably to have mailbox-wide ACLs. In the current behavior, when someone removes an ACL from the INBOX, it will still be present in subfolders, which is error-prone in a setup where users expect that their INBOX ACL is enforced throughout their mailbox. I think that avoiding propagating INBOX ACL when creating a new folder in the case where "acl_defaults_from_inbox" is activated would be more intuitive. Am I missing something ? Cheers, Francois

1 0

Recursive doveadm acl add for shared mailbox
by r.barclay＠habmalnefrage.de 17 Dec '24

17 Dec '24

Hello, I have a shared mailbox (e.g. "info(a)example.org") and want to give a new user (e.g. "john.doe(a)example.org") access. I can use: doveadm acl add -u info(a)example.org INBOX user=john.doe(a)example.org create delete expunge insert lookup post read write write-deleted write-seen Unfortunately, the shared mailbox contains several nested folders. And the new user needs to access these, too. So I probably had to use doveadm acl add -u info(a)example.org .INBOX.SubfolderXY user=john.doe(a)example.org create delete expunge insert lookup post read write write-deleted write-seen ... for each and every subfolder. Is there a way to give permissions recursively? INBOX and all (sub-)subfolders? And, by the way, do I have to use doveadm acl recalc -u info(a)example.org OR doveadm acl recalc -u john.doe(a)example.org after that? At the moment I always do both. Thank you! Reg

3 3

Is there anyway for mail logger plugins to log RETR event??
by Chi Min Wang 17 Dec '24

17 Dec '24

Hello Everyone: The dovecot mail_logger_plugins did support delete/undelete/expunge/mailbox_delete/mailbox_rename event log,is it possible to add RETR event log?? Thanks!!

1 0

dovecot configuration question userdb driver
by Stanislav 17 Dec '24

17 Dec '24

Greetings, I have a mail server for a few folks, basically my family. My current Dovecot configuration is the following, which works like a charm: ========== passdb { driver = sql args = /usr/local/etc/dovecot/dovecot-sql.conf.ext } userdb { driver = static args = uid=981 gid=981 home=/var/mail/virtual/%d/%n/home } ========== I've decided to deploy Solr to be able to search faster. Now, when I try to execute "doveadm index -A inbox" I get an error "Error: auth-master: userdb list: User listing returned failure" because I'm using the static userdb. My question is, how do I implement the listing users feature while using "static driver" or a similar approach? I really want to keep using the template "/var/mail/virtual/%d/%n/home" instead of defining a custom path for each user. So I came up with this idea to replace "static" with "sql" driver for "userdb" since there's "iterate_query" I can use to achieve my goal, tho I have to define "user_query", so I can do something like: ======= SELECT '/var/mail/virtual/%d/%n/home' AS maildir, 981 AS uid, 981 AS gid FROM mailbox WHERE username='%u' and active='1'; ======= However, this is a useless waste of resources since I'm not really querying anything, and I'm not even sure if there's template support (e.g., %d/%n) in there. Appreciate any help Best

2 3

Error: Couldn't open INBOX: Permission denied
by dovecot＠crighton.me.uk 15 Dec '24

15 Dec '24

I'm trying to get Dovecot working on Rocky 9.5. In 10-mail.conf I have: mail_privileged_group = mail mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u In /var/spool: drwxr-x---. 3 mail mail 64 Dec 13 16:29 mail In /var/spool/mail: -rw-rw----. 1 peter mail 500 Dec 13 16:29 peter When I try to login using Telnet I get the following in /var/log/maillog: Dec 13 17:03:23 Backup dovecot[690594]: pop3-login: Login: user=<peter>, method=PLAIN, rip=172.21.10.5, lip=172.21.10.5, mpid=690664, secured, session=<8Or5zikp7uCsFQoF> Dec 13 17:03:23 Backup dovecot[690594]: pop3(peter)<690664><>: Error: Couldn't open INBOX: Permission denied Dec 13 17:03:23 Backup dovecot[690594]: pop3(peter)<690664><>: Disconnected: Couldn't open INBOX: Permission denied top=0/0, retr=0/0, del=0/0, size=0 (There is a random data between <> - I've deleted it as I'm not sure if it is sensitive. I'm certain I'm typing the password correctly in Telnet and I think the first of the three lines from the log indicate that I successfully connected. But why do I get Permission denied when Dovecot tries to open the INBOX? As far as I can see I've set them right (as per the permissions pasted above).

5 8

Rebuild uuidlist?
by Gandalf Corvotempesta 14 Dec '24

14 Dec '24

Guys i did a mess. A bad script made by me, changed (a lot) of filenames in the maildir, in example almost all email filenames were changed. I think I have to rebuild the UID <> filename mapping because dovecot is still trying to read the old file that doesn't exists anymore (it has a new name) Any suggestions? I think this would lead to a full-download of all messages client side, right ?

1 0

Mail gone when recreating a folder in a second IMAP session
by Ewald Dieterich 13 Dec '24

13 Dec '24

I'm running Dovecot 2.3.21 with the mdbox mailbox format. I lose mails (with an asterisk, see below) when I'm doing the following in 2 IMAP sessions: Session 1: Create a folder, save a mail and select it: . create folder . append folder {1} . select folder * 1 EXISTS * OK [UIDVALIDITY 1734013510] UIDs valid Session 2: Delete the folder, create it again, save a mail in it, check the number of messages and the uidvalidity:. . delete folder . create folder . append folder {1} . status folder (messages uidvalidity) * STATUS folder (MESSAGES 1 UIDVALIDITY 1734013511) Everything is as expected until here, the uidvalidity was increased by 1, which makes sense. Session 1: Just do a noop . noop * BYE IMAP session state is inconsistent, please relogin. Dovecot notices that something is wrong and closes the connection. This error is logged: Error: Mailbox folder: Corrupted transaction log file /var/spool/dovecot/user/mailboxes/folder/dbox-Mails/dovecot.index.log seq 2: indexid changed: 1734011270 -> 1734011403 (sync_offset=0) Session 2: Check the folder again: . status folder (messages uidvalidity) * STATUS folder (MESSAGES 0 UIDVALIDITY 1734013512) The mail is gone, uidvalidity was again increased by 1, so this is a new folder. I think the problem is that the folder's transaction log is deleted in session 1 in mail_transaction_log_file_open() when Dovecot notices discrepancies in what it expects: if (ret == 0) { /* corrupted */ if (index->readonly) { /* don't delete */ } else { i_unlink_if_exists(file->filepath); } *reason_r = "File is corrupted"; return 0; } This basically recreates the folder, so now it's empty. Here's the asterisk: I know that technically the mail isn't lost because it's still in the storage file and can be recovered. But it's still ugly. And when I copy a mail from another folder instead of appending it, I can't recover it for the folder because the information that the mail was copied is definitely lost. Can this be fixed in Dovecot?

3 4

sieve enotify mixes message body and subject
by Cajus Korn 12 Dec '24

12 Dec '24

Dear Community, I found that the following lines of a sieve filter require ["enotify"]; # rule:[enotify] if true { notify :importance "2" :message "New Message received." "mailto:xyz@somedomain.com"; } results in getting the following reply: [...] X-Sieve: Pigeonhole Sieve 0.5.21.1 (49005e73) Message-ID: <dovecot-sieve-1733953974-73072-0(a)ironman.cajus.name> Date: Wed, 11 Dec 2024 22:52:54 +0100 Subject: New Message received. From: Postmaster <postmaster(a)ironman.cajus.name> To: xyz(a)somedomain.com Auto-Submitted: auto-notified; owner-email="contacta(a)ironman.cajus.name" Precedence: bulk X-Priority: 3 (Normal) Importance: Normal MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Notification of new message. Shouldn't the message "New Message received." be in the mail body and "Notification of new message." be in the subject? So body and subject got mixed up. Until now I do not know how to debug this further. Any ideas? kind regards Cajus

1 0