November 2013 - dovecot

Re: [Dovecot] Replication via sneakernet
by David Bishop 28 Nov '13

28 Nov '13

D'oh. Replied to Timo instead of to the list. Apologies! On Thu, Nov 28, 2013 at 1:07 PM, David Bishop <dovecot(a)dpe.lusars.net>wrote: > On Thu, Nov 28, 2013 at 1:02 AM, Timo Sirainen <tss(a)iki.fi> wrote: > >> On 28.11.2013, at 5.17, David Bishop <dovecot(a)dpe.lusars.net> wrote: >> >> > There are trams shuttling back and forth along this road (stopping at >> each >> > station), and adding a small box (such as a weatherproofed Raspberry Pi >> > with a wifi dongle) to transport files up and down the road is pretty >> > simple. >> >> But if you do it this way and you can keep a full copy of the shared mail >> storage on your Raspberry, that would be possible already with dsync I >> think. dsync supports quick incremental updates by keeping track of the >> previous state between the servers. This state is saved in a file, so you >> could keep a different state for each different dsynced server. >> > > Bravo for a solution that doesn't require a code change and doesn't seem > to require directly touching the spools! :) > > Reading the man page, it looks like only mirroring for people who happen > to be checking email at a given place (as well as people who have received > mail and the shared mailboxes) seems like a pretty simple thing to do. > Hurrah! > > Thank you, this is wonderful. > > And more questions... > > If I'm running a virtual mail domain, the user/pass I give is for the > virtual mail user, correct? And, in a virtual mail setup, do I specify > "username" or "username@domain"? > > Is there a window beyond which synchronization becomes more difficult? For > instance, if messages (or metadata updates, like "I deleted this message") > get parked overnight without updating, and in the morning (9 hours later), > the trams (one at a time) pull into range of wifi, there won't be > confusion, right? > >

2 1

[Dovecot] sendmail to postfix-dovecot
by Roger Berger 28 Nov '13

28 Nov '13

Hi, I am a newbie to postfix and dovecot so I hope you can help me. I have an old server running sendmail for many years now. On this server I have about 100 domains and 500 users. The users are named as myuser or myuser.dom. People use pop3 and imap for fetching reading their email. I've setup a new server with postfix and dovecot2 on freebsd and managed to get it all working with virtual users. However, now I found out that I overlooked something; People have to login with username(a)domain.tld<mailto:username@domain.tld> on the new server but only use their username on the old server. This means they all have to change their login credentials, which is not an option. Is it possible to do some scripting before authentication where the username is looked up in the database and the right domain is added to the account? If I understand right it is not possible to use system and virtual users together. Thanks, Roger

5 6

Re: [Dovecot] Permissions problems
by Joseph Tam 27 Nov '13

27 Nov '13

<md.benson(a)gmail.com> wrote: > Nov 24 17:34:27 proliant-1 dovecot: [ID 583609 mail.error] imap(mark): Error: > rename(/mpool/mail/mark/dovecot.index.log.newlock, > /mpool/mail/mark/dovecot.index.log) failed: Permission denied > ... > This is what the directory currently looks like: > > mark@proliant-1:~$ ls -la /mpool/mail > total 6 > drwxrwxrwx+ 3 root root 3 2013-11-24 17:17 . > drwxr-xr-x+ 5 root root 5 2013-11-24 13:50 .. > drwxrwxrwx+ 5 mark staff 9 2013-11-24 22:20 mark I'm think the "+" is the problem: you have, in the words of the manpage for ls, ... this character is a plus sign (+) character if a non-trivial ACL is associated with the file ... Try ls -alv /mpool/mail I don't use ACLs, so I can help you how to modify them. Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] Enabling quota
by Andreas Kasenides 27 Nov '13

27 Nov '13

Hello everybody. Sorry if this has been answered before, I just could not find any info. Just point me if that is so. Can somebody please explain why there is no option --with-quota (ot may be --with-fs-quota) for the configure command? As it stands now, at least for the fs back-end the only thing that tells us that Dovecot does not do quotas is after the build/configuration we get dovecot: imap(xxdxx): Error: quotactl(Q_GETQUOTA, csfs9.cs.ucy.ac.cy:/mail) failed: No such file or directory which essentially means that during the build no quota development libraries were found and therefore fs quota will not function. This is rather confusing and the above error does not help much. Note also that "dovecot --build-options" is also silent on this. I suppose other back-ends do not have this requirement since there is no need for such devel libraries. thankx Andreas

