- dovecot - dovecot.org

[Dovecot] Fw: Shared mailboxes and INBOX
by Keith Edmunds 01 Aug '09

01 Aug '09

Should users of a shared mailbox be able to see both their personal inbox and that of the shared mailbox? Thanks, Keith Begin forwarded message: Date: Wed, 29 Jul 2009 17:50:08 +0100 From: Keith Edmunds <kae(a)midnighthax.com> To: dovecot(a)dovecot.org Subject: [Dovecot] Shared mailboxes and INBOX I'm trying to implement a shared mailbox: in other words, we have a generic email address ("security@") which we want a number of users to be able to monitor. The problem I have is that users can see folders under that shared mailbox but can't see the INBOX. All the users in question have their own INBOX in their private namespace, so does this raise a conflict with monitoring another mailbox's INBOX? Configuration: -------------------------------------------------------------------------------- # dovecot -n # 1.2.1: /etc/dovecot/dovecot.conf # OS: Linux 2.6.26-2-686 i686 Debian 5.0.2 log_timestamp: %Y-%m-%d %H:%M:%S disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_privileged_group: mail namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: public separator: / prefix: shared/ location: maildir:/home/publicfolders:INDEX=~/Maildir/public list: yes namespace: type: shared separator: / prefix: security/ location: maildir:/home/securitymailbox/Maildir:INDEX=~/Maildir/securitymailbox list: yes auth default: passdb: driver: pam userdb: driver: passwd -------------------------------------------------------------------------------- Thanks, Keith

1 0

[Dovecot] Solaris 10 dovecot-latest configure error
by Tomi Vainio 31 Jul '09

31 Jul '09

Hi, I've got latest source code from http://dovecot.org/nightly/dovecot-20090731.tar.gz It's a minor bug that mysql.h test fails because CFLAGS are missing from this test. Tomppa > checking for mysql_init in -lmysqlclient... yes > checking mysql.h usability... yes > checking mysql.h presence... no > configure: WARNING: mysql.h: accepted by the compiler, rejected by the preprocessor! > configure: WARNING: mysql.h: proceeding with the compiler's result > checking for mysql.h... yes > checking for mysql_ssl_set in -lmysqlclient... yes > configure:33185: checking mysql.h usability > configure:33197: cc -c -xO4 -I/usr/sfw/include/mysql -R/usr/sfw/lib:/usr/lib/sasl -L/usr/sfw/lib -L/usr/lib/sasl -I/usr/sfw/include conftest.c >&5 > configure:33203: $? = 0 > configure:33207: test -z > || test ! -s conftest.err > configure:33210: $? = 0 > configure:33213: test -s conftest.o > configure:33216: $? = 0 > configure:33226: result: yes > configure:33230: checking mysql.h presence > configure:33240: cc -E conftest.c > "conftest.c", line 127: cannot find include file: <mysql.h> > cc: acomp failed for conftest.c

4 4

[Dovecot] Clients and dovecot-uidlist
by Thomas Hummel 31 Jul '09

31 Jul '09

Hello, I'm trying to figure out what exactly (and why) are the consequences of a lost or removal of the dovecot-uidlist file on an IMAP client (Thunderbird for instance). I took for granted that it was that the client would download all messages again since it might be confused by some UID changes. But I don't really see why (on the IMAP protocol level) and I don't know how to reproduce it. My understanding is that . dovecot-uidlist is not recreated until some client selects the mailbox . the client does something like : x UID fetch 1:* (FLAGS) to begin with anyway. So I guess the problem does not occur when no new messages arrive on the mailbox since the same UIDs would be assigned to the same messages ? But why would that change ? In which situation ? But can you show me some IMAP protocol command exchange that would illustrate . when such a problem can occur . how the client would detect that there has been some UID corruption . how it would fix it Thanks -- Thomas Hummel

2 33

[Dovecot] sieve delivery to utf folders
by Nikita Koshikov 31 Jul '09

31 Jul '09

