- dovecot - dovecot.org

[Dovecot] newbie with dovecot acls needs a little help :-)
by Rachid Zarouali 22 May '07

22 May '07

hy all, i'm trying to make an acl so a local unix user 'sie' can access exalead mboxes. my exalead mboxes are stored in : /opt/exalead/mail/sie/ mailboxes are automatically created every week like sie.2007.W17 for the 17th week of the year. how can i do this ? i've tried several things but none succedded. dovecot version 1.0.rc15 # /etc/dovecot.conf ddIEffective uid=65534, gid=65534 ddILoading modules from directory: /usr/lib64/dovecot/imap ddIModule loaded: /usr/lib64/dovecot/imap/lib01_acl_plugin.so log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot-info.log protocols: imap imaps login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login login_greeting_capability: yes mail_extra_groups: exalead mail_location: mbox:/opt/exalead/mail mail_debug: yes mail_plugins: acl auth default: verbose: yes debug: yes passdb: driver: pam userdb: driver: passwd userdb: driver: prefetch socket: type: listen client: master: path: /var/run/dovecot/auth-master mode: 384 user: exalead group: exalead thanks for your help -- Rachid Zarouali Administrateur Systèmes/Applications AFNIC rachid.zarouali(a)nic.fr 01.39.30.83.47

2 2

[Dovecot] simultaneous access to folder
by David Lee 22 May '07

22 May '07

We have for many years been a UW-IMAP site, with users having their own traditional, private, mbox-format INBOX and folders: almost (but not quite) no complications of shared or simultaneous access. We have just completed a transparent transition to dovecot (official 1.0.0 release). But we have one residual issue affecting one important user account. UW-IMAP specifically only allows single access to "mbox" folders. If different IMAP connections are attempted to such a folder, the latest attempt kills off earlier connections. (That's just the way it works, which was mostly fine for us.) On this particular account we had explicitly set two folders to UW-IMAP's different "mbx" format, so that a group of staff could simultaneously access that folder and delete messages. This is by a single, common, id/pw account. But dovecot doesn't support "mbx" format. Is there a way for us to set up such a group-access folder under dovecot? I've checked wiki pages such as "http://wiki.dovecot.org/SharedMailboxes" but that doesn't seem to be clear on the particular matter of which formats are suitable for such simultaneous access. It talks about different users accessing a folder; in our case it is multiple instances of the the same user. Under dovecot, can we simply let it be "mbox" format? And can dovecot (unlike UW-IMAP) then handle the simultaneous access? [Background: this is just two folders (amongst many) on one username; the overall service successfully handles over 15,000 usernames. And the solution (work-around) will only need to last a few months until that whole account is Exchange-ified (but let's not digress...!)] If I've missed something on the wiki which addresses this matter, point me in the right direction... -- : David Lee I.T. Service : : Senior Systems Programmer Computer Centre : : UNIX Team Leader Durham University : : South Road : : http://www.dur.ac.uk/t.d.lee/ Durham DH1 3LE : : Phone: +44 191 334 2752 U.K. :

2 1

[Dovecot] [PATCH] add some const's
by Andrey Panin 22 May '07

22 May '07

Add some const's. I think patch is self-explaining :) -- Andrey Panin | Linux and UNIX system administrator pazke(a)donpac.ru | PGP key: wwwkeys.pgp.net

2 1

Re: [Dovecot] No authentication sockets found
by Stewart Dean 22 May '07

22 May '07

