January 2010 - dovecot

[Dovecot] how to create maildir on local mail delivery
by Sebastian Logar 24 Jan '10

24 Jan '10

Hi! I am using Dovecot 1.0.10 with LDA/postfix option reading user data from ldap, but the problem would be nonexistent maildir. Connection with ldap should be fine since reading proper maildir folder. Is it possible to auto creating maildir folders even on received mail since the you can auto create when user login with mail_executable scripts as it's seen from configuration I am doing for pop3 and imap. Jan 23 00:23:17 dovecot postfix/qmgr[14579]: 75AADD212F: from=<someuser(a)domain.tld>, size=354, nrcpt=1 (queue active) Jan 23 00:23:17 dovecot deliver(erikp): Loading modules from directory: /usr/lib/dovecot/modules/lda Jan 23 00:23:17 dovecot deliver(erikp): Module loaded: /usr/lib/dovecot/modules/lda/lib10_quota_plugin.so Jan 23 00:23:17 dovecot deliver(erikp): auth input: erikp Jan 23 00:23:17 dovecot deliver(erikp): auth input: home=/nas/5b/7d/5f/erikp/www Jan 23 00:23:17 dovecot deliver(erikp): auth input: uid=5000 Jan 23 00:23:17 dovecot deliver(erikp): auth input: gid=5000 Jan 23 00:23:17 dovecot deliver(erikp): auth input: mail=/nas/5b/7d/5f/erikp/Maildir/ Jan 23 00:23:17 dovecot deliver(erikp): auth input: quota=maildir:storage=100000000 Jan 23 00:23:17 dovecot deliver(erikp): Home dir not found: /nas/5b/7d/5f/erikp/www Jan 23 00:23:17 dovecot deliver(erikp): maildir autodetect: stat(/nas/5b/7d/5f/erikp/Maildir//cur) failed: No such file or directory Jan 23 00:23:17 dovecot deliver(erikp): mbox autodetect: data=/nas/5b/7d/5f/erikp/Maildir/ Jan 23 00:23:17 dovecot deliver(erikp): mbox autodetect: INBOX file: stat(/nas/5b/7d/5f/erikp/Maildir/) failed: No such file or directory Jan 23 00:23:17 dovecot deliver(erikp): mbox autodetect: has .imap/: stat(/nas/5b/7d/5f/erikp/Maildir//.imap) failed: No such file or directory Jan 23 00:23:17 dovecot deliver(erikp): mbox autodetect: has inbox: stat(/nas/5b/7d/5f/erikp/Maildir//inbox) failed: No such file or directory Jan 23 00:23:17 dovecot deliver(erikp): mbox autodetect: has mbox: stat(/nas/5b/7d/5f/erikp/Maildir//mbox) failed: No such file or directory Jan 23 00:23:17 dovecot deliver(erikp): Ambiguous mail location setting, don't know what to do with it: /nas/5b/7d/5f/erikp/Maildir/ (try prefixing it with mbox: or maildir:) Jan 23 00:23:17 dovecot deliver(erikp): Failed to create storage for 'erikp' with mail '/nas/5b/7d/5f/erikp/Maildir/' Jan 23 00:23:17 dovecot postfix/pipe[15537]: 75AADD212F: to=<erikp(a)somelocaldomain.tld>, relay=dovecot, delay=2146, delays=2146/0.02/0/0.02, dsn=4.3.0, status=deferred (temporary failure) dovecot -n # 1.0.10: /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap pop3 disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login mail_privileged_group: mail mail_debug: yes mail_executable(default): /usr/lib/dovecot/imap.sh mail_executable(imap): /usr/lib/dovecot/imap.sh mail_executable(pop3): /usr/lib/dovecot/pop3.sh mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv auth default: passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: quota: maildir:storage=100000 Regards, Sebastian

2 5

[Dovecot] feature question: local delivery from SMTP
by Phil Howard 23 Jan '10

23 Jan '10

Does Dovecot really need a separate MTA for inbound mail? Or can it receive SMTP directly if there is no forwarding to do? What about spam/virus filtering in that case? -- Phil Howard KA9WGN - ka9wgn(a)gmail.com

6 7

[Dovecot] Mail process plans: multiple connections in a process + idle processes
by Timo Sirainen 23 Jan '10

23 Jan '10