Hello list, Today, my users have noticed, that delivery to folders with non-english names is broken. For example, if I create russian directory, it correct encoded and display into mail-client program and my webmail: Encoded: Normal view .INBOX.&BEIENQRBBEI- русс This is part of sieve script, which routing delivery to russian folder. .... elsif allof (header :contains "Subject" "qwe") { fileinto "INBOX/&BEIENQRBBEI-"; } But, when actualy delivery take place, in logs I have Jul 30 17:13:49 deliver(koshikov.n(a)domain.com): Info: sieve: msgid=<4A71A9E6.5040301(a)domain.com>: stored mail into mailbox 'INBOX/&-BEIENQRBBEI- And folder .INBOX.&-BEIENQRBBEI- appears in users maildir. This folder can't be unencoded by mail-client program and user see exactly "&-BEIENQRBBEI-" under INBOX directory(also normaly encoded directory "&BEIENQRBBEI-" --> "русс" displays correct). Something breaks encoding and adds sing "-" to all words in utf encoded directory names. I can't tell exactly when this problem appear, but I remember that I have tested delivery to russian directories by sieve scripts and all worked fine. My current dovecot installation is 1.2.2, dovecot-sieve-0.1.9 and managesieve-0.11.7

4 6

Re: [Dovecot] whining
by A. van Harten 31 Jul '09

31 Jul '09

Be a man, Jim, and write this in public. [QUOTE] Jim Reid[/QUOTE] > On 31 Jul 2009, at 09:36, A. van Harten wrote: > >> Sorry, but the answers on this mail group are written with as few >> words as >> possible - if it was written in Finnish, I'd understand just as much >> as I >> do now. >> Googling on a Dovecot problems results always in www.dovecot.org or >> one of >> its child sites. Always. >> Googling on a Linux question results always in experts-exchange. >> Always. > > Clearly, dovecot is not for you. Now please go back to the linux world > you came from. You appear to be comfortable there. > > I am also disgusted and very annoyed with the tone of your recent > email: negative, childish, destructive and counter-productive. You did > not identify any particular problem, suggest other approaches or point > at areas where specific improvements could be made. You just whined > about the results of google searches. > -- Med venlig hilsen, Met vriendelijke groeten,

2 2

Re: [Dovecot] Several errors
by A. van Harten 31 Jul '09

31 Jul '09

Tried that, same result. dovecot: Jul 25 00:55:41 Info: Dovecot v1.0.7 starting up dovecot: Jul 25 00:55:42 Error: Temporary failure in creating login processes, slowing down for now dovecot: Jul 25 00:55:42 Error: imap-login: USER environment missing dovecot: Jul 25 00:55:42 Error: imap-login: USER environment missing dovecot: Jul 25 00:55:42 Info: Created login processes successfully, unstalling dovecot: Jul 25 00:55:42 Error: child 3850 (login) returned error 89 dovecot: Jul 25 00:55:42 Error: child 3851 (login) returned error 89 dovecot: Jul 25 00:55:42 Error: Temporary failure in creating login processes, slowing down for now dovecot: Jul 25 00:55:42 Error: imap-login: USER environment missing dovecot: Jul 25 00:55:42 Error: child 3852 (login) returned error 89 dovecot: Jul 25 00:55:42 Info: Created login processes successfully, unstalling [root@nestorix etc]# dovecot -n # 1.2.1: /usr/local/etc/dovecot.conf Warning: There is no way to login to this server: disable_plaintext_auth=yes, ssl=no, no non-plaintext auth mechanisms. Warning: There is no way to login to this server: disable_plaintext_auth=yes, ssl=no, no non-plaintext auth mechanisms. # OS: Linux 2.6.18-128.2.1.el5 i686 CentOS release 5.3 (Final) ext3 base_dir: /var/run/dovecot/ log_path: /var/log/dovecot info_log_path: /var/log/dovecot protocols: pop3 pop3s imap imaps ssl: no login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap login_executable(imap): /usr/libexec/dovecot/imap login_executable(pop3): /usr/libexec/dovecot/pop3-login login_greeting: Havecom Mailserver ready. valid_chroot_dirs: /var/mail/vhosts mail_location: maildir:/var/mail/vhosts/%d/%n/ mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: executable: /usr/libexec/dovecot/dovecot-auth username_translation: "/$ verbose: yes passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: passwd-file args: /etc/dovecot/userdb socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix [root@nestorix etc]# service dovecot stop Stopping Dovecot Imap: [ OK ] [root@nestorix etc]# gedit /var/log/dovecot [root@nestorix etc]# service dovecot start Starting Dovecot Imap: [ OK ] [root@nestorix etc]# gedit /var/log/dovecot ^C [root@nestorix etc]# dovecot -n # 1.2.1: /usr/local/etc/dovecot.conf Warning: There is no way to login to this server: disable_plaintext_auth=yes, ssl=no, no non-plaintext auth mechanisms. Warning: There is no way to login to this server: disable_plaintext_auth=yes, ssl=no, no non-plaintext auth mechanisms. # OS: Linux 2.6.18-128.2.1.el5 i686 CentOS release 5.3 (Final) ext3 base_dir: /var/run/dovecot/ log_path: /var/log/dovecot info_log_path: /var/log/dovecot protocols: pop3 pop3s imap imaps ssl: no login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap login_executable(imap): /usr/libexec/dovecot/imap login_executable(pop3): /usr/libexec/dovecot/pop3-login login_greeting: Havecom Mailserver ready. valid_chroot_dirs: /var/mail/vhosts mail_location: maildir:/var/mail/vhosts/%d/%n/ mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: executable: /usr/libexec/dovecot/dovecot-auth username_translation: "/$ verbose: yes passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: passwd-file args: /etc/dovecot/userdb socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix [root@nestorix etc]# Albert [QUOTE] Timo Sirainen[/QUOTE] > On Sat, 2009-07-25 at 00:07 +0200, FraNL wrote: >> Running OS: CentOS 5.3 (2.6.18-128.2.1.el5) >> >> 1. >> My Linux distribution comes with Dovecot 1.0.7. After trying to make it running, I encoutnered many problems. So I decided to upgrade to 1.2.1. When running dovecot -r from CLI, it returns with version 1.2.1. But at the top of the log file it says: Info: Dovecot v1.0.7 starting up >> >> So I am not sure which version I am running. > > It means you're using some weird mix of both. Get rid of all of Dovecot v1.0 binaries (rpm -e dovecot or something) and your problems should go away. > > -- Med venlig hilsen, Met vriendelijke groeten, -- Med venlig hilsen, Met vriendelijke groeten,

