- dovecot - dovecot.org

Re: Assistance with doveadm backup...
by SH Development 21 Feb '19

21 Feb '19

Sorry for being such a newbie when it comes to scripting. Created a directory for the backups on the network mounted volume. Changed the appropriate path and am getting this: dsync(root): Error: user nfsnobody: Initialization failed: Namespace 'INBOX.': mkdir(/mnt/maelstrombackups/vmailbackup/nfsnobody) failed: Permission denied (euid=5000(vmail) egid=5000(vmail) missing +w perm: /mnt/maelstrombackups/vmailbackup, euid is not dir owner) dsync(root): Fatal: User init failed Backup done for user: nfsnobody ... dsync(root): Error: user vmail: Initialization failed: Namespace 'INBOX.': mkdir(/mnt/maelstrombackups/vmailbackup/vmail) failed: Permission denied (euid=5000(vmail) egid=5000(vmail) missing +w perm: /mnt/maelstrombackups/vmailbackup, euid is not dir owner) dsync(root): Fatal: User init failed Backup done for user: vmail … After running the script, I suddenly have two new directories in my vmail folder, “nfsnobody” and “vmail”. What are these users? Jeff > On Feb 20, 2019, at 10:32 PM, Kenren Taisho <toushin.taishi(a)gmail.com> wrote: > > No worries, that simple script should get you to a start though. Just replace the path with a mounted NFS share if you want it to reside in a network volume. > > On Thu, Feb 21, 2019 at 12:10 PM SH Development <listaccount(a)starionline.com> wrote: > My apologies, you are absolutely right. Will post this in the correct forum. > > Spent the last couple of hours poring through the postfix list and just forgot where I was at. > > Jeff > > > >> On Feb 20, 2019, at 8:55 PM, Kenren Taisho <toushin.taishi(a)gmail.com> wrote: >> >> Hi Jeff, >> >> This should be better off to dovecot's mailing list. >> But just to get you started, this is the first thing that came to mind: >> >> example: >> >> for users in `doveadm user "*"`; do >> LOCALPART=${users%%@*} >> dsync -v -f -u $users backup maildir:/tmp/backup/$LOCALPART >> echo "Backup done for user: $users ..." >> done >> >> HTH >> >> >> On Thu, Feb 21, 2019 at 9:55 AM SH Development <listaccount(a)starionline.com> wrote: >> I am having trouble locating examples of how to use doveadm backup. All the examples I see are for sync. I simply want to create a backup to a network volume of the email server's vmail folders. The goal here is to have a reasonably current backup should the main drive on the email server go south. >> >> We currently authenticate our users from a mysql database. User’s mailboxes are stored as domainname/username/Maildir >> >> I assume what I will wind up on the network volume is a duplicate directory structure as the vmail folder on the email server? >> >> Can someone help get me started here? >> >> Jeff >

1 0

sieve filter not working
by subin ks 20 Feb '19

20 Feb '19

I've Dovecot and dovecot-sieve v 2.2.27 installed on a Debian 9.6. I'm trying to set a Sieve filter which will redirect all emails from `info` (i.e. .info) TLD to another email. This is the filter: require ["regex"]; # rule:[test] if header :regex "from" "info$" { redirect "subbs(a)domain.com"; } It's not being honored; all emails from .info TLD ends up in the inbox and none are redirected. Let me know what I'm doing wrong. Thanks.

4 6

Error sending email from client
by Latin Bishop 20 Feb '19

20 Feb '19

Latest So if I telnet into port 25 I am able to send an email to my gmail account True it comes into my spam folder But when I try sending via client where my server is I get error 4 6 5 configuration error Also email I send to server are lost ??????? Pleas3 help

3 3

Need to authenticate Outlook and NTLM
by Mark Foley 20 Feb '19

20 Feb '19