Maybe for v2.1: imap and pop3 processes can currently handle multiple connections, but they're assigned pretty much randomly to processes. It would be better if it was possible to: a) Require that a process handles only a specific user's connections b) Require that a process handles only a specific UNIX UID's connections (e.g. if each domain has a separate UID) c) Prefer to put user's connections to same process, but don't require it. To do this, there needs to be a process between imap/pop3-login and imap/pop3. Let's call it imap/pop3-tracker process (or aggregator? or any suggestions?). This process accepts all connections coming from login processes when they've finished authenticating a connection. Internally it figures out if the connection should go to a new or an existing process. It keeps track of username -> { mail_process[], cookie (see idle processes below) } mail_process -> { unix_socket_fd, connection_count } So there's a connection to each mail process. This connection is used to send connection fds for the process to handle. It's also used to receive notifications when a connection is closed. The mail process sockets could also be used to communicate to a specific process. For example doveadm could use this in future to ask what a specific user or process is currently doing, by connecting to imap-tracker, which forwards the request to wanted process(es). The above isn't really anything new, just a more specific plan about what I had been thinking for a long time. A new and more interesting idea is to gather IDLEing imap connections under a few imap-idle processes: When a connection has been IDLEing for a few minutes (or something), and there's no special state in the connection (e.g. CONTEXT=SEARCH searches), the connection could be moved to a separate imap-idle process that simply waits for something to happen. When something does happen, it'll move the connection back to imap process, which restores state and continues. The idea would be to reduce the number of idling imap processes that are wasting memory. The state that needs to be saved and restored is: - selected mailbox name, GUID, UIDVALIDITY (for reliably selecting back the original mailbox, or reliably fail if it's gone) - flag: mailbox is EXAMINEd, not SELECTed - highest seen modseq - UIDs of \Recent messages - SEARCHRES extension: last saved SEARCH result - List of keywords that had been advertised in FLAGS/PERMANENTFLAGS reply to client. Or probably MD5 sum of it would be enough. If MD5 had changed, the list would be re-sent to client. - connection fd - paths that are being monitored with [id]notify/kqueue Connection is moved back when a) new command is received from connection fd, b) one of the monitored files changes. The connections are moved back via imap-tracker process, by sending the saved state along the request. For security there's a per-user security cookie (128 bits of randomness), which is sent to imap processes, and when restoring connection from imap-idle, the request must provide the correct cookie or imap-tracker fails the login. (Normally new post-login imap/pop3 connections can't be created without having authenticated first via dovecot-auth. They verify it.) So when connection comes back, imap process opens the mailbox based on saved information. If this fails for some reason (e.g. mailbox deleted), client gets disconnected. Next Dovecot gets a list of changes to mailbox since the saved modseq, and based on that sends the missing FETCH, EXPUNGE, EXISTS and RECENT events. Again if it somehow fails, the client gets disconnected. At least initially this would only be done for connections that are running IDLE command, because non-IDLE connections are a lot more difficult to restore to their original state. This is mainly because if a message gets expunged, it's still visible to the connection until it issues a command that allows sending EXPUNGE event. To handle that, there would have to be code that allows building a view of mailbox where there are some expunged messages. Also it can be difficult to find out the expunged messages' flags, unless they're also part of the saved state.

1 1

[Dovecot] format of file dict
by Frank Cusack 22 Jan '10

22 Jan '10

For shared (between users) mailboxes, I am using a file dict. plugin { acl_shared_dict = file:/etc/dovecot/acl_shared_dict/shared.db } What is the format of this file? I would like to manage it directly rather than have SETACL update it. I see lines which describe a sharing entry (the format of those looks obvious) but also lines with just a '1'. Do I just need to separate entries by lines with just '1' in them? -frank

2 1

[Dovecot] Thinderbird+delete+move to Trash folder
by Papp Tamás 22 Jan '10

22 Jan '10

hi All, I have a problem, which makes me headache. I can't find out, what is the problem. I have a mail szerver, which works just fine as expected, TB move messages to trash folder after I delete it, and they are moved. I have an other server. If I delete a message, it doesn't move to the Trash folder. As deleted_to_trash plugin is installed, if I only mark messages as deleted, they are moved to thee Trash folder and also with Outlook works well. It's like when a messages is deleted from TB, the message get moved to the Trash folder, and it's expunged(?) at the same time. Is it possible? Could you help me? The system is Ubuntu 9.04 with docecot 1.2.5-0~auto+0 from http://xi.rename-it.nl/debian/, but builded by myself for x86_64. Thank you, tamas

6 15

[Dovecot] Modifying the underlying maildir externally (webmail, replication)
by Attila Nagy 22 Jan '10

22 Jan '10

Hello, I have a setup where there are multiple maildir users, one of them being the pop/imap server itself, the others are for example a maildir capable webmail and message replication. I would like to evaluate Dovecot, but I wonder how would its binary indexes and logs fit into this picture. After running through http://wiki.dovecot.org/IndexFiles I'm not sure how well would Dovecot work with other programs modifying the maildirs (adding, deleting, moving messages, folders etc). The "Main index" section says "The index file is synchronized against mailbox only if the syncing information changes.", where syncing information consists or cur and new directories' timestamps. Does that mean I am safe there? The cache file is hopefully just a cache, so it won't contain information from messages which are inserted or moved by an external program, and I assume Dovecot fetches the message lists and other information from the main index, which seems to be OK. The transaction log is for the main index, so if the latter is OK, the former should be OK too. http://wiki.dovecot.org/MailboxFormat/Maildir talks about MUAs and there nothing scary can be found, except for some temporary conditions, where the changes won't propagate to Dovecot in real time, but it's OK. Are the above right, and can Dovecot use its indexes and caches safely with others using the same maildirs? Thanks,

3 3

[Dovecot] ldap login with userid
by spamvoll＠googlemail.com 22 Jan '10

22 Jan '10

hi.. Dovecot Version 1.2.9 im trying to login to dovecot with my ldap uid. currently im using: user_attrs = homeDirectory=home,uid=mail=maildir:/mail/%$ user_filter = (&(objectClass=gosaMailAccount)(|(mail=%u)(gosaMailAlternateAddress=%u))) to match the mailaddress and deliver the mail to the users homdir (/mail/uid_of_the_user) But i cant login to dovecot: pass_attrs = uid=user,userPassword=password pass_filter = (&(objectClass=gosaMailAccount)(uid=%u)) the Log: Jan 22 17:21:51 testimap dovecot: auth(default): client in: AUTH 1 PLAIN service=imap secured lip=10.0.0.15 rip=10.0.0.20 lport=993 rport=36879 Jan 22 17:21:51 testimap dovecot: auth(default): client out: CONT 1 Jan 22 17:21:51 testimap dovecot: auth(default): client in: CONT 1 AG1zbWlhdGVrAHRpYWFrdGVuZXI= Jan 22 17:21:51 testimap dovecot: auth(default): ldap(myuser,10.0.0.20): bind search: base=dc=example,dc=com filter=(&(objectClass=gosaMailAccount)(uid=myuser)) Jan 22 17:21:51 testimap dovecot: auth(default): ldap(myuser,10.0.0.20): result: uid(user)=myuser Jan 22 17:21:51 testimap dovecot: auth(default): client out: OK 1 user=myuser Jan 22 17:21:51 testimap dovecot: auth(default): master in: REQUEST 1 2541 1 Jan 22 17:21:51 testimap dovecot: auth(default): passwd(myuser,10.0.0.20): lookup Jan 22 17:21:51 testimap dovecot: auth(default): passwd(myuser,10.0.0.20): unknown user Jan 22 17:21:51 testimap dovecot: auth(default): ldap(myuser,10.0.0.20): user search: base=dc=example,dc=com scope=subtree filter=(&(objectClass=gosaMailAccount)(|(mail=myuser)(gosaMailAlternateAddress=myuser))) fields=homeDirectory,uid Jan 22 17:21:51 testimap dovecot: auth(default): ldap(myuser,10.0.0.20): Unknown user Jan 22 17:21:51 testimap dovecot: auth(default): userdb(myuser,10.0.0.20): user not found from any userdbs Jan 22 17:21:51 testimap dovecot: auth(default): master out: NOTFOUND 1 Jan 22 17:21:51 testimap dovecot: imap-login: Internal login failure (auth failed, 1 attempts): user=<myuser>, method=PLAIN, rip=10.0.0.20, lip=10.0.0.15, TLS any ideas ?

2 1

[Dovecot] config file option to switch off CONDSTORE support?
by Harald Dunkel 22 Jan '10

22 Jan '10

Hi folks, Is there some config file option to switch off CONDSTORE support? Of course I checked the manual on the Wiki, but I haven't seen CONDSTORE mentioned at all. Forgive me if I am too blind to see. Many thanx Harri

2 1

[Dovecot] when does dovecot create a mailbox
by spamvoll＠googlemail.com 22 Jan '10

22 Jan '10

hi.. im using ldap. what happens when i add a new ldap user and that user tryes to login to dovecot ? does dovecot create the mailbox on first login? or do i have to send a mail first ? thx

2 1

[Dovecot] Files Moving From /New to /Cur
by Tony Rutherford 22 Jan '10

22 Jan '10

Using Dovecot 1.2-9 with Maildir and layout=FS. We have our own delivery pushing messages to the /new and then /cur folder eventually. When I have an IMAP client attached, there is apparently some sort of race going on. I believe that Dovecot is moving files from /new to /cur (and renaming them) before our own delivery gets the job done. This is causing a problem for us. Is there a way to disable this in Dovecot? I have the LDA section commented out of the config file..so I don't think that's in play. Bottom line is that I don't want Dovecot to move any files around whether an IMAP client is attached or not (except for handling the IMAP COPY/APPEND). Regards, Tony

2 2