3 3

[Dovecot] Dsync on a medium sized site
by Skeffling 27 Nov '13

27 Nov '13

Hello, We're looking at changing our current Dovecot setup to use dsync between 2 servers in different data centres to share the load and to provide resilience. We're quite excited about the possibilities! We receive about 100,000 emails a day, to about 10,000 mailboxes - a mix of IMAP and POP3. We'll use Dovecot Deliver via exim to put mail in to the Maildir. Has dsync been used on sites of this size? -Any tips? Do people tend to sync between 2 servers, or do some people use more than 2? I'm interested in other people's experience before setting up some test boxes. Thanks! Andrew.

1 0

[Dovecot] Failute to compile of pigeonhole-0.4.2 with Dovecot 2.2.7
by Andreas Kasenides 27 Nov '13

27 Nov '13

On trying to compile pigeonhole-0.4.2 on Dovecot 2.2.7 on a CentOS 6.4 machine Linux xxx.xxx 2.6.32-358.14.1.el6.x86_64 #1 SMP Tue Jul 16 23:51:20 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux with ./configure --with-dovecot=/usr/local/lib/dovecot I get the following error: ............ /bin/sh ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/local/include/dovecot -I../.. -I../../src/lib-sieve -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -MT sieve-storage.lo -MD -MP -MF .deps/sieve-storage.Tpo -c -o sieve-storage.lo sieve-storage.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/local/include/dovecot -I../.. -I../../src/lib-sieve -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -MT sieve-storage.lo -MD -MP -MF .deps/sieve-storage.Tpo -c sieve-storage.c -fPIC -DPIC -o .libs/sieve-storage.o sieve-storage.c: In function 'sieve_storage_inbox_script_attribute_set': sieve-storage.c:702: error: 'MAILBOX_ATTRIBUTE_PREFIX_DOVECOT_PVT_SERVER' undeclared (first use in this function) sieve-storage.c:702: error: (Each undeclared identifier is reported only once sieve-storage.c:702: error: for each function it appears in.) sieve-storage.c:702: error: expected ')' before string constant sieve-storage.c:693: warning: unused parameter 'name' sieve-storage.c: In function 'sieve_storage_inbox_script_attribute_rename': sieve-storage.c:718: error: 'MAILBOX_ATTRIBUTE_PREFIX_DOVECOT_PVT_SERVER' undeclared (first use in this function) sieve-storage.c:718: error: expected ')' before string constant sieve-storage.c:720: error: expected ')' before string constant sieve-storage.c:709: warning: unused parameter 'oldname' sieve-storage.c:709: warning: unused parameter 'newname' sieve-storage.c: In function 'sieve_storage_inbox_script_attribute_unset': sieve-storage.c:738: error: 'MAILBOX_ATTRIBUTE_PREFIX_DOVECOT_PVT_SERVER' undeclared (first use in this function) sieve-storage.c:738: error: expected ')' before string constant sieve-storage.c:729: warning: unused parameter 'name' make[3]: *** [sieve-storage.lo] Error 1 make[3]: Leaving directory `/root/dovecot-2.2-pigeonhole-0.4.2/src/lib-sievestorage' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/root/dovecot-2.2-pigeonhole-0.4.2/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/dovecot-2.2-pigeonhole-0.4.2' make: *** [all] Error 2 Dovecot 2.2.7 compiles and runs fine. Any help appreciated. Andreas

2 2

[Dovecot] Permissions problems
by Google 27 Nov '13

27 Nov '13

