- dovecot - dovecot.org

[Dovecot] Bug: quota-maildir.c, array accessed out of bounds
by Bill Boebel 22 Apr '06

22 Apr '06

Timo, In src/plugins/quota/quota-maildir.c, in the maildirsize_read() function, if the maildirsize file is greater that 5120 bytes, this code breaks because the while loop executes multiple times, incrementing size to a value larger than 5120, and then size is later used to referece the buf array out of bounds. To fix it you could add a break statement after "size+= ret;" so that the while loop is always only executed once: char buf[5120+1]; ... size = 0; while ((ret = read(fd, buf, sizeof(buf)-1)) != 0) { if (ret < 0) { if (errno == ESTALE) break; mail_storage_set_critical(storage, "read(%s) failed: %m", path); } size += ret; } if (ret < 0 || size == sizeof(buf)-1) { /* error / recalculation needed. */ (void)close(fd); t_pop(); return ret < 0 ? -1 : 0; } /* file is smaller than 5120 bytes, which means we can use it */ root->total_bytes = root->total_count = 0; /* skip the last line if there's no LF at the end */ while (size > 0 && buf[size-1] != '\n') size--; buf[size] = '\0';

1 0

[Dovecot] PAM authentication woes with MacOSX
by Jim Reid 22 Apr '06

22 Apr '06

