- dovecot - dovecot.org

Quota policy service not rejecting messages when user over quota
by james＠lottspot.com 17 Jul '15

17 Jul '15

For some very odd reason, the quota-status service is failing to enforce quotas. Every other aspect of my configuration is working with absolutely no problems. When I attempt delivery via LTMP, the message is, as expected, rejected due to the user's inbox being full. root@smtp:/usr/local/etc/mail-config # nc -U /var/spool/postfix/private/dovecot-lmtp < 220 mx0.lottspot.com Dovecot ready. > LHLO localhost < 250-mx0.lottspot.com < 250-8BITMIME < 250-ENHANCEDSTATUSCODES < 250 PIPELINING > MAIL FROM:<root@localhost> < 250 2.1.0 OK > RCPT TO:<james(a)lottspot.vpn> < 552 5.2.2 <james(a)lottspot.vpn> Quota exceeded (mailbox for user is full) The policy service however, just lets everything go right through. I know that accessing the userdb is not an issue, because I passed a bogus user before passing my real user and received the expected response. root@smtp:/usr/local/etc/mail-config # nc -U /var/spool/postfix/private/policy-quota > recipient=noop(a)fake.tld > < action=551 User not found < > recipient=james(a)lottspot.vpn > < action=250 Quota status success < I'm using Dovecot 2.2.15, and I have included my quota configuration below. If anyone wants to see full doveconf -n output, I can provide it, but figured it was a bit much for this case. Thanks in advance for any pointers! --> Note: I'm the quota_status_* directives have been set as is for testing purposes only. I'm fully aware not to do that in production. plugin { quota = maildir:User quota quota_rule = *:bytes=1G quota_rule2 = Trash:storage=+10%% quota_status_success = "250 Quota status success" quota_status_nouser = "551 User not found" quota_status_overquota = "552 5.2.2 Recipient mailbox is full" } service quota-status { executable = quota-status -p postfix unix_listener /var/spool/postfix/private/policy-quota { user = postfix group = wheel mode = 0666 } }

2 1

[Sieve] Unable to fileinto subfolders
by james＠lottspot.com 17 Jul '15

17 Jul '15

Hello again list! I am configuring a server running Dovecot 2.2.15 (Pigeonhole 0.4.6), and I am having an issue with Sieve scripts where I cannot sort messages into a subfolder of a mailbox. An email which is matched by the following script: require "fileinto"; if header :contains "Subject" "[SORT ME]" { fileinto "INBOX.Sorted"; } Yields the following error: Jul 16 18:54:46 smtp dovecot: lmtp(james(a)lottspot.vpn): Error: DiJmNGZgqFWLFAEANWXNPw: sieve: msgid=<4973528.yvy4Yu8Tt4@arch_project>: failed to store into mailbox 'INBOX.Sorted': Character not allowed in mailbox name: '.' As far as I can tell based on the Sieve usage page in the wiki (http://wiki2.dovecot.org/Pigeonhole/Sieve/Usage) this is *supposed* to work. I have included my namespace configuration below, but if anyone wants the whole doveconf -n, I will gladly provide it. Thanks in advance for any help! namespace inbox { type = private separator = / prefix = inbox = yes mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } } namespace { type = shared separator = / prefix = shared/%%d/%%n/ location = maildir:/home/%%d/%%n/mail:INDEX=~/indexes/%%d/%%n:INDEXPVT=~/indexes/%%d/%%n subscriptions = no list = children }

3 2

question on Dovecot replication
by Arnold Wang 17 Jul '15

17 Jul '15

I'm running Dovecot 2.2.x and have a question on its replication capability. I plan to run Dovecot in two different sites with two nodes at each site. My question is how many replication partners can each Dovecot node have? Can I define three "mail_replica" entries in every node so any message received by one node will be replicated to three other nodes automatically? Thanks in advance for your help.

1 0

Admin access to sieve filters with managesieve
by Christian Theune 15 Jul '15

15 Jul '15

Hi, I’ve been a long-time user of Cyrus and started using sieve with Dovecot recently. A question that came up is: how do I access a users’s sieve scripts through managesieve without their credentials? Managesieve allows separating authentation and the corresponding mailbox identification, right? That’s what I used with cyrus sieve all the time. :) I didn’t find documentation in the wiki or googling where to configure someone as admin in Dovecot so he can access foreign sieve scripts through managesieve. Pointers? Am I using the right words? Cheers, Christian — Christian Theune · ct(a)flyingcircus.io · +49 345 219401 0 Flying Circus Internet Operations GmbH · http://flyingcircus.io Forsterstraße 29 · 06112 Halle (Saale) · Deutschland HR Stendal HRB 21169 · Geschäftsführer: Christian. Theune, Christian. Zagrodnick

3 3

doveadm search -A problem with dropped privileges
by Sebastian Kricner 14 Jul '15

14 Jul '15