Hi, I have dovecot 2.0.20 running (its an old version, I know, it came from the stable archive at OpenCSW) with Solaris SMF integration working fine. It enables and disables okay. However, I cantt connect to it, it is allowing the connection, but spewing on permissions: Nov 24 17:34:20 proliant-1 dovecot: [ID 583609 mail.info] master: Dovecot v2.0.20 starting up Nov 24 17:34:27 proliant-1 dovecot: [ID 583609 mail.info] imap-login: Login: user=<mark>, method=PLAIN, rip=192.168.1.69, lip=192.168.1.72, mpid=18816 Nov 24 17:34:27 proliant-1 dovecot: [ID 583609 mail.info] imap-login: Login: user=<mark>, method=PLAIN, rip=192.168.1.69, lip=192.168.1.72, mpid=18818 Nov 24 17:34:27 proliant-1 dovecot: [ID 583609 mail.info] imap-login: Login: user=<mark>, method=PLAIN, rip=192.168.1.69, lip=192.168.1.72, mpid=18820 Nov 24 17:34:27 proliant-1 dovecot: [ID 583609 mail.info] imap(mark): Connection closed bytes=17/340 Nov 24 17:34:27 proliant-1 dovecot: [ID 583609 mail.info] imap-login: Login: user=<mark>, method=PLAIN, rip=192.168.1.69, lip=192.168.1.72, mpid=18822 Nov 24 17:34:27 proliant-1 dovecot: [ID 583609 mail.error] imap(mark): Error: rename(/mpool/mail/mark/dovecot.index.log.newlock, /mpool/mail/mark/dovecot.index.log) failed: Permission denied Nov 24 17:34:27 proliant-1 dovecot: [ID 583609 mail.error] imap(mark): Error: rename(/mpool/mail/mark/dovecot-uidlist.tmp, /mpool/mail/mark/dovecot-uidlist) failed: Permission denied Nov 24 17:34:27 proliant-1 dovecot: [ID 583609 mail.error] imap(mark): Error: unlink(/mpool/mail/mark/dovecot-uidlist.tmp) failed: Permission denied Nov 24 17:34:27 proliant-1 dovecot: [ID 583609 mail.error] imap(mark): Error: rename(/mpool/mail/mark/dovecot-uidlist.tmp, /mpool/mail/mark/dovecot-uidlist) failed: Permission denied Nov 24 17:34:27 proliant-1 dovecot: [ID 583609 mail.error] imap(mark): Error: unlink(/mpool/mail/mark/dovecot-uidlist.tmp) failed: Permission denied Nov 24 17:34:27 proliant-1 dovecot: [ID 583609 mail.error] imap(mark): Error: rename(/mpool/mail/mark/dovecot-uidlist.tmp, /mpool/mail/mark/dovecot-uidlist) failed: Permission denied Nov 24 17:34:27 proliant-1 dovecot: [ID 583609 mail.error] imap(mark): Error: unlink(/mpool/mail/mark/dovecot-uidlist.tmp) failed: Permission denied Nov 24 17:34:27 proliant-1 dovecot: [ID 583609 mail.error] imap(mark): Error: rename(/mpool/mail/mark/dovecot-uidlist.tmp, /mpool/mail/mark/dovecot-uidlist) failed: Permission denied Nov 24 17:34:27 proliant-1 dovecot: [ID 583609 mail.error] imap(mark): Error: unlink(/mpool/mail/mark/dovecot-uidlist.tmp) failed: Permission denied If I actually try to copy mail to the inbox of the account it core-dumps and does, and the SMF service drops into maintenance mode which requires re-enabling. The output from doveconf -n (this is changes from the default settings I think?) is: root@proliant-1:~# doveconf -n # 2.0.20: /etc/opt/csw/dovecot/dovecot.conf # OS: SunOS 5.11 i86pc zfs auth_first_valid_uid = 101 disable_plaintext_auth = no first_valid_uid = 101 mail_location = maildir:/mpool/mail/%u passdb { driver = pam } ssl_cert = </opt/csw/ssl/certs/dovecot.pem ssl_key = </opt/csw/ssl/private/dovecot.pem userdb { driver = passwd } The mail_location is in a ZFS filesystem on my RAIDz array. I couldnt think of any other way of creating user-specific folders in the location. As the value suggests, each user gets their own directory on the filesystem for mail. Is this still a ‘safe’ way to do things or would I be better off relocating each user’s ‘home’ directory to the pool somehow? This is what the directory currently looks like: mark@proliant-1:~$ ls -la /mpool/mail total 6 drwxrwxrwx+ 3 root root 3 2013-11-24 17:17 . drwxr-xr-x+ 5 root root 5 2013-11-24 13:50 .. drwxrwxrwx+ 5 mark staff 9 2013-11-24 22:20 mark mark@proliant-1:~$ ls -la /mpool/mail/mark/ total 14 drwxrwxrwx+ 5 mark staff 9 2013-11-24 22:20 . drwxrwxrwx+ 3 root root 3 2013-11-24 17:17 .. drwxrwxrwx+ 2 mark staff 2 2013-11-24 17:17 cur -rwxrwxrwx+ 1 mark staff 51 2013-11-24 22:20 dovecot-uidlist.tmp -rwxrwxrwx+ 1 mark staff 8 2013-11-24 22:20 dovecot-uidvalidity -rwxrwxrwx+ 1 mark staff 0 2013-11-24 17:17 dovecot-uidvalidity.529234ad -rwxrwxrwx+ 1 mark staff 40 2013-11-24 22:20 dovecot.index.log.newlock drwxrwxrwx+ 2 mark staff 2 2013-11-24 17:17 new drwxrwxrwx+ 2 mark staff 3 2013-11-24 17:21 tmp Any ideas? -- Mark Benson http://DECtec.info Twitter: @DECtecInfo HECnet: STAR69::MARK Online Resource & Mailing List for DEC Enthusiasts.

