- dovecot - dovecot.org

[Dovecot] Sieve and Namespace in dovecot 2.0.X
by Mauricio Tavares 11 Oct '13

11 Oct '13

Based on what I read in http://wiki2.dovecot.org/Pigeonhole/Sieve/Usage, if I have a namespace defined as tail conf.d/10-mail.conf namespace inbox { inbox = yes location = prefix = INBOX. separator =. type = private } A global script like cat /etc/dovecot/sieve/global-spam.sieve require ["fileinto", "regex"]; # Must use regex here as 'contains' may not be valid, it erroneously # moved: # X-Spam-Status: No, score=-4.0 required=8.0 tests=ALL_TRUSTED,BAYES_00, # DCC_CHECK_NEGATIVE,HTML_MESSAGE,T_TM2_M_HEADER_IN_MSG,UNTRUSTED_Relay, # XM_SPF_Neutral autolearn=disabled version=3.2.5, No # # Due to the 'YES' in BAYES, let's just make sure YES is at the # _beginning_ of X-Spam-Status, while ignoring anything past it. #if header :regex "X-Spam-Status" "^[Yy][Ee][Ss].*" { if header :matches "X-Spam-Status" "Yes*" { fileinto "INBOX.Spam"; stop; } should put spam in bob/.Spam. But, I am getting an error message stating that INBOX.Spam does not exist: Oct 11 09:57:33 mail dovecot: lda(bob(a)domain.com): Error: sieve: msgid=<0.0.0.71C.1CEC689A21CFF08.7068B7(a)ip.aidolip.us>: failed to store into mailbox 'INBOX.Spam': Mailbox doesn't exist: INBOX.Spam How come?

2 5

[Dovecot] Optimisation opportunity for IMAP searches
by Rick van Rein (OpenFortress) 11 Oct '13

11 Oct '13

Hello, I love Dovecot, but when developing a small IMAP tool, I ran into searching behaviour can easily be optimised. Please forgive a rather detailed suggestion. This was on Dovecot 1.2.15 on Debian Squeeze. My tool? It's called "midget" and retrieves documents from an IMAP box based on their mid: or cid: identifier, as per RFC 2392. I thought this would be useful to retrieve email attachments into a remote shell environment. When using Kerberos, the credentials and a strong hint of one's mail address are already present anyway, DNS SRV does the rest. If you want to see the early code, I'll be happy to share it here. The three formats of the URIs in RFC 2392 are: * mid:messageid * cid:contentid * mid:messageid/contentid Searching for a mid: with only a Message-ID part is quick and probably indexed, (HEADER Message-ID <messageid>) Searching for a cid: meant ploughing through body text to get to the attachments, so it was a slow and costly and needed checking of the outcome: (TEXT <contentid>) The quicker URI form to get to a Content-Id should be to mention it at the end of a mid: URI, and search for (HEADER Message-ID <messageid>)(TEXT <conentid>) Much to my surprise, this took about as long as the cid: query -- ploughing through lots of body text while it only needed to look through a one message bodies! As a human, I can see a straightforward improvement. However, it is more difficult to find a general solution -- but that is what I'm describing below, in the hope that it will help to improve Dovecot's search performance. 0. In general, searches are Boolean expressions composed with implied AND and explicit (NOT …) and (OR ….) constructs. 1. Using the theorems of The Morgan, push all (NOT …) constructs inside as far as possible, until they surround elementary statements. Some may have a trivial solution, such as (NOT (ALL)). Others will retain the NOT but that might be handled with a different use of the indexes. In general, this phase turns all AND and OR constructs into positive logic, without duplicating search terms. 2. Estimate the effort involved in every part of the calculation. (HEADER) is lighter than (TEXT) and headers may be further split into with / without index. Larger sets could be more work to search than smaller ones. In general, an estimate of the number of comparisons could be a good metric for work to be done. 3. For AND compositions, start with the simplest one in the AND compostition, and continue with increasingly heavier ones. Apply later conditions only on the output of the previous conditions, either after collecting all of it or everytime something is found. Whatever is optimal -- bulk operations are more efficient, but may collect large sets to handle. 4. For OR compositions, either start a thread for each part, or switch focus and collect sorted streams into one collectively sorted stream. I've been doing this stuff all through my PhD thesis work, so it come easy to me :-) But this optimisation does not appear to be implemented yet, so I thought I'd suggest it. I hope this is useful to Dovecot! Best wishes, Rick van Rein