Hello, if you want to answer to this mail, please send it directly to me. I have found a big issue with the following command "doveadm -search -A". It whatsoever works by setting doveadm_worker_count = 0 in the dovecot.conf configuration file. The problem is that doveadm-server or something similar uses privileges of "nobody" and so it fails searching e-mails. Instead also the process tries to create a maildir for "nobody": Debug: Namespace : /var/mail/nobody doesn't exist yet, using default permissions Debug: Namespace : Using permissions from /var/mail/nobody: mode=0700 gid=default Error: User initialization failed: Namespace '': mkdir(/var/mail/nobody) failed: Permission denied (euid=65534(nobody) egid=65534(nobody) missing +w perm: /var/mail, we're not in group 12(mail), dir owned by 0:12 mode=0775) Error: search: User init failed Error: userdb lookup: connect(/var/run/dovecot//auth-userdb) failed: Permission denied (euid=65534(nobody) egid=65534(nobody) missing +r perm: /var/run/dovecot//auth-userdb, we're not in group 12(mail), dir owned by 0:0 mode=0755) Error: search: User lookup failed: Internal error occurred. Refer to server log for more information. Even after setting permissions, so that the process can create a maildir for "nobody" in the /var/mail location, it fails to "setresgid" to the particular user to be scanned. It can´t work because it is not possible to gain other user privileges from another user. # 2.2.16: /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.7 # OS: Linux Gentoo Base System release 2.2 auth_cache_negative_ttl = xx mins auth_cache_size = xx M auth_cache_ttl = xx mins auth_mechanisms = xx xx auth_worker_max_count = xx base_dir = /var/run/dovecot/ default_process_limit = xx dict { expire = sqlite:/xx } doveadm_worker_count = 1 first_valid_gid = xx first_valid_uid = xx login_greeting = xx.xx mail_location = maildir:/xx/xx/%u mail_privileged_group = xx 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 passdb { args = scheme=SHA512 /xx/xx/xx.xx driver = passwd-file } plugin { expire = xx expire2 = xx expire_dict = proxy::expire sieve = ~/.xx.xx sieve_dir = ~/.xx } protocols = imap sieve service auth { unix_listener auth-client { group = xx mode = 0660 } unix_listener auth-userdb { group = xx mode = 0660 } } service dict { unix_listener dict { mode = 0666 } } service imap-login { inet_listener imap { port = 0 } process_limit = 6 service_count = 1 } ssl_cert = </xx/xx/xx/xx.xx.xx ssl_key = </xx/xx/xx/xx.xx.xx ssl_parameters_regenerate = xx days userdb { driver = passwd } protocol lda { mail_plugins = sieve expire } protocol imap { imap_idle_notify_interval = xx mins mail_max_userip_connections = xx mail_plugins = expire } Regards Sebastian Kricner -- http://tuxwave.net -- the difference to think makes it real!

1 0

does dovecot support aio(asynchronous IO)
by boyd 13 Jul '15

13 Jul '15

Dear, Does dovecot support aio(asynchronous IO)? Or do we have a plan/need to support it? Thanks!

1 0

doveadm save message ...
by Hardy Flor 11 Jul '15

11 Jul '15

How can I set the flags for a saved message without search?

2 1

Error while executing dovecot
by Sachin Kulkarni1 10 Jul '15

10 Jul '15

Hello All, I am trying to execute dovecot by below command /opt/app/dovecot/latest/sbin/dovecot -c /opt/app/dovecot/latest/etc/dovecot/dovecot.conf I am getting below error doveconf: Fatal: Error in configuration file /opt/app/dovecot/latest/etc/dovecot/dovecot.conf: default_login_user doesn't exist: dovenull please guide me to resolve this. Thanks and Regards, Sachin ============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra. ============================================================================================================================

2 1

Re: Systemd and listen restriction to localhost not enforced
by Joseph Tam 09 Jul '15

09 Jul '15

Sven Strickroth <sven(a)cs-ware.de> writes: > in /etc/dovecot/conf.d/10-master.conf I have restricted IMAP to > localhost only: > > service imap-login { > inet_listener imap { > address = 127.0.0.1 > #port = 143 > } > inet_listener imaps { > #port = 993 > #ssl = yes > } > } > > However, /lib/systemd/system/dovecot.socket make it listen on > 0.0.0.0:143 and [::]:143 causing the service being available to > the public which it should not. - IMHO this is a security issue. I don't know much about systemd, but you'll probably need dovecot configuration listen = 127.0.0.1 Joseph Tam <jtam.home(a)gmail.com>

1 0

Systemd and listen restriction to localhost not enforced
by Sven Strickroth 09 Jul '15

09 Jul '15

Hi, in /etc/dovecot/conf.d/10-master.conf I have restricted IMAP to localhost only: service imap-login { inet_listener imap { address = 127.0.0.1 #port = 143 } inet_listener imaps { #port = 993 #ssl = yes } } However, /lib/systemd/system/dovecot.socket make it listen on 0.0.0.0:143 and [::]:143 causing the service being available to the public which it should not. - IMHO this is a security issue. PS: When starting dovecot I got: Jul 6 22:52:14 srv1 dovecot[19921]: Error: systemd listens on port 143, but it's not configured in Dovecot. Closing. Jul 6 22:52:14 srv1 dovecot: master: Error: systemd listens on port 143, but it's not configured in Dovecot. Closing. -- Best regards, Sven Strickroth PGP key id F5A9D4C4 @ any key-server

1 0