4 15

Re: [Dovecot] Several errors
by A. van Harten 31 Jul '09

31 Jul '09

[QUOTE] Charles Marcus[/QUOTE] > > Who says you have to install it? Almost all the fora which are speaking of setting up a mail server tell me to install Dovecot > And who is it that you think owes you 'descent support' for free? When and where did I spoke about FREE? I never said I didn't want to pay for it!!! Please don't think for me... > That said, the support on the dovecot list is the best I've seen, even > when people get attitudes (like yours)... Attitudes? Since when is a normal business inquiry not appropriate? > If you want to learn linux, and learn how to admin a mail server, you're > expected to do some leg work yourself... no one expects you to be a > guru, but a little googling on how to change ownership of files in linux > would most likely answer this particular question. Sorry, but the answers on this mail group are written with as few words as possible - if it was written in Finnish, I'd understand just as much as I do now. Googling on a Dovecot problems results always in www.dovecot.org or one of its child sites. Always. Googling on a Linux question results always in experts-exchange. Always. > > Also, the attititude will most likely get surprising little response. If > you want to get help from someone for free, it helps to ask nicely. I don't agree. I know the way of asking isn't the most nice way - and I also apologise to them, who assisted me! But who cares if I agree with someone, who didn't assist me at all, but who only is capable of writing negatively about me? > Thats said, I wouldn't be surprised if Timo responds nicely anyway... > I've seen him respond to much worse emails than yours, and yours was > pretty bad... Pretty bad? You misunderstood me, my friend. Try to read reasonable next time. That helps! > > -- > > Best regards, > > Charles > -- Med venlig hilsen, Met vriendelijke groeten,

1 0

[Dovecot] Limiting user access
by Darvin Denmian 30 Jul '09

30 Jul '09

Hello, Is there a way to restrict clients access, for example: user1(a)domain.com -> only access pop3 user2(a)domain.com -> can access pop3 and imap in Dovecot? Thanks !!!

2 2

Re: [Dovecot] POSIX stupidity
by Timo Sirainen 30 Jul '09

30 Jul '09

