- dovecot - dovecot.org

[Dovecot] Patch to fix leak in imap_refresh_proctitle in beta[5, 6]
by Mike Abbott 17 Jun '10

17 Jun '10

The "imap" process of dovecot-2.0.beta[5,6] grows very large (I impose no system limits), e.g. exceeding 4.8GB on a 64-bit system. These messages appear in the logs: Warning: Growing pool 'imap client' with: 2048 Warning: Growing pool 'Cache fields' with: 2048 Warning: Growing data stack with: 32768 Warning: Growing data stack with: 65536 Warning: Growing data stack with: 131072 [...] Warning: Growing data stack with: 1073741824 Warning: Growing data stack with: 2147483648 Warning: Growing data stack with: 4294967296 Every time the data stack grows, the backtrace ends with either: 2 libdovecot.0.dylib 0x00000001059a35c3 pool_data_stack_realloc + 72 -> 3 libdovecot.0.dylib 0x0000000105994d59 buffer_alloc + 59 -> 4 libdovecot.0.dylib 0x0000000105994ef9 buffer_check_limits + 127 -> 5 libdovecot.0.dylib 0x00000001059950e8 buffer_append + 38 -> 6 imap 0x0000000105867333 imap_refresh_proctitle + 218 -> 7 imap 0x000000010585f18e client_command_input + 190 -> [...] or 2 libdovecot.0.dylib 0x00000001059a35c3 pool_data_stack_realloc + 72 -> 3 libdovecot.0.dylib 0x0000000105994d59 buffer_alloc + 59 -> 4 libdovecot.0.dylib 0x0000000105994ef9 buffer_check_limits + 127 -> 5 libdovecot.0.dylib 0x00000001059950e8 buffer_append + 38 -> 6 imap 0x0000000105867333 imap_refresh_proctitle + 218 -> 7 imap 0x00000001058666ce cmd_sync_continue + 199 -> [...] Here is a patch to fix it: --- a/src/imap/main.c (beta6) +++ b/src/imap/main.c (working copy) @@ -39,11 +39,12 @@ #define IMAP_PROCTITLE_PREFERRED_LEN 80 struct client *client; struct client_command_context *cmd; - string_t *title = t_str_new(128); + string_t *title; if (!verbose_proctitle) return; + title = str_new(default_pool, 128); str_append_c(title, '['); switch (imap_client_count) { case 0: @@ -72,6 +73,7 @@ } str_append_c(title, ']'); process_title_set(str_c(title)); + str_free(&title); } static void client_kill_idle(struct client *client) And perhaps there should be a warning when data is allocated out of the primordial data stack (as opposed to a nested one)?

2 5

[Dovecot] search bug?
by Pozsar Balazs 16 Jun '10

16 Jun '10

Hi all, I have emails with multiple Delivered-To: headers in them. The problem is that the SEARCH command only searches in the first instances. For example: 1 FETCH 14557 BODY[HEADER.FIELDS (Delivered-To)] * 14557 FETCH (BODY[HEADER.FIELDS (DELIVERED-TO)] {85} Delivered-To: pozsy(a)ojjektum.uhulinux.hu Delivered-To: szamlagyar(a)uhusystems.com ) 1 OK Fetch completed. 1 SEARCH HEADER Delivered-To szamlagyar(a)uhusystems.com * SEARCH 14589 1 OK Search completed (0.146 secs). You can see the meesage with the id 14557 _has_ a "Delivered-To: szamlagyar(a)uhusystems.com" header field, but the SEARCH does not find it, only another message. This is with dovecot 1.2.11. For the record, cyrus-imapd behaves as I would have expected, and I could not find anything relevant in the RFCs. Could anyone tell me if this is a bug, or how to search like I would want? Thanks, Balazs Pozsar

3 6

[Dovecot] New admin, not much success
by Chuck McManis 16 Jun '10

16 Jun '10