Back on 5/9, I made a post by this subject http://dovecot.org/list/dovecot/2007-May/022482.html Timo replied: > The error message means that /var/run/dovecot/login directory or its > contents was deleted while Dovecot was running. I'd guess that you start > Dovecot too early and after startup another script goes and deletes the > entire /var/run/ directory. Or maybe that's done in background. Or > something.. and funkypunkydrunky reported: > I have lived the same problem in my system. But not evrytime sometimes it > only happens when i restart dovecot while mta is working. I think postfix > (my mta) cannot connect the new authentication socket. If i need the > restarting dovecot, i restart postfix too. It happens only for the above > situation. This happened again under these circumstances: 1) The machine had been up for 5 days. Having made some changes (largely de-verbosifying the dovecot.conf file), I killed the master dovecot process and restarted it (this before I was informed I could just do a kill -1 to effect the same result with less trouble). > May 14 15:34:09 mercury mail:info dovecot: Dovecot v1.0.0 starting up > > 2) Using TBird a an imap client, I got back on > May 14 15:24:48 mercury mail:info dovecot: auth(default): client out: CONT 1 > May 14 15:24:48 mercury mail:info dovecot: auth(default): client in: CONT 1 AHNkZWFuAEFsYW1hcjJi > May 14 15:24:48 mercury mail:info dovecot: auth(default): pam(sdean,10.20.10.75): lookup service=dovecot > May 14 15:24:49 mercury mail:info sendmail-SndRcv[2220248]: l4EJOief2949348: to=<cooper(a)bard.edu>, delay=00:00:01, xdelay=00:00:01, mailer=local, pri=36928, dsn=2.0.0, stat=Sent > May 14 15:24:49 mercury mail:info dovecot: auth(default): client out: OK 1 user=sdean > May 14 15:24:49 mercury mail:info dovecot: auth(default): master in: REQUEST 6 909440 1 > May 14 15:24:49 mercury mail:info dovecot: auth(default): passwd(sdean,10.20.10.75): lookup > May 14 15:24:49 mercury mail:info dovecot: auth(default): master out: USER 6 sdean system_user=sdean uid=202 gid=200 home=/home/hcrc/sdean > May 14 15:24:49 mercury mail:info dovecot: imap-login: Login: user=<sdean>, method=PLAIN, rip=10.20.10.75, lip=192.246.229.21, TLS > May 14 15:24:49 mercury mail:info dovecot: IMAP(sdean): Effective uid=202, gid=200, home=/home/hcrc/sdean > May 14 15:24:49 mercury mail:info dovecot: IMAP(sdean): mbox: data=/home/hcrc/sdean/mail:INBOX=/var/spool/mail/sdean:INDEX=/var/dcndx/sdean > May 14 15:24:49 mercury mail:info dovecot: IMAP(sdean): mbox: root=/home/hcrc/sdean/mail, index=/var/dcndx/sdean, inbox=/var/spool/mail/sdean > > > 3) 15 seconds after that, I started seeing a slew of these error messages, every 15 seconds or so: > May 14 15:25:03 mercury mail:info imapd[2052334]: Logout user=ot119 host=[10.20.10.10] > May 14 15:25:04 mercury mail:err|error dovecot: imap-login: No authentication sockets found > May 14 15:25:04 mercury mail:err|error dovecot: child 835676 (login) returned error 89 > 4) Since this is the production server, I kill the master dovecot instance and reinvoke dovecot in the foreground. I haven't seen the problem again since....but twice is problematic with just 3 people using DC. Now. My thoughts about what has been suggested so far, first by Timo: 1) This machine had been booted 5 days before so it's not a boot related problem 2) I'd find it hard to believe that something is nuking the contents of /var/run because: a) The directory doesn't exist by default in AIX; I created it for the DC install b) I have cron jobs that do cleanup with /var/log, /var/log/arc and /var/spool/mqueue, but nothing that does anything to /var/run 3) /var/run is local to the DC host and is not exported 4) funkypunkydrunky's comments about interaction with the MTA (sendmail in my case) seem unlikely, since it doesn't use SSL...or the same ports My questions: 1) What is happening? This is OpenSSL related, yes? 2a) Will this affect my production UWIMAP (which also supports/utilizes SSL)? If it doesn't, I can take my time debugging it (given that there are only 3 IT guys using DC currently), instead of frantically shutting it up by rebooting ASAP. I /think/ previously established DC connections continued to work 2b) How will this affect other imaps DC nex and pre-extant connections? I'm thinking of putting the whole IT dept on DC, but it'd be good to know how flaky things would get if/when this happens again. 3) What can I do to debug it, given that it happens infrequently and of no known causation? What should I check and look for afterwards? I guess I could put a cronjob that checks that /var/run/dovecot/login/ default= and ssl-parameters.dat exists periodically ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

3 5

[Dovecot] per user quota using LDAP entries
by Kenneth Oncinian 22 May '07

22 May '07

Hi List, This is my first post to this list so please be gentle :-). First of all, kudos to the developers of dovecot! Im trying to implement quota, and I followed the instructions in the wiki. My problem is the quota specified per user is not being honored, only the global quota setting. I do have an "quota = maildir:storage=204800" in the plugin area and enabled quota in the mail_plugins for both imap and pop3. This is my user attribute in /etc/dovecot-ldap.conf: user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid,mailQuota=quota wherein the "mailQuota" attribute has an entry of "mailQuota: maildir:storage=30720". So i was expecting of a 300MB quota for that user, but dovecot is using the global quota of 200MB instead of 300MB. My dovecot version is 1.0.0 My dovecot.conf: ----------------------- # /etc/dovecot.conf log_path: /var/log/dovecot.log protocols: imap pop3 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_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no mail_location: /var/mail/vhost/%u mail_debug: yes maildir_copy_with_hardlinks: yes maildir_copy_preserve_filename: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/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/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: passwd userdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: prefetch plugin: quota: maildir:storage=204800 trash: /etc/dovecot-trash.conf --- my dovecot-ldap.conf ------------------------------------------ hosts = localhost.localdomain dn = "cn=Directory Manager" dnpass = "xxxxxx" tls = no auth_bind = no ldap_version = 3 base = ou=people, dc=xx, dc=xx, dc=xx user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid,mailQuota=quota pass_attrs = uid=user,userPassword=password pass_filter = (&(objectClass=posixAccount)(uid=%u)) default_pass_scheme = LDAP-MD5 -------------- sample LDAP query: ------------------------------ ldapsearch -x -Z '(uid=kenneth.oncinian)' # LDAPv3 # base <> with scope sub # filter: (uid=kenneth.oncinian) # requesting: ALL # # kenneth.oncinian, People, ph.panasonic.com dn: uid=kenneth.oncinian,ou=People, dc=xx,dc=xx,dc=xx givenName: Kenneth sn: Oncinian telephoneNumber: xxx-xxxx loginShell: /bin/bash gidNumber: 2516 uidNumber: 1000 mail: kenneth.oncinian(a)xx.xx.xx facsimileTelephoneNumber: xxx xxxx objectClass: top objectClass: person objectClass: organizationalPerson objectClass: inetorgperson objectClass: posixAccount objectClass: account objectClass: mailgroup objectClass: mailgroupmanagement objectClass: mailgroupmanagement-globalconfig objectClass: mailgroupmember objectClass: mailrecipient objectClass: netscapemailserver objectClass: nsmailclient objectClass: ntuser objectClass: sambaSamAccount objectClass: proxyaccess objectClass: jabberaccess uid: kenneth.oncinian preferredLanguage: en cn: Kenneth Oncinian homeDirectory: /var/mail/vhost/kenneth.oncinian ou: Information Systems Department (ISD) x500UniqueIdentifier: mailAlternateAddress: koncinian(a)gmail.com ntUserDomainId: kenneth.oncinian ntUserCreateNewAccount: true ntUserDeleteAccount: true sambaSID: S-1-5-21-1685363153-499155089-1962420841-3000 sambaPrimaryGroupSID: S-1-5-21-1685363153-499155089-1962420841-3001 displayName: Kenneth Oncinian sambaPwdMustChange: 2147483647 sambaPasswordHistory: 00000000000000000000000000000000000000000000000000000000 00000000 sambaAcctFlags: [U ] myproxyaccess: yes myjabberaccess: yes sambaPwdCanChange: 1179303932 sambaLMPassword: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx sambaNTPassword: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx sambaPwdLastSet: 1179303932 mailQuota: maildir:storage=30720 # search result search: 3 result: 0 Success # numResponses: 2 # numEntries: 1 -- snip-- thanks and best regards, Kenneth

