- dovecot - dovecot.org

[Dovecot] INBOX as mbox, other mailboxes as maildir
by Paul de Weerd 21 Apr '06

21 Apr '06

All, I'm trying to teach dovecot to use the mbox format for /var/mail/%u and maildir for /home/%u/Mail/ but I'm having quite a hard time. This is Dovecot v1.0.beta3 under OpenBSD 3.9 on sparc64. I've been fiddling with default_mail_env and also tried separate namespaces, but all to no avail. Here's some of the things I tried : default_mail_env = maildir:/home/%u/Maildir:INBOX=mbox:/var/mail/%u ... default_mail_env = INBOX=mbox:/var/mail/%u:MAIL=maildir:/home/%u/Maildir/ ... namespace private { separator = / prefix = inbox = yes location = mbox:/var/mail/%u } namespace private { separator = / prefix = "Folders/" location = maildir:/home/%u/Mail } ... But all it does is complain that my mbox files dont have a cur/ directory in them or create mbox-type files in /home/%u/mail/, in stead of saving my mail in a maildir under /home/%u/Mail/. So using namespaces doesn't seem to be such a good idea after all, I can have extra maildirs under Folders/ in ~/Mail, but that's not where my IMAP client saves its sent mail. I'm quite obviously doing something wrong, is this possible at all ? What is the correct incantation for the default_mail_env setting for such a setup ? Any clues would be greatly appreciated, Cheers, Paul 'WEiRD' de Weerd -- >++++++++[<++++++++++>-]<+++++++.>+++[<------>-]<.>+++[<+ +++++++++++>-]<.>++[<------------>-]<+.--------------.[-] http://www.weirdnet.nl/

3 3

Re: [Dovecot] mountpoint_get broke the quota plugin
by Bill Boebel 21 Apr '06

21 Apr '06

On Fri, April 21, 2006 9:35, Timo Sirainen <tss(a)iki.fi> said: > On Tue, 2006-04-18 at 08:17 -0400, Bill Boebel wrote: > > Looks like the new mountpoint_get code broke the quota plugin. > > That's because linker is being smart and not linking the mountpoint code > in because it's not used by the binary itself. Fixed now in CVS by > linking mountpoint.o file manually to imap and deliver binaries. Cool. Thanks for fixing this. Bill

1 0

[Dovecot] multiple domains for the same user
by pyroneus 21 Apr '06

21 Apr '06

I have postfix and dovecot set up to use virtual domains. I am now experiencing a problem that when I log in as user1(a)domain1.tld and then log in as user1(a)domain2.tld all the emails are downloaded for user1(a)domain2.tld as it thinks all the messages are new. is there anyway to stop dovecot from saying that all the messages are new?

2 1

[Dovecot] dovecot.rawlog for imap-login
by Jared 21 Apr '06

21 Apr '06