Hello, I'm trying to set up something fairly simple (famous last words) using Dovecot. I have a very small setup (just a dozen users) I'm using qmail as my MTA. I'm running FreeBSD 8.0 I've got qmail delivering into a file named 'Mailbox' in user's home directories. I prefer not to use Maildir delivery because from a shell its a PITA to get a Maildir aware MUA (I use /bin/mail when I'm attached locally) What I'm trying to do is configure an SSL only POP3 server so that folks can retrieve their email on the road without divulging their passwords. My backup scenario is to put VPN software on my user's clients and having them VPN into the network and then do un-encrypted POP3 from the VPN. I prefer not to do this as it means maintaining the VPN client as well. Users have a mix of MacOS, Windows, and Linux. So, I can't get dovecot to work at all. In an unusual turn about I got the SSL stuff working but not the mailbox handling. I'm running 2.0beta6 Output from dovecot -n ------------------------------------------------------------------------------------ # 2.0.beta6: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 8.0-RELEASE-p2 i386 nfs auth_debug = yes auth_verbose = yes default_internal_user = nobody default_login_user = nobody listen = * mail_full_filesystem_access = yes mail_location = mbox:/home/%u/:INBOX=/home/%u/ passdb { driver = pam } protocols = pop3 service pop3-login { inet_listener pop3s { port = 995 ssl = yes } } service pop3 { process_limit = 1024 } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = passwd } ----------------------------------------------------------------------- A typical failure looks like this in maillog: Jun 15 22:19:20 eeebox dovecot: master: Dovecot v2.0.beta6 starting up Jun 15 22:20:29 eeebox dovecot: pop3-login: Login: user=<cmcmanis>, method=PLAIN, rip=66.125.189.27, lip=66.125.189.30, mpid=78871, TLS Jun 15 22:20:29 eeebox dovecot: pop3(cmcmanis): Error: Opening INBOX failed: Mailbox isn't selectable Jun 15 22:20:29 eeebox dovecot: pop3(cmcmanis): Error: Couldn't open INBOX: Mailbox isn't selectable Jun 15 22:20:29 eeebox dovecot: pop3(cmcmanis): Couldn't open INBOX top=0/0, retr=0/0, del=0/0, size=0 -------------------------------------------------------------- Home directories are mounted via NFS and root doesn't have access, but if dovecot accesses the Mailbox as the user it should work fine. I'm about ready to start hacking in additional logging into mail-storage.c to figure out what "mailbox isn't selectable" means. --Chuck

4 12

[Dovecot] Logout after SSL/TLS negociation
by bmfr 16 Jun '10

16 Jun '10

Hi All, I've set up Dovecot to use my signed SSL certificate and IMAP client is using STARTTLS on port 143 without secure authentication. The TLS negociation process seems to go through ok but once the negociation is finished the client sends an IMAP LOGOUT message; he does not try to authenticate, below is the Dovecot's info log: dovecot: 2010-06-15 15:37:01 Info: auth(default): new auth connection: pid=3932 dovecot: 2010-06-15 15:37:03 Info: imap-login: Aborted login (0 authentication attempts): rip=130.100.32.54, lip=10.0.3.3, TLS I've decrypted the TLS negociation thanks to Wireshark (in SSL preferences I added the certificate's private key to decode the stream between client and server) but unfortunately it does not say why the client is sending the LOGOUT command. Do you have an idea of what could be wrong in my server set up? What debugging process would you advise me to follow? Thanks a lot for your precious help. Bastien -- View this message in context: http://old.nabble.com/Logout-after-SSL-TLS-negociation-tp28900688p28900688.… Sent from the Dovecot mailing list archive at Nabble.com.

3 4

[Dovecot] Mail Stuck in cur file
by jason hirsh 16 Jun '10

16 Jun '10

I am running dovecot 1.1.7 with postfix 2.6.5. Ihad a server down issue and when it rebooted the IPFW firewalll on my FReebsd server prevented mail from being delivered..at least thatis what I think the issue was... when i stopped IPFW .. mail resumed anyway I use vmail structure..and there are message in the cur directory.. how do i get them "reprocessed" or "released" I presume this are incoming

3 5

[Dovecot] A new director service in v2.0 for NFS installations
by Timo Sirainen 16 Jun '10

16 Jun '10