2 2

[Dovecot] Something about IMAP log
by Mu-Cheng Hsieh 22 May '07

22 May '07

Hi When the user used POP3 to handle her/his mailbox, we could know something happened as below. May 16 10:16:29 server dovecot: [ID 107833 local5.info] POP3(user): Disconnected: Logged out top=675/723063, retr=0/0, del=1/675, size=18124546 However, if the user used IMAP, we can not know what happened. May 18 15:25:42 server dovecot: [ID 107833 local5.info] IMAP(user): Disconnected: Logged out Is it possible to log something (e.g. delete or expunge) through IMAP? Thanks. -- Mu-Cheng Hsieh

2 1

Re: [Dovecot] Conflict -> Dovecot + Maildrop (maildirsize)
by Kenny Dail 21 May '07

21 May '07

> As I said in my original mail, this is simply a configuration issue: > > Looks like you're trying to tell the quota in bytes to Dovecot. Dovecot > wants it to be in kilobytes in its configuration file / userdb (it still > writes it in bytes to maildirsize, as you can see above it writes 1GB * > 1024 value in there). > > Where do you get the quota value for Dovecot? Divide it by 1024 and > it'll work right. I also use maildrop + dovecot. My quotas are stored in a mysql DB in couriers expected format: 50000000S (note the S on the end for storage). It makes for a very ugly userdb query trying to get that formatted to dovecot style of "maildir:storage=48828:ignore=Trash" How much would it take to allow dovecot's quota plugin to alternately accept "maildir:50000000S:ignore=Trash"? -- Kenny Dail <kend(a)amigo.net>

2 1

[Dovecot] Conflict -> Dovecot + Maildrop (maildirsize)
by Roberto Gonzalez Azevedo 21 May '07

21 May '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm having some problems with quota from sql (maildir++) and dovecot + maildrop. I'm using maildrop for MDA and dovecot as IMAP server. When an e-mail arrives, maildrop calculates the quota and updates the 'maildirsize' file. When i use dovecot (webmail, thunderbird) it updates the 'maildirsize' too, overwriting it, but in a different way. Both programas don't use the same pattern for 'maildirsize'. Let me show: 'maildirsize' with maildrop: " 1073741824S 117395679 1760 3675 1 3675 1 1610 1 1612 1 3222 2 9641 1 9641 1 5301 1 6415 1 11716 2 15419 1 15419 1 " 'maildirsize' with dovecot: " 1099511627776S 585847701 102542 5504023 959 " In both examples the quota is 1GB (1073741824S). And now ? Does anybody known how to fix that ? thanks - -- - ---------------------------- Roberto Gonzalez Azevedo Rio de Janeiro, Brazil -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFGQcttF+EMwkXLsEwRAoUOAKC0VXeC4USHyxOhsE5TQixk77hpmwCgxk5P ABOk8XHurCx/gEnd5StCkB8= =B+0f -----END PGP SIGNATURE-----

3 6

[Dovecot] mail_location %d expansion
by Mark Par 21 May '07

21 May '07

hi, i'm trying to read the mails of virtual users by setting the value of mail_location to /mail/virtual/%d/%u/Maildir. however, the %d does not resolve to the domain. i am using ldap as my passdb and userdb. what am i missing here? using this telnet session, | $ telnet localhost imap | Trying 209.235.254.94... | Connected to localhost | Escape character is '^]'. | * OK Dovecot ready. | 1 login foo.bar(a)mydom.com TopSecret | 1 OK Logged in. | 2 select inbox | 2 NO Internal error occurred. Refer to server log for more information. [2007-05-21 04:32:42] here are the relative entries from the log: | May 21 04:32:42 localhost dovecot: auth(default): auth(iris.lames(a)pointwest.com.ph,xx.xx.xx.xx): username changed foo.bar(a)mydom.com -> foo.bar | May 21 04:32:42 localhost dovecot: auth(default): ldap(foo.bar,xx.xx.xx.xx): result: uid(user)=foo.bar uidNumber(userdb_uid)=2301 gidNumber(userdb_gid)=2301 userPassword(password)=TopSecret | May 21 04:32:42 localhost dovecot: auth(default): client out: OK 1 user=foo.bar | May 21 04:32:42 localhost dovecot: auth(default): master in: REQUEST 3 99112 1 | May 21 04:32:42 localhost dovecot: auth(default): prefetch(foo.bar,xx.xx.xx.xx): success | May 21 04:32:42 localhost dovecot: auth(default): master out: USER 3 foo.bar uid=2301 gid=2301 | May 21 04:32:42 localhost dovecot: imap-login: Login: user=<foo.bar>, method=PLAIN, rip=xx.xx.xx.xx, lip=xx.xx.xx.xx, secured | May 21 04:32:42 localhost dovecot: IMAP(foo.bar): mkdir(/mail/virtual//foo.bar/Maildir/cur) failed: Permission denied | May 21 04:32:59 ptwest1 dovecot: IMAP(foo.bar): mkdir(/mail/virtual//foo.bar/Maildir/cur) failed: Permission denied dovecot --version: 1.0rc29 dovecot.conf: ssl_disable: yes ssl_cert_file: ssl_key_file: disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login verbose_proctitle: yes first_valid_gid: 0 mail_extra_groups: mail mail_location: maildir:/share/mail/virtual/%d/%u/Maildir imap_client_workarounds: delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf userdb: driver: prefetch dovecot-ldap.conf: auth_bind = no hosts = localhost base = dc=mycompany,dc=com dn = uid=dovecot,ou=auth,dc=mycompany,dc=com dnpass = TooMuchToAsk pass_attrs = uid=user,userPassword=password,uidNumber=userdb_uid,gidNumber=userd b_gid pass_filter = (&(objectClass=posixAccount)(uid=%n)) default_pass_scheme = PLAIN ldap_version = 3