I'm trying to see what users are sending for login. I added the rawlog binary in front of the imap-login in the config file. I'm not seeing any rawlogs. I added the dovecot.rawlog in the dovecot user directory (since that's what the imap-login process seems to run as) and it's permission are wide open. Still nothing. Help?

3 4

[Dovecot] Very Complex Master Password Challenge
by Marc Perkel 21 Apr '06

21 Apr '06

This might require adding some new code to Dovecot to pull this off. But it would be extremely powerful if I could get this to work. Here's the situation. Having a master password is great for helping users and doing tech support. But - suppose I'm hosting many domains and I want to create master passwords for each domain separately so that the owners of the domain can log in as any user within that domain? Here's the way I have things set up. I have a directory of passwd/shadow pairs for each domain as follows: /etc/vmail/passwd.domain1.com /etc/vmail/shadow.domain1.com /etc/vmail/passwd.domain2.com /etc/vmail/shadow.domain2.com Additionally I have a master domain used for management of the other domains. The master domain is an email account for each domain under the domain junkemailfilter.net. domain1.com(a)junkemailfilter.net domain2.com(a)junkemailfilter.net The password and shadow files are like the others: /etc/vmail/passwd.junkemailfilter.net /etc/vmail/shadow.junkemailfilter.net So - the idea is that the owners of the domain have access to the email accounts on junkemailfilter.net and what I'm hoping to do is that they can use this as the master password for their domain only. Example: domain1.com(a)junkemailfilter.net domain2.com(a)junkemailfilter.net I suppose that the master password feature needs another new feature to limit the scope of what it is allowed to be a master password for. Something perhaps like: passdb passwd-file { # Path for passwd-file args = /etc/vmail/shadow.junkemailfilter.net master = yes scope = *@%u } In the above example "%u" is the user part of the master password. So that that master user would be for example "domain1.com(a)junkemailfilter.net" and it would be the master password only for users of domain1.com and not domain2.com. So - if you can follow this - then you will see that this would be a really cool feature to have. And - I'm guessing that it might be easy to implement.

2 1

[Dovecot] okay, working, but not quite pretty...
by Chris Lea 21 Apr '06

21 Apr '06

Hi all. I got my previous problem fixed. Effective uid and gid fix in dovecot.conf file made it work. However, I'm still seeing this in my /var/log/dovecot.conf dovecot: 2006-04-13 21:09:00 Info: imap(chl(a)iaminla.com): Effective uid=1000, gid=1000 The uid and gid *should* both be 1009, and I can't for the life of me figure out how to configure that. I looked around the list and couldn't find the answer. Help a noob out please? I promise I'll write up a detailed howto for my debian + postfix + dovecot using static userdb's when I have it all working. :) -- --------------------------------------------------------------- "When moderate to highly intelligent people get bored, bad things happen." -- Ann Moreno (310) 709-4021 http://www.chrislea.com ---------------------------------------------------------------

2 1

[Dovecot] Master Password not working
by Marc Perkel 21 Apr '06

21 Apr '06

Trying to get the master password to work. What am I doing wrong? Trying this test: /etc/dovecot.masterusers master:{plain}test auth_master_user_separator=* auth default_with_listener { mechanisms = plain passdb passwd-file { # Master users that can log in as anyone args = /etc/dovecot.masterusers master = yes #pass =yes } passdb passwd-file { # Path for passwd-file args = /etc/vmail/shadow.%d } userdb passwd-file { # Path for passwd-file args = /etc/vmail/passwd.%d } socket listen { master { path = /var/run/dovecot/auth-master mode = 0666 } } } telnet localhost imap Trying 127.0.0.1... Connected to localhost.ctyme.com (127.0.0.1). Escape character is '^]'. * OK Dovecot ready. 1 login master*marc(a)perkel.com test 1 NO Authentication failed. Thanks in advance.

3 3

[Dovecot] dovecot died
by Obantec Support 21 Apr '06

21 Apr '06

Hi Still running 1.0 stable (an old release i know but until i see more stable reports on beta7 i will hold out). last night is the first time in months the dovecot has died. maillog has repeated lines of this. Apr 16 02:31:37 proteus2 dovecot: pipe() failed: Too many open files dovecot.log just shows last login Apr 16 02:31:36 Info: pop3-login: Login: username [IP] i restarted it Apr 16 08:38:04 Info: Dovecot v1.0-stable starting up and now it seems ok. anyone got a monitor script for watching the dovecot daemon and send a start if it dies? Mark

3 3

[Dovecot] hard link between courierimapuiddb and dovecot-uidlist?
by Jeff Tucker 21 Apr '06

21 Apr '06

Hi, guys. I'm attempting to transition between Courier IMAP and Dovecot. I may not be able to transition all the courierimapuiddb files instantly or even transition all my servers at the same time. Ideally, it wouldn't matter. Users can login and get to a Courier IMAP machine or a Dovecot machine and read their email (all mounted via NFS). My question is: is there any reason I can't just do a hard link between courierimapuiddb and dovecot-uidlist? That way, I can transition users over to Dovecot at my leisure. And, if I need to, I can move back to Courier. The hard link is essentially free and lets me make sure these files stay synced. Thanks Jeff

2 1

[Dovecot] Beta 7 maildir++ "unlimited quota"
by Apps Lists 21 Apr '06

21 Apr '06

Hi. It looks like Beta 7 is treating a zero quota in maildirsize as a literal quota value. The maildir++ specification says a zero quota means unlimited. Steve

2 1