I've posted questions on this before, but now I really, really need a solution. Using Dovecot 2.2.33.2 We've been using Dovecot as IMAP server for several years on a Linux host which is also the Active Directory / Domain Controller. We have both Thunderbird and Outlook clients. The Thunderbird clients authenticate w/o problem with AD credentials using Kerberos/GSSAPI. I've never been able to get the Outlook clients to authenticate using domain credentials, so I've also hard-coded user and password into /etc/passwd and let the Dovecot authenticate via PLAIN LOGIN. Now, however, I am mandated to switch all users to Outlook, so I need an AD credential solution. I found https://wiki2.dovecot.org/HowTo/ActiveDirectoryNtlm and followed those instructions. The first problem I ran into was in Step 3 where it said to put the following line in the config: auth_ntlm_use_winbind = yes This gave me an error when I restarted Dovecot: Restarting Dovecotdoveconf: Fatal: Error in configuration file /usr/local/etc/dovecot/conf.d/10-auth.conf line 84: Unknown setting: auth_ntlm_use_winbind googling this error indicated that this was a version 1.x directive and 2.x used only auth_use_winbind. I removed the auth_ntlm_use_winbind and Dovecot restart. If this is true, the wiki should be updated since it purports to be a version 2.x wiki. I followed the rest of the instructions on that wiki and my modified config is: $ doveconf -n # 2.2.33.2 (d6601f4ec): /usr/local/etc/dovecot/dovecot.conf # OS: Linux 4.4.157 x86_64 Slackware 14.2 auth_debug = yes auth_debug_passwords = yes auth_gssapi_hostname = $ALL auth_krb5_keytab = /etc/dovecot/dovecot.keytab auth_mechanisms = plain login gssapi ntlm auth_use_winbind = yes auth_username_format = %n auth_verbose = yes auth_verbose_passwords = plain disable_plaintext_auth = no info_log_path = /var/log/dovecot_info mail_location = maildir:~/Maildir passdb { driver = shadow } protocols = imap ssl_cert = </etc/ssl/certs/OHPRS/GoDaddy/Apache/2016-08-10/54e789087d419b6e.crt ssl_key = # hidden, use -P to show it userdb { driver = passwd } verbose_ssl = yes New additions to my pre-ntlm conf is only the 'ntlm' added the the auth_mechanism and: auth_winbind_helper_path = /usr/bin/ntlm_auth which interestingly doesn't show into the 'doveconf -n' output, above. Is it a default? I then attempted to connect from Outlook and got the error: auth: Info: ntlm(?,192.168.0.58,<qd9nulmB4sLAqAA6>): ntlm_auth reports broken helper: NT_STATUS_UNSUCCESSFUL After more searching I came across this post, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774263 which, in summary, said that ntlm_auth had to run as root. So, I added the following to my dovecot config per that post's suggestion: service auth { user = root } After restarting and trying again to connect from Outlook I got the message: auth: Info: ntlm(?,192.168.0.58,<SCINjFqBKcXAqAA6>): user not authenticated: NT_STATUS_NO_MEMORY At this point I've been unable to find a solution to this error. I've listed the entire dovecot log output for this last attempt to connect from Outlook below. Has anyone in the Universe successfully connected from Outlook using active domain credentials? If so, what's the secret? What am I not doing correctly? Thanks for any and all help! --Mark dovecot log: Feb 07 23:39:40 auth: Debug: Loading modules from directory: /usr/local/lib/dovecot/auth Feb 07 23:39:40 auth: Debug: Module loaded: /usr/local/lib/dovecot/auth/lib20_auth_var_expand_crypt.so Feb 07 23:39:40 auth: Debug: Read auth token secret from /usr/local/var/run/dovecot/auth-token-secret.dat Feb 07 23:39:40 auth: Debug: auth client connected (pid=16357) Feb 07 23:39:40 auth: Debug: client in: AUTH 1 NTLM service=imap session=SCINjFqBKcXAqAA6 lip=192.168.0.2 rip=192.168.0.58 lport=143 rport=50473 Feb 07 23:39:40 auth: Debug: client passdb out: CONT 1 Feb 07 23:39:40 auth: Debug: client in: CONT 1 TlRMTVNTUAABAAAAB4IIogAAAAAAAAAAAAAAAAAAAAAGAbEdAAAADw== (previous base64 data may contain sensitive data) Feb 07 23:39:40 auth: Debug: client passdb out: CONT 1 TlRMTVNTUAACAAAACAAIADgAAAAFgomifTyOI3AwfogAAAAAAAAAAGIAYgBAAAAABgEAAAAAAA9IAFAAUgBTAAIACABIAFAAUgBTAAEACABNAEEASQBMAAQAFABoAHAAcgBzAC4AbABvAGMAYQBsAAMAHgBtAGEAaQBsAC4AaABwAHIAcwAuAGwAbwBjAGEAbAAHAAgAVIrLTWi/1AEAAAAA Feb 07 23:39:40 auth: Debug: client in: CONT 1 TlRMTVNTUAADAAAAGAAYAGwAAAD8APwAhAAAAAAAAABYAAAACAAIAFgAAAAMAAwAYAAAAAAAAACAAQAABYKIogYBsR0AAAAPEulY2h+wL/nnNAXbmMSVx20AYQByAGsAQwBPAE0ATQBPAE4AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA5+rNhVU1odt5650z/pNVpQEBAAAAAAAAVIrLTWi/1AFg5+W08PtmxQAAAAACAAgASABQAFIAUwABAAgATQBBAEkATAAEABQAaABwAHIAcwAuAGwAbwBjAGEAbAADAB4AbQBhAGkAbAAuAGgAcAByAHMALgBsAG8AYwBhAGwABwAIAFSKy01ov9QBBgAEAAIAAAAIADAAMAAAAAAAAAABAAAAACAAAOity40ZG1J9BpqGn4TwBjP02UByQ6D/OUD6DrRDhg+3CgAQAAAAAAAAAAAAAAAAAAAAAAAJABIAaQBtAGEAcAAvAG0AYQBpAGwAAAAAAAAAAAAAAAAA (previous base64 data may contain sensitive data) Feb 07 23:39:40 auth: Info: ntlm(?,192.168.0.58,<SCINjFqBKcXAqAA6>): user not authenticated: NT_STATUS_NO_MEMORY Feb 07 23:39:42 auth: Debug: client passdb out: FAIL 1