2 1

[Dovecot] LDAP for Virtual Domains
by Bryan Vyhmeister 21 May '07

21 May '07

Is anyone using LDAP along with Dovecot where mail is being accessed in the form of /var/vmail/${domain}/${user}? I have not figured out how to extract the domain from LDAP in order to make this work. I know this is sparse information but maybe there is an easy fix. If not, I can post more information. Bryan

6 13

[Dovecot] [Blasphemy] Can I build dovecot with "-fstack-protector"?
by Ralf Hildebrandt 21 May '07

21 May '07

I tried building dovecot using : CPPFLAGS="-fstack-protector" LDFLAGS="-lssp" ./configure That would result in a proper build, yet the binary would complain once being run: dlopen(/usr/local/lib/dovecot/imap/lib10_quota_plugin.so) failed: /usr/local/lib/dovecot/imap/lib10_quota_plugin.so: undefined symbol: __stack_chk_fail_local Error: imap dump-capability process returned 89 and the like. So: Is it possible at all? And sorry for the blasphemy of daring to ask this in the first place :) -- Ralf Hildebrandt (Ralf.Hildebrandt(a)charite.de) plonk(a)charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de First Law of System Requirements: "Anything is possible if you don't know what you're talking about..."

3 14

[Dovecot] NFS lock contention for dovecot-uidlist
by Doug Council 21 May '07

21 May '07

We are in the process of migrating away from Courier-IMAP/POP3 and Maildrop. I want to use Dovecot (LDA, IMAP, POP3). During my testing, it has worked great except for dotlocking on the dovecot-uidlist file. The problem: When a delivery is being made with deliver and a mail client has the mailbox open (Thunderbird in this case), neither Thunderbird or deliver can get a dotlock on the dovecot-uidlist file, causing both deliver and Thunderbird to hang until the dotlock timeout runs out and the lock gets replaced. Once the lock is replaced, both will go about their business until the next lock miss and hang again. Eventually, everything is delivered and Thunderbird wakes up. Looking at each of the processes with truss, they are looping trying to stat the dotcot-uidlist.lock file, which no longer exists. We are using NFS, and based on reading through the mailing list archives, it can be a little difficult to get working reliably. But, I've read quite a few posts with our same or similar configuration having good luck with the setup. To reduce multiple box access-issues for now, I've been doing all testing with a single NFS client. Our configuration: NetApp filers for storage FreeBSD 6.2-RELEASE NFS clients Postfix 2.3.9 MTA Dovecot 1.0.0 LDA for local deliveries Dovecot 1.0.0 IMAP for pickup My dovecot.conf file is at the end of this message. NFS access cachcing on the FreeBSD has been disabled (vfs.nfs.access_cache_timeout = 0, see NFS mount options below). Postfix destination recipient and concurrency limit for the Dovecot LDA is set to 1. The NFS mount options: rw,tcp,-r=32768,-w=32768,nfsv3,dumbtimer,noatime,acregmin=0, acregmax=0,acdirmin=0,acdirmax=0 The dovecot.conf file: protocols = imap imaps pop3 pop3s disable_plaintext_auth = no syslog_facility = local0 ssl_cert_file = /nethere/conf/dovecot/ssl-nh-cert.pem ssl_key_file = /nethere/conf/dovecot/ssl-nh-key.pem login_greeting = Server ready. login_log_format_elements = user=<%u> ip=[%r] method=%m encryption=%c pid=%p login_log_format = %U$: %s mail_location = maildir:~/Maildir:INDEX=MEMORY mmap_disable = yes dotlock_use_excl = no lock_method = dotlock first_valid_uid = 200 last_valid_uid = 200 first_valid_gid = 200 last_valid_gid = 200 maildir_copy_with_hardlinks = yes namespace private { prefix = INBOX. inbox = yes } protocol imap { login_executable = /usr/local/libexec/dovecot/imap-login mail_executable = /usr/local/libexec/dovecot/imap imap_client_workarounds = outlook-idle delay-newmail } protocol pop3 { login_executable = /usr/local/libexec/dovecot/pop3-login mail_executable = /usr/local/libexec/dovecot/pop3 pop3_uidl_format = UID%u-%v pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } protocol lda { postmaster_address = postmaster(a)nethere.com sendmail_path = /usr/sbin/sendmail auth_socket_path = /var/run/dovecot/auth-master syslog_facility = mail } auth_executable = /usr/local/libexec/dovecot/dovecot-auth auth default { mechanisms = plain digest-md5 cram-md5 passdb ldap { args = /nethere/conf/dovecot/dovecot-ldap.conf } userdb ldap { args = /nethere/conf/dovecot/dovecot-ldap.conf } user = root socket listen { master { path = /var/run/dovecot/auth-master mode = 0600 user = mailuser group = mailuser } } } It may just be "how it works", but the lock contention seems a little too fragile for busy mailboxes. Does anyone have any ideas? Thanks in advance for any assistance. -Doug

