- dovecot - dovecot.org

[Dovecot] master user
by Tom Bombadil 15 Feb '07

15 Feb '07

Greetings all... We are thinking about using the master DB, so a few admins can impersonate an ordinary user. So, we want to define one master for a set of users. And this administrator cannot be master of the other users? Can this be done somehow? Reading the docs, it seems that if a user is defined as master, it can login as everyone. Thanks for any hint.

4 3

[Dovecot] Startup errors
by Steven F Siirila 15 Feb '07

15 Feb '07

I just finished setting up a test Dovecot server (1.0-rc15, Solaris 10) and noticed upon start of Dovecot (after rebooting the server) that the imap-login and pop3-login processes spew errors as follows, which I can only assume is due to the fact that dovecot-auth has not fully initialized yet... it seems to me that these login processes are getting started too early, or should at least be waiting for dovecot-auth to get started. Jan 31 15:55:06 hostname dovecot: Dovecot v1.0.rc15 starting up Jan 31 15:55:07 hostname dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 31 15:55:07 hostname dovecot: pop3-login: Can't connect to auth server at default: Connection refused Jan 31 15:55:07 hostname dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 31 15:55:07 hostname last message repeated 1 time Jan 31 15:55:07 hostname dovecot: pop3-login: Can't connect to auth server at default: Connection refused Jan 31 15:55:07 hostname last message repeated 1 time Jan 31 15:55:07 hostname dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 31 15:55:07 hostname last message repeated 9 times Jan 31 15:55:07 hostname dovecot: pop3-login: Can't connect to auth server at default: Connection refused Jan 31 15:55:07 hostname last message repeated 9 times -- Steven F. Siirila Office: Lind Hall, Room 130B Internet Services E-mail: sfs(a)umn.edu Office of Information Technology Voice: (612) 626-0244 University of Minnesota Fax: (612) 626-7593

2 1

[Dovecot] Q on configuring shared mboxes
by Mikhail Teterin 15 Feb '07

15 Feb '07

Hello! I have the following three types of mailboxes on my server: 1) Regular user mail /var/mail/<user> in mbox format 2) Suspected spam in /var/tmp/spamprobe in mbox format 3) Archived mailing list in /home/mks/mksarch in mbox format I want the 1) to be only accessible to the respective <user>, obviously (POP3 and/or IMAP4). I wanted the 2) to be accessible to all users -- and I want them to be able to move stuff out of it into their own mboxes (IMAP4 is enough). I want the 3) to be accessible _read only_ to anyone, who enters the correct username/password (preferably -- without creating a special Unix account). (IMAP4 or POP3) So far, I have only been able to achieve 1). Could someone, please, help me configure dovecot for the 2) and the 3)? Thanks! -mi

2 1

[Dovecot] Dovecot ACL
by Barry Kwok 15 Feb '07

15 Feb '07

I am using 1.0-rc19 version. I made a global ACL file in /etc/dovecot-acls/Public as: owner lrsi user=manager rl The owner cannot delete/move mail inside his Public folder as I want. But the user "manager" cannot subscribe/view to other's Public folder. What I have missed?

2 1

[Dovecot] lda sieve broken after upgrade
by lenny＠edpausa.com 15 Feb '07

15 Feb '07