Hi. I've just compiled and installed 1.0beta7 on MacOSX 10.4.6. I have lost the battle with PAM authentication. When I connect to the IMAP server and provide the correct user name and password, the mail client is told authentication failed. Here's what's in the log: Apr 21 22:47:43 shaun dovecot: auth(default): client in: AUTH 2 PLAIN service=IMAP secured lip=195.54.233.68 rip=195.54.233.69 resp=AGppbQB1bmxpbmsoLik= Apr 21 22:47:43 shaun dovecot: auth(default): pam(jim,195.54.233.69): pam_authenticate() failed: Authentication failure Apr 21 22:47:45 shaun dovecot: auth(default): client out: FAIL 2 user=jim Apr 21 22:47:53 shaun dovecot: auth(default): client in: AUTH 3 PLAIN service=IMAP secured lip=195.54.233.68 rip=195.54.233.69 resp=AGppbQB1bmxpbmsoLik= Apr 21 22:47:53 shaun dovecot: auth(default): pam(jim,195.54.233.69): pam_authenticate() failed: Authentication failure Apr 21 22:47:53 shaun dovecot: auth(default): client out: FAIL 3 user=jim Apr 21 22:47:55 shaun dovecot: imap-login: Aborted login: user=<jim>, method=PLAIN, rip=195.54.233.69, lip=195.54.233.68, TLS After some googling, I found a posting from this list that claimed the following PAM setup would work for MacOSX: # dovecote: auth account password session auth required pam_nologin.so auth sufficient pam_securityserver.so auth sufficient pam_unix.so auth required pam_deny.so account required pam_permit.so password required pam_deny.so session required pam_uwtmp.so It didn't. :-( If it had, I wouldn't be posting this. :-) BTW, that posting said the wiki entry for PAM didn't work on MacOSX. Which is true. I tried that unsuccessfully too. Can anyone shed any light on what's been misconfigured or how to turn on enough debugging to show where I'm going wrong? Thanks. BTW, here's what I think is the relevant bit of dovecote.conf: auth default { mechanisms = plain passdb pam { args = dovecot } userdb passwd { } user = root }

1 0

[Dovecot] Bug: maidirsize double counting moved messages
by Bill Boebel 21 Apr '06

21 Apr '06

The maildirsize file is double counting messages when moving them from folder to folder when "maildir_copy_with_hardlinks = no": 1024000000000S 99337571 19370 14010590 2 <--- moved from subfolder to subfolder -7005295 -1 14010590 2 <--- moved from subfolder to INBOX -7005295 -1 14010590 2 <--- moved from INBOX to subfolder -7005295 -1 14010590 2 <--- moved from subfolder to subfolder -7005295 -1 When I change "maildir_copy_with_hardlinks" to "yes", this problem only occurs when moving in and out of the INBOX, but not when moving from subfolder to subfolder: 7005295 1 <--- moved from subfolder to subfolder -7005295 -1 14010590 2 <--- moved from subfolder to INBOX -7005295 -1 14010590 2 <--- moved from INBOX to subfolder -7005295 -1 7005295 1 <--- moved from subfolder to subfolder -7005295 -1

1 0

[Dovecot] Question about mail storage
by Stewart Dean 21 Apr '06

21 Apr '06

I am in the throes of trying to understand all the issues of transforming an old UW Imap server with mbox (I think) INBOX format running sendmail and procmail serving 3500 users to dovecot and maildir format. Currently, the folders are under ~/mail and the INBOXes are under /var/spool/mail. If I understand correctly, the typical default Dovecot/maildir format installation will have both the INBOX and folders (prefixed with a period), so they take the format: .<foldername>) under ~/Maildir. Right? I am planning to do a gradual phaseover of one chunk of ids at a time........ "I am in a maze of twisty tunnels, all alike. A dwarf runs by........" Some questions: 1) In the UW IMap docs, formats.txt discusses a bunch of different mailbox formats. I am unclear as to whether I currently have what Crispin describes at .unix format or .mbx format. > . unix This is the traditional UNIX mailbox format, in use for nearly > 30 years. It uses a line starting with "From " to indicate > start of message, and stores the message status inside the > RFC822 message header. > > unix is not particularly efficient; the entire mailbox file > must be read when the mailbox is open, and when reading message > texts it is necessary to convert the newline convention to > Internet standard CR LF form. unix preserves UIDs, and allows > the creation of keywords. > > Only one process may have a unix-format mailbox open > read/write at a time. > and ... > . mbx This is the current preferred mailbox format. It can be > handled quite efficiently by c-client, without the problems > that exist with unix and mmdf formats. Messages are stored > in Internet standard CR LF format. > > mbx permits shared access, including shared expunge. It > preserves UIDs, and allows the creation of keywords. How do I tell them apart? Alternately, how do I tell if what I now have (some sort of one big single-file INBOX) is mbox? Or is what he's referring to as unix just mbox 2) How to change Where Things End Up a) The users' ~/.procmailrc pretty much consists of: MAILDIR=$HOME/mail Am I correct in assuming that this should be changed to: MAILDIR=$HOME/Maildir/ ? b) Mail appears to end up in /var/spool/mail/<username> because that's the procmail default (ORGMAIL). To redirect individual users (because this will be a gradual changeover), am I correct in assuming that putting: DEFAULT=$HOME/Maildir/ in ~/.procmailrc will redirect incoming mail? 3) I see that, in the default configuration, /everything/ will now be under ~/Maildir and thus in the home directories. Is there a reason to get away from a separate INBOX directory (we use /var/spool/mail)? I'd have to rebuild the homedir filesystems to accommodate the INBOX demands. This isn't all that big a deal, I'd like to understand the rationale..or should I just bow to the inevitable? 4) Pardon my stupidity, but how is the Dovecot INBOX under maildir++ organized? a) Is it a separate directory under ~/Maildir (say ~/Maildir/INBOX or some such) that has a separate file for each message or b) are the INBOX messages just mixed in with the folders under ~/Maildir. If so, how are they differentated? Enlighten my ignorance,.please! I've been reading docs today until my brain feels like custard, but I couldn't seem to get clear definitive answers to these questions........ Thanks in advance. -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

5 6

[Dovecot] How to configure virtual use suport.
by Slawomir Orlowski (Cympak) 21 Apr '06

21 Apr '06

Hello, I have RHEL v4 Linux. I have always been using exim with teapop (po3 client) for my emails. I would like to try dovecot (imap) because I would like to implement squirrelmail. I'm hosting several domains with email each on different IP. I have the some user names in different domains with my pop3 teapop. Can I have it with dovecot. I managed to configure exim to deliver messages for localuser to Maildir directory. directory = /var/spool/mail/${local_part}/Maildir and for virtual_users to Maildir directory. directory = /var/spool/mail/${domain}/${local_part}/Maildir This is working. Email are delivered. But I cannot to connect with my Outlook Express to imap server and download them. I cannot see how dovecot would differentiate between users with the some named in different domains. I believe that me configurations is not right. I would like for starters to have real user to be checked (like in teapop) against /etc/password /etc/shadow file, and virtual user against /etc/mail/passwd.domain file which would contain login:passwd pairs. Do I need like with teapop different IP for every domain ? How do I do that? Any advice would be appreciated. I'm going for a few days vacation I hope that somebody will be able to give me some hints. I have attached my dovecot.conf file. regards Slawomir Orlowski

1 0

[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