2 3

Re: [Dovecot] LDAP for Virtual Domains
by Bryan Vyhmeister 21 May '07

21 May '07

On May 18, 2007, at 11:33 PM, Daniel L. Miller wrote: >> Thank you for that info. Do you mind posting the relevant portions >> of your Postfix config? > main.cf: > .... > virtual_mailbox_base = /var/mail > virtual_mailbox_domains = <all your external / internal domains here> > virtual_mailbox_maps = ldap:/etc/postfix/maps/ldap-virtual.cf > virtual_uid_maps = static:5000 > virtual_gid_maps = static:8 > virtual_alias_maps = hash:/etc/postfix/maps/virtual-aliases > .... > ##EOF > > ldap-virtual.cf: > server_host = localhost > search_base = ou=People,dc=amfeslan,dc=local > query_filter = (&(mail=%s)) > result_attribute = mail > result_format = /%d/%u/ > version = 3 > > The ldap-virtual settings look a little odd - but I'm rather proud > of my gimmick. You look for the mail address matching the sender > (mail = %s). Return that same address - but format it as domain/ > user. Append it to /var/mail and there it is! > > virtual-aliases is a simple file for me - I haven't settled on an > LDAP implentation for aliases yet I'm satisfied with. I'm using > ldap-account-manager for adminstration, and there's no explicit > provision for aliases within LAM or the base schemas used. I just asked Pascal as well how he gets around Postfix asking for mailacceptinggeneralid in order to allow messages to be accepted. How do you get around that? Dovecot is working fine but I can't get Postfix to accept messages because it keeps trying to find mailacceptinggeneralid. Bryan

3 3

[Dovecot] per-user delivery to commands
by martin f krafft 20 May '07

20 May '07

Hi, we are using dovecot IMAP in a complex virtual setup with almost 4000 accounts; postfix hands over to deliver for local delivery into a home directory as stored in the SQL database. That's /srv/vmail/$DOMAIN/$LOCALPART for most of them, but I'd rather not hardcode this scheme anywhere as it's in SQL. By a policy change, we need to insert a filter in this chain and the filter must be called in such a way that it knows where to find the "home" directory since the command needs to read a configuration file in ~/.mailfilt.rc. Thus I am looking for a way to make deliver pass incoming messages via this filter, but I cannot find any way to do that. Ideally I want this to happen before the LDA runs the mail through sieve. As an alternative, is there a command I can call to make dovecot look up $HOME for me so that I can use the dovecot data in the SQL database without making assumptions about the representation? A command that would proxy and convert my request into an SQL select as per dovecot.conf and feed back the result? Then I could use a Maildir delivery programme or even procmail to do the delivery according to the dovecot configruation. Thanks for any insights, hints, tips, help, jokes, flames, and useful information. -- martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck spamtraps: madduck.bogus(a)madduck.net will kill for oil!

1 1

[Dovecot] CVS to Mercurial switch
by Timo Sirainen 20 May '07

20 May '07

I've been meaning to switch away from CVS for a few years now, but I was never sure what I wanted to switch to, so I kept delaying it. I finally decided yesterday that Mercurial is pretty nice. The Mercurial repository is available from http://hg.dovecot.org/ (has a nice web interface). I wrote a small Mercurial mini-howto below. I'm not a Mercurial expert yet, so if you know better ways to do some things please let me know. The CVS repositories will still exist for a while, but they won't be updated anymore. If you notice the CVS being referenced somewhere (wiki, docs, etc.) please let me know (or fix yourself in wiki). 1. Fetch the initial repository: - ex. CVS HEAD: hg clone http://hg.dovecot.org/dovecot/ - ex. branch_1_0: hg clone http://hg.dovecot.org/dovecot-1.0/ - sieve plugin: hg clone http://hg.dovecot.org/dovecot-sieve-1.0/ The Sieve plugin currently works only with v1.0. I'll make a new "dovecot-sieve" repository for CVS HEAD later. 2. Update the repository: hg pull hg merge # only needed if you had done any changes hg update # to actually see the pulled changes All of this can be done with fetch extension. You can enable it by adding to ~/.hgrc: [extensions] hgext.fetch = After that you can use "hg fetch" which does all the above 3 commands (as far as I know, haven't really tried yet). 3. If you want to modify the sources, add your name to ~/.hgrc so it goes nicely into changelogs: [ui] username = Timo Sirainen <tss(a)iki.fi> You're able to "hg commit" your own changes into your repository. If you want to publish them, use "hg log" to see the changeset ID, and then use "hg export changesetid" to get patch ("hg export tip" might work too if you just want the last change(?)). You can then email the patch to Dovecot mailing list to get it merged. With CVS the ChangeLog file was updated every 15 minutes. Now the ChangeLog file doesn't exist in the repository at all. Instead it's generated with "hg log --style=changelog" when running "make dist".

6 12

Re: [Dovecot] LDAP for Virtual Domains
by Bryan Vyhmeister 20 May '07

20 May '07

