- dovecot - dovecot.org

sieve size match with multiple of 4GB not matching (BUG?)
by Matthias Lay 24 Jan '20

24 Jan '20

Hi, I have noticed a strange behaviour when using size matches with GB in sieve. If I use filter that matches mails smaller then 4, or 8GB it does not match in any case. same filter matches with 3,5,6,7 GB example filter: require "vnd.dovecot.debug"; if allof (size :under 4G) { debug_log "MATCH"; } else { debug_log "NO MATCH"; } # sieve-filter -u johnd filter.sieve INBOX >> Filtering message: ID: <5167DFC8.8040207@XXXXXX> Date: Fri, 12 Apr 2013 12:19:52 +0200 Size: 1820898 bytes Subject: Fwd: Multi-media mail demonstration info: DEBUG: NO MATCH. ************************************************************************** same mail with this sieve rule: if allof (size :under 5G) { debug_log "MATCH"; } else { debug_log "NO MATCH"; } # sieve-filter -u johnd filter.sieve INBOX >> Filtering message: ID: <5167DFC8.8040207@XXXXXX> Date: Fri, 12 Apr 2013 12:19:52 +0200 Size: 1820898 bytes Subject: Fwd: Multi-media mail demonstration info: DEBUG: MATCH. same for M. 4096M => NO MATCH 4097M => MATCH Greetz Matze

1 0

Re: Namespace problem? duplicated folders...
by Daniel Miller 24 Jan '20

24 Jan '20