3 2

[Dovecot] Dovecot 2.1.16
by paolo.brocchi 27 Nov '13

27 Nov '13

Hi, i would ask you a question about a particular dovecot configuration. I would like to have in INBOX folder some emails (e.g email with a header key). The same emails i would like to have into the folders, under INBOX, create by users. How can i do? Thanks Paolo

2 4

[Dovecot] Dovecot 2.1 Panic
by Alexandr Sabitov 27 Nov '13

27 Nov '13

Hi, Dovecot 2.1.12 sends panic message when it tries to authenticate some users. Apparently because they use different authentication mechanisms on different email clients at the same time. For example, in debug logs this user uses CRAM-MD5, NTLM and PLAIN in account settings of his email clients. All passwords are stored in plain text (base64) in LDAP. Please advise me what I can tweak to fix this issue ? Nov 27 06:38:36 dovecot-1 auth: Error: ldap(gone(a)in.com.au,201.45.21.151,<qZlhoBnsvQDLLRuX>): Multiple password values not supported Nov 27 06:38:36 dovecot-1 auth: Panic: file passdb-ldap.c: line 95 (ldap_lookup_finish): assertion failed: (password == NULL || scheme != NULL) Nov 27 06:38:36 dovecot-1 auth: Error: ldap(gone(a)in.com.au,201.45.21.151,<qZlhoBnsvQDLLRuX>): Multiple password values not supported Nov 27 06:38:36 dovecot-1 auth: Error: Raw backtrace: /usr/local/dovecot/lib/dovecot/libdovecot.so.0(+0x485ca) [0x7f90ed51b5ca] -> /usr/local/dovecot/lib/dovecot/libdovecot.so.0(+0x48616) [0x7f90ed51b616] -> /usr/local/dovecot/lib/dovecot/libdovecot.so.0(i_error+0) [0x7f90ed4eeeef] -> dovecot-proxy/auth() [0x42967c] -> dovecot-proxy/auth() [0x428da1] -> /usr/local/dovecot/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x36) [0x7f90ed5277a6] -> /usr/local/dovecot/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x9f) [0x7f90ed5287df] -> /usr/local/dovecot/lib/dovecot/libdovecot.so.0(io_loop_run+0x28) [0x7f90ed527748] -> /usr/local/dovecot/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f90ed513123] -> dovecot-proxy/auth(main+0x376) [0x41bd26] -> /lib/libc.so.6(__libc_start_main+0xfd) [0x7f90ec2d8c8d] -> dovecot-proxy/auth() [0x40d0f9] Nov 27 06:38:36 dovecot-1 auth: Error: Raw backtrace: /usr/local/dovecot/lib/dovecot/libdovecot.so.0(+0x485ca) [0x7f90ed51b5ca] -> /usr/local/dovecot/lib/dovecot/libdovecot.so.0(+0x48616) [0x7f90ed51b616] -> /usr/local/dovecot/lib/dovecot/libdovecot.so.0(i_error+0) [0x7f90ed4eeeef] -> dovecot-proxy/auth() [0x42967c] -> dovecot-proxy/auth() [0x428da1] -> /usr/local/dovecot/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x36) [0x7f90ed5277a6] -> /usr/local/dovecot/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x9f) [0x7f90ed5287df] -> /usr/local/dovecot/lib/dovecot/libdovecot.so.0(io_loop_run+0x28) [0x7f90ed527748] -> /usr/local/dovecot/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f90ed513123] -> dovecot- proxy/auth(main+0x376) [0x41bd26] -> /lib/libc.so.6(__libc_start_main+0xfd) [0x7f90ec2d8c8d] -> dovecot-proxy/auth() [0x40d0f9] Nov 27 06:38:36 dovecot-1 director: Error: Auth server disconnected unexpectedly Nov 27 06:38:36 dovecot-1 auth: Fatal: master: service(auth): child 26841 killed with signal 6 (core dumps disabled) This is LDAP configuration on one of director servers where clients are authenticated. uris = ldap://ldap-node-2.mynetwork.net, ldap://ldap-node-3.mynetwork.net debug_level = 0 base = ou=email, dc=netregistry, dc=net user_attrs = homeDirectory=home, uidNumber=uid, gidNumber=gid, mailQuotaSize=quota_rule=*:storage=%$ user_filter = (&(objectClass=nrPOPAccount)(uid=%u)) pass_attrs = uid=user, userPassword=password, =proxy=y, =destuser=%u, =pass=Secret456 pass_filter = (&(objectClass=nrPOPAccount)(uid=%u)) default_pass_scheme = PLAIN Regards, Alexandr Sabitov System Administrator

