Re: [Dovecot] Clients to manage ACL
On 06.04.2010 9:52, Martin Ott wrote: Hi, is there any list with clients which support setting ACL on imap-mailboxes? Up to now, a only know about KMail and imapACLM. Thanks, Martin Thunderbird will soon support that, patch already in review queue now.
Re: [Dovecot] dovecot 1.2.11 + virtual plugin + deliver
Tirsdag 06 april 2010 20:06:26 skrev Stef Simoens : Hello List and Timo, I configured the virtual mailboxes which are really nice. To create the virtual-folder, I made a postlogin-script as described in the wiki. However, as my mail is delivered by dovecot's deliver ... I'm getting errors for people not yet logged in... Namespace 'virtual.': virtual : Root mail directory doesn't exist: /var/vmail/domain.org/username/virtual I tried removing the virtual-plugin from the protocol lda-section; and putting the namespace only in the protocol imap-section; but then the error becomes Namespace 'virtual.': Unknown mail storage driver virtual After an IMAP login (thanks to the postlogin-script) the virtual folder is created. However, I would prefer that mails to existing users and new users works even before they logged-in (and before the postlogin-script creates the virtual folder). Any help? Greetings, I use Postfix admin ( http://sourceforge.net/projects/postfixadmin/ ) to create the mailboxes. Upon creation a welcome message is sent to the user, and delivering this creates the virtual mailbox. Regards, Arne -- Arne K. Haaje | www.drlinux.no T: 69 51 15 52 | M: 92 88 44 66
[Dovecot] dovecot upgrade problems
Hi list, i made an upgrade from dovecot 1.0RC15 to 1.1.20 the default installation was under /etc/dovecot. The upgrade installation was made under /usr/local/etc. After that i changed all the paths in the /usr/local/etc/dovecot.conf and the dovecot-binary to work with the new installation. Even path-changes were made for /etc/init.d/dovecot to work with the version 1.1.20. Changes in the /etc/init.d/dovecot: PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin DAEMON=/usr/local/sbin/dovecot NAME=dovecot DESC=mail server test -x $DAEMON || exit 0 set -e # The init script should do nothing if dovecot is being run from inetd for p in `sed -r s/^ *(([^:]+|\[[^]]+]|\*):)?(pop3s?|imaps?)[ \t].*/\3/;t;d \ /etc/inetd.conf` do for q in `sed -r s/^ *protocols[ \t]*=[ \t]*(([^\]*)|\(.*)\)/\2\3/;t;d \ /usr/local/etc/dovecot.conf` do if [ $p = $q ]; then exit 0 fi done done case $1 in start) if grep protocols /usr/local/etc/dovecot.conf | sed 's/#.*$//' | tr -d '' | \ egrep -q '[^#]*(\bpop3s?\b|\bimaps?\b)'; then if [ -x /usr/local/libexec/dovecot/imap-login -a -x /usr/local/libexec/dovecot/imap ] \ || [ -x /usr/local/libexec/dovecot/pop3-login -a -x /usr/local/libexec/dovecot/pop3 ] If I leave the DAEMON-Path to =/usr/sbin/dovecot Dovecot is running fine!!! The only thing which is missing under /usr/local is the auth-master file. Under /var/run/dovecot the old auth-master file exists. Why not under the upgrade path? Anyway, here is the logging when i try to start dovecot: Apr 6 16:18:37 server dovecot: dovecot v1.1.20 starting up (core dumps disabled) Apr 6 16:18:37 server dovecot: Fatal: auth(default): Dovecot version mismatch: Master is v1.1.20, dovecot-auth is v1.0.rc15 (if you don't care, set version_ignore=yes) Apr 6 16:18:37 server dovecot: Fatal: Auth process died too early - shutting down server:/usr/local/etc# /etc/init.d/dovecot restart Restarting mail server: dovecotWarning: Last died with error (see error log for more information): Auth process died too early - shutting down Also the configuration output: dovecot -n # 1.1.20: /usr/local/etc/dovecot.conf # OS: Linux 2.6.18-4-686 i686 Debian 4.0 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imaps pop3s imap ssl_key_file: /etc/ssl/private/dovecot.key 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 login_max_processes_count: 256 first_valid_uid: 1000 last_valid_uid: 5000 mail_access_groups: mail mail_location: maildir:~/Maildir mail_debug: yes mail_full_filesystem_access: yes mbox_write_locks: fcntl 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_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 lda: postmaster_address: cies...@folkwang-hochschule.de hostname: server log_path: /var/log/dovecot-deliver.log info_log_path: /var/log/dovecot-deliver.log sendmail_path: /usr/lib/sendmail auth default: mechanisms: login plain verbose: yes debug: yes process_size: 512 passdb: driver: passwd args: /etc/passwd passdb: driver: shadow args: /etc/shadow passdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf userdb: driver: passwd args: blocking=yes userdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf socket: type: listen master: path: /usr/local/var/run/dovecot/auth-master mode: 384 user: mail plugin: quota: maildir ###auth-master is not existing under the path /usr/local/var/run/dovecot/auth-master. Is this the fault? Can anyone help me out? Andreas Cieslak IT-Systeme Folkwang Hochschule Musik | Theater | Tanz | Gestaltung | Wissenschaft Klemensborn 39 45239 Essen Fon: 0201_4903-218 Fax: 0201_4903-288 cies...@folkwang-hochschule.de www.folkwang-hochschule.de http://www.folkwang-hochschule.de/
[Dovecot] Maildir archive utility for historical filing
Hi all! Is there any utility to archive maildir folders based on message date? I found cleanup-maildir, but you have to supply the directory as parameter. thanks in advance Dimitrios
Re: [Dovecot] dovecot upgrade problems
On Wed, 2010-04-07 at 09:58 +0200, Cieslak, Andreas wrote:
Hi list,
i made an upgrade from dovecot 1.0RC15 to 1.1.20
the default installation was under /etc/dovecot.
The upgrade installation was made under /usr/local/etc.
{snip}
###auth-master is not existing under the path
/usr/local/var/run/dovecot/auth-master. Is this the fault?
What creates that socket? Something like Exim or Postfix?
Chances are the external program still creates that socket under it's
original directory and will either need to be changed to match your new
path, or point it to the existing socket.
find / -iname auth-master
May be worth a run just to see if it still exists in the 'old' location
the last dovecot was looking at.
Can anyone help me out?
Andreas Cieslak
IT-Systeme
Folkwang Hochschule
Musik | Theater | Tanz | Gestaltung | Wissenschaft
Klemensborn 39
45239 Essen
Fon: 0201_4903-218
Fax: 0201_4903-288
cies...@folkwang-hochschule.de
www.folkwang-hochschule.de http://www.folkwang-hochschule.de/
Re: [Dovecot] dovecot upgrade problems
Thanks,
It is still in the old location
/var/run/dovecot/auth-master.
The old version is running proper with it.
But the new version shows the following
/var/run/dovecot# ls -la /usr/local/var/run/dovecot
drwxr-sr-x 3 root staff 4096 2010-04-06 17:18 .
drwxr-sr-x 3 root staff 4096 2010-04-06 16:12 ..
srw--- 1 root root 0 2010-04-06 17:18 auth-worker.4270
srwxrwxrwx 1 root staff 0 2010-04-06 17:18 dict-server
drwxr-x--- 2 root dovecot 4096 2010-04-06 17:18 login
-rw--- 1 root staff 43 2010-04-06 17:18 master-fatal.lastlog
-rw--- 1 root staff 5 2010-04-06 17:18 master.pid
Andreas Cieslak
IT-Systeme
Folkwang Hochschule_die Kunsthochschule im Ruhrgebiet
Klemensborn 39
45239 Essen
Tel.: +49 (201) 4903-218
Fax.: +49 (201) 4903-288
cies...@folkwang-hochschule.de
-Ursprüngliche Nachricht-
Von: dovecot-bounces+cieslak=folkwang-hochschule...@dovecot.org
[mailto:dovecot-bounces+cieslak=folkwang-hochschule...@dovecot.org] Im Auftrag
von corpus.defero
Gesendet: Mittwoch, 7. April 2010 11:52
Cc: dovecot@dovecot.org
Betreff: Re: [Dovecot] dovecot upgrade problems
On Wed, 2010-04-07 at 09:58 +0200, Cieslak, Andreas wrote:
Hi list,
i made an upgrade from dovecot 1.0RC15 to 1.1.20
the default installation was under /etc/dovecot.
The upgrade installation was made under /usr/local/etc.
{snip}
###auth-master is not existing under the path
/usr/local/var/run/dovecot/auth-master. Is this the fault?
What creates that socket? Something like Exim or Postfix?
Chances are the external program still creates that socket under it's
original directory and will either need to be changed to match your new
path, or point it to the existing socket.
find / -iname auth-master
May be worth a run just to see if it still exists in the 'old' location
the last dovecot was looking at.
Can anyone help me out?
Andreas Cieslak
IT-Systeme
Folkwang Hochschule
Musik | Theater | Tanz | Gestaltung | Wissenschaft
Klemensborn 39
45239 Essen
Fon: 0201_4903-218
Fax: 0201_4903-288
cies...@folkwang-hochschule.de
www.folkwang-hochschule.de http://www.folkwang-hochschule.de/
Re: [Dovecot] dovecot upgrade problems
On Wed, 2010-04-07 at 12:08 +0200, Cieslak, Andreas wrote: AFAIR Dovecot does not create that socket: /var/run/dovecot/auth-master Some other program creates it - so either tell that other program to create the socket where you want it now, or tell Dovecot where that socket actually is. I can't say for sure that is your error, but if the socket is not where Dovecot is looking, it's going to complain about an auth issue. Also, I would be surprised if the new version will start, if you already have an old version running - sanity would say that is a bad thing to try and do.
[Dovecot] ImapTest build problem
Hello. My system is: Debian Lenny 2.6.26-2-amd64 I try to build Imaptest and follow http://www.imapwiki.org/ImapTest/Installation But get this: ./configure --with-dovecot=../dovecot-2.0.beta4 make checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking how to run the C preprocessor... gcc -E checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking for a sed that does not truncate output... /bin/sed checking for egrep... grep -E checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking how to recognise dependent libraries... pass_all checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... gcc3 checking how to run the C++ preprocessor... g++ -E checking for g77... no checking for f77... no checking for xlf... no checking for frt... no checking for pgf77... no checking for fort77... no checking for fl32... no checking for af77... no checking for f90... no checking for xlf90... no checking for pgf90... no checking for epcf90... no checking for f95... no checking for fort... no checking for xlf95... no checking for ifc... no checking for efc... no checking for pgf95... no checking for lf95... no checking for gfortran... no checking whether we are using the GNU Fortran 77 compiler... no checking whether accepts -g... no checking the maximum length of command line arguments... 32768 checking command to parse /usr/bin/nm -B output from gcc object... ok checking for objdir... .libs checking for ar... ar checking for ranlib... ranlib checking for strip... strip checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes configure: creating libtool appending configuration tag CXX to libtool checking for ld used by g++... /usr/bin/ld -m elf_x86_64 checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC checking if g++ PIC flag -fPIC works... yes checking if g++ static flag -static works... yes checking if g++ supports -c -o file.o... yes checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate appending configuration tag F77 to libtool configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating stamp.h config.status: creating imaptest-config.h config.status: imaptest-config.h is unchanged config.status: executing depfiles commands make all-recursive make[1]: Entering directory `/root/imaptest-20100221' Making all in src make[2]: Entering directory `/root/imaptest-20100221/src' if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/root/dovecot-2.0.beta4 -I/root/dovecot-2.0.beta4/src/lib -I/root/dovecot-2.0.beta4/src/lib-mail
Re: [Dovecot] Clients to manage ACL
On 2010-04-07 2:34 AM, Nikolay Shopik wrote: is there any list with clients which support setting ACL on imap-mailboxes? Up to now, a only know about KMail and imapACLM. Thunderbird will soon support that, patch already in review queue now. Hi Nikolay, Do you know if it will make it into 3.1? -- Best regards, Charles
Re: [Dovecot] ImapTest build problem
On Wed, 2010-04-07 at 14:31 +0400, Proskurin Kirill wrote: I try to build Imaptest and follow http://www.imapwiki.org/ImapTest/Installation But get this: ./configure --with-dovecot=../dovecot-2.0.beta4 make Yeah, imaptest currently builds only against v1.2 code. I'll update it to compile with v2.0 sometimes in future.. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Testing 2.0b3 - problem with pop3
Zitiere Timo Sirainen t...@iki.fi: On Mon, 2010-02-22 at 19:32 +0300, Odhiambo Washington wrote: Now it starts normally, at least, but funnily, the auth mechanisms I am using in beta1 don't work with the same db in beta3. Unless I missed something, the following is what I get: Feb 22 19:29:48 auth: Error: md5_verify(u...@domain.tld): Not a valid MD5-CRYPT or PLAIN-MD5 password What does it log with auth_debug_passwords=yes? I guess it's possible I broke something, but .. I don't think I really touched that part of the code.. We've got the same problem with 2.0b4. The debug output with auth_debug_passwords=yes is: Apr 07 11:38:45 auth: Info: passwd(user1,10.1.1.99): Password mismatch Apr 07 11:38:45 auth: Debug: passwd(user1,10.1.1.99): CRYPT(password1) != 'x' the config line for auth: auth_mechanisms = login plain is there any solution yet? regards Arnold BTW. doveconf -n output is better than the full output, no point in printing defaults.
Re: [Dovecot] Clients to manage ACL
On Tue, 2010-04-06 at 12:41 -0500, Brian Hayden wrote: Since few clients support ACLs and even fewer do it right (and Horde has all sorts of its own problems), I wrote a web client and a system daemon to handle ACL manipulation. However, the daemon only works on Solaris with real system users (not mysql userdb or etc). I don't know what kind of things you're doing with real users, but with v2.0 you can do via unix socket: 1) userdb lookup for specified user (well, this works work v1.x too). This also allows getting a list of user's ACL groups (acl_groups extra field). 2) get a list of all usernames signature.asc Description: This is a digitally signed message part
Re: [Dovecot] dovecot upgrade problems
On Wed, 2010-04-07 at 11:14 +0100, corpus.defero wrote: On Wed, 2010-04-07 at 12:08 +0200, Cieslak, Andreas wrote: AFAIR Dovecot does not create that socket: /var/run/dovecot/auth-master Dovecot does create auth-master socket, but not by default. http://wiki.dovecot.org/LDA#Virtual_users signature.asc Description: This is a digitally signed message part
Re: [Dovecot] ImapTest build problem
On 04/07/2010 03:39 PM, Timo Sirainen wrote: On Wed, 2010-04-07 at 14:31 +0400, Proskurin Kirill wrote: I try to build Imaptest and follow http://www.imapwiki.org/ImapTest/Installation But get this: ./configure --with-dovecot=../dovecot-2.0.beta4 make Yeah, imaptest currently builds only against v1.2 code. I'll update it to compile with v2.0 sometimes in future.. Thx! But seems to wiki needs fixing then. Because http://dovecot.org/nightly/dovecot-latest.tar.gz is 2.0 -- Best regards, Proskurin Kirill
Re: [Dovecot] Testing 2.0b3 - problem with pop3
On Wed, Apr 07, 2010 at 12:25:48PM +0200, Arnold Jäger wrote: Apr 07 11:38:45 auth: Info: passwd(user1,10.1.1.99): Password mismatch Apr 07 11:38:45 auth: Debug: passwd(user1,10.1.1.99): CRYPT(password1) != 'x' At a guess, it looks like it's trying to match against the password field in /etc/passwd (where the password field just contains 'x') instead of /etc/shadow (where the real crypted password lives) What's your config?
Re: [Dovecot] ImapTest build problem
On Wed, 2010-04-07 at 16:08 +0400, Proskurin Kirill wrote: Yeah, imaptest currently builds only against v1.2 code. I'll update it to compile with v2.0 sometimes in future.. Thx! But seems to wiki needs fixing then. Because http://dovecot.org/nightly/dovecot-latest.tar.gz is 2.0 Well, I'm rather thinking that the code needs fixing, not wiki. :) signature.asc Description: This is a digitally signed message part
Re: [Dovecot] dovecot upgrade problems
On Wed, 2010-04-07 at 15:00 +0300, Timo Sirainen wrote: On Wed, 2010-04-07 at 11:14 +0100, corpus.defero wrote: On Wed, 2010-04-07 at 12:08 +0200, Cieslak, Andreas wrote: AFAIR Dovecot does not create that socket: /var/run/dovecot/auth-master Dovecot does create auth-master socket, but not by default. http://wiki.dovecot.org/LDA#Virtual_users My apologies! I'm back to front. I just looked at Dovecot creates the socket that my Postfix uses to talk to it. Doh!
Re: [Dovecot] Testing 2.0b3 - problem with pop3
Zitiere Brian Candler b.cand...@pobox.com: On Wed, Apr 07, 2010 at 12:25:48PM +0200, Arnold Jäger wrote: Apr 07 11:38:45 auth: Info: passwd(user1,10.1.1.99): Password mismatch Apr 07 11:38:45 auth: Debug: passwd(user1,10.1.1.99): CRYPT(password1) != 'x' At a guess, it looks like it's trying to match against the password field in /etc/passwd (where the password field just contains 'x') instead of /etc/shadow (where the real crypted password lives) h - yes, you're right. Shame on us. driver should be shadow (not passwd). regards Arnold What's your config?
Re: [Dovecot] dovecot upgrade problems
I got this problem solved, pointing the socket to the old path /var/run/dovecot/auth-master. Thanks. Andreas Cieslak IT-Systeme Folkwang Hochschule_die Kunsthochschule im Ruhrgebiet Klemensborn 39 45239 Essen Tel.: +49 (201) 4903-218 Fax.: +49 (201) 4903-288 cies...@folkwang-hochschule.de -Ursprüngliche Nachricht- Von: dovecot-bounces+cieslak=folkwang-hochschule...@dovecot.org [mailto:dovecot-bounces+cieslak=folkwang-hochschule...@dovecot.org] Im Auftrag von Timo Sirainen Gesendet: Mittwoch, 7. April 2010 14:00 An: dovecot@dovecot.org Betreff: Re: [Dovecot] dovecot upgrade problems On Wed, 2010-04-07 at 11:14 +0100, corpus.defero wrote: On Wed, 2010-04-07 at 12:08 +0200, Cieslak, Andreas wrote: AFAIR Dovecot does not create that socket: /var/run/dovecot/auth-master Dovecot does create auth-master socket, but not by default. http://wiki.dovecot.org/LDA#Virtual_users
Re: [Dovecot] ImapTest build problem [SOLVED]
On 04/07/2010 04:24 PM, Timo Sirainen wrote: On Wed, 2010-04-07 at 16:08 +0400, Proskurin Kirill wrote: Yeah, imaptest currently builds only against v1.2 code. I'll update it to compile with v2.0 sometimes in future.. Thx! But seems to wiki needs fixing then. Because http://dovecot.org/nightly/dovecot-latest.tar.gz is 2.0 Well, I'm rather thinking that the code needs fixing, not wiki. :) Yes, but code update may be not soon but wiki update is few seconds and fix an misunderstanding. ;-) Anyway - could you give some examples of using ImapTest for testing\benchmarking? Yes I saw http://www.imapwiki.org/ImapTest/Examples but I not a programmer and I don`t know IMAP protocol well and this numbers give me near nothing. If you have some time - it will be nice to make some examples for admins. Especially I(and I think many others) interested in stress testing and benchmarking. Ideal it will be something like a Postfix smtp-source. It is just a friendly feature request. -- Best regards, Proskurin Kirill
Re: [Dovecot] dovecot 1.2.11 + virtual plugin + deliver
Hello, That's my problem ... an IMAP-connection makes the imap-postlogin-script run which creates the virtual directory but the imap-postlogin-script is not run if dovecot deliver is run by postfix so, new users cannot receive mail until they make a first connection and the welcome-mail stays in the postfix-queue Ideally, I would like to hide the virtual namespace for deliver; but even if I put the namespace definition in the protocol imap-section, it is still seen by deliver... Kind regards, Op 7/04/2010 9:09, Arne K. Haaje schreef: Tirsdag 06 april 2010 20:06:26 skrev Stef Simoens : Hello List and Timo, I configured the virtual mailboxes which are really nice. To create the virtual-folder, I made a postlogin-script as described in the wiki. However, as my mail is delivered by dovecot's deliver ... I'm getting errors for people not yet logged in... Namespace 'virtual.': virtual : Root mail directory doesn't exist: /var/vmail/domain.org/username/virtual I tried removing the virtual-plugin from the protocol lda-section; and putting the namespace only in the protocol imap-section; but then the error becomes Namespace 'virtual.': Unknown mail storage driver virtual After an IMAP login (thanks to the postlogin-script) the virtual folder is created. However, I would prefer that mails to existing users and new users works even before they logged-in (and before the postlogin-script creates the virtual folder). Any help? Greetings, I use Postfix admin ( http://sourceforge.net/projects/postfixadmin/ ) to create the mailboxes. Upon creation a welcome message is sent to the user, and delivering this creates the virtual mailbox. Regards, Arne -- Stef Simoens stef.simo...@numericable.be +32 486 577 963 http://users.numericable.be/stef
Re: [Dovecot] Maildir archive utility for historical filing
tar? On 4/7/10 11:51 AM +0300 Dimitrios Karapiperis wrote: Hi all! Is there any utility to archive maildir folders based on message date? I found cleanup-maildir, but you have to supply the directory as parameter. thanks in advance
Re: [Dovecot] Maildir archive utility for historical filing
Hi, Is there any utility to archive maildir folders based on message date? I found cleanup-maildir, but you have to supply the directory as parameter. http://archivemail.sourceforge.net/
Re: [Dovecot] Clients to manage ACL
On 07.04.2010 15:13, Charles Marcus wrote: On 2010-04-07 2:34 AM, Nikolay Shopik wrote: is there any list with clients which support setting ACL on imap-mailboxes? Up to now, a only know about KMail and imapACLM. Thunderbird will soon support that, patch already in review queue now. Hi Nikolay, Do you know if it will make it into 3.1? Hi Charles, Don't take my word on that but from what I see it should make it into 3.1. In reality this depends on when MoMo decide to release 3.1 and I highly doubt this happens in summer 2010, final release probably be ready at fall. Minus few months for release candidates and you've got feature freeze date.
[Dovecot] pigeonhole: naming and versioning
Hi Stephan, many thanks for all the work you do on the new sieve parts to dovecot. As a (downstream) packager I have some questions: a) pigeonhole is called a working title - will the final release be called something else like dovecot-sieve again? b) The versioning seems to go from 0.1.15 to 0.1.13. From a packager's POV it would be better to allow a natural version upgrade path. Perhaps the version in hg is just not updated? The reason for these questions/clarifications are that Angel and I are packaging dovecot 2.x betas and matching sieve plugins for allowing more people to a broader testing before the projects go gold. We'd like to have proper naming and versioning in place already for the beta packages. Thanks! -- Axel.Thimm at ATrpms.net pgpqB7XG6rRST.pgp Description: PGP signature
Re: [Dovecot] pigeonhole: naming and versioning
On 07/04/10 21:08, Axel Thimm wrote: b) The versioning seems to go from 0.1.15 to 0.1.13. From a packager's POV it would be better to allow a natural version upgrade path. Perhaps the version in hg is just not updated? Since -sieve and -managesieve codebases have been merged, the ideal version number from a packaging POV would be higher than last -managesieve release (0.11.11) to ensure simpler upgrade paths on -managesieve packages. -- Angel Marin http://anmar.eu.org/
Re: [Dovecot] pigeonhole: naming and versioning
On 07/04/10 21:08, Axel Thimm wrote: b) The versioning seems to go from 0.1.15 to 0.1.13. From a packager's POV it would be better to allow a natural version upgrade path. Perhaps the version in hg is just not updated? Since -sieve and -managesieve codebases have been merged, the ideal version number from a packaging POV would be higher than last -managesieve release (0.11.11) to ensure simpler upgrade paths on -managesieve packages. -- Angel Marin http://anmar.eu.org/
Re: [Dovecot] Forcing NOSELECT for a Maildir folder?
On Tue, Apr 06, 2010 at 12:38:15AM +0300, Timo Sirainen wrote: INBOX Local Folders --- (standard flags, but no NOSELECT) Public Folders --- NOSELECT That's a pretty uncommon setup. I fixed it now for v2.0: http://hg.dovecot.org/dovecot-2.0/rev/944591ed8ceb You could try if similar fix happens to work for v1.x. It looks like it would solve the problem I reported before, which is when you set the config to be Courier-compatible with an INBOX. namespace prefix, you can select INBOX.INBOX However, the code for mailbox_list_mailbox in 1.2 seems to be quite different to 2.0, and the patch doesn't apply. (1.2 doesn't have code to work out 'fname', for instance) Regards, Brian.
[Dovecot] Per-user flags for shared folders
As I see in 2.0 there willn't be ability to control which flags should be shared, and which should be per-user. But may be there is some plans to implement settings to control that? It'll be great if you can write in dovecot-shared file which flags should be per-user. It's very usefull for group mailboxes, when each user should work with such mailbox like with their own. Now I can't add permission for delete on group mailbox for anybody, because if somebody delete a message, it dissapear for other users of group mailbox. So my group mailboxes look like a big scrapyard[?] I can compile from sources and add also \Deleted flag to private flags, but it's not an elegant solution[?] And my idea is easy to implement :) Only add here: 305 shared_path = t_strconcat(box-path, /dovecot-shared, NULL); 306 if (stat(shared_path, st) == 0) 307 box-private_flags_mask = MAIL_SEEN; in maildir-storage.c some code for reading a mask from dovecot-shared file. Unfortunatelly I'm not a good programmer, so I can't make a patch myself((( 323.gif330.gif
Re: [Dovecot] sasl problem
Thank you,
my problem has been solved.
Are passwords stored as clear text in the sql database? I think apop
authentication requires that dovecot have the clear text password.
[...]
auth default {
mechanisms = plain login apop cram-md5
passdb sql {
args = /usr/local/etc/dovecot-sql.conf
}
userdb sql {
args = /usr/local/etc/dovecot-sql.conf
}
--
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
Re: [Dovecot] Manage mails from server
Hmm, PREAUTH is cool. But all Perl CPAN modules for IMAP can work only throw UNIX local sockets (or usual internet connection). May be there is an ability to create a socket when launchind 'dovecot --exec-mail imap' instead of working directly with STDIN/STDOUT?
[Dovecot] push mail support
Hello, I would like to use push in qmail+dovecot environments. Can someone tell me which components should I use to enable this feature for mobile devices? Thanks. -Ibrahim.
Re: [Dovecot] dovecot upgrade problems
Hi, Firstly its clear you did not remove your existing version installed by your OS's package manager. Backup your conf file before doing so. By default most source installs of any software install into /usr/local/ you might also want to consider make uninstall from your existing source build directory. Try as a starting point ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var ...other_options_here... then you'll end up with /var/run/dovecot/auth-master your conf files will end up in /etc and binary files will be in /usr/sbin and so on... with other goodies in /usr/lib/dovecot On Wed, 2010-04-07 at 09:58 +0200, Cieslak, Andreas wrote: Hi list, i made an upgrade from dovecot 1.0RC15 to 1.1.20 the default installation was under /etc/dovecot. The upgrade installation was made under /usr/local/etc. After that i changed all the paths in the /usr/local/etc/dovecot.conf and the dovecot-binary to work with the new installation. Even path-changes were made for /etc/init.d/dovecot to work with the version 1.1.20.
[Dovecot] dsync convert Maildir - mdbox, separators in subscriptions file
Hello,
I'm playing around with Dovecot 2.0 beta 4.
If I use dsync to convert a users mail stored in Maildir format to mdbox
format, the subscriptions file in the new mdbox is created using the wrong
mailbox separator ('.') leading to folders within folders not being readable by
clients using the subscription feature.
Excerpt from IMAP:
. LIST *
* LIST (\HasChildren) / Spam
* LIST (\HasNoChildren) / Spam/Test
. LSUB *
* LSUB () / Spam
* LSUB () / Spam.Test
I am not currently using Maildir, and have no plans to either, so I am very
pleased with mdbox using '/' as seperator.
I am considering to use Maildir as a transition format so that I can use
allready available scripts to do the job (uw2dovecot.pl first, then dsync).
So the question is, is this a bug in dsync?
At the time of conversion mail_location = maildir:~/Maildir
I used the following command to do the conversion:
# dsync -u username convert mdbox:~/mdbox
--
Frode Nordahl
[Dovecot] Dovecot 2.0 and QUOTA capability
Hello, In Dovecot 2.0 the QUOTA capability is not announced until after the user has logged in. This breaks quota-support in some webmail clients (Roundcube, Atmail, probably more). After searching the lists, I see that this was fixed as a bug back in 1.0, but I guess it crept back in. :-) 1.0.7: * OK Dovecot ready. . CAPABILITY * CAPABILITY IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS QUOTA STARTTLS AUTH=PLAIN . OK Capability completed. 2.0: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN] Dovecot ready. . capability * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN . OK Capability completed. -- Frode Nordahl
Re: [Dovecot] ImapTest build problem [SOLVED]
On Wed, 2010-04-07 at 17:10 +0400, Proskurin Kirill wrote: But seems to wiki needs fixing then. Because http://dovecot.org/nightly/dovecot-latest.tar.gz is 2.0 Well, I'm rather thinking that the code needs fixing, not wiki. :) Yes, but code update may be not soon but wiki update is few seconds and fix an misunderstanding. ;-) The wiki would then have to be updated back. I anyway updated imaptest now. Anyway - could you give some examples of using ImapTest for testing\benchmarking? Yes I saw http://www.imapwiki.org/ImapTest/Examples but I not a programmer and I don`t know IMAP protocol well and this numbers give me near nothing. There isn't really much else it can give you.. imaptest isn't useful for testing real world performance. The numbers it gives are mostly useful only when compared against another setup with the same imaptest parameters. The one exception I can think of is how many msgs/second you can save to a mailbox: imaptest - append=100 clients=10 signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Manage mails from server
On Thu, 2010-04-08 at 01:38 +0400, Неворотин Вадим wrote: Hmm, PREAUTH is cool. But all Perl CPAN modules for IMAP can work only throw UNIX local sockets (or usual internet connection). May be there is an ability to create a socket when launchind 'dovecot --exec-mail imap' instead of working directly with STDIN/STDOUT? With v2.0 you can add a UNIX socket listener to IMAP, but you still have to log in with it. Maybe you should enable some kind of master user logins. http://wiki.dovecot.org/Authentication/MasterUsers signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Dovecot 2.0 and QUOTA capability
On Thu, 2010-04-08 at 02:39 +0200, Frode Nordahl wrote: Hello, In Dovecot 2.0 the QUOTA capability is not announced until after the user has logged in. This breaks quota-support in some webmail clients (Roundcube, Atmail, probably more). This is pretty much intentional, because v1.x used to do horrible horrible things to get the capability line. I was hoping to avoid that in v2.0. This works for the most commonly used IMAP clients, so I don't think I'm going to change this. It's time to get the clients fixed instead. :) Besides, it's possible to support per-user capabilities, and presenting capabilities before login makes this impossible. Dovecot v2.0 presents capabilities in two possible ways, depending on if client sent a CAPABILITY command: a) the right way (use CAPABILITY imap resp code): * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN] Dovecot ready. x login user pass x 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] Logged in b) the wrong way (use untagged CAPABILITY), which is required to make it work with Outlook etc.: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN] Dovecot ready. a capability * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN a OK Capability completed. b login user pass * 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 b OK Logged in signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Manage mails from server
Thanks! Master Users are very good solution for me. 2010/4/8 Timo Sirainen t...@iki.fi On Thu, 2010-04-08 at 01:38 +0400, Неворотин Вадим wrote: Hmm, PREAUTH is cool. But all Perl CPAN modules for IMAP can work only throw UNIX local sockets (or usual internet connection). May be there is an ability to create a socket when launchind 'dovecot --exec-mail imap' instead of working directly with STDIN/STDOUT? With v2.0 you can add a UNIX socket listener to IMAP, but you still have to log in with it. Maybe you should enable some kind of master user logins. http://wiki.dovecot.org/Authentication/MasterUsers
Re: [Dovecot] push mail support
Hello, On 08/04/2010 00:35, Ibrahim Harrani wrote: Hello, I would like to use push in qmail+dovecot environments. Can someone tell me which components should I use to enable this feature for mobile devices? I think z-push is probably what you are looking for http://z-push.sourceforge.net/soswp/ Best Regards smime.p7s Description: S/MIME Cryptographic Signature