And I should have seen that from your first post but output from "doveconf" is definitive. -- Daniel On 1/23/2020 6:57 PM, Daniel Miller wrote: > Keeping in mind I'm 0% Dovecot certified and 100% certifiable... > > I'm guessing you have your namespace definition separate from your > special-use mailbox declarations. Possibly in 10-mail.conf and > 15-mailboxes.conf? Not that it matters. > > First sugggestion - that first namespace definition. Change it from: > > namespace { > > to > > namespace inbox { > > and see what happens. > > -- > Daniel > > > On 1/23/2020 4:40 PM, Gregory Sloop wrote: >> >> >> *DM> Interesting. >> >> DM> While I don't use mbox (dbox or maildir) I wouldn't think that would >> DM> matter. Your namespace layout looks nearly the same as my own. But to >> DM> verify what's going on - post the output of "doveconf namespace". >> >> DM> Possibly just reviewing that output may tell you enough - otherwise >> DM> share it (fully) here. >> >> DM> -- >> DM> Daniel >> >> *namespace { >> disabled = no >> hidden = no >> ignore_on_failure = no >> inbox = yes >> list = yes >> location = >> order = 0 >> prefix = INBOX/ >> separator = / >> subscriptions = yes >> type = private >> } >> namespace inbox { >> disabled = no >> hidden = no >> ignore_on_failure = no >> inbox = no >> list = yes >> location = >> mailbox Drafts { >> auto = no >> autoexpunge = 0 >> comment = >> driver = >> special_use = \Drafts >> } >> mailbox Junk { >> auto = no >> autoexpunge = 0 >> comment = >> driver = >> special_use = \Junk >> } >> mailbox Sent { >> auto = no >> autoexpunge = 0 >> comment = >> driver = >> special_use = \Sent >> } >> mailbox "Sent Messages" { >> auto = no >> autoexpunge = 0 >> comment = >> driver = >> special_use = \Sent >> } >> mailbox Trash { >> auto = no >> autoexpunge = 0 >> comment = >> driver = >> special_use = \Trash >> } >> order = 0 >> prefix = >> separator = >> subscriptions = yes >> type = private >> } >> > >

1 0

wrong Messages in virtual Folder
by Frank-Ulrich Sommer 24 Jan '20

24 Jan '20

Hello, I created a virtual Folder that should contain all Mails from several different Folders and their subfolders. Recently I added a new folder to the dovecot-virtual file and then found that most Mails from this folder were missing. I always restartet dovecot (is this necessary?) after any change. The system is running Debian Stretch and I am using the supplied dovecot 2.2.7 (see below for output of doveconf -n). To narrow this down I removed all other directories from the dovecot-virtual file and then found that the number of mails is correct, but most mails are the wrong ones from other directories. The dovecot-virtual file currently contains only the source directory and in the last line 4 spaces followed by the keyword "all" and a newline. Mails that where moved there after the directory was added to the virtual folder seemed to be displayed correct. If I move one Mail away from the source diectory a totally different Mail in the virtual Folder disappers. After moving the file back to the source folder it correctly appears in the virtual folder. What might be the cause and how can I fix it? Thanks, Frank Output of "doveconf -n": # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.9.0-11-amd64 x86_64 Debian 9.11 zfs auth_verbose = yes log_path = /var/log/dovecot.log mail_location = maildir:/home/bananamail/Maildir:INDEX=/var/dovecot_indexes/%u mail_plugins = " virtual fts fts_solr" mailbox_list_index = 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 namespace { location = virtual:~/Maildir/virtual prefix = _virtual. separator = . type = private } namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = scheme=CRYPT username_format=%u /etc/dovecot/users driver = passwd-file } plugin { fts = solr fts_autoindex = yes fts_enforced = yes fts_solr = break-imap-search url=http://localhost:8080/solr/ sieve = file:~/sieve;active=~/.dovecot.sieve } postmaster_address = postmaster@localhost protocols = imap service imap-login { inet_listener imaps { port = XXXX ssl = yes } } ssl = required ssl_cert = <XXXXXXXXX/fullchain.pem ssl_cipher_list = ALL:!LOW:!SSLv2:!SSLv3:!EXP:!aNULL ssl_dh_parameters_length = 2048 ssl_key = # hidden, use -P to show it ssl_protocols = !SSLv3 !TLSv1 userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } protocol imap { mail_max_userip_connections = 200 }

1 0

intermittant passdb error
by NeuralNET 23 Jan '20

23 Jan '20

I'm having great difficulty debugging this problem.. I'm having intermittant problems connecting to dovecot. This started a couple of days ago following an apt-get update on the server. I'm running Ubuntu 14.04, dovecot 2.2.9. Here's my dovecot -n --- # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.19.0-59-generic x86_64 Ubuntu 14.04.4 LTS auth_mechanisms = plain login mail_location = maildir:~/Maildir namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } plugin { sieve_dir = ~/sieve } protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } user = $default_internal_user } ssl = required ssl_cert = </etc/dovecot/box.neuralnet.org.uk_crt.pem ssl_key = </etc/dovecot/box.neuralnet.org.uk_key.pem ssl_protocols = !SSLv2 !SSLv3 userdb { driver = passwd } --- Pretty standard stuff. In addition disable_plaintext_auth = yes is set in 10-auth.conf This showed up in the mail.err after the reboot; --- May 17 09:04:51 server dovecot: imap-login: Error: read(anvil) failed: EOF May 17 09:04:51 server dovecot: auth: Error: read(anvil-auth-penalty) failed: EOF May 17 09:04:51 server dovecot: auth: Error: net_connect_unix(anvil-auth-penalty) failed: Permission denied --- At that point The following commands were run on the server a few minutes apart with no changes made in the interim; --- username@box /etc/dovecot $ doveadm user username field valueuserdb lookup: user username doesn't exist username@box /etc/dovecot $ doveadm user username field value uid 1000 gid 1000 home /home/username mail maildir:~/Maildir system_groups_user username --- so, passdb wasn't accessible, but now it is ? Imap logins are showing in mail.log as failing, but thunderbird is currently connected; --- May 18 12:00:58 box dovecot: imap-login: Disconnected (auth failed, 3 attempts in 19 secs): user=<username>, method=PLAIN, rip=10.0.0.3, lip=10.0.0.99, TLS, session=<********> May 18 12:08:27 box dovecot: imap-login: Disconnected (auth failed, 3 attempts in 20 secs): user=<username>, method=PLAIN, rip=10.0.0.3, lip=10.0.0.99, TLS, session=<********> May 18 12:08:50 box dovecot: imap-login: Disconnected (auth failed, 3 attempts in 12 secs): user=<username>, method=PLAIN, rip=10.0.0.3, lip=10.0.0.99, TLS, session=<********> --- do I conclude that method=plain is failing, whereas method=login succeeds ? I tried setting auth_debug_password=yes and get the following; --- May 18 12:26:42 box dovecot: auth: Debug: client in: CONT#0111#011A********== (previous base64 data may contain sensitive data) May 18 12:26:42 box dovecot: auth-worker(12214): Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth May 18 12:26:42 box dovecot: auth-worker(12214): Debug: pam(expert,10.0.0.3): lookup service=dovecot May 18 12:26:42 box dovecot: auth-worker(12214): Debug: pam(expert,10.0.0.3): #1/1 style=1 msg=Password: May 18 12:26:42 box dovecot: auth-worker(12211): pam(username,10.0.0.3): pam_authenticate() failed: Authentication failure (password mismatch?) (given password: ******) May 18 12:26:44 box dovecot: auth: Debug: client passdb out: FAIL#0112#011user=username --- Any assistance debugging this further is greatly recieved! Thanks.

2 2

Bug: Regex doesn't match ungreedy
by Lorenz Steinert 23 Jan '20

23 Jan '20

Hello, first the mandatory dovecot specs: - dovecot 2.3.9.2-1 - Operating system: Archlinux - x84 cpu - ext4 filesystem My problem is that the sieve regex filter doesn't seem to match ungreedely so the regex: ^(Re: |)\\[(.*?)\\/(.*?)\\] evaluates the last capturing group of [matrix-org/synapse] [Don't merge!!] Backport fix for MAU limits to v1.8.0 (#6763) to synapse] [Don't merge!! wich should have been synapse Best Regards Lorenz Steinert

2 1

Is it possible to enable push notifications for iOS/macOS mail clients on a stock dovecot?
by Gerben Wierda 23 Jan '20

23 Jan '20

Now that Apple has abandoned mail server capabilities in macOS Server.app we have to move to an open source solution. I have done this using Macports and it works well (no thanks to Apple as it never published the in 2018 promised migration info for mail services). The MacPorts Apple Push Notification variant based on a patch written a few years ago for dovecot supports APNS but it requires you to export a certificate form your old High Sierra Server.app. With the patch and that certificate, dovecot tells an email client it supports XAPPLEPUSHSERVICE and that makes Apple mail clients think they are talking to macOS Server and they switch to push notifications for updates. Now, that certificate needs to be renewed yearly by Server.app and imported by hand etc. At some point this will stop working (apart from that you need to keep an old macOS Server around to renew) Is there another way to get this working with an open source dovecot, outside of using Apple’s push notification service? Some other standard? Some other service? Probably not, right? G

5 5

Using dsync for a single mailbox?
by Wim Lewis 23 Jan '20

23 Jan '20

Is it possble to use `doveadm sync` to migrate a single mailbox? I'm migrating accounts from another IMAP server,and most of the mailboxes are in mbox or maildir format, but a few are in MBX. As far as I can tell the only recommended way to "convert" an MBX mailbox is to sync it via imap. But dsync fails in inscrutable ways, and the documentation is kind of scant on how to control what it does. Even just an example command line showing how to copy remote mailbox FOO into dovecot mailbox BAR would be extremely helpful.

2 4

Dovecot - Upgrade Solr 7.7.2 to 8.4.1
by Domenico Pastore 23 Jan '20

23 Jan '20

Hello, I have Dovecot configured with Solr for the indexes. I have need your support for upgrade solr 7.7.2 to 8.4.1. Solr 7.7.2 has a security issue CVE-2019-12409. It's possible upgrade of Solr? Dovecot work correctly with Solr 8.x? The Solr documentation recommended after updating: "It is always strongly recommended that you fully reindex your documents after a major version upgrade." There are tips for Dovecot? Br, Domenico

4 4

Re: JMAP support in Dovecot
by Mike Gao 22 Jan '20

22 Jan '20

Hi, Any news for jmap Support in Dovecot? Thanks, Mike

1 0

socket dovecot-lmtp is not created anymore
by ratatouille 22 Jan '20

22 Jan '20

Hello! Since experiments on my testserver two days ago /var/spool/postfix/private/dovecot-lmtp is not created anymore. This the setting in /etc/dovecot/conf.d/10-master.conf service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } I searched nearly the whole system for lmtp but can't find the reason why. What can I do? Debug? Andreas

2 2