February 2019 - dovecot

dovecot Buch 2014 vs 2016
by Heiko Schlittermann 22 Feb '19

22 Feb '19

Moin, Es geht um das Dovecot-Buch. Ich nehme an, daß hier mindestens einer, der sich auskennt, mitliest: Gibt es - außer der Sprache und dem Preis - einen Unterschied zwischen der ersten (und einzigen?) deutschen Auflage von 2014 und der englischen Auflage von 2016? -- Heiko

3 3

Sieve vnd.dovecot.filter hanging issue
by Scott M. 22 Feb '19

22 Feb '19

I am trying to add a signature to all messages and it should be possible via vnd.dovecot.filter, the problem is that any script I try to filter through just hangs. I am running on FreeBSD 11.2 and I tried with dovecot 2.2.32 & pigeonhole 0.4.19 and with dovecot 2.3.2 && pigeonhole 0.5.2. In both cases, the output from dovecot is the same: Feb 19 18:24:22 mx13 dovecot: lda(user1): Debug: sieve: action filter: running program: append Feb 19 18:24:22 mx13 dovecot: lda(user1): Debug: Mailbox stdin: Opened mail UID=1 because: mail stream Feb 19 18:24:22 mx13 dovecot: lda(user1): Debug: waiting for program `/usr/local/gtech/sieve/append' to finish after 3 msecs Feb 19 18:25:22 mx13 dovecot: lda(user1): Debug: program `/usr/local/gtech/sieve/append'(55055) execution timed out after 60000 milliseconds: sending TERM signal Feb 19 18:25:27 mx13 dovecot: lda(user1): Debug: program `/usr/local/gtech/sieve/append' (55055) did not die after 5000 milliseconds: sending KILL signal at first I tried using my actual script but since it was failing I switched to a simple shell script: #!/bin/sh cat /dev/null echo "hey" exit 0 I got that idea after reading: http://dovecot.2317879.n4.nabble.com/execute-sieve-command-fails-to-notice-… (http://dovecot.2317879.n4.nabble.com/execute-sieve-command-fails-to-notice-…) The result is unfortunately the same. From what I can gather ( ran it inside strace/truss too), dovecot-lda hangs on the output. Is this accurate ? How can I get this to work ?

2 1

Using SHA256/512 for SQL based password
by Robert Moskowitz 21 Feb '19

21 Feb '19

I have trying to find how to set the dovecot-sql.conf for using SHA256/512. I am going to start clean with the stronger format, not migrate from the old MD5. It seems all I need is: driver = mysql connect = host=/var/lib/mysql/mysql.sock dbname=postfix user=postfix password=$Postfix_Database_Password default_pass_scheme = SHAxxx-CRYPT # following should all be on one line. password_query = SELECT username as user, password, concat('/home/vmail/', maildir) as userdb_home, concat('maildir:/home/vmail/', maildir) as userdb_mail, 101 as userdb_uid, 12 as userdb_gid FROM mailbox WHERE username = '%u' AND active = '1' # following should all be on one line user_query = SELECT concat('/home/vmail/', maildir) as home, concat('maildir:/home/vmail/', maildir) as mail, 101 AS uid, 12 AS gid, CONCAT('*:messages=30000:bytes=', quota) as quota_rule FROM mailbox WHERE username = '%u' AND active = '1' where xxx is either 256 or 512. All the rest I have been finding in my searches concern converting the format and are not needed for a clean start? thanks

13 30

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

21 Feb '19

Here is my command: [root@mail maelstrombackups] #mkdir -p vmailbackup [root@mail vmail]# chown: vmail:vmail /mnt/maelstrombackups/vmailbackup [root@mail vmail]# doveadm backup -u jeff maildir:/mnt/maelstrombackups/vmailbackup Only gives me the usage list, doesn’t work. Jeff > On Feb 21, 2019, at 1:29 AM, Sami Ketola <Sami.Ketola(a)Open-Xchange.com> wrote: > > > >> On 21 Feb 2019, at 7.04, SH Development via dovecot <dovecot(a)dovecot.org> wrote: >> >> Not really. The suggestions in the post seemed to be: >> >> 1. Tar the whole directory, which I have tried in the past, but a 130G directory takes over 18 hours to tar. >> 2. It was also suggested to rsync the directory, but the question was brought up, and not answered, about whether it was advisable to copy live mail, thus the need for doveadm sync/backup. >> >> Based on what I’ve read about doveadm backup, this is what I need, I am just having a hard time formulating the syntax for the command. >> > > root@ketola ~]# mkdir -p /backup/sami > root@ketola ~]# chown vmail:vmail /backup/sami > root@ketola ~]# doveadm backup -u sami Maildir:/backup/sami > <snip> > root@ketola ~]# du -hs /backup/sami > 211M /backup/sami > > does this help? > > Sami

1 0

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