upgraded to rc19. using maildirs. solaris 9/cc. removed all modules from pop/imap/lda subdirs and first upgraded dovecot to rc19 and then used dovecot-sieve-1.0.1 sources to build against the dovecot source directory ( everything now builds nicely on Solaris, thank you Timo ). added "cmusieve" to the list of plugins used by lda. ail_plugins = cmusieve now getting this: deliver(lenny): Error: dlopen(/usr/local/dovecot/lib/dovecot/lda//lib90_cmusieve_plugin.so) failed: ld.so.1: deliver: fatal: relocation error: file /usr/local/dovecot/lib/dovecot/lda//lib90_cmusieve_plugin.so: symbol deliver_mail: referenced symbol not found anyone ? on the same machine, mbox based dovecot rc19 with dovecot ( sieve ) lda, works and upgraded without any issues, although the prior version must have been different, since the cmusieve statement was already present.

2 2

[Dovecot] Hello, new to the list
by Vikram Goyal 15 Feb '07

15 Feb '07

Hello Guys! I have just joined the list as I needed some clarifications, help etc. I am not sure what I want is possible and I have been unable to do it myself, read lots of dovecot wiki pages, debian lists, dovecot archives, experimented myself and so on. I have a mail dir ~/Mail where all my mails get distributed to their respective folders through procmail filters. The heirarchy is as follows: ~/Mail/ /inbox --> maildir /trash --> trash maildir /newsletter --> mbox lists/ --> normal dir /dovecot --> dovecot list maildir /some other list maildirs I wanted to access them through dovecot. I have tried namespaces etc but have been unable to accomplish till now. Kindly help. Thanks! -- vikram... |||||||| |||||||| ^^'''''^^||root||^^^'''''''^^ // \\ )) //(( \\// \\ // /\\ || \\ || / )) (( \\ -- o ~|~ = Registered Linux User #285795

3 3

[Dovecot] sieve question
by Xueron Nee 15 Feb '07

15 Feb '07

hi, I am testing deliver with sieve support, and want to use it to filter chinese. But I found it doesn't work. an encoded subject: =?GB2312?B?aSBhbSBhIGNoaW5lc2U=?= decoded content is: i am a chinese and i have such rules: require "fileinto"; if header :contains "Subject" "GB2312" { fileinto "Hello"; } if header :contains "Subject" "chinese" { fileinto "Trush"; } but the first one acts. if a delete the first rule, like this: require "fileinto"; if header :contains "Subject" "chinese" { fileinto "Trush"; } message was delived to INBOX. so, any help? Thanks! -- Xueron Nee <xueron(a)gmail.com>

2 1

[Dovecot] auto-detection of user mailbox type - followup
by John Harper 15 Feb '07

15 Feb '07

In http://www.dovecot.org/list/dovecot/2006-December/018253.html Timo Sirainen wrote > > You can still change NAMESPACE_* environments. I don't remember how > exactly now, but you can do eg. "set > /tmp/sets" in the script, see > what it has set and modify them in the script. in response to my query regarding setting the mail_location in namespaces from a mail_executable script. The purpose of this is to be able to select on a per-user basis whether they're using Maildir or mbox format (I don't want to convert 12000 users all at once, and some users have no need or desire to change formats - they still use mail/elm etc) and also have the UW-IMAP compatibility namespaces to take care of all the clients currently configured with imap server directory = mail/. This all works, with one small bug left. For reference, here's the gist: In the dovecot.conf file place the usual namespace directives following the Namespaces wiki: namespace private { separator = / prefix = inbox = yes } #for UW backwards compatibility: namespace private { separator = / prefix = mail/ hidden = yes } namespace private { separator = / prefix = ~/mail/ hidden = yes } namespace private { separator = / prefix = ~%u/mail/ hidden = yes } define the mail_executable under protocol imap: mail_executable = /usr/local/dovecot/lbin/imap.sh and write the imap.sh script: ------start imap.sh--------------------------------------------------- #!/bin/sh # determine if user is in mbox or Maildir mode # Maildir takes precedence and is identified by the existence of # both a .procmailrc recipe and the Maildir directory. # Without a .procmailrc file, there's no recipe to force delivery in # Maildir format, so any existing Maildir is spurious # The .procmailrc should contain DEFAULT=Maildir/ # Set the absolute path to this script as the mail_executable for # the imap protocol in dovecot.conf. # It appears that this script is run as the user in their home dir if [ -f .procmailrc -a -d Maildir ]; then MAIL='maildir:~/Maildir'; export MAIL else MAIL='mbox:~/mail:INBOX=~/.mail'; export MAIL fi # each namespace defined in the conf file needs to have the mail # location defined which is set in environment vars # NAMESPACE_1 etc NAMESPACE_1=$MAIL; export NAMESPACE_1 NAMESPACE_2=$MAIL; export NAMESPACE_2 NAMESPACE_3=$MAIL; export NAMESPACE_3 NAMESPACE_4=$MAIL; export NAMESPACE_4 #debugging to see what else we can play with #set >> /tmp/d exec /usr/local/dovecot/libexec/dovecot/imap ------end imap.sh----------------------------------------------------- However, it appears that the root dir '~/mail' string is used at some point before the tilde-expansion takes place. I see a literal ~ directory in the users home, with an empty mail directory inside. After that it picks up the proper location and works correctly. I tried a %h and got a literal %h directory. So for now I made a simple workaround by using the absolute path to the home directory: # use home variable (depends on this script running in users home) # During startup it seems like ~/mail is interpreted as a string and # a spurious ~ folder is created, before the ~ is expanded home=`/bin/pwd` if [ -f .procmailrc -a -d Maildir ]; then MAIL="maildir:$home/Maildir"; export MAIL else MAIL="mbox:$home/mail:INBOX=$home/.mail"; export MAIL fi Thanks, John Harper ------------------------------------------------- Senior Systems Administrator Information and Instructional Technology Services University of Toronto Scarborough harper(a)utsc.utoronto.ca

2 1

[Dovecot] dovecot and libnss-ldap
by Nicolas Boullis 15 Feb '07

15 Feb '07

Hi, I've been using dovecot 0.99.14 for a few years, with libpam-ldap and libnss-ldap, and never experienced any problem with those. I expect to soon switch to dovecot 1.0rc15 (or whatever gets available in Debian Etch, hopefuly dovecot 1.0), but I've seen some warnings against dovecot+libnss-ldap... Is the problem with libnss-ldap a recent problem (I mean it was not a problem with older dovecot such as my 0.99.14)? Is it still a problem even with 1.0rc22? Is there any hope to have it fixed before 1.0? Note that while most of the users I have to deal with are in my LDAP directory, a few ones are not and are in /etc/passwd. Hence, "userdb ldap" is probably not an option for me (and I'm quite happy with configuring all my servers with PAM and NSS). Cheers, Nicolas

2 6

[Dovecot] who limit the process deliver number?
by Antonio Casado Rodríguez 15 Feb '07

15 Feb '07

Hi, i have postfix-2.3.6, dovecot-1.0-rc19 and dovecot-lda Where i limit the process number deliver, in postfix or dovecot.conf Thanks.

2 1