1 0

[Dovecot] Dovecot software testing and release practice
by Andreas Kasenides 26 Nov '13

26 Nov '13

Since this, it seems, was lost in, the now infamous, 2.2.9 thread I would like to resubmit the following proposal for Timo's consideration. Thanks Timo for doing an excellent job. I believe that the following will add further value to Dovecot in the long run. Thankx Andreas ============================ > On 23-11-2013 3:47, Noel Butler wrote: > > On Fri, 2013-11-22 at 10:14 +0100, Ralf Hildebrandt wrote: > * Thomas Leuxner <tlx(a)leuxner.net>: > * Ralf Hildebrandt <Ralf.Hildebrandt(a)charite.de> 2013.11.22 > 09:44: > > Which patch? > > > http://www.dovecot.org/list/dovecot/2013-November/093654.html > Pigeonhole related patches. > Damn. Those are biting me as well :/ > > These would be found if Timo reverted back to issuing RC's before any > official release, to iron out the > niggly off-putting bugs, like most software does, or gets his devs and > a community of official > >testers>each with wildly different > configurations and set ups, ASF have an excellent model that could be > >followed, >bunch of devs and testers who each report on different distros and configs, why? because no >single dev can imagine and test every possible configuration. it might just save dovecot's good name, I >recall a lot of damage was done to that in the circles I'm in when 2.0 was released with patches nearly >every few days and weeks, I know a few ISP's and businesses that went back to courier or Wu's because >major bugs were getting in often, though it has been a lot better since 2.1 series, until this release >that is :) I second this and offer my services for two, three different system configs from Dovecot's plain old simple config with MAILDIR to slightly more complicated configurations with proxying/LDAP/dsync/mySQL etc based on virtualization with KVM. I also propose that upon employing above strategy that Timo should come up with a release cycles (long term, short term) with announced targets. Patches should be released as patches strictly as needed, not releases, and should be announced on a low traffic list like he is already doing with releases. OR something along these lines. I know these are growing pains but essential. Email systems are CRITICAL for most of us. Andreas

1 0