On May 18, 2007, at 11:33 PM, Daniel L. Miller wrote: >> Thank you for that info. Do you mind posting the relevant portions >> of your Postfix config? > main.cf: > .... > virtual_mailbox_base = /var/mail > virtual_mailbox_domains = <all your external / internal domains here> > virtual_mailbox_maps = ldap:/etc/postfix/maps/ldap-virtual.cf > virtual_uid_maps = static:5000 > virtual_gid_maps = static:8 > virtual_alias_maps = hash:/etc/postfix/maps/virtual-aliases > .... > ##EOF > > ldap-virtual.cf: > server_host = localhost > search_base = ou=People,dc=amfeslan,dc=local > query_filter = (&(mail=%s)) > result_attribute = mail > result_format = /%d/%u/ > version = 3 > > The ldap-virtual settings look a little odd - but I'm rather proud > of my gimmick. You look for the mail address matching the sender > (mail = %s). Return that same address - but format it as domain/ > user. Append it to /var/mail and there it is! > > virtual-aliases is a simple file for me - I haven't settled on an > LDAP implentation for aliases yet I'm satisfied with. I'm using > ldap-account-manager for adminstration, and there's no explicit > provision for aliases within LAM or the base schemas used. Thank you. I'll try this out. Bryan

1 0

[Dovecot] IMAP "freezing" on OSX
by Ben Carter 20 May '07

20 May '07

Hi, I've got a problem with dovecot on an Intel Mac OSX box. Basically, I was running an older verion (0.8.?, I think), and everything was fine. Then, when I upgraded to 1.0.0 via MacPorts, I found that periodically the system gets into a state where it simply stops dealing with IMAP requests. This tends to manifest itself as Thunderbird simply stalling, not fetching any new messages or folder contents. Sometimes quitting and restarting Thunderbird will help, but at other times the problem persists even afterwards. It seems to be linked to specific mailboxes (or messages?) - often one "problem folder" will reproduce the effect 100% whilst operating on the rest of the mailbox is fine. The problem /seems/ to often start as a result of trying to move messages between folders. I'm not certain if that's a root cause, though, or simply a consequence of "opening" an affected folder to perform the move. I have a spam folder with a large number (>10000) of messages in it, and trying to file stuff in there is a relatively surefire way to generate the problem. Once it's happened once, it inevitably escalates - restarting the client helps a bit, as does restarting dovecot. However, the only way to "fix" it and restore full functionality seems to be to delete all of the index and dovecot* files from the mailbox and folders... it generally takes a day or so after that before things start to go wrong again. All of this seems to point to corruption of the index files in some way, but the log is universally unhelpful - there are no error messages of any kind showing up there. The actual dovecot instance doesn't appear to crash or even "hang" properly - you can still make inbound IMAP connections OK, it's just that they don't ever give a response to commands that touch the affected mailboxes. Sometimes, I end up with temporary files lying around in the folders in the mailbox - apparently mails which were in the process of being moved when the server "gave up". I'm not sure if this is actually part of the problem, though, or just a symptom. My configuration (from dovecot -n) is: # /opt/local/etc/dovecot/dovecot.conf ssl_disable: yes disable_plaintext_auth: no login_dir: /opt/local/var/run/dovecot/login login_executable: /opt/local/libexec/dovecot/imap-login mail_location: maildir:~/Library/Mail/IMAP auth default: passdb: driver: pam args: * userdb: driver: passwd I'm running this on my personal machine, so there's only one user on the system, which I have set up using MailDir (on HFS). There's a fair bit of mail in many of my folders, but I doubt that's the problem as the previous version didn't seem to have any issues... I'm doing mail delivery using postfix directly into the maildir folders. That doesn't seem to be affected at all by this, though - mail still arrives fine even when Dovecot is failing to serve the folder contents to IMAP clients... you just can't see it ^-^ Has anyone seen an effect like this? Or does anyone have any pointers as to what I could try to debug it? Any suggestions would be very greatly appreciated! Thanks! -- Ben Carter - ben(a)gunk.demon.co.uk / ben(a)saillune.net (preferred)

4 6

[Dovecot] Thinking Outside the Box - Extending IMAP
by Marc Perkel 19 May '07

19 May '07

Here's some thoughts I'd like to throw out there. I know it's not standard IMAP protocol but someone has to try new ideas first and I want to see what people (Timo) think of this. IMAP establishes a connection between the client and the server. Wouldn't it be great if it could be a conduit to let custom Thunderbird plugins talk to custom server application over the IMAP interface? For example, personalized server settings. Suppose for example I want Thunderbird to edit my server side white lists or black lists or any other setting? Wouldn't it be nice if IMAP supported these changes? The connection is made. It's a secure connection that's been authenticated. Lets use it! Here's my initial thoughts on this. Suppose we extended IMAP to include an EXECUTE command as follows: EXECUTE command parameter, parameter .... On the server side is a config file that has the commands that execute will allow and what programs they run. When the execute command is seen by Dovecot then Dovecot runs the program in the list with the parameters passed. For example, suppose there is a command to add a user to a server side blacklist. 100 execute blacklist add joe(a)smith.com 100 ok Dovecot would open a two way connection to the server application allowing the client to talk to any application that is configured and can send and receive text. The connection persists until the server end terminates or the client closes the connection. With a tool like this one can write generic applications easily that would greatly expand what email clients can do interacting with the server. Not only can setting be changes but you could interact with server side calendars, pick up voice messages from phone systems, run any sort of groupware, all over a generic IMAP connection with this simple extension. Example: 100 EXECUTE calendar 100 ok 100 list schedule today 8:00 10:00 100 8:00 make coffee 100 9:00 meeting with boss 100 9:30 Call Joe Blow at 415-555-1212 100 ok 100 quit 100 ok One thing I'd like to use it for is an outgoing SMTP connection to send outgoing email over IMAP. A session might look like this: 999 EXECUTE smtp 999 220 darwin.ctyme.com ESMTP Exim 4.67 Sun, 13 May 2007 06:52:26 -0700 999 helo ctyme.com 999 250 darwin.ctyme.com Hello localhost [127.0.0.1] 999 mail from:marc@perkel.com 999 250 OK 999 rcpt to:dovecot@dovecot.org 999 250 Accepted ...... 999 quit 999 OK Who likes this idea?