As http://wiki.dovecot.org/NFS describes, the main problem with NFS has always been caching problems. One NFS client changes two files, but another NFS client sees only one of the changes, which Dovecot then assumes is caused by corruption. The recommended solution has always been to redirect the same user to only a single server at the same time. User doesn't have to be permanently assigned there, but as long as a server has some of user's files cached, it should be the only server accessing the user's mailbox. Recently I was thinking about a way to make this possible with an SQL database: http://dovecot.org/list/dovecot/2010-January/046112.html The company here in Italy didn't really like such idea, so I thought about making it more transparent and simpler to manage. The result is a new "director" service, which does basically the same thing, except without SQL database. The idea is that your load balancer can redirect connections to one or more Dovecot proxies, which internally then figure out where the user should go. So the proxies act kind of like a secondary load balancer layer. When a connection from a newly seen user arrives, it gets assigned to a mail server according to a function: host = vhosts[ md5(username) mod vhosts_count ] This way all of the proxies assign the same user to the same host without having to talk to each others. The vhosts[] is basically an array of hosts, except each host is initially listed there 100 times (vhost count=100). This vhost count can then be increased or decreased as necessary to change the host's load, probably automatically in future. The problem is then of course that if (v)hosts are added or removed, the above function will return a different host than was previously used for the same user. That's why there is also an in-memory database that keeps track of username -> (hostname, timestamp) mappings. Every new connection from user refreshes the timestamp. Also existing connections refresh the timestamp every n minutes. Once all connections are gone, the timestamp expires and the user is removed from database. The final problem then is how multiple proxies synchronize their state. The proxies connect to each others forming a connection ring. For example with 4 proxies the connections would go like A -> B -> C -> A. Each time a user is added/refreshed, a notification is sent to both directions in the ring (e.g. B sends to A and C), which in turn forward it until it reaches a server that has already seen it. This way if a proxy dies (or just hangs for a few seconds), the other proxies still get the changes without waiting for it to timeout. Host changes are replicated in the same way. It's possible that two connections from a user arrive to different proxies while (v)hosts are being added/removed. It's also possible that only one of the proxies has seen the host change. So the proxies could redirect users to different servers during that time. This can be prevented by doing a ring-wide sync, during which all proxies delay assigning hostnames to new users. This delay shouldn't be too bad because a) they should happen rarely, b) it should be over quickly, c) users already in database can still be redirected during the sync. The main complexity here comes from how to handle proxy server failures in different situations. Those are less interesting to describe and I haven't yet implemented all of it, so let's just assume that in future it all works perfectly. :) I was also thinking about writing a test program to simulate the director failures to make sure it all works. Finally, there are the doveadm commands that can be used to: 1) List the director status: # doveadm director status mail server ip vhosts users 11.22.3.44 100 1312 12.33.4.55 50 1424 1) Add a new mail server (defaults are in dovecot.conf): # doveadm director add 1.2.3.4 2) Change a mail server's vhost count to alter its connection count (also works during adding): # doveadm director add 1.2.3.4 50 3) Remove a mail server completely (because it's down): # doveadm director remove 1.2.3.4 If you want to slowly get users away from a specific server, you can assign its vhost count to 0 and wait for its user count to drop to zero. If the server is still working while "doveadm director remove" is called, new connections from the users in that server are going to other servers while the old ones are still being handled.

6 22

[Dovecot] list command and shared folders
by Wolfram Greinert 16 Jun '10

16 Jun '10