3 7

Virtual mailbox shows mails that are too old
by Stefan Hagen 19 Feb '19

19 Feb '19

Hello, I'm using dovecot on my personal / private email server. I have set up virtual mailboxes in my inbox namespace like this: namespace inbox { inbox = yes prefix = "Virtual/" separator = / location = "virtual:~/.emails_virtual:LAYOUT=fs:INDEX=dovecot.virtual.index:LISTINDEX=dovecot.virtual.list.index" list = yes subscriptions = yes mailbox { auto = subscribe } } I had quite some trouble with it at first with UIDs changing all the time, but after adding INDEX and LISTINDEX it started to work just fine. I've created dovecot_virtual files like this one: $ cat ~/.emails_virtual/2-LastDay/dovecot-virtual * -Trash -Sent -Drafts -Spam -Virtual -Virtual/* all younger 86400 After stopping dovecot and deleting the index files and restarting dovecot, the virtual mailbox shows all mail from the last day - as expected. But after one day, it shows mail from two days. After three, it shows mails from three days. It looks like dovecot selects emails from the last day, but never cleans out emails that are older, once they have been selected. My full dovecot -n can be found here: https://codevoid.de/?q=/0/p/dovecot-n.txt Any ideas about what could be wrong? Best Regards, Stefan -- Stefan Hagen | (gopher|https)://codevoid.de(/gpg) CBD3 C468 64B4 6517 E8FB B90F B6BC 2EC5 52BE 43BA

3 2

freebsd log process problem
by Bane Ivosev 19 Feb '19

19 Feb '19

After version 2.2.32 we have an issue that occures randomly a couple times per day, log process gets stuck at 100% CPU usage with message dovecot: log(56027): Warning: Log connection fd 20 listen_fd 20 prefix 'imap: ' is sending input faster than we can write It happens with several Dovecot version after 2.2.32 on FreeBSD 10.4 and 11.2-RELEASE. We tried 2.2.34, 2.3.2, 2.3.4 On the same system version 2.2.32 and earlier works perfectly. Did anyone experience similar problem?

1 0

dovecot/lmtp dumps core when proxying to multiple recipients via protocol=smtp
by Piper Andreas 19 Feb '19

19 Feb '19

Hello, when trying to set up a migration scenario from my old mailbox-servers to my new dovecot-cluster, I get a coredump from dovecot/lmtp when proxying mail-delivery to more than one recipient on the old mailbox-server. My setup: 3 director-hosts (Debian stretch) are proxying to a pair of replicator-hosts and during migration also to the old mailbox-server. For migration the not-migrated user-addresses are included via a passwd-file with entries like: grtest1@hrz.uni-marburg.de:::::::director_tag=hrz protocol=smtp user=grtest1 grtest2@hrz.uni-marburg.de:::::::director_tag=hrz protocol=smtp user=grtest2 ... The director_tag points to the old mailbox-server, with 'protocol=smtp' SMTP is used for delivery, as the old machine is not capable of LMTP. The setup works fine for imap-proxying and for mail-delivery to single recipients. But if a mail is addressed to more than one recipient, lmtp produces a coredump after delivering to all recipients. The error-message in the log is: Feb 14 12:15:05 vhrzxxx dovecot[63861]: lmtp(64663): Connect from 127.0.0.1 Feb 14 12:15:05 vhrzxxx dovecot[63861]: lmtp(64663): 206UIrlNZVyX/AAAGwthQA: Sent message to <grtest2> at 137.248.xxx.yyy:25: 250 2.0.0 x1EBF5Ro016092 Message accepted for delivery (1/2 at 79 ms) Feb 14 12:15:05 vhrzxxx dovecot[63861]: lmtp(64663): 206UIrlNZVyX/AAAGwthQA: Sent message to <grtest2> at 137.248.xxx.yyy:25: 250 2.0.0 x1EBF5Ro016092 Message accepted for delivery (2/2 at 79 ms) Feb 14 12:15:05 vhrzxxx dovecot[63861]: lmtp(64663): Fatal: master: service(lmtp): child 64663 killed with signal 11 (core dumped) The backtrace from the coredump is: Reading symbols from /usr/lib/dovecot/lmtp...(no debugging symbols found)...done. [New LWP 64663] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `dovecot/lmtp'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f347fc7a2c0 in ?? () from /usr/lib/dovecot/libdovecot.so.0 (gdb) bt full #0 0x00007f347fc7a2c0 in ?? () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #1 0x00007f347fc77d73 in smtp_client_command_fail_reply () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #2 0x00007f347fc77fbe in smtp_client_commands_list_fail_reply () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #3 0x00007f347fc7c8dc in smtp_client_connection_disconnect () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #4 0x00007f347fc7cf19 in smtp_client_connection_unref () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #5 0x00007f347fc7e35d in ?? () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #6 0x00007f347fd1f5d5 in io_loop_call_io () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #7 0x00007f347fd20fd9 in io_loop_handler_run_internal () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #8 0x00007f347fd1f6e6 in io_loop_handler_run () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #9 0x00007f347fd1f8f8 in io_loop_run () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #10 0x00007f347fc93d43 in master_service_run () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #11 0x00005613fcbc1f70 in main () No symbol table info available. (gdb) doveconf -n gives: # 2.3.4.1 (3c0b8769e): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 (60b0f48d) # OS: Linux 4.9.0-8-amd64 x86_64 Debian 9.7 # Hostname: vhrzxxx.HRZ.Uni-Marburg.DE auth_cache_negative_ttl = 0 auth_cache_size = 10 M auth_master_user_separator = * auth_worker_max_count = 1024 base_dir = /var/run/dovecot/ default_vsz_limit = 1 G director_mail_servers = 172.25.1.93 172.25.1.95 137.248.xxx.yyy@hrz 137.248.xxx.zzz@staff 137.248.aaa.bbb@students director_servers = 172.25.1.42:9090 172.25.1.41:9090 172.25.1.92:9090 director_username_hash = %Ln@%Ld doveadm_password = # hidden, use -P to show it doveadm_port = 12345 imap_max_line_length = 640 k lmtp_proxy = yes 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 passdb { args = /etc/dovecot.deny deny = yes driver = passwd-file } passdb { args = /etc/dovecot/private/passwd.masterusers driver = passwd-file master = yes } passdb { args = /etc/dovecot/dovecot-ldap.staff.conf.ext driver = ldap result_success = continue-ok } passdb { args = /etc/dovecot/migration/migrate-staff driver = passwd-file name = passdb_staff_query } passdb { args = /etc/dovecot/dovecot-ldap.students.conf.ext driver = ldap result_success = continue-ok } passdb { args = /etc/dovecot/migration/migrate-students driver = passwd-file name = passdb_students_query } passdb { args = /etc/dovecot/dovecot-ldap.hrz.conf.ext driver = ldap result_success = continue-ok } passdb { args = /etc/dovecot/migration/migrate-hrz driver = passwd-file name = passdb_hrz_query } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve } pop3_uidl_format = %08Xv%08Xu postmaster_address = postmaster(a)hrz.uni-marburg.de protocols = imap pop3 lmtp sieve service auth-worker { user = $default_internal_user } service auth { client_limit = 6000 } service director { inet_listener { port = 9090 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service doveadm { inet_listener { port = 12345 } vsz_limit = 768 M } service imap-login { executable = imap-login director process_min_avail = 64 service_count = 0 } service imap { process_limit = 4096 } service lmtp { inet_listener lmtp { port = 24 } } service managesieve-login { executable = managesieve-login director inet_listener sieve { port = 4190 } } service pop3-login { executable = pop3-login director } ssl = required ssl_ca = </etc/ssl/certs/umr-chain.pem ssl_cert = </etc/ssl/certs/vhrzxxx.hrz.uni-marburg.de.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_require_crl = no userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf.ext driver = ldap } protocol lmtp { auth_socket_path = director-userdb } protocol doveadm { auth_socket_path = director-userdb } protocol imap { mail_max_userip_connections = 25 mail_plugins = " zlib imap_zlib" } I would appreciate any help on this. If any more information is needed, please ask. With many thanks and best regards, Andreas -- ________________________________________________________________________ Dr. Andreas Piper, Hochschulrechenzentrum der Philipps-Univ. Marburg Hans-Meerwein-Straße 6, 35032 Marburg, Germany Phone: +49 6421 28-23521 Fax: -26994 E-Mail: piper(a)HRZ.Uni-Marburg.DE

1 1

Migrate mail data from Dovecot to Dovecot
by Odhiambo Washington 19 Feb '19

19 Feb '19

I have built a new server (FreeBSD-12) running dovecot-2.3.4. My old server (FreeBSD-9.3) is running dovecot-2.3.4 as well. The configurations are 1:1 identical. The are about 250 users on this server, all virtual. They are mostly POP3 users, but they do "leave a copy of message on the server" for set various number of days. Now, to migrate the mail data, can I simply rsync the mail directories between the old and the new server? Would that create a pitfall?? What is the recommended method? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

2 2

Error configuring unix_listener stats-writer
by Peter Nabbefeld 18 Feb '19

18 Feb '19

Hello, I've got a very strange problem: When I try to configure the stats-writer socket, I'm told the configuration is a duplicate, though none exists in the configuration files. So I'd guess the configuration is set either built-in or implicitly. I've put the following into conf.d/10-master.conf: service auth { unix_listener auth-userdb { } unix_listener stats-writer { user = vmail group = vmail mode = 0666 } } BTW, using imap for mail traffic. Is there any tool displaying an "effective" config tree (i.e., a tool displaying the resulting configuration from every file, displaying the original file and line number)? "dovecot -a" only displays all configurations, but without source reference, so it's impossible to find out about the details. :-( Kind regards Peter

4 9

Dsync and network issues
by Danilo G. Baio 18 Feb '19

18 Feb '19

Hi. Our scenario: dovecot-2.3.4.1 Two FreeBSD servers, A (master) and B (slave). replication_max_conns = 10 doveadm_port = 60025 All mails are received on server A and replicated to server B. Sometimes we get these messages on server B: Feb 18 08:27:35 dsync-server(XX@XX): Error: client_connection_tcp_free: close((&conn->fd)) @ client-connection-tcp.c:632 failed (fd=15): Connection reset by peer Feb 18 08:28:00 dsync-server(XZ@XZ): Error: client_connection_tcp_free: close((&conn->fd)) @ client-connection-tcp.c:632 failed (fd=15): Connection reset by peer Feb 18 08:33:14 dsync-server(XY@XY): Error: client_connection_tcp_free: close((&conn->fd)) @ client-connection-tcp.c:632 failed (fd=15): Connection reset by peer Feb 18 08:44:07 dsync-server(XW@XW): Error: client_connection_tcp_free: close((&conn->fd)) @ client-connection-tcp.c:632 failed (fd=15): Connection reset by peer It happens sometimes (usually early morning) when users are syncing their mailboxes. Is there a way to debug this and find what is happening? Thanks for your time. -- Danilo G. Baio

1 0