10 23

[Dovecot] [Fwd: An invitation to the "morg" (Message Organization) mailing list]
by Luigi Rosa 19 May '07

19 May '07

This messages has been posted on SquirrelMail development mailing list. Maybe someone is interested in morg mailing list. Ciao, luigi -------- Original Message -------- Subject: [SM-DEVEL] An invitation to the "morg" (Message Organization) mailing list Date: Sat, 19 May 2007 17:08:03 +0300 To: squirrelmail-devel(a)lists.sourceforge.net Hello all, [Note: Yes, I'm not gone after all... There has been a change of plans! I'll be mostly active, time permitting] There is a new IETF effort on IMAP standards, continuing on the work of "IMAPExt" Working Group which has practically closed now. I'm sending this here because people might be interested in joining it and either contributing actively or simply keeping an eye on what will be available in IMAP servers soon. Personally I'm very interested on message and mailbox annotations / metadata, but some other stuff like dynamic, multi-mailbox, persistent searches and virtual mailboxes might be of more interest to you. Anyway, you can join this effort by subscribing to the morg mailing list: https://www1.ietf.org/mailman/listinfo/morg http://www.ietf.org/maillist.html To quote Dave Cridland about the purpose of the list: ====== Quote start ======== This list has been created to look carefully at how existing mail clients search through, sort, and generally organize email. We're also going to - hopefully - have client developers talk about what they'd like to be able to do. There's another group that might be interested in this, too - the "desktop search" people might well be interested in the ability to search effectively through remote message stores. Kjetil commented (on IMAPEXT) that this area might be very interesting to IMAP webmail people, who can't simply download everything and work locally, so if there are any IMAP webmail developers about it'd be interesting to hear from you, and if anyone knows any, please invite them to join. Meanwhile, we're also going to look at what features we have on the store - the IMAP server - that we can leverage for this. There's a number of RFCs and Drafts in the area of searching, organization, etc, and we'll need to ensure we're all aware of the current state of play. So, IMAP specialists need to start to enumerate these - any volunteers? It occurs to me that both the above might benefit from a Wiki page or two - Lisa, is there an Apps Wiki we can use for this, or should I just set one up? [For anyone new to the IETF, Lisa and Chris are the Applications Area Directors] Finally, we'll look at what new work we can do to satisfy client requirements, write up a draft charter, and move to BOF (the first stage in forming a new IETF working group), aiming to form a new working group to do the work, and produce RFCs as we decide is appropriate. I'd like to take a decision on going down this road after Chicago in the summer, hopefully ready for a BOF at the IETF in December. I personally think our ultimate output is likely to be some Standards Track and some Experimental specifications for extensions, and maybe a couple of Informational documents on how this stuff ties together. I'd also note that searching is something that, like a lot of IETF work, has patent minefields in places - please do read that Note Well stuff, and let us know of any IPR you're aware of as soon as you can. ====== Quote end ======== -- / +--[Luigi Rosa]-- \ Sheridan: We have an open door policy. Ivanova: And an open airlock policy. --"The Illusion of Truth", Babylon 5

1 0

[Dovecot] permissions on some dovecot directories
by Arkadiusz Miskiewicz 19 May '07

19 May '07

Hello, What smallest permissions are needed on directories: /var/run/dovecot /var/run/dovecot/login /var/lib/dovecot dovecot run as dovecot:dovecot. Currently I have 775 dovecot:dovecot /var/run/dovecot 750 root:dovecot /var/run/dovecot/login 755 root:root /var/lib/dovecot -- Arkadiusz Miśkiewicz PLD/Linux Team arekm / maven.pl http://ftp.pld-linux.org/

1 0

[Dovecot] Maildir subfolder conversion from courier-imap
by Remy Blank 19 May '07

19 May '07

Hello, I am trying to convert a maildir that was managed by courier-imap up to now to dovecot. I am using the courier-dovecot-migrate.pl script as follows: courier-dovecot-migrate.pl --convert --recursive ~/Maildir However, this command only seems to convert the base maildir, but not all the subfolders. I thought that that's what the --recursive option was for. Is the command above supposed to convert the base maildir as well as the subfolders, or should I run the command on all subfolders separately (e.g. using a shell script)? Thanks. -- Remy

2 2

Re: [Dovecot] Replication plans
by Bill Boebel 19 May '07

19 May '07

On Fri, May 18, 2007 1:42 am, Troy Benjegerdes <hozer(a)hozed.org> said: > I'm going to throw out a warning that it's my feeling that replication > has ended many otherwise worthwhile projects. Once you go down that > rabbit hole, you end up finding out the hard way that you just can't > avoid the stability, performance, complexity, and whatever problems. > .. > I've found myself pretty much in the same "all roads lead to the > filesystem" situation. I don't want to replicate just imap, I want to > replicate the build directory with my source code, my email, and my MP3 > files. One of the problems with the clustered file system approach seems to be that accessing Dovecot's index, cache and control files are slow over the network. For speed, ideally you want your index, cache and control on local disk... but still replicated to another server. So what about tackling this replication problem from a different angle... Make it Dovecot's job to replicate the index and control files between servers, and make it the file system's job to replicate just the mail data. This would require further disconnecting the index and control files from the mail data, so that there is less syncing required. i.e. remove the need to check directory mtimes and to compare directory listings against the index; and instead assume that the indexes are always correct. Periodically you could still check to see if a sync is needed, but you'd do this must less frequently. I agree that there are already great solutions available for replicated storage, so this would allow us to take advantage of these solutions for the bulk of our storage without impacting the speed of IMAP. Bill