Hello, I try to setup shared folders with real unix users: user "test2": setacl t2_t4 test4 lrswi user "test3": setacl t3_t4 test4 lrswi Now I see entries in ~test2/Maildir/.t2_t4/dovecot-acl, ~test3/Maildir/.t3_t4/dovecot-acl and /var/lib/dovecot/acl_dict.db (see below) But "test4" don't see the shared folders in the list command :-( ---- 01 login test4 xxxxxxx 01 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS ACL RIGHTS=texk QUOTA] Logged in 02 namespace * NAMESPACE (("" "/")) (("shared/" "/")) NIL 02 OK Namespace completed. 03 list "" * * LIST (\HasNoChildren) "/" "INBOX" 03 OK List completed. ---- The select command is possible: ---- 04 select shared/test2/t2_t4 * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 4 EXISTS * 4 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1276509851] UIDs valid * OK [UIDNEXT 5] Predicted next UID * OK [HIGHESTMODSEQ 1] Highest 04 OK [READ-WRITE] Select completed. ---- What is wrong in this setup, why can't see "test4" the shared folders in the list command ??? Best regards Wolfram dovecot -n: ----------- # 1.2.11: /etc/dovecot.conf # OS: Linux 2.6.32.12-0.7-default x86_64 SUSE Linux Enterprise Server 11 (x86_64) base_dir: /var/run/dovecot/ syslog_facility: local5 protocols: imap imaps pop3 pop3s ssl_cert_file: /etc/ssl/private/server.cert ssl_key_file: /etc/ssl/private/server.cert ssl_cipher_list: ALL:!LOW login_dir: /var/run/dovecot/login login_executable(default): /opt/dovecot/libexec/dovecot/imap-login login_executable(imap): /opt/dovecot/libexec/dovecot/imap-login login_executable(pop3): /opt/dovecot/libexec/dovecot/pop3-login login_log_format_elements: user=%u rip=%r method=%m %c login_processes_count: 10 login_max_processes_count: 2048 max_mail_processes: 4096 mail_max_userip_connections(default): 15 mail_max_userip_connections(imap): 15 mail_max_userip_connections(pop3): 10 verbose_proctitle: yes first_valid_uid: 290 last_valid_uid: 39000 first_valid_gid: 100 last_valid_gid: 1000 mail_debug: yes mbox_lock_timeout: 30 mail_executable(default): /opt/dovecot/libexec/dovecot/imap mail_executable(imap): /opt/dovecot/libexec/dovecot/imap mail_executable(pop3): /opt/dovecot/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota acl imap_acl mail_plugins(imap): quota imap_quota acl imap_acl mail_plugins(pop3): quota mail_plugin_dir(default): /opt/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /opt/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /opt/dovecot/lib/dovecot/pop3 mail_log_prefix: %Us[%p]: user=%u, rip=%r: imap_client_workarounds(default): delay-newmail imap_client_workarounds(imap): delay-newmail imap_client_workarounds(pop3): pop3_reuse_xuidl(default): no pop3_reuse_xuidl(imap): no pop3_reuse_xuidl(pop3): yes pop3_save_uidl(default): no pop3_save_uidl(imap): no pop3_save_uidl(pop3): yes pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): oe-ns-eoh namespace: type: private separator: / location: maildir:~/Maildir:INDEX=/var/dovecot/%1u/%u/indexes:CONTROL=/var/dovecot/%1u/%u/control inbox: yes list: yes subscriptions: yes namespace: type: shared separator: / prefix: shared/%%u/ location: maildir:/home1/users/%%u/Maildir:INDEX=/var/dovecot/%1u/%u/shared/%%u/indexes:CONTROL=/var/dovecot/%1u/%u/shared/%%u/control list: children lda: mail_plugins: quota mail_plugin_dir: /opt/dovecot/lib/dovecot/lda sendmail_path: /usr/sbin/sendmail auth_socket_path: /var/run/dovecot/auth-master auth default: mechanisms: plain login cache_negative_ttl: 600 executable: /opt/dovecot/libexec/dovecot/dovecot-auth username_format: %Lu count: 10 worker_max_count: 1024 passdb: driver: passwd-file args: /etc/dovecot.deny deny: yes passdb: driver: pam args: max_requests=100 dovecot userdb: driver: passwd plugin: quota: fs acl: vfile: acl_shared_dict: proxy::acl_dict dict: acl_dict: db:/var/lib/dovecot/acl_dict.db ~test2/Maildir/.t2_t4/dovecot-acl: ---------------------------------- user=test4 ilrws ~test3/Maildir/.t3_t4/dovecot-acl: ---------------------------------- user=test4 ilrws db_dump -p /var/lib/dovecot/acl_dict.db: ---------------------------------------- VERSION=3 format=print type=btree db_pagesize=4096 HEADER=END shared/shared-boxes/user/test4/test2 1 shared/shared-boxes/user/test4/test3 1 DATA=END -- ########################################### # Wolfram Greinert # # URZ der Uni Leipzig, Abteilung Netze # # 04109 Leipzig, Neumarkt 9-19 # # Tel.: +(0341) 97-33325 # # email: greinert(a)rz.uni-leipzig.de # ###########################################

2 4

[Dovecot] Sieve doesn't appear to be active
by Darek M 16 Jun '10

16 Jun '10