2 2

[Dovecot] Questio about replication
by Patrick Westenberg 11 Oct '13

11 Oct '13

Hi everyone, this article (http://blog.dovecot.org/2012/02/dovecot-clustering-with-dsync-based.html) describes the situation for director/NFS-based clusters and SSH-based clusters. Right now I'm running the first setup with one proxy/director and two backends (all 2.2.x) mounting an NFS-share but I'd like to get rid of NFS (it's slow) and, if one backend is down, the proxy still sends the user to that backend. The article says: "High-availability non-NFS setup One possibility is to use Dovecot proxies, which know which servers are down. Instead of directing users to those servers, it would direct them to replica servers." My question is, if I can still use my proxy/direcot setup but every backend having it's local (or iSCSI-backed) ext4 storage and not using the SSH-based replication method? Regards Patrick

2 1

[Dovecot] SSL with startssl.com certificates
by Dan Langille 11 Oct '13

11 Oct '13

I'm using Dovecot 2.2.5. I'm setting up and new IMAPS server for personal use (i.e. only me). I have success with self-signed certificates but not with others (e.g. StartSSL.com) With StartSSL certs: I've been able to connect and test commands via: openssl s_client -connect imaps.unixathome.org:993 Can you configure your iPhone or Macbook to access the above? Authentication isn't the issue. Connection is the issue. I've been able to get Thunderbird to connect and access my mail. However, I've been unable to get my iPhone or my Mac configured to use the same IMAP server. On the iPhone, adding the new Mail account causes the Settings app to crash on a persistently consistent basis when adding the new account. The crash occurs when connecting to the IMAPS server. Configuration never completes. I suspect the problem is SSL because in both cases (iPhone and Mac), I see these messages I see in the logs: *** /var/log/debug.log *** Sep 13 11:50:32 imaps dovecot: imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3 read client certificate A [166.137.84.11] Sep 13 11:50:45 imaps dovecot: auth: Debug: auth client connected (pid=31647) Sep 13 11:50:45 imaps dovecot: imap-login: Debug: SSL: where=0x10, ret=1: before/accept initialization [166.137.84.11] Sep 13 11:50:45 imaps dovecot: imap-login: Debug: SSL: where=0x2001, ret=1: before/accept initialization [166.137.84.11] Sep 13 11:50:45 imaps dovecot: imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv2/v3 read client hello A [166.137.84.11] Sep 13 11:50:45 imaps dovecot: imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read client hello A [166.137.84.11] Sep 13 11:50:45 imaps dovecot: imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write server hello A [166.137.84.11] Sep 13 11:50:45 imaps dovecot: imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write certificate A [166.137.84.11] Sep 13 11:50:45 imaps dovecot: imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write server done A [166.137.84.11] Sep 13 11:50:45 imaps dovecot: imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 flush data [166.137.84.11] Sep 13 11:50:45 imaps dovecot: imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3 read client certificate A [166.137.84.11] *** /var/log/maillog *** Sep 13 11:50:46 imaps dovecot: imap-login: Warning: SSL failed: where=0x2002: SSLv3 read client certificate A [166.137.84.11] Sep 13 11:50:46 imaps dovecot: imap-login: Disconnected (no auth attempts in 1 secs): user=<>, rip=166.137.84.11, lip=199.233.228.197, TLS handshaking: Disconnected, session=<a7AJd0LmWwCmiVQL> /usr/local/etc/ssl/imaps.unixathome.org.crt contains only the cert issued by StartSSL /usr/local/etc/ssl/imaps.unixathome.org.nopassword.key contains a no-password key generated by myself. Output of doveconf -n: # 2.2.5: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 9.1-RELEASE-p6 amd64 auth_debug = yes auth_verbose = yes first_valid_gid = 1001 first_valid_uid = 1001 mail_debug = yes mail_location = maildir:~/Maildir mail_privileged_group = mail passdb { args = scheme=BLF-CRYPT /var/db/dovecot.users driver = passwd-file } protocols = imap service imap-login { inet_listener imap { port = 0 } inet_listener imaps { address = 199.233.228.197 } } ssl = required ssl_cert = </usr/local/etc/ssl/imaps.unixathome.org.crt ssl_key = </usr/local/etc/ssl/imaps.unixathome.org.nopassword.key userdb { args = /var/db/dovecot.users driver = passwd-file } verbose_proctitle = yes verbose_ssl = yes protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep } -- Dan Langille - http://langille.org/

10 53

[Dovecot] cached message size errors
by Charles Sprickman 11 Oct '13

11 Oct '13

Hello, We recently moved from courier to dovecot, and I'm seeing a handful of errors that prevent people from retrieving email. Below is a snippet of the log sequence I see when this happens: Oct 10 13:44:24 mbox dovecot: imap(xxx(a)bway.net): Error: Cached message size smaller than expected (1759 < 1830) Oct 10 13:44:24 mbox dovecot: imap(xxx(a)bway.net): Error: Maildir filename has wrong S value, renamed the file from /home/vpopmail/domains/bway.net/1/xxx/Maildir/cur/1381381552.91972.xena.bway.net,S=1759:2,b to /home/vpopmail/domains/bway.net/1/xxx/Maildir/cur/1381381552.91972.xena.bway.net,S=1830:2,b Oct 10 13:44:24 mbox dovecot: imap(xxx(a)bway.net): Error: Corrupted index cache file /home/vpopmail/domains/bway.net/1/xxx/Maildir/dovecot.index.cache: Broken physical size for mail UID 447401 Oct 10 13:44:24 mbox dovecot: imap(xxx(a)bway.net): Error: read(/home/vpopmail/domains/bway.net/1/xxx/Maildir/cur/1381381552.91972.xen… failed: Invalid argument Oct 10 13:44:24 mbox dovecot: imap(xxx(a)bway.net): Disconnected: Internal error occurred. Refer to server log for more information. [2013-10-10 13:44:24] in=784 out=3017 Basically it looks like dovecot detects a mismatch in the file size vs. the file size embedded in the maildir filename, tries to fix it and then has issues reading the fixed file. Removing the file in question allows the user to retrieve email. The "invalid argument" error seems especially strange, as I'm able to view the file by hand with no problems. Blowing away the indexes and letting them get recreated seems to not help at all. This was an old vpopmail setup with both maildrop and vdelivermail doing the final delivery both now and prior to the migration to dovecot. For a quick fix, is there a way to have dovecot ignore the error and present the rest of the mailbox? Longer term fix, I'm not even sure where to start I've used dovecot elsewhere for quite some time (with maildirs) and I've never had an issue like this. 'doveconf -n' below... Thanks, Charles -- Charles Sprickman NetEng/SysAdmin Bway.net - New York's Best Internet www.bway.net spork(a)bway.net - 212.655.9344 # 2.2.5: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 8.4-RELEASE-p1 amd64 auth_default_realm = bway.net auth_socket_path = /var/run/dovecot/auth-userdb auth_verbose = yes base_dir = /var/run/dovecot/ default_process_limit = 300 disable_plaintext_auth = no first_valid_uid = 89 instance_name = dovecot1 last_valid_uid = 90 listen = 127.0.0.1,216.220.96.26,216.220.96.25 login_greeting = Dovecot ready - bway.net. mail_plugins = " quota" mailbox_list_index = yes namespace inbox { hidden = no inbox = yes list = yes location = mailbox Drafts { special_use = \Drafts } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Spam { special_use = \Junk } mailbox Trash { special_use = \Trash } prefix = INBOX. separator = . subscriptions = yes type = private } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { quota = maildir:User quota quota_rule = Inbox.Trash:storage=+100M quota_rule2 = Inbox.Spam:storage=+100M } pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %v-%u protocols = imap pop3 ssl_cert = </usr/local/etc/ssl/bwaynet.pem ssl_key = </usr/local/etc/ssl/bwaynet.key userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol imap { mail_max_userip_connections = 40 mail_plugins = " quota imap_quota" } protocol pop3 { mail_max_userip_connections = 20 }

1 1

[Dovecot] Maildir and home location
by Florian Lindner 10 Oct '13

10 Oct '13

Hello! My current mail setup looks like that: MTA is postfix, MDA is maildrop. Each system user configures mail delivery using the .mailfilter of maildrop to arbitrary maildirs in his home. For each maildir a POP3/IMAP account can be configured, currently I use courier-imap/-pop and think about replacing it by dovecot. AFAIK with dovecot each account has a home and maildir assigned which should not be equal neither should a home dir be used for mulitple accounts. My problem is where to put these homedirs? System users have full SSH access on the machine. I would really prefer to put them somewhere where the users could delete them (if they need to reset or delete their account). Optimal would be in the maildir itself, but... What are your suggestions? Regards, Florian

1 0

[Dovecot] v2.2: Fix to slow process creation in some setups
by Timo Sirainen 10 Oct '13

10 Oct '13

Especially some imap/pop3 login bursts could have caused errors like: imap-login: Error: net_connect_unix(imap) failed: Resource temporarily unavailable Fix in http://hg.dovecot.org/dovecot-2.2/rev/69179ca6007d Explanation & workaround in http://wiki2.dovecot.org/SocketUnavailable : Dovecot v2.2.0 - v2.2.6 were attempting to optimize host.domain lookups by doing them only once in the master process. Unfortunately they were actually doing the lookup every time when creating a new process. In some configuration this lookup could have done a somewhat slow DNS lookup, causing the process creation to become very slow and triggering this message. The fix is in v2.2.7 and you can also workaround this: • Add to dovecof.conf: import_environment = TZ DEBUG_OUTOFMEM DOVECOT_HOSTDOMAIN • Before "dovecot" binary is started, run: export DOVECOT_HOSTDOMAIN=mailserver.example.com (of course changing the value)

1 0

[Dovecot] smartsieve managesieve-login failure with dovecot 2.1.7
by Wouter Berkepeis 09 Oct '13

09 Oct '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I just subscribed to the mailing list because I am stuck trying to solve a problem getting smartsieve to work with a new version of dovecot. But let me first explain the situation shortly. I am running a mail server at home for personal use, and for fun. At this moment this is an old, slow machine running Debian Squeeze, Dovecot 1.2.15 and Exim 4.72. Authentication is done with LDAP, running OpenLDAP 2.4.23. For managing mail filtering I use Smartsieve 1.0.0-RC2 in conjunction with Dovecot's Managesieve plugin. It's all working properly. But because this machine is slow, I'm now busy upgrading building a new machine running Debian Wheezy, Dovecot 2.1.7 and Exim 4.80. I've got it all running and working now (that is: locally in my lan): imap with dovecot, smtp with exim, Dovecot's sieve plugin working properly, authentication done through LDAP backend. But what I can't get to work is Smartsieve. Looking at the logs on my server I can tell managesieve-login is not working well with Smartsieve. As far as I understand authentication is always done over a secure connection using TLS. Here is some logged output, Dovecot as well as Smartsieve. dovecot-info.log: 2013-10-06 21:16:20 managesieve-login: Info: Disconnected (no auth attempts in 0 secs): user=<>, rip=127.0.0.1, lip=127.0.0.1, TLS handshaking: SSL_accept() failed: error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure: SSL alert number 40, session=<NkXdXhfodwB/AAAB> syslog: Oct 6 21:51:40 jingo smartsieve[12168]: getCryptLib: using rc4 Oct 6 21:51:40 jingo smartsieve[12168]: getCryptLib: using rc4 Oct 6 21:51:40 jingo smartsieve[12168]: FAILED LOGIN: jingo [192.168.2.12] {Private Lotus}: starttls: TLS initialization failed: socket timed out while reading server response: #002 Oct 6 21:51:40 jingo smartsieve[12168]: 2Z#027#015141003200542Z0??1#0130#011#006#003U#004#006#023#002NL1#0230#021#006#003U#004#010#014#012Overijssel1#0200#016#006#003U#004#007#014#007Hengelo1#0!#006#003U#004#012#014#032Private Lotus Organization1#0230#021#006#003U#004#013#014#012Jingo Mail1&0$#006#003U#004#003#014#035jingo.private-lotus.no-ip.net1&0$#006#011*?H?÷#015#001#011#001#026#027amigo(a)private-lotus.org0?#001"0#015#006#011*?H?÷#015#001#001#001#005 Oct 6 21:51:40 jingo smartsieve[12168]: #003#001 Oct 6 21:51:40 jingo smartsieve[12168]: èm¬NþgHÁßt#021×?Ð#011$?f+»#013?#021?ø#013yùZd#032Òí}Ì#012ù?#003xPË What is clear is that somehow no user information is being negotiated. Issuing a manual TLS login give the following results: root@amigos:~# gnutls-cli --starttls -p 4190 jingo.private-lotus.no-ip.net Resolving 'jingo.private-lotus.no-ip.net'... Connecting to '82.161.181.183:4190'... - - Simple Client Mode: "IMPLEMENTATION" "Dovecot Pigeonhole" "SIEVE" "fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave" "NOTIFY" "mailto" "SASL" "" "STARTTLS" "VERSION" "1.0" OK "Dovecot ready." STARTTLS OK "Begin TLS negotiation now." *** Starting TLS handshake - - Ephemeral Diffie-Hellman parameters - Using prime: 1024 bits - Secret key: 1022 bits - Peer's public key: 1024 bits - - Certificate type: X.509 - Got a certificate list of 1 certificates. - Certificate[0] info: - subject `C=NL,ST=Overijssel,L=Hengelo,O=Private Lotus Organization,OU=Jingo Mail,CN=jingo.private-lotus.no-ip.net,EMAIL=amigo(a)private-lotus.org', issuer `C=NL,ST=Overijssel,L=Hengelo,O=Private Lotus Organization,OU=Private Lotus Certificate Authority,CN=private-lotus.no-ip.net,EMAIL=amigo(a)private-lotus.org', RSA key 2048 bits, signed using RSA-SHA, activated `2013-10-03 20:05:42 UTC', expires `2014-10-03 20:05:42 UTC', SHA-1 fingerprint `85ff6b5846a53e7eb5d46c3c4ebfd7beb253ba15' - - The hostname in the certificate matches 'jingo.private-lotus.no-ip.net'. - - Peer's certificate issuer is unknown - - Peer's certificate is NOT trusted - - Version: TLS1.1 - - Key Exchange: DHE-RSA - - Cipher: AES-128-CBC - - MAC: SHA1 - - Compression: NULL Everything OK I guess. Especially the first part of the output is interesting: "IMPLEMENTATION" "Dovecot Pigeonhole" This is what Smartsieve is looking at. With the former version the string was 'dovecot', so I changed this in the 'Managesieve.php' file. This file was already patched as stated on the site. Furthermore I changed everything referring to port 2000 to port 4190. But it still ain't working. Am I doing something wrong? Or is Smartsieve just becoming too outdated to work with newer versions of Dovecot? To get the picture complete, hereby my used config of Dovecot, generated with 'dovecot -n' : root@jingo:~# dovecot -n # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-686-pae i686 Debian 7.1 info_log_path = /var/log/dovecot/dovecot-info.log log_path = /var/log/dovecot/dovecot.log log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:~/Maildir 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 ihave 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 = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { mail_log_fields = uid box msgid size flags sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_global_dir = /etc/dovecot/sieve/ } protocols = " imap sieve" service auth-worker { user = $default_internal_user } service imap-login { inet_listener imap { address = * port = 143 } inet_listener imaps { address = * port = 993 } } service managesieve-login { executable = /usr/lib/dovecot/managesieve-login inet_listener sieve { port = 4190 } } service managesieve { executable = /usr/lib/dovecot/managesieve } ssl_cert = </etc/pki_jingo/private-lotus_CA/certs/server.crt ssl_cipher_list = HIGH:+TLSv1:+SSLv3:!LOW:!SSLv2:!EXP:!aNULL ssl_key = </etc/pki_jingo/private-lotus_CA/private/server.key ssl_protocols = !SSLv2 SSLv3 userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf.ext driver = ldap } protocol lda { info_log_path = /var/log/dovecot/deliver.log log_path = /var/log/dovecot/deliver-errors.log mail_plugin_dir = /usr/lib/dovecot/modules mail_plugins = sieve postmaster_address = amigo(a)private-lotus.org } protocol imap { mail_max_userip_connections = 50 } protocol sieve { mail_debug = 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 ihave } Any help would be appreciated. Thanks in advance. Greetings Wouter -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJSUeueAAoJEHmiGeisoomH6LEH/irXWxa7kRDB1Gy929Z7E1p6 sZR7pk3tfDPz5PUPNVro+8AG5a+mjUhlVVsxi7pHfadgqGmXZmbbpQLBKQcAbtHI WzY//0t6Dvnn/ywBloWIarWO10SGFRrMBKEBJp/5glUJu0XMnB1PLEZjpFKobwuo WBHjynIEs9fzPjPk7/Kc74LysbtQ931OSeKFsLfqMfP3/Iem75CLGgNg8QFuzZj3 yTv/Kk2D8gMkvSNsP1dmZ8i2B3p75kV6hTvbU9Z8fS2P1rqi3DpbRilKXxw0wMdi gRE3r8yfcRCOhA7vjRe6o63DbadeDm0ZTepIcf8cjFtd9Bsq3cdS9TqUH//jMPI= =Rv4p -----END PGP SIGNATURE-----

4 12

[Dovecot] dovecot: ssl-params
by Frank Elsner 09 Oct '13

09 Oct '13

Hello *, what is the reason for this strange behaviour? May I ignore it? Oct 8 19:32:20 seymour dovecot: ssl-params: Generating SSL parameters Oct 8 19:32:29 seymour dovecot: ssl-params: SSL parameters regeneration completed Oct 9 07:01:05 seymour dovecot: ssl-params: Generating SSL parameters Oct 9 07:01:06 seymour dovecot: imap-login: Login: frank, 192.168.28.1, TLS Oct 9 07:01:06 seymour dovecot: ssl-params: SSL parameters regeneration completed Oct 9 07:01:07 seymour dovecot: ssl-params: Error: epoll_ctl(del, 7) failed: No such file or directory Oct 9 07:01:07 seymour dovecot: ssl-params: Error: epoll_ctl(del, 8) failed: No such file or directory Kind regards, Frank Elsner

1 0

[Dovecot] shared or acl or etc
by John Smith 09 Oct '13

09 Oct '13

Hello, I need help: [root@dovecot]# dovecot -n # 2.1.16: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-358.18.1.el6.x86_64 x86_64 CentOS release 6.4 (Final) auth_debug = yes auth_mechanisms = plain login auth_use_winbind = yes auth_username_format = %u auth_verbose = yes base_dir = /var/run/dovecot/ disable_plaintext_auth = no listen = * mail_access_groups = vmail mail_debug = yes mail_gid = 5000 mail_location = maildir:~/:LAYOUT=fs mail_plugins = " quota acl" mail_privileged_group = vmail mail_uid = 5000 mbox_write_locks = fcntl namespace { list = children location = maildir:%%h:INDEX=~/shared/%%u prefix = shared/%%u/ separator = / subscriptions = no type = shared } 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 = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile:/etc/dovecot/global-acls:cache_secs=300 autocreate = Sent autocreate2 = Trash autocreate3 = Drafts autosubscribe = Sent autosubscribe2 = Trash autosubscribe3 = Drafts quota = maildir:User quota quota_rule = *:storage=100M quota_rule2 = Trash:storage=+100M quota_rule3 = Sent:storage=+100M quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u } service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } unix_listener auth-userdb { mode = 0666 user = vmail } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { user = vmail } user = dovecot } ssl = no ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } userdb { args = uid=5000 gid=5000 driver = static } valid_chroot_dirs = /home/vmail/ protocol imap { mail_plugins = " quota acl autocreate imap_quota imap_acl" } [root@dovecot]# grep -v '^ *$#.*$\?$' dovecot-ldap.conf.ext hosts = dc1.domain.local dc2.domain.local dn = CN=ldapsearch,OU=Service Accounts,DC=domain,DC=local dnpass = ****** auth_bind = yes auth_bind_userdn = %Lu base = OU=GroupOfCompanies,DC=domain,DC=local deref = never scope = subtree user_filter = (&(!(userAccountControl:1.2.840.113556.1.4.803:=2))(|(mail=%Lu)(otherMailbox=%Lu)(sAMAccountName=%Lu))) user_attrs = sAMAccountName=home=/home/vmail/%L$, maxStorage=quota_rule=*:bytes=%$M pass_filter = (&(sAMAccountType=805306368)(sAMAccountName=%Lu)) pass_attrs = sAMAccountName=user,userPassword=password With these settings the domain users successfully authenticate and can receive mail from their mail_localtion, however there are a few users with the same email address, but different sAMAccountName These users use the same e-mail on all connected by imap. Tell me how to beat this situation?

2 1