3 2

Re: [Dovecot] dbox redesign
by Bill Boebel 19 May '07

19 May '07

On Sat, May 12, 2007 9:10 am, Timo Sirainen <tss(a)iki.fi> said: > Fast copying > ============ > > Would be nice if copying a message from one mailbox to another wouldn't > require actually reading+writing the whole message contents. But I can't > really figure out how to implement this without requiring that there is > only a single dbox storage which contains the mails for all the > mailboxes, and the mailboxes themselves are just Dovecot's index files > containing pointers to the dbox storage. > > The problem with having everything in one storage is that if the index > files are broken, the messages can't be placed into correct mailboxes > anymore. > > Although one possibility would be treat mailboxes a bit similarly than > keywords. So that when a message is copied to another mailbox, the > message in dbox file is updated to contain information that it exists in > such and such mailboxes. Hmm. Perhaps that would be good enough, yes. > Yes, I think treating mailboxes similary to keywords is ideal. There really is no reason to physically separate mailboxes on disk. All that is needed is this logical separation if it can be done in a reliable way. Or maybe track this in mailbox-specific index files, and also have a corespodning text file that stores a list of messages that are contained in that mailbox... similar to maildir's dovecot-uidlist file. Then if you lose the index you can rebuild the index from the text file. Bill

4 7

[Dovecot] dovecot-shared being ignored?
by bhayden＠umn.edu 19 May '07

19 May '07

So, I'm working on a shared folder. Everything is nice except for one bit. My dovecot-shared file in the Maildir is either being ignored, or doesn't work the way I think it does. Any messages copied into the Maildir using a mail client are mode 660 and owned by the user who did the copy. Perms on the dovecot-shared file are 700 (I'm using Solaris ACLs in addition to the Dovecot ACLs in order to prevent unauthorized access via means that don't pass through Dovecot's IMAP server... ie SFTP/SCP, and so I'm using 700 with a rwx mask and access to the file set per user in the Solaris ACL). The message files being created 660 means they are accessible via SFTP/SCP to anyone in the group, and we have a single one for (nearly) all users. This is not really acceptable, so if anyone can offer guidance on the dovecot-shared that'd be great. I checked the wiki, and it has very minimal information. -Brian

2 1

[Dovecot] Virtual mailbox plans
by Timo Sirainen 18 May '07

18 May '07

Configuration ------------- There could be global and user-specific configuration files, similar to how ACLs work. I think the global virtual mailboxes should be only defaults though, so that users could delete them and create a new mailbox (virtual or non-virtual) with the same name. The global virtual mailboxes could be described in a single file, such as: Trash deleted Work/My Unseen (mailboxes "box1" "box2" "box2/*") or to "tss(a)iki.fi" to "timo.sirainen(a)iki.fi" unseen So the format would be <virtual mailbox name> LF <search condition, allowed to wrap to new line> LF LF <next virtual mailbox, etc.> Per-user virtual mailboxes could also be listed in a similar file. If the search condition is empty, a globally defined virtual mailbox has been deleted. Another way would be to have per-mailbox dovecot-virtual files, but I'm not sure how global virtual mailboxes could then be easily deleted. Also having all of them in a single file makes listing the mailboxes pretty fast. The search condition would be a standard IMAP SEARCH reply, with the exception of the mailboxes parameter to specify what mailboxes are used. Virtual mailboxes would be implemented as a new mail storage backend, so their namespace configuration would be like: namespace private { prefix = "virtual/" location = virtual:~/virtual:GLOBAL=/etc/dovecot/virtual-globals.conf } Syncing ------- ~/virtual directory would contain index files for the virtual mailboxes. If the index files don't exist, a full resync for the virtual mailbox is done. This means opening all the real mailboxes configured for the vbox, running the SEARCH command and adding the returned UIDs to the vbox's indexes. The index would contain at least mailbox ID and message UID numbers. Probably would be a good idea to also save UIDVALIDITY numbers just to be safe, although that's a bit of a waste of space and it could be handled in other ways too, such as changing the mailbox ID whenever its UIDVALIDITY changes.. Mailbox IDs would be mapped to names in mailbox list index. This index already exists, although there still seems to be some bugs in it. At least creating a new list index has a race condition. I should look into making the list index a bit more realiable. Also the list indexes work only with Maildir++ layout currently. After the vbox has initially been synced, it needs to also handle updates. I think optionally the updates could be done the same way as full sync (opening all mailboxes to see if there are changes), but a faster way would be to update the virtual mailboxes immediately when the real mailboxes are being modified. So IMAP, POP3 and deliver all need to be aware of the virtual mailboxes and what real mailboxes are mapped to what virtual ones. Whenever doing a change that causes the message to either be added to or removed from a virtual mailbox according to their rules, the virtual mailbox's index is updated immediately. Being able to determine this change quickly might be the biggest change required to Dovecot's base code. Changes ------- Virtual mailboxes would share their state with the real mailbox, so any flag changes done in the vbox would be immediately changed in the real mailbox as well. The same goes for expunges. Virtual mailboxes' transaction logs would use different records for expunges and removals. Expunges would be handled normally, but removals wouldn't be removed from the in-memory view of the mailbox until EXPUNGE command was given (although they would be removed from dovecot.index immediately, so new sessions wouldn't see them). This makes it possible to have a vbox with only unseen messages, but without the message getting expunged immediately after a client opens the mail. So the EXPUNGE command could act as a "session synchronization" command. And of course it would also expunge the messages that had been marked as \Deleted.

1 0