On Thu, 2009-07-30 at 20:21 +0200, Remi Gacogne wrote: > Le jeudi 30 juillet 2009, Timo Sirainen a écrit : > > > > What the hell were POSIX people thinking?? This is the first syscall > > > I've seen that behaves like this, and apparently without any good > > > reason! Wonder how many other new system calls there are like this, that > > > I haven't noticed yet.. > > > > Looks like all posix_*() syscalls do that. Wonder if there are more. > > Looks like too many people were incorrectly using errno, especially in multi- > threaded context. > > From http://www.unix.org/whitepapers/reentrant.html : > > "In addition, all POSIX.1c functions avoid using errno and, instead, return > the error number directly as the function return value, with a return value of > zero indicating that no error was detected. This strategy is, in fact, being > followed on a POSIX-wide basis for all new functions. " But that doesn't solve anything, because old functions' API can't be changed. The only thing this change did was to make it more difficult for programmers to remember how functions' error handling should be done. In both APIs the success is indicated by returning 0, which makes it especially difficult to notice when it's being used wrong. If they really had to change this, it would have been much better to both set errno and return -error, that way it would have allowed also 2/3 of the old style error checks: if (posix_fallocate(..) < 0) perror() // works if (posix_fallocate(..) != 0) perror() // works if (posix_fallocate(..) == -1) perror() // doesn't work Now none of them work. I did also a quick google code search for posix_fallocate and found several other programs that handle the error wrong. And I'm sure it's only going to grow. Oh well, maybe some day gcc and libc add some features to catch at least the < 0 and == -1 usage (which would already work if posix_fallocate() had been specified to return unsigned int, not int).

1 0

[Dovecot] AIX and posix_fallocate
by Ralf Becker 30 Jul '09

30 Jul '09

Hi, AIX's implementation of posix_fallocate is a little bit, let me say, peculiar. Attached is a patch to "fix" (=work around) this. Without you'll see this in the logs: Jul 28 01:17:41 trevi mail:err|error dovecot: IMAP(beckerr): posix_fallocate() failed: File exists Jul 28 01:17:41 trevi mail:err|error dovecot: IMAP(beckerr): file_set_size() failed with mbox file /u/f0/rzuser/beckerr/Mail/Ham: File exists Funny, isn't it? This is what it should be: Jul 28 01:17:41 trevi mail:err|error dovecot: IMAP(beckerr): posix_fallocate() failed: Operation not supported on socket Jul 28 01:17:41 trevi mail:err|error dovecot: IMAP(beckerr): file_set_size() failed with mbox file /u/f0/rzuser/beckerr/Mail/Ham: Operation not supported on socket The problem is, that errno is not correcly set, when posix_fallocate returns EOPNOTSUPP (="Operation not supported on socket"). In this case the return code has to be checked rather than errno. When patched dovecot handles err==EOPNOTSUPP the same way like errno==EINVAL on Solaris. A note for all AIX Admins: Without APAR IZ48778: POSIX_FALLOCATE() FAILS WITH ERROR-25(ENOTTY) resp. IZ46961: POSIX_FALLOCATE() FAILS WITH ERROR-25(ENOTTY) APPLIES TO AIX 5300-06 you don't even get EOPNOTSUPP: posix_fallocate fails with NOTTY. So you have to install one of this fixes to make the patch work. Ralf -- ______________________________________________________________________ Dipl.-Inform. (FH) Ralf Becker Rechenzentrum (r/ft) der FH Trier (Network|Mail|Web|Firewall) University of applied sciences Administrator Schneidershof, D-54293 Trier Mail: beckerr(a)fh-trier.de Fon: +49 651 8103 499 Web: http://www.fh-trier.de/~beckerr Fax: +49 651 8103 214 PubKey: http://www.fh-trier.de/~beckerr Crypto: GnuPG, S/MIME ______________________________________________________________________ Wenn Gott gewollt haette, dass E-Mail in HTML geschrieben wuerden, endeten Gebete traditionell mit </amen>. (Tom Listen) --- ./lib/file-set-size.c.org 2009-07-06 12:56:17.000000000 +0200 +++ ./lib/file-set-size.c 2009-07-06 12:54:40.000000000 +0200 @@ -43,9 +43,15 @@ #ifdef HAVE_POSIX_FALLOCATE if (posix_fallocate_supported) { - if (posix_fallocate(fd, st.st_size, size - st.st_size) == 0) + int err; + if ((err = posix_fallocate(fd, st.st_size, size - st.st_size)) == 0) return 0; + if (err == EOPNOTSUPP /* AIX */ ) { + /* Ignore this error silently. + You have to test err, because errno is not + correcly set on some versions of AIX */ + } else if (errno != EINVAL /* Solaris */) { if (!ENOSPACE(errno)) i_error("posix_fallocate() failed: %m");

4 4