I'm hoping that this isn't something stupid and that I'm not wasting bandwidth here, but I'm stuck and don't know any further ways of debugging this. And most non-documentation, end-user created info I find is for 1.0 with cmusieve. Running Dovecot 1.2.11 on Fedora Core 12. Added 'sieve' to 'mail_plugins'. Have enabled verbose logging with 'mail_debug = yes'. But I'm not seeing anything in the logs relating to sieve, and the sieve script I point to isn't being compiled (no .log file). Everything else works fine, this is a production system where I'm trying to add sieve support. What steps can I take to troubleshoot? Config files: # dovecot -n ========= # 1.2.11: /etc/dovecot.conf # OS: Linux 2.6.31.6-166.fc12.i686.PAE i686 Fedora release 12 (Constantine) ext3 log_path: /var/log/dovecot/dovecot-err.log info_log_path: /var/log/dovecot/dovecot-info.log protocols: imap imaps pop3 pop3s managesieve ssl_cert_file: /etc/postfix/ssl/dovecot/certs/dovecot.pem ssl_key_file: /etc/postfix/ssl/dovecot/private/dovecot.pem disable_plaintext_auth: yes login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_executable(managesieve): /usr/libexec/dovecot/managesieve-login login_process_per_connection: no login_processes_count: 10 first_valid_gid: 5000 last_valid_gid: 5000 mail_uid: 5000 mail_gid: 5000 mail_location: maildir:/home/vmail/%d/%n/Maildir mail_debug: yes maildir_very_dirty_syncs: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_executable(managesieve): /usr/libexec/dovecot/managesieve mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 mail_plugin_dir(managesieve): /usr/lib/dovecot/managesieve lda: postmaster_address: postmaster(a)domain.com hostname: domain.com mail_plugins: sieve quota auth default: mechanisms: plain login apop user: nobody passdb: driver: sql args: /etc/postfix/dovecot.sql socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: vmail master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: sieve: /home/vmail/sieve-scripts/sieve.siv /etc/postfix/dovecot.sql: ================= driver = mysql connect = host=/var/lib/mysql/mysql.sock dbname=postfix user=dovecot password=dovecot user_query = SELECT concat('/home/vmail/', maildir) as home, concat('maildir:/home/vmail/', maildir) as mail, 5000 AS uid, 5000 AS gid, concat('maildir:storage=', quota) AS quota FROM mailbox WHERE username = '%u' AND active = '1' password_query = SELECT username as user, password, concat('/home/vmail/', maildir) as userdb_home, concat('maildir:/home/vmail/', maildir) as userdb_mail, 5000 as userdb_uid, 5000 as userdb_gid FROM mailbox WHERE username = '%u' AND active = '1' ================= [root@sys ~]# cd /var/log/dovecot/ [root@sys dovecot]# grep -i sieve * dovecot-info.log:Jun 14 13:09:22 managesieve-login: Info: Disconnected (no auth attempts): rip=::1, lip=::1, secured Only log entry from me telnetting to the managesieve port. -- Darek

2 2

[Dovecot] Dovecot passdb LDAP queries
by Wilberth Pérez 15 Jun '10

15 Jun '10

Hi: When runs dovecot, I can see that dovecot sends two ldap queries to my OpenLDAP server and establishes one conection, however when test my dovecot-ldap configurarion with telnet My OpenLDAP server don't received ldap request from my clients. dovecot-auth process need special permissions?. my dovecot-ldap.conf file is wrong?. Any suggestion ? Thanks. My Telnet messages are: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN] Dovecot ready. 1 login USER PASSWORD 1 NO [AUTHENTICATIONFAILED] Authentication failed. My Dovecot logs are: Jun 15 13:27:42 auth(default): Info: shadow(USER,X.X.X.X): lookup Jun 15 13:27:42 auth(default): Info: shadow(USER,X.X.X.X): unknown user Jun 15 13:27:42 auth(default): Info: ldap(USER,X.X.X.X): invalid credentials (given password: PASSWORD) Jun 15 13:27:44 auth(default): Info: client out: FAIL 1 user=USER My dovecot.conf configuration: log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot.log protocols: imap pop3 listen(default): X.X.X.X:143 listen(imap): X.X.X.X:143 listen(pop3): X.X.X.X:110 ssl: no disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login first_valid_uid: 100 mail_location: maildir:%h/Maildir/:INDEX=/var/indexes/%u/:CONTROL=/var/control/%u/:INBOX=/var/mail/%u/ mail_debug: yes mail_full_filesystem_access: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota trash mail_plugins(imap): quota imap_quota trash mail_plugins(pop3): quota mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 pop3_reuse_xuidl(default): no pop3_reuse_xuidl(imap): no pop3_reuse_xuidl(pop3): yes lda: mail_plugins: cmusieve quota auth default: mechanisms: plain login verbose: yes debug: yes debug_passwords: yes passdb: driver: shadow passdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf userdb: driver: passwd userdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix plugin: quota: fs:INBOX:mount=/var/mail/ quota2: fs:HOME:mount=/u/ quota_warning: storage=95%% /usr/local/bin/quota-warning.sh 95 quota_warning2: storage=80%% /usr/local/bin/quota-warning.sh 80 My dovecot-ldap.conf configuration: hosts = Y.Y.Y.Y:389 dn = cn=abc,ou=def,dc=ghi,dc=jk dnpass = password auth_bind = yes ldap_version = 3 auth_bind_userdn = cn=abc,ou=def,dc=ghi,dc=jk base = ou= xyz,dc=abc,dc=def scope = subtree pass_attrs = uid=user,userPassword=password pass_filter = (&(objectClass=posixAccount)(uid=%u)) default_pass_scheme = CRYPT -- -------------------------------------------------------- LCC Wilberth de Jesús Pérez Segura CCSA- Administración de Servicios y Seguridad de las TI Correo: wilberth.perez(a)uady.mx Universidad Autónoma de Yucatán Secretaría General Coordinación Administrativa de Tecnologías de Información RIUADY C-59 x Av. Itzáes (999)923-74-28 Ext. 1117 Mérida, Yucatán, México 2010 --------------------------------------------------------

1 0

[Dovecot] R: Re: R: Re: Dovecot 2.0 shared mailbox using ACLs problem
by p.quidacciolu＠libero.it 15 Jun '10

15 Jun '10

...something is still wrong. On the shared folders the commands "select" and "examine" work only the first time: -------%<-------------------------------------------------------- 3 select "shared/user1(a)pec.inail.gov.it" * FLAGS (\Answered \Flagged \Deleted \Seen \Draft Junk) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft Junk \*)] Flags permitted. * 6 EXISTS * 0 RECENT * OK [UNSEEN 4] First unseen. * OK [UIDVALIDITY 1276393110] UIDs valid * OK [UIDNEXT 15] Predicted next UID * OK [HIGHESTMODSEQ 7] Highest 3 OK [READ-WRITE] Select completed. .... 3 select "shared/user1(a)pec.inail.gov.it" 3 NO Mailbox doesn't exist: shared/user1(a)pec.inail.gov.it -------%<-------------------------------------------------------- >----Messaggio originale---- >Da: p.quidacciolu(a)libero.it >Data: 14/06/2010 12.32 >A: <tss(a)iki.fi> >Cc: <dovecot(a)dovecot.org> >Ogg: R: Re: [Dovecot] R: Re: Dovecot 2.0 shared mailbox using ACLs problem > >Yesterday I have tried the 2.0beta6. It seems to work fine! >Thanks a lot. > >>----Messaggio originale---- >>Da: tss(a)iki.fi >>Data: 11/06/2010 17.28 >>A: "p.quidacciolu(a)libero.it"<p.quidacciolu(a)libero.it> >>Cc: <dovecot(a)dovecot.org> >>Ogg: Re: [Dovecot] R: Re: Dovecot 2.0 shared mailbox using ACLs problem >> >>On to, 2010-06-10 at 19:38 +0200, p.quidacciolu(a)libero.it wrote: >>> Hi, >>> now I'm able to share/access to the shared mailbox, >>> but when try to write (as owner) in each mailbox, I catch a segfault of >the >>> imap process. >>> In the next the trace. >>> I'm using "dovecot-2-0-2d6cf78982dc". >> >>Hopefully http://hg.dovecot.org/dovecot-2.0/rev/f37d19f1c0a3 fixes this >>crash? >> >> >> > >

2 1