- dovecot - dovecot.org

[Dovecot] [PATCH] pass struct io * to io_loop_handle_add()/io_loop_handle_remove()
by Andrey Panin 25 Aug '04

25 Aug '04

Hello, currently I'm working on new ioloop handler which uses epoll(4) API introduced in Linux kernel 2.6. In this API each fd added to fd set by epoll_ctl system call can be accompanied with user supplied data (integer or void pointer). epoll_wait syscall reports arrived events as an array of structures containing event mask and user data. Attached patch replaces fd and condition parameters passed to io_loop_handle_add() with struct io pointer. Now io_loop_handle_add() can pass this pointer as user data to epoll_ctl syscall and when event arrives we will have corresponding io structure pointer for free withiot traversing possibly long ioloop->ios list. Please take a look. Best regards. -- Andrey Panin | Linux and UNIX system administrator pazke(a)donpac.ru | PGP key: wwwkeys.pgp.net

2 5

[Dovecot] FreeBSD - dovecot: We couldn't drop root group privileges
by Igor B. Bykhalo 25 Aug '04

25 Aug '04

Hi, I installed Dovecot on FreeBSD 4-STABLE machine and have a problem. MTA is postfix delivering to ~/Maildir, runs perfectly. Dovecot is configured to use plaintext auth, config file is at the end of this mail. When trying to get mail via IMAP, I'm getting the following errors: /var/log/dovecot.log > Aug 24 12:00:35 Info: Dovecot starting up > Aug 24 12:00:51 Info: Login: goshik [193.233.44.234] /var/log/maillog > Aug 24 12:00:51 banka dovecot: We couldn't drop root group privileges > Aug 24 12:00:51 banka imap(goshik): child 2045 (imap) returned error 89 Am I missing something? What was done incorrectly? Help please, Igor -------------------------------------------- /usr/local/etc/dovecot.conf > ## Dovecot 1.0 configuration file > > #base_dir = /var/run/dovecot/ > > protocols = imap pop3 > imap_listen = 193.233.44.213 > pop3_listen = 193.233.44.213 > ssl_disable = yes > > #disable_plaintext_auth = no > > #log_path = > info_log_path = /var/log/dovecot.log > #login_dir = /var/run/dovecot/login > #login_chroot = yes > > login = imap > login_user = dovecot > > login = pop3 > > #max_mail_processes = 1024 > verbose_proctitle = yes > #verbose_ssl = no > #first_valid_uid = 500 > #last_valid_uid = 0 > first_valid_gid = 0 > #last_valid_gid = 0 > > valid_chroot_dirs = /var/mail > #mail_chroot = > > default_mail_env = maildir:%h/Maildir > > #mail_cache_fields = MessagePart > #mail_never_cache_fields = > > client_workarounds = oe6-fetch-no-newmail outlook-idle outlook-pop3-no-nuls > > #mail_full_filesystem_access = no > #mail_max_flag_length = 50 > #mail_save_crlf = no > #mail_read_mmaped = no > > #maildir_stat_dirs = no > maildir_copy_with_hardlinks = yes > #maildir_check_content_changes = no > > #umask = 0077 > > mail_drop_priv_before_exec = no > > #imap_executable = /usr/local/libexec/dovecot/imap > #imap_process_size = 256 > #imap_use_modules = no > #imap_modules = /usr/local/lib/dovecot/imap > > #pop3_executable = /usr/local/libexec/dovecot/pop3 > #pop3_process_size = 256 > #pop3_use_modules = no > #pop3_modules = /usr/local/lib/dovecot/pop3 > > auth = default > auth_mechanisms = plain > #auth_realms = > #auth_default_realm = > auth_userdb = passwd > auth_passdb = passwd > #auth_executable = /usr/local/libexec/dovecot/dovecot-auth > #auth_process_size = 256 > auth_user = root > #auth_chroot = > #auth_count = 1 > #auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ > #auth_anonymous_username = anonymous > auth_verbose = yes > > #auth = digest_md5 > #auth_methods = digest-md5 > #auth_realms = > #auth_userdb = passwd-file /etc/passwd.imap > #auth_passdb = passwd-file /etc/passwd.imap > #auth_user = imapauth > #auth_chroot =

2 4

[Dovecot] UIDPLUS Status?
by Chris Alexander 25 Aug '04

25 Aug '04

I saw in the archives that UIDPLUS had been removed from dovecot back in June. Are there any plans to re-implement? I have a Windows/Eudora user that wants UIDPLUS so the client side spam filtering works. Thanks. -- Chris Alexander UNIX Network Administrator, Information Networks and Systems Division Communications Research Centre [ http://www.crc.ca ] Government of Canada [ http://www.gc.ca ]

2 1

[Dovecot] Problem with emails larger than 10k
by Peter Hessler 25 Aug '04

25 Aug '04

I cannot download emails that are larger than 10k. I can download them fine with test32. I am running test35 on OpenBSD/macppc -current. I am downloading the files with Sylpheed-Claws 0.9.9claws on OpenBSD/macppc -current (different machines), over pop3-ssl on IPv6. Problem still occurs with IPv4. On the large files, the download hangs at 4.0k. Multiple small emails work fine. -- A day for firm decisions!!!!! Or is it?

2 1

[Dovecot] [PATCH] move highest_fd calculations to ioloop-select.c
by Andrey Panin 25 Aug '04

25 Aug '04

Hello, ioloop->highest_fd is used by ioloop-select.c only, so its handling can be moved out of generic ioloop code. Attached patch (agains -test35) does exactly this. Please consider applying. Best regards. -- Andrey Panin | Linux and UNIX system administrator pazke(a)donpac.ru | PGP key: wwwkeys.pgp.net

1 0

[Dovecot] Re: ssl_ca_file
by jan＠weitan.org 24 Aug '04

24 Aug '04

> I am using 0.99.10.7-1 on Debian, and I'm having some trouble with SSL. I > purchased a certificate from Thawte and I can't figure out how to tell > dovecot about the CA cert. Adding ssl_ca_file to my configuration produces > "Unknown setting: ssl_ca_file" on dovecot startup. > > Postfix has a smtpd_tls_CAfile argument and that part is working fine. > > Is this a Debian-specific problem or is ssl_ca_file newer than 0.99.10.7? I guess ssl_ca_file is newer than 0.99. I have the same settings (debian -sarge) and i am using ssl_cert_file and ssl_key_file to get the certificate working. I checked ssl_ca_file and i got the same error, nevertheless it's in the recent dovecot.conf file from 1.x.testing, therefore it should be newer than 0.99.

1 0

[Dovecot] Unknown setting: ssl_ca_file
by Jacob Elder 24 Aug '04

24 Aug '04

I am using 0.99.10.7-1 on Debian, and I'm having some trouble with SSL. I purchased a certificate from Thawte and I can't figure out how to tell dovecot about the CA cert. Adding ssl_ca_file to my configuration produces "Unknown setting: ssl_ca_file" on dovecot startup. Postfix has a smtpd_tls_CAfile argument and that part is working fine. Is this a Debian-specific problem or is ssl_ca_file newer than 0.99.10.7? -- Jacob Elder

1 0

[Dovecot] Underquoted macros in aclocal (was: MIME structure intermittently lost)
by Kenneth Porter 24 Aug '04

24 Aug '04

--On Monday, August 23, 2004 6:50 PM +0900 Jim Tittsler <jt(a)OnJapan.net> wrote: > You can get dovecot-0.99.10.9-1.FC3.2.src.rpm from the > Fedora Core development tree. (Seems to be working well for us.) I just built this and it has a lot of complaints about underquoted macros in aclocal. Red Hat refers developers to this reference: <http://sources.redhat.com/automake/automake.html#Extending%20aclocal>

1 0

[Dovecot] 1.0-test35
by Timo Sirainen 23 Aug '04

23 Aug '04

http://dovecot.org/test/ Test33/34 weren't usable for very long. Test35 fixes several problems in them.

1 0

[Dovecot] Newbie: dovecot not running.
by Simon Waters 23 Aug '04

23 Aug '04

Okay, sure it must be trivial.... I have old Redhat box, want a quick and dirty IMAP server, thought good time to try out dovecot (I'd rather it had Debian on too ;). Downloaded and compiled from source - no options to configure. Auth data is in /etc/passwd and /etc/shadow (as well as NIS). vi /usr/local/etc/dovecot.conf as expected. Disable ssl in conf. Basically email is in mbox format in /var/spool/mail/%u Should go somewhere ~%u/mail is fine, as would be ~%u/Mail (I don't care at the moment). created a user "dovecot..." to run as and edited conf file. If I run /usr/local/sbin/dovecot it terminates without errors, the fork is completing I think, and the main program returns as expect. Running imap-auth from xinetd gets me a greeting banner, but then the connection is closed. Trying to run "imap" directly just dies in a blizarrd of "dot locking" errors and the like, where it seems to ignore the locking directives (should I set an env or some such?), but I think that it is basically running (it creates indexes in ~/mail/...mumble) but complains about the dotlocking, and then spews an internal error (which it claims is logged to server log?). I'm off to try auth_verbose, but any tips or hints appreciated. I'm assuming /usr/local/sbin/dovecot is what was called "master" given it is in the master src directory. Simon

1 1

[Dovecot] 1.0-test33
by Timo Sirainen 23 Aug '04

23 Aug '04

http://dovecot.org/test/ I think I found and fixed the last bug that was giving me problems. Now that Dovecot has been successfully working for a few hours, time for a new test release :) This release has major changes, so there might still be some bugs left. Be careful. If you're upgrading from previous 1.0-test release, you must delete all existing dovecot.index.log files or you will get errors. So, the changes are: - All network sockets are nonblocking now and all the waiting is done in a single event loop. This required tons of changes all over the code. - Transaction log file doesn't use locks for reading anymore - Some mbox fixes - search text was broken

2 2

[Dovecot] MIME structure intermittently lost
by Kenneth Porter 23 Aug '04

23 Aug '04

I'm using Dovecot-0.99.10.5-0.FC2 on Fedora Core 2 on the server, and Mulberry 3.1.6 over Win2kSP4 on the client. Intermittently messages with multiple parts show up as a single text part. I'm not sure if it's Mulberry or Dovecot. I just turned on IMAP logging and restarted Mulberry and a message with two text/plain parts that wasn't showing the 2nd part is now displaying it correctly. I hate heisenbugs!

3 3

RE: [Dovecot] Unusual behaviour
by Mark Lidstone 23 Aug '04

23 Aug '04

Ahh! Now you've explained it, it makes a lot of sense. Many thanks, Mark Lidstone IT and Network Support Administrator BMT SeaTech Ltd Grove House, Meridians Cross, 7 Ocean Way Ocean Village, Southampton. SO14 3TJ. UK Tel: +44 (0)23 8063 5122 Fax: +44 (0)23 8063 5144 E-Mail: mailto:mark.lidstone@bmtseatech.co.uk Website: www.bmtseatech.co.uk ======================================================================== == Confidentiality Notice and Disclaimer: The contents of this e-mail and any attachments are intended only for the use of the e-mail addressee(s) shown. If you are not that person, or one of those persons, you are not allowed to take any action based upon it or to copy it, forward, distribute or disclose the contents of it and you should please delete it from your system. BMT SeaTech Limited does not accept liability for any errors or omissions in the context of this e-mail or its attachments which arise as a result of Internet transmission, nor accept liability for statements which are those of the author and not clearly made on behalf of BMT SeaTech Limited. ======================================================================== == -----Original Message----- From: Timo Sirainen [mailto:tss@iki.fi] Sent: 23 August 2004 09:07 To: Mark Lidstone Cc: dovecot(a)dovecot.org Subject: RE: [Dovecot] Unusual behaviour On Mon, 2004-08-23 at 08:48 +0100, Mark Lidstone wrote: > Is it supposed to give the current time and date in the error message. > I've no problem with it giving an "internal error" message to the > client, but I am a little confused about the time being in there. > That's all I'm asking about. Client should never see any "real" error messages to make sure no extra information about the system gets leaked. So any time something unexpected happens, Dovecot gives the "internal error" message to user while writing the real error to log file. The timestamp is there to help sysadmin find the real error message from log files when user gives a copy&pasted internal error message. Instead of timestamp I guess there could be also some unique identifier which could be grepped from logs but I think timestamp is better. And about the original problem of giving "internal error" when Dovecot process didn't have access to some maildir.. Maybe it could have replied "Permission denied" to client in that case. It already does in several cases, but I guess the problem here was that it was trying to create the missing dirs but couldn't. I'll look over all these permission issues properly when creating real shared folder support.

1 0

RE: [Dovecot] Unusual behaviour
by Mark Lidstone 23 Aug '04

23 Aug '04

OK, last try. Is it supposed to give the current time and date in the error message. I've no problem with it giving an "internal error" message to the client, but I am a little confused about the time being in there. That's all I'm asking about. Mark Lidstone IT and Network Support Administrator BMT SeaTech Ltd Grove House, Meridians Cross, 7 Ocean Way Ocean Village, Southampton. SO14 3TJ. UK Tel: +44 (0)23 8063 5122 Fax: +44 (0)23 8063 5144 E-Mail: mailto:mark.lidstone@bmtseatech.co.uk Website: www.bmtseatech.co.uk ======================================================================== == Confidentiality Notice and Disclaimer: The contents of this e-mail and any attachments are intended only for the use of the e-mail addressee(s) shown. If you are not that person, or one of those persons, you are not allowed to take any action based upon it or to copy it, forward, distribute or disclose the contents of it and you should please delete it from your system. BMT SeaTech Limited does not accept liability for any errors or omissions in the context of this e-mail or its attachments which arise as a result of Internet transmission, nor accept liability for statements which are those of the author and not clearly made on behalf of BMT SeaTech Limited. ======================================================================== == -----Original Message----- From: Andrew Boothman [mailto:andrew@mux.org.uk] Sent: 20 August 2004 18:09 To: Dovecot list Subject: Re: [Dovecot] Unusual behaviour Mark Lidstone wrote: > I thought that Dovecot was supposed to handle that kind of thing? > Reading from the website: > > "Any kind of crash is considered as bug and will be fixed - even if > it happens only by deliberately poking the index files." > > I've done it in the past by just creating the bare folders - they > appear in the IMAP folder list then when they're used Dovecot seems to > create the sub folders anyway. > > The issue I'm asking about here is, should the error message say > "Internal Error [date time]" rather than something useful? Did Dovecot actually crash? Did it log a more sensible error message to syslog? I think Dovecot quite often reports an "internal error" to the client but then writes a more sensible error message to syslog. Which is probably no bad thing as you may well not want clients to see detailed error messages - there's nothing they can do about it anyway. Andrew

2 1

[Dovecot] Multiple dovecot processes stepping on each other
by Peter Hessler 23 Aug '04

23 Aug '04

I have two instances of dovecot running, one for v6 and one for v4 connections. The only differences in the config files are: --- /etc/dovecot-ip6.conf Wed Aug 18 11:15:43 2004 +++ /etc/dovecot-ip4.conf Wed Aug 18 11:09:17 2004 @@ -10,7 +10,7 @@ # *** NOTE *** Some values HAVE been changed for OpenBSD use. # Base directory where to store runtime data. -base_dir = /var/dovecot-v6/ +base_dir = /var/dovecot-v4/ # Protocols we want to be serving: # imap imaps pop3 pop3s @@ -23,7 +23,7 @@ # "host:port", although with multiple protocols you probably want to move # this setting inside protocol imap/pop3 { ... } section, so you can # specify different ports for IMAP/POP3. -listen = [::] +listen = * # IP or host address where to listen in for SSL connections. Defaults # to above if not specified. For the most part it is working, but every so often, the auth freaks out for one (random) account. The error for one example is below: Aug 18 11:13:12 gir dovecot: login: Authentication process 21082 doesn't exist Aug 18 11:13:12 gir dovecot: pop3-login: Internal login failure: phessler [208.201.244.164] This happens on both v4 and v6 connections, but infrequently. If you try again immediatly, it works. If I do a `ps -p 21082` I can see the process (dovecot-auth). This does not happen when I have only one dovecot process running. What is the best way to have multiple dovecot processes without them stepping on each others toes? This is on OpenBSD/macppc -current, running dovecot-1.0-test32. -- Mosher's Law of Software Engineering: Don't worry if it doesn't work right. If everything did, you'd be out of a job.

2 4

[Dovecot] Dovecot stop accepting command When reading disk quota (soft)
by Chan Min Wai 23 Aug '04

23 Aug '04

Hello all, I've face some problem here and I think it should be the way. 1) I'm running Dovecot version 0.99.10.4 (fc1 release) on RH9 2) One of the users have reach the soft disk quota limits 3) Dovecot stop the users from deleting email. What I think was, dovecot should let the user continue to use the services until it reach the hard limits, but pop up message each and every time ;). Anyone have that problem before? Thank You Chan Min Wai

3 3

[Dovecot] Sent, Drafts, Trash folders
by Jason M. Wilde 23 Aug '04

23 Aug '04

I am hosting imap mail for a new affiliate and am offering webmail via squirrelmail as well. Squirrelmail created INBOX.Sent, INBOX.Trash, etc by default and I would like to use these folders for my Dovecot imap users. I am using the mbox format, Postfix and users retrieve mail via the Outlook client remotely in addition to webmail access. Thank you for any help. Jason

2 1

[Dovecot] What about saving your INBOX at ~/mbox ?
by Nico Kadel-Garcia 23 Aug '04

23 Aug '04

Hi, folks. I'm testing out RedHat's "Fedora Core 2" release, which has switched from the old WashU imapd to dovecot-0.99.10. Overall, this looks like a really, really good move on their part: it looks like a very sweet little tool without some of the ingrained idiocy of Mark Crispin insisting that every home directory consist of nothing but mbox files and allowing you to use a configurable subdirectory by default, ~/mail. Cool. There is one feature of the old WashU imapd that I miss, though. That daemonn could be configured to automatically transfer the user's email to the "~/mbox" upon activation of the daemon, effectively reducing the size of the /var/spool/mail/{username}" mail spool and helping keep the user's disk usage in their home directories, not in /var/spool/mail. This can be a good thing for various reasons. But I don't see any way to enable that behavior for dovecot. Is there something I'm missing, or do folks feel it would be reasonable to add? -- Nico Kadel-Garcia Systems Engineer Mitsubish Electric Research Lab <nkadel(a)merl.com>

4 6

[Dovecot] Is 1.0-test stabilising?
by Curtis Maloney 23 Aug '04

23 Aug '04

Has Timo backed off work, and been busy with something else, or has 1.0 really stabilised that much? Seems to me just a couple of weeks ago we were seeing a new test release every few days... now there's been nothing all month... I'm hoping it's ready for release... but if it's just that Timo's busy, well, I can understand that. We're about to receive some new servers, and I hope to migrate from 0.99 to 1.0 as we migrate to the new machines. -- Curtis Maloney

3 3

RE: [Dovecot] Unusual behaviour
by Mark Lidstone 20 Aug '04

20 Aug '04

I thought that Dovecot was supposed to handle that kind of thing? Reading from the website: "Any kind of crash is considered as bug and will be fixed - even if it happens only by deliberately poking the index files." I've done it in the past by just creating the bare folders - they appear in the IMAP folder list then when they're used Dovecot seems to create the sub folders anyway. The issue I'm asking about here is, should the error message say "Internal Error [date time]" rather than something useful? Mark Lidstone IT and Network Support Administrator BMT SeaTech Ltd Grove House, Meridians Cross, 7 Ocean Way Ocean Village, Southampton. SO14 3TJ. UK Tel: +44 (0)23 8063 5122 Fax: +44 (0)23 8063 5144 E-Mail: mailto:mark.lidstone@bmtseatech.co.uk Website: www.bmtseatech.co.uk ======================================================================== == Confidentiality Notice and Disclaimer: The contents of this e-mail and any attachments are intended only for the use of the e-mail addressee(s) shown. If you are not that person, or one of those persons, you are not allowed to take any action based upon it or to copy it, forward, distribute or disclose the contents of it and you should please delete it from your system. BMT SeaTech Limited does not accept liability for any errors or omissions in the context of this e-mail or its attachments which arise as a result of Internet transmission, nor accept liability for statements which are those of the author and not clearly made on behalf of BMT SeaTech Limited. ======================================================================== == -----Original Message----- From: Keith Edmunds [mailto:keith@midnighthax.com] Sent: 20 August 2004 12:42 To: dovecot(a)dovecot.org Subject: Re: [Dovecot] Unusual behaviour On Fri, 20 Aug 2004 11:26:44 +0100 "Mark Lidstone" <mlidstone(a)bmtseatech.co.uk> wrote: > I've just noticed something strange in dovecot 0.99.10.5. I created > some IMAP folders from the command line (mkdir .INBOX.Folder1) No: you created a directory. IMAP folders need cur/ tmp/ and new/ as subdirectories under the new folder directory. Keith -- ---------------------------------------------------------------------- Small business computer support: http://www.tiger-computing.co.uk Linux consultancy: http://www.TheLinuxConsultancy.co.uk ----------------------------------------------------------------------

2 1

[Dovecot] Unusual behaviour
by Mark Lidstone 20 Aug '04

20 Aug '04

Hi, I've just noticed something strange in dovecot 0.99.10.5. I created some IMAP folders from the command line (mkdir .INBOX.Folder1) as a different user to the owner of the mailbox. Obviously when I tried to view them via IMAP I got an error message, but the message to the client was "internal error[date time]" where date and time appeared to be the current date and time. Is this correct behaviour? Dovecot was running on FC2, and the client was Mozilla Thunderbird under Windows. Mark Lidstone IT and Network Support Administrator BMT SeaTech Ltd Grove House, Meridians Cross, 7 Ocean Way Ocean Village, Southampton. SO14 3TJ. UK Tel: +44 (0)23 8063 5122 Fax: +44 (0)23 8063 5144 E-Mail: mailto:mark.lidstone@bmtseatech.co.uk Website: www.bmtseatech.co.uk ======================================================================== == Confidentiality Notice and Disclaimer: The contents of this e-mail and any attachments are intended only for the use of the e-mail addressee(s) shown. If you are not that person, or one of those persons, you are not allowed to take any action based upon it or to copy it, forward, distribute or disclose the contents of it and you should please delete it from your system. BMT SeaTech Limited does not accept liability for any errors or omissions in the context of this e-mail or its attachments which arise as a result of Internet transmission, nor accept liability for statements which are those of the author and not clearly made on behalf of BMT SeaTech Limited. ======================================================================== ==

2 1

[Dovecot] Question: email system architecture
by Gland Vador 18 Aug '04

18 Aug '04

Hi, I have a question about how to implement a mail system, but I don't know where to ask. Until now, I have a mail system who receive mail by postfix and transport it through procmail to the /var/spool/mail/username mailbox. From here it is retrieved through dovecot (POP3). Now I have two more users, I want to implement a IMAP server, and also provide a webmail (squirrelmail) interface. And in order to filter spam, I want to install spamassassin. Until now it was thunderbird who made the filterring, but with a webmail interface it's no more possible. So suppose that I have configured procmail to deliver "good" mail in an Inbox folder and "spam" in a SPAM folder. This for each user mailbox. I also have configured dovecot as IMAP server and any IMAP client can see the two folder with spam and ham. And here comes my implementation problem. If a user see a "good" mail in his spam folder (or vice-versa) he will take this mail and move to his inbox folder. But, I want to be able to say to spamassassin to learn that this message is ham, with the command sa-learn, and also remove the x-spam* headers. And I don't see a good way to do that. In my opinion, it should be the MUA task, but spamassassin is server based. It's any way that dovecot when it moves the mail between tho folders can call an external script who will make this job in fonction of source/destination folder? Maybe it's a silly question (I don't know IMAP and his possibilities). In this case, can anyone explain (or point to) me a way to do that ? Sorry for this long message. Edd.

4 5

[Dovecot] We couldn't drop root group privileges.
by Greg M 16 Aug '04

16 Aug '04

Hello all, This is my first post to this list. I have tried finding this answer online but while it seems that there are some people out there asking, I cant seem to get an answer to it. I have installed Dovecot some many month ago, and just recently I have been getting an error while trying to log into one of my accounts that I used all the time. The error that comes up is pop3: We couldn't drop root group privileges I have seen where someone else has asked this same question, but there was no response to the list. Anyone have any ideas? I use squirrel mail to check the account as well as KMail (IMAP), and have even tried logging in through telnet to port 110 to see if it was a client issue, but it appears to be dovecot. I am using BSD 4.9 and Exim if that helps any. Thanks a bunch, for now I have to ssh into the machine to check my mail via PINE or mail. -Greg M.

2 1

[Dovecot] Imap process killed
by Yann Rouillard 16 Aug '04

16 Aug '04

Hi, I get the following message each time I try to access a mailbox. dovecot: [ID 684838 mail.error] child 27041 (imap) killed with signal 11 Using dovecot 1.0-test32 under Solaris 9. Using truss I get the following lines: 27041: read(0, " 2 s e l e c t " I N".., 4096) = 18 27041: open64("/var/mail/toto", O_RDWR|O_CREAT|O_EXCL, 0660) Err#17 EEXIST 27041: time() = 1092672589 27041: open64("", O_RDWR) Err#14 EFAULT 27041: Incurred fault #6, FLTBOUNDS %pc = 0xFF1B347C 27041: siginfo: SIGSEGV SEGV_MAPERR addr=0x00000000 27041: Received signal #11, SIGSEGV [default] 27041: siginfo: SIGSEGV SEGV_MAPERR addr=0x00000000 I attached the complete result of the truss command and my configuration file. Any idea what is the problem ? Cheers, Yann ## Dovecot 1.0 configuration file # '#' character and everything after it is treated as comments. Extra spaces # and tabs are ignored. If you want to use either of these explicitly, put the # value inside quotes, eg.: key = "# char and trailing whitespace " # Default values are shown after each value, it's not required to uncomment # any of the lines. Exception to this are paths, they're just examples # with real defaults being based on configure options. The paths listed here # are for configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var # --with-ssldir=/etc/ssl # Base directory where to store runtime data. base_dir = /var/run/dovecot/ # Protocols we want to be serving: # imap imaps pop3 pop3s protocols = imap # IP or host address where to listen in for connections. It's not currently # possible to specify multiple addresses. "*" listens in all IPv4 interfaces. # "[::]" listens in all IPv6 interfaces, but may also listen in all IPv4 # interfaces depending on the operating system. You can specify ports with # "host:port", although with multiple protocols you probably want to move this # setting inside protocol imap/pop3 { ... } section, so you can specify # different ports for IMAP/POP3. #listen = * # IP or host address where to listen in for SSL connections. Defaults # to above if not specified. #ssl_listen = # Disable SSL/TLS support. ssl_disable = yes # PEM encoded X.509 SSL/TLS certificate and private key. They're opened before # dropping root privileges, so keep the key file unreadable by anyone but # root. Included doc/mkcert.sh can be used to easily generate self-signed # certificate, just make sure to update the domains in dovecot-openssl.cnf ssl_cert_file = /usr/local/public/ssl/certs/imapd.pem ssl_key_file = /usr/local/public/ssl/certs/imapd.pem # File containing trusted SSL certificate authorities. Usually not needed. #ssl_ca_file = # Request client to send a certificate. #ssl_verify_client_cert = no # SSL parameter file. Master process generates this file for login processes. # It contains Diffie Hellman and RSA parameters. #ssl_parameters_file = /var/run/dovecot/ssl-parameters.dat # How often to regenerate the SSL parameters file. Generation is quite CPU # intensive operation. The value is in hours, 0 disables regeneration # entirely. #ssl_parameters_regenerate = 24 # SSL ciphers to use #ssl_cipher_list = all:!low # Disable LOGIN command and all other plaintext authentications unless # SSL/TLS is used (LOGINDISABLED capability). Note that 127.*.*.* and # IPv6 ::1 addresses are considered secure, this setting has no effect if # you connect from those addresses. disable_plaintext_auth = no # Use this logfile instead of syslog(). /dev/stderr can be used if you want to # use stderr for logging (ONLY /dev/stderr - otherwise it is closed). #log_path = # For informational messages, use this logfile instead of the default #info_log_path = # Prefix for each line written to log file. % codes are in strftime(3) # format. #log_timestamp = "%b %d %H:%M:%S " ## ## Login processes ## # Directory where authentication process places authentication UNIX sockets # which login needs to be able to connect to. The sockets are created when # running as root, so you don't have to worry about permissions. Note that # everything in this directory is deleted when Dovecot is started. #login_dir = /var/run/dovecot/login # chroot login process to the login_dir. Only reason not to do this is if you # wish to run the whole Dovecot without roots. login_chroot = no # User to use for the login process. Create a completely new user for this, # and don't use it anywhere else. The user must also belong to a group where # only it has access, it's used to control access for authentication process. #login_user = dovecot # Set max. process size in megabytes. If you don't use # login_process_per_connection you might need to grow this. #login_process_size = 32 # Should each login be processed in it's own process (yes), or should one # login process be allowed to process multiple connections (no)? Yes is more # secure, espcially with SSL/TLS enabled. No is faster since there's no need # to create processes all the time. #login_process_per_connection = yes # Number of login processes to create. If login_process_per_user is # yes, this is the number of extra processes waiting for users to log in. #login_processes_count = 3 # Maximum number of extra login processes to create. The extra process count # usually stays at login_processes_count, but when multiple users start logging # in at the same time more extra processes are created. To prevent fork-bombing # we check only once in a second if new processes should be created - if all # of them are used at the time, we double their amount until limit set by this # setting is reached. This setting is used only if login_process_per_use is yes. #login_max_processes_count = 128 # Maximum number of connections allowed in login state. When this limit is # reached, the oldest connections are dropped. If login_process_per_user # is no, this is a per-process value, so the absolute maximum number of users # logging in actually login_processes_count * max_logging_users. #login_max_logging_users = 256 ## ## Mail processes ## # Maximum number of running mail processes. When this limit is reached, # new users aren't allowed to log in. #max_mail_processes = 1024 # Show more verbose process titles (in ps). Currently shows user name and # IP address. Useful for seeing who are actually using the IMAP processes # (eg. shared mailboxes or if same uid is used for multiple accounts). #verbose_proctitle = no # Show protocol level SSL errors. #verbose_ssl = no # Valid UID range for users, defaults to 500 and above. This is mostly # to make sure that users can't log in as daemons or other system users. # Note that denying root logins is hardcoded to dovecot binary and can't # be done even if first_valid_uid is set to 0. first_valid_uid = 200 last_valid_uid = 0 # Valid GID range for users, defaults to non-root/wheel. Users having # non-valid GID as primary group ID aren't allowed to log in. If user # belongs to supplementary groups with non-valid GIDs, those groups are # not set. #first_valid_gid = 1 #last_valid_gid = 0 # Grant access to these extra groups for mail processes. Typical use would be # to give "mail" group write access to /var/mail to be able to create dotlocks. #mail_extra_groups = # ':' separated list of directories under which chrooting is allowed for mail # processes (ie. /var/mail will allow chrooting to /var/mail/foo/bar too). # This setting doesn't affect login_chroot or auth_chroot variables. # WARNING: Never add directories here which local users can modify, that # may lead to root exploit. Usually this should be done only if you don't # allow shell access for users. See doc/configuration.txt for more information. #valid_chroot_dirs = # Default chroot directory for mail processes. This can be overridden by # giving /./ in user's home directory (eg. /home/./user chroots into /home). #mail_chroot = # Default MAIL environment to use when it's not set. By leaving this empty # dovecot tries to do some automatic detection as described in # doc/mail-storages.txt. There's a few special variables you can use, eg.: # # %u - username # %n - user part in user@domain, same as %u if there's no domain # %d - domain part in user@domain, empty if user there's no domain # %h - home directory # # See doc/variables.txt for full list. Some examples: # # default_mail_env = maildir:/var/mail/%1u/%u/Maildir # default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u # default_mail_env = mbox:/var/mail/%d/%n/:INDEX=/var/indexes/%d/%n # default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u:INDEX=MEMORY # Space-separated list of fields to cache for all mails. Currently these # fields are allowed followed by a list of commands they speed up: # # Envelope - FETCH ENVELOPE and SEARCH FROM, TO, CC, BCC, SUBJECT, # SENTBEFORE, SENTON, SENTSINCE, HEADER MESSAGE-ID, # HEADER IN-REPLY-TO # Body - FETCH BODY # Bodystructure - FETCH BODY, BODYSTRUCTURE # MessagePart - FETCH BODY[1.2.3] (ie. body parts), RFC822.SIZE, # SEARCH SMALLER, LARGER, also speeds up BODY/BODYSTRUCTURE # generation. This is always set with mbox mailboxes, and # also default with Maildir. # # Different IMAP clients work in different ways, that's why Dovecot by default # only caches MessagePart which speeds up most operations. Whenever client # does something where caching could be used, the field is automatically marked # to be cached later. For example after FETCH BODY the BODY will be cached # for all new messages. Normally you should leave this alone, unless you know # what most of your IMAP clients are. Caching more fields than needed makes # the index files larger and generate useless I/O. # # With maildir there's one extra optimization - if nothing is cached, indexing # the maildir becomes much faster since it's not opening any of the mail files. # This could be useful if your IMAP clients access only new mails. #mail_cache_fields = MessagePart # Space-separated list of fields that Dovecot should never set to be cached. # Useful if you want to save disk space at the cost of more I/O when the fields # needed. #mail_never_cache_fields = # Dovecot can notify client of new mail in selected mailbox soon after it's # received. This setting specifies the minimum interval in seconds between # new mail notifications to client - internally they may be checked more or # less often. Setting this to 0 disables the checking. # NOTE: Evolution client breaks with this option when it's trying to APPEND. #mailbox_check_interval = 0 # Like mailbox_check_interval, but used for IDLE command. #mailbox_idle_check_interval = 30 # Allow full filesystem access to clients. There's no access checks other than # what the operating system does for the active UID/GID. It works with both # maildir and mboxes, allowing you to prefix mailboxes names with eg. /path/ # or ~user/. #mail_full_filesystem_access = no # Maximum allowed length for mail keyword name. It's only forced when trying # to create new keywords. #mail_max_keyword_length = 50 # Save mails with CR+LF instead of plain LF. This makes sending those mails # take less CPU, especially with sendfile() syscall with Linux and FreeBSD. # But it also creates a bit more disk I/O which may just make it slower. #mail_save_crlf = no # Use mmap() instead of read() to read mail files. read() seems to be a bit # faster with my Linux/x86 and it's better with NFS, so that's the default. # Note that OpenBSD 3.3 and older don't work right with mail_read_mmaped = yes. #mail_read_mmaped = no # Don't use mmap() at all. This is required if you store indexes in remote # filesystems (NFS or clustered filesystem). #mmap_disable = no # Don't write() to mmaped files. This is required for some operating systems # which use separate caches for them, such as OpenBSD. #mmap_no_write = no # Don't use fcntl() locking. Alternatives are dotlocking and other tricks # which may be slower. Required for NFS. fcntl_locks_disable = yes # By default LIST command returns all entries in maildir beginning with dot. # Enabling this option makes Dovecot return only entries which are directories. # This is done by stat()ing each entry, so it causes more disk I/O. # (For systems setting struct dirent->d_type, this check is free and it's # done always regardless of this setting) #maildir_stat_dirs = no # Copy mail to another folders using hard links. This is much faster than # actually copying the file. This is problematic only if something modifies # the mail in one folder but doesn't want it modified in the others. I don't # know any MUA which would modify mail files directly. IMAP protocol also # requires that the mails don't change, so it would be problematic in any case. # If you care about performance, enable it. #maildir_copy_with_hardlinks = no # Check if mails' content has been changed by external programs. This slows # down things as extra stat() needs to be called for each file. If changes are # noticed, the message is treated as a new message, since IMAP protocol # specifies that existing messages are immutable. #maildir_check_content_changes = no # Which locking methods to use for locking mbox. There's four available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory. # fcntl : Use this if possible. Works with NFS too if lockd is used. # flock : May not exist in all systems. Doesn't work with NFS. # lockf : May not exist in all systems. Doesn't work with NFS. # # You can use multiple locking methods; if you do the order they're declared # in is important to avoid deadlocks if other MTAs/MUAs are using multiple # locking methods as well. Some operating systems don't allow using some of # them simultaneously. #mbox_read_locks = fcntl #mbox_write_locks = dotlock fcntl # Maximum time in seconds to wait for lock (all of them) before aborting. #mbox_lock_timeout = 300 # If dotlock exists but the mailbox isn't modified in any way, override the # lock file after this many seconds. #mbox_dotlock_change_timeout = 30 # umask to use for mail files and directories #umask = 0077 # Drop all privileges before exec()ing the mail process. This is mostly # meant for debugging, otherwise you don't get core dumps. It could be a small # security risk if you use single UID for multiple users, as the users could # ptrace() each others processes then. #mail_drop_priv_before_exec = no # Set max. process size in megabytes. Most of the memory goes to mmap()ing # files, so it shouldn't harm much even if this limit is set pretty high. #mail_process_size = 256 # Log prefix for mail processes. See doc/variables.txt for list of possible # variables you can use. #mail_log_prefix = "%Up(%u): " ## ## IMAP specific settings ## protocol imap { # Login executable location. #login_executable = /usr/libexec/dovecot/imap-login # IMAP executable location #mail_executable = /usr/libexec/dovecot/imap # This would write rawlogs into ~/dovecot.rawlog/ directory: #mail_executable = /usr/libexec/dovecot/rawlog /usr/libexec/dovecot/imap # Maximum IMAP command line length in bytes. Some clients generate very long # command lines with huge mailboxes, so you may need to raise this if you get # "Too long argument" or "IMAP command line too large" errors often. #imap_max_line_length = 65536 # Support for dynamically loadable modules. #mail_use_modules = no #mail_modules = /usr/lib/dovecot/imap # Workarounds for various client bugs: # oe6-fetch-no-newmail: # Never send EXISTS/RECENT when replying to FETCH command. Outlook Express # seems to think they are FETCH replies and gives user "Message no longer # in server" error. Note that OE6 still breaks even with this workaround # if synchronization is set to "Headers Only". # outlook-idle: # Outlook and Outlook Express never abort IDLE command, so if no mail # arrives in half a hour, Dovecot closes the connection. This is still # fine, except Outlook doesn't connect back so you don't see if new mail # arrives. #imap_client_workarounds = } ## ## POP3 specific settings ## protocol pop3 { # Login executable location. #login_executable = /usr/libexec/dovecot/pop3-login # POP3 executable location #mail_executable = /usr/libexec/dovecot/pop3 # Don't try to set mails non-recent with POP3 sessions. This is mostly # intended to reduce disk I/O. With maildir it doesn't move files from # new/ to cur/, with mbox it doesn't write Status-header. #pop3_mails_keep_recent = no # Support for dynamically loadable modules. #mail_use_modules = no #mail_modules = /usr/lib/dovecot/pop3 # Workarounds for various client bugs: # outlook-no-nuls: # Outlook and Outlook Express hang if mails contain NUL characters. # This setting replaces them with 0x80 character. #pop3_client_workarounds = } ## ## Authentication processes ## # You can have multiple authentication processes. With plaintext authentication # the password is checked against each process, the first one which succeeds is # used. This is useful if you want to allow both system users (/etc/passwd) # and virtual users to login without duplicating the system users into virtual # database. # Executable location #auth_executable = /usr/libexec/dovecot/dovecot-auth # Set max. process size in megabytes. #auth_process_size = 256 # Space separated list of realms for SASL authentication mechanisms that need # them. You can leave it empty if you don't want to support multiple realms. # Many clients simply use the first one listed here, so keep the default realm # first. #auth_realms = # Default realm/domain to use if none was specified. This is used for both # SASL realms and appending @domain to username in plaintext logins. #auth_default_realm = # List of allowed characters in username. If the user-given username contains # a character not listed in here, the login automatically fails. This is just # an extra check to make sure user can't exploit any potential quote escaping # vulnerabilities with SQL/LDAP databases. If you want to allow all characters, # set this value to empty. #auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ # Username to use for users logging in with ANONYMOUS SASL mechanism #auth_anonymous_username = anonymous # More verbose logging. Useful for figuring out why authentication isn't # working. #auth_verbose = no auth default { # Space separated list of wanted authentication mechanisms: # plain digest-md5 cram-md5 apop anonymous mechanisms = plain # Where user database is kept: # passwd: /etc/passwd or similiar, using getpwnam() # passwd-file <path>: passwd-like file with specified location # static uid=<uid> gid=<gid> home=<dir template>: static settings # vpopmail: vpopmail library # ldap <config path>: LDAP, see doc/dovecot-ldap.conf # pgsql <config path>: a PostgreSQL database, see doc/dovecot-pgsql.conf # mysql <config path>: a MySQL database, see doc/dovecot-mysql.conf userdb = passwd # Where password database is kept: # passwd: /etc/passwd or similiar, using getpwnam() # shadow: /etc/shadow or similiar, using getspnam() # pam [<service> | *]: PAM authentication # checkpassword <path>: checkpassword executable authentication # passwd-file <path>: passwd-like file with specified location # vpopmail: vpopmail authentication # ldap <config path>: LDAP, see doc/dovecot-ldap.conf # pgsql <config path>: a PostgreSQL database, see doc/dovecot-pgsql.conf # mysql <config path>: a MySQL database, see doc/dovecot-mysql.conf passdb = pam # User to use for the process. This user needs access to only user and # password databases, nothing else. Only shadow and pam authentication # requires roots, so use something else if possible. Note that passwd # authentication with BSDs internally accesses shadow files, which also # requires roots. user = root # Directory where to chroot the process. Most authentication backends don't # work if this is set, and there's no point chrooting if auth_user is root. #chroot = # Number of authentication processes to create #count = 1 # Require a valid SSL client certificate or the authentication fails. #ssl_require_client_cert = no } # PAM doesn't provide a way to get uid, gid or home directory. If you don't # want to use a separate user database (passwd usually), you can use static # userdb. #auth onlypam { # mechanisms = plain # userdb = static uid=500 gid=500 home=/var/mail/%u # passdb = pam # user = dovecot-auth #} #auth ldap { # mechanisms = plain # userdb = ldap /etc/dovecot-ldap.conf # passdb = ldap /etc/dovecot-ldap.conf # user = dovecot-auth #} #auth virtualfile { # mechanisms = plain digest-md5 # userdb = passwd-file /etc/passwd.imap # passdb = passwd-file /etc/passwd.imap # user = dovecot-auth #} # It's possible to export the authentication interface to other programs, # for example SMTP server which supports talking to Dovecot. Client socket # handles the actual authentication - you give it a username and password # and it returns OK or failure. So it's pretty safe to allow anyone access to # it. Master socket is used to a) query if given client was successfully # authenticated, b) userdb lookups. # listener sockets will be created by Dovecot's master process using the # settings given inside the auth section #auth default_with_listener { # mechanisms = plain # passdb = passwd # userdb = pam # socket listen { # master { # path = /var/run/dovecot/auth-master # #mode = 0600 # # Default user/group is the one who started dovecot-auth (root) # #user = # #group = # } # client { # path = /var/run/dovecot-auth-client # mode = 0660 # } # } #} # connect sockets are assumed to be already running, Dovecot's master # process only tries to connect to them. They don't need any other settings # than path for the master socket, as the configuration is done elsewhere. # Note that the client sockets must exist in login_dir. #auth external { # socket connect { # master { # path = /var/run/dovecot/auth-master # } # } #}

2 1

[Dovecot] no local users - mbox all under /var/spool/mail/
by Daniel 15 Aug '04

15 Aug '04

Hi there, im new to dovecot but I made my way trough configuring it. I almost get it running at least for one IMAP user. The problem is I got no local user thus no home directories, all Mailboxes are in mbox format under: /var/spool/mail: Looks like this: -SNIP- drwx------ 3 web1p2 poponly 19 2004-08-13 00:05 indexes -rw------- 1 nobody nobody 0 2004-03-26 21:51 nobody -rw------- 1 root root 0 2004-03-26 21:51 root -rw------- 1 web1p2 poponly 14 2004-08-13 00:10 .subscriptions -rw------- 1 web1p2 poponly 8571 2004-08-13 00:10 Trash -rw-rw---- 1 web0p1 root 23068262 2004-08-12 21:27 web0p1 -rw-rw---- 1 web0p2 root 17749 2004-08-12 23:55 web0p2 ... -SNAP I´ve set up the mail-environment this way: default_mail_env = mbox:/var/spool/mail/:INBOX=/var/spool/mail/%u:INDEX=/var/spool/mail/indexes/%u The problem is, that the directory "indexes" has permisions that only the owner can write to (well, I could change permissions, but?) and that the ".subscription" file and "Trash" folder is directly in this directory. So if I add a second user (e.g. web0p1) I got error messages imho due to the use of the "same" folder....? What would be the proposed setup for this system with mostly non-local users without real home directories and all their mbox in a shared directory? Thanks for your time! Daniel

2 1

[Dovecot] LDAP-auth not working
by Roger Bystrom 15 Aug '04

15 Aug '04

I have set up dovecot to use ldap authentication, but it only results in dovecot crashing without any error message that would indicate why this is the case. I have spent *many* hours trying to fix this problem, but not found any solution as to why it should crash. maillog: Aug 15 10:05:08 era dovecot: Dovecot starting up Aug 15 10:05:09 era dovecot: Auth process died too early - shutting down Aug 15 10:05:09 era dovecot: child 20833 (auth) killed with signal 11 Aug 15 10:05:09 era imap-login: fd_send(-1) failed: Broken pipe Settings to indicate ldap in dovecot.conf: auth_userdb = ldap /etc/dovecot-ldap.conf auth_passdb = ldap /etc/dovecot-ldap.conf Basically, the settings in dovecot-ldap.conf is: hosts = localhost:389 dn = cn=dovecot,ou=servers,dc=remiss,dc=org dnpass = nada base = dc=remiss,dc=org deref = never scope = subtree user_attrs = uid,homeDirectory,,,uidNumber,gidNumber user_filter = (&(objectClass=posixAccount)(uid=%u)) pass_attrs = uid,userPassword using ldapsearch -x -D "cn=dovecot,ou=servers,dc=remiss,dc=org" -w nada .... is successful. Therefor I am wondering what in the world that causes "Auth process" to die too early. Output of strace -f dovecot -F is available from http://remiss.org/download/log Pid of auth-process here is 23286. Any help is appreciated. Thanks, Roger.

2 2

[Dovecot] Dovecot Local Delivery Agent
by news.gmane.org 12 Aug '04

12 Aug '04

Hi I noticed in a post that Timo might start work on a LDA Great! If so, here is something I would really like included. Support for PAM There is quite a lengthy reason behind this. In my organisation, user accounts are created on ldap. It is up to the services to create home directories whenever the user first uses them. For instance, Samba will do this the first time they connect to their windows home share. This achieved in other places using pam, using the pam_mkhomedir module. The MTA we run, Exim, is incapable of creating the home directory automatically, or using PAM for local delivery, thus we have the problem that when an account is created in the LDAP directory, it cannot receive email until the user first logs in through IMAP - Dovecot calls pam, which creates the home directory :-) Also attributing to this is the fact that exim is configured to deliver email into $home using maildir format rather than a mbox mail spool. We needed to do this because of the huge size of some of the inboxes of our users. This caused a severe amount of i/o blocking. So far, I have been unable to find a LDA capable of doing this. Since we migrated to dovecot, performance has improved ten-fold. I will give it a week then show you the graphs to prove it! Keep up the great work! Regards -- Chris Hills IT Services North East Worcestershire College

6 10

Re: [Dovecot] Newbie about Mbox or Maildir
by alan premselaar 11 Aug '04

11 Aug '04

Zoong Pham wrote: > > >>-----Original Message----- >>From: dovecot-bounces(a)dovecot.org >>[mailto:dovecot-bounces@dovecot.org]On >>Behalf Of nino(a)swiftdsl.com.au >>Sent: Tuesday, 10 August 2004 3:07 PM >>To: dovecot(a)dovecot.org >>Subject: [Dovecot] Newbie about Mbox or Maildir > > >>Thanks in advance. I am not sure if my system is setup to use >>'mbox' or >>'maildir'. How do I find this out? > > >>I am running an OpenBSD (v3.5) box with an Intel P3 >>motherboard. I have >>installed the OpenBSD port of Dovecot (0.99.10) and have >>manually started >>dovecot and configured the ssl certificates as per the >>documentation. As >>far as I can tell there is no problems but I am confused >>about 'mbox' and >>'maildir' > > > It's mbox. > The default MTA of OpenBSD is Sendmail. > More specifically, this is related to your local delivery agent (LDA). Although I'm not extremely familiar with default OpenBSD installations, it's been typical for default RedHat installations (up to and including RH 9) to have sendmail installed and configured to use procmail for its LDA. while recent versions of procmail can support maildir format, it defaults to using mbox format. alan

2 2

[Dovecot] mkdir imap with user@domain.com
by wiki kaha 10 Aug '04

10 Aug '04

I have a bit a problem. In a virtual domain enviroment i use for login "user(a)domain.com" and the password. in the mysql authentication it works beautiful with %d and %u placeholder. Now when is whould like ad a folder via imap i get an error imap(user(a)domain.com): mkdir(/var/mail/domain.com/user@domain.com/.test) failed: No such file or directory It should be mkdir(/var/mail/domain.com/user/.test) Is there a way to configure this? Thanks Regards Karl-Heinz __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! http://promotions.yahoo.com/new_mail

2 2

[Dovecot] [PATCH] RPA authentication mechanism
by Andrey Panin 10 Aug '04

10 Aug '04

Hello all, attached patch implements Compuserve RPA athentication mechanism. Tested with: - Eudora 6 (uses Compuserve "Virtual Key" RPA software); - TheBat! 2.11 (uses it's own RPA implementation). I hope it can be useful for someone. Best regards. -- Andrey Panin | Linux and UNIX system administrator pazke(a)donpac.ru | PGP key: wwwkeys.pgp.net

2 2

FW: [Dovecot] dovecot-auth: Aug 04 10:48:29 Fatal: Unknown userdb type'mysql'
by Alex Low (e-wise) 10 Aug '04

10 Aug '04

After better looking in the config.log, We found this, mysql wasn't compiled because of this; /usr/lib/mysql/libmysqlclient.a(my_compress.o)(.text+0xd8): In function `my_compress_alloc': : undefined reference to `compress' /usr/lib/mysql/libmysqlclient.a(my_compress.o)(.text+0x171): In function `my_uncompress': : undefined reference to `uncompress' I am using Fedora Core 2, using own compiled mysql 4.x rpm's. Timo Sirainen wrote: It looks like it's needed to be linked with zlib. Hmm. I haven't heard this to be necessary before. It seems to be statically linked in my mysql library. I think it'd work with: LDFLAGS=-lz ./configure --with-mysql And indeed adding -lz to LDFLAGS= in the spec file helped. Anyways I have dovecot rpm for Fedora Core 2 compiled with mysql 4. So if anybody want it, mail away. Greets, Alex _____ From: dovecot-bounces(a)dovecot.org [mailto:dovecot-bounces@dovecot.org] On Behalf Of Alex Low (e-wise) Sent: woensdag 4 augustus 2004 11:15 To: dovecot(a)dovecot.org Subject: [Dovecot] dovecot-auth: Aug 04 10:48:29 Fatal: Unknown userdb type'mysql' Hi, I am trying this way(mailinglist), as I cant find good 'support'/howto/tutorials on the website. I am running Fedora Core II, using postfix with mysql, and I want to use dovecot as imap server. Now I installed Dovecot using dag wieers SRPM, I compiled it with mysql, pgsql; %configure \ --with-ssl="openssl" \ --with-ssldir="%{_datadir}/ssl" \ --with-ldap \ --with-pgsql \ --with-mysql \ --with-cyrus-sasl2 \ --with-rawlog %{__make} %{?_smp_mflags} After compiling it, I installed the rpm. No problem at all. I configure the dovecot.conf like this; #auth = plain digest-md5 #auth_methods = plain digest-md5 auth_userdb = mysql /etc/dovecot-mysql.conf auth_passdb = mysql /etc/dovecot-mysql.conf default_mail_env = maildir:/home/mail/virtual/%d/%n # Use this logfile instead of syslog(). /dev/stderr can be used if you want to # use stderr for logging (ONLY /dev/stderr - otherwise it is closed). log_path = /tmp/dovecot/log1 # For informational messages, use this logfile instead of the default info_log_path = /tmp/dovecot/log2 Then I try run it: [root@octa SPECS]# cat /tmp/dovecot/log1 dovecot-auth: Aug 04 10:48:29 Fatal: Unknown userdb type 'mysql' dovecot: Aug 04 10:48:29 Error: Auth process died too early - shutting down dovecot: Aug 04 10:48:29 Error: child 2118 (auth) returned error 89 imap-login: Aug 04 10:48:29 Fatal: fd_send(-1) failed: Broken pipe dovecot-auth: Aug 04 11:04:39 Fatal: Unknown userdb type 'mysql' dovecot: Aug 04 11:04:39 Error: Auth process died too early - shutting down dovecot: Aug 04 11:04:39 Error: child 11137 (auth) returned error 89 imap-login: Aug 04 11:04:39 Fatal: fd_send(-1) failed: Broken pipe imap-login: Aug 04 11:04:39 Fatal: fd_send(-1) failed: Broken pipe [root@octalys SPECS]# cat /tmp/dovecot/log2 dovecot: Aug 04 10:48:28 Info: Dovecot starting up dovecot: Aug 04 11:04:38 Info: Dovecot starting up [root@octalys SPECS]# Can anyone tell me whats wrong please ? Thank you in advance, Alex

1 0

RE: [Dovecot] Newbie about Mbox or Maildir
by Zoong Pham 10 Aug '04

10 Aug '04

> -----Original Message----- > From: dovecot-bounces(a)dovecot.org > [mailto:dovecot-bounces@dovecot.org]On > Behalf Of nino(a)swiftdsl.com.au > Sent: Tuesday, 10 August 2004 3:07 PM > To: dovecot(a)dovecot.org > Subject: [Dovecot] Newbie about Mbox or Maildir > Thanks in advance. I am not sure if my system is setup to use > 'mbox' or > 'maildir'. How do I find this out? > I am running an OpenBSD (v3.5) box with an Intel P3 > motherboard. I have > installed the OpenBSD port of Dovecot (0.99.10) and have > manually started > dovecot and configured the ssl certificates as per the > documentation. As > far as I can tell there is no problems but I am confused > about 'mbox' and > 'maildir' It's mbox. The default MTA of OpenBSD is Sendmail. I have similar configuration here. Let me know if you need any help. Cheers, Zoong PHAM UNIX systems Administrator ICT - Information, Communications & Technology Mercy Health & Aged Care 678 Victoria Street Richmond 3121 ___________________________________________________________________________________ THIS EMAIL IS CONFIDENTIAL. If you have received this email in error please forward it to information(a)mercy.com.au. It may contain personal information and it is intended for the addressee only. If you receive this email in error you must not use, copy forward, print or otherwise disseminate any information it contains. Mercy Health & Aged Care is a Catholic community benefit organisation. Each year one in twenty Victorian families are touched by the services we provide. Visit www.mercy.com.au for more information. Our services include: * Mercy Hospital for Women - East Melbourne (moving to Heidelberg in 2005) * Werribee Mercy Hospital - Werribee * Mount Alvernia Mercy Hospital - Bendigo * Mercy Hospice - Western suburbs * O'Connell Family Centre - Canterbury * Corporate Office - Richmond * Rice Village - Geelong * Tullamore Mercy - Montrose * Eventide Mercy - Colac * Bethlehem Home for the Aged - Bendigo *

1 0

[Dovecot] Newbie about Mbox or Maildir
by nino＠swiftdsl.com.au 10 Aug '04

10 Aug '04

Hi, Thanks in advance. I am not sure if my system is setup to use 'mbox' or 'maildir'. How do I find this out? I am running an OpenBSD (v3.5) box with an Intel P3 motherboard. I have installed the OpenBSD port of Dovecot (0.99.10) and have manually started dovecot and configured the ssl certificates as per the documentation. As far as I can tell there is no problems but I am confused about 'mbox' and 'maildir' Any assistance is appreciated. Thankyou NS

1 0

[Dovecot] Debian sarge release and dovecot
by Jaldhar H. Vyas 10 Aug '04

10 Aug '04

In what must surely be the first sign of the apocalypse, Debian is actually freezing in preperation for a new release. Probably the last day for uploads will be August 17. Is there likely to be another dovecot release by then? In the event of 0.99.10.9 being the released version, are there any other patches Debian users would like me to include? -- Jaldhar H. Vyas <jaldhar(a)debian.org> La Salle Debain - http://www.braincells.com/debian/

3 4

[Dovecot] Problem moving folders with Thunderbird
by Loek 10 Aug '04

10 Aug '04

I can move around folders to sub-folders in an IMAP account on my dovecot server, but when I try to move a sub-folder back to the top-level (by dragging it to the account name), I get an error: "The current command did not succeed. The mailserver responded: Mailbox exists." It doesn't exist on the server though, and I can create a folder with that name on the top-level. But it is a little annoying. I am using TB 0.7.2. I tried different IMAP server settings in Thunderbird under the account options, but without success. Loek

3 3

[Dovecot] Both mbox and Maildir
by Yann Rouillard 09 Aug '04

09 Aug '04

Hi, I would like to know if it's possible to configure dovecot so that it use mbox file format for the INBOX mailbox but Maildir format for all the subfolders. My problem is I would like an IMAP server which allow to easily create folders and subfolders of folders, but at the same time I don't want to break all MUA which rely on /var/mail/johndoe in mbox format. Thanks in advance. Yann

2 1

Re: [Dovecot] Dovecot Local Delivery Agent
by Apostolos Papayanakis 09 Aug '04

09 Aug '04

Timo, a very simple save-only LDA would be enough for many configurations. Other full featured LDAs such as procmail could also use dovecot-LDA as the final delivering program. This would keep gigantic mboxes always indexed, and make access on them snappy always, especially on the important first access. However this should not take many programming resources away from releasing a robust, migration-ready v1.0. I am eager to migrate 25,000 users (~100GB), onto dovecot and then provide them more disk space, which now I dare not allow them. Keep up the excelent work! apap > Date: Mon, 9 Aug 2004 02:03:53 +0300 > From: Timo Sirainen <tss(a)iki.fi> > Subject: Re: [Dovecot] Dovecot Local Delivery Agent > To: Dovecot mailing list <dovecot(a)dovecot.org> > ... > Anyway, I'm still hoping someone else to do the LDA so I don't have to > worry about it.

1 0

[Dovecot] Little problem with dovecot using mbox format
by Jd 09 Aug '04

09 Aug '04

Hi everyone, this is my first post on this mailing list. I recently installed postfix+dovecot+fetchmail on OpenBSD for my dad's office. (dovecot is setup as an imap server using mbox). Everything worked flawlessly...until now. I don't know why, but now some emails seem to de-double themselves. For exemple, yesterday morning I printed out all the emails. To my surprise 30 minutes later, I received 60 'new'' emails. But these 60 emails weren't new, they were all copies of emails I had printed out earlier. Some emails were repeated some 10-15 times. Now we never got this kind of problem until recently. Has anyone ever experienced this kind of problem? If so how did you fix the situation? Most responses I got from the openBSD mailing list was to use maildir format. Any insight into this? Thanks, Jean-Daniel BTW we don't get THAT much email, maybe 200 a day for that 1 account that seems to be acting weird now.

3 2

Re: [Dovecot] Dovecot Local Delivery Agent
by Mark E. Mallett 09 Aug '04

09 Aug '04

On Mon, Aug 09, 2004 at 02:07:27AM +0300, Timo Sirainen wrote: > On 7.8.2004, at 07:25, Mark E. Mallett wrote: [ I hope you don't mind me answering this back on the list; it seems like it's relevant. ] > > >That's probably just a result of my poor communications skills. I did > >include very brief LICENSE and FUTURE files with the sources, and those > >files probably led you to that conclusion. For clarification, I do > >intend that the program be open source, but I feel that there are some > >things that I should still finish up myself before foisting it off on > >any potential contributers. It's not a matter of "I don't want you to > >have it" -- it's more a matter of "I don't feel right burdening you > >with > >filling in holes just yet" (for the generic "you"). (That makes it > >sound like it's not usable: it's quite usable right now. There are > >just > >features still left to add.) > > > >Plus, as with many other packages and maintainers, I just want to > >control any official version. > > Well, doesn't that mean that it's currently not really open source? As > in I can't modify and re-distribute it (with possibly different name)? My current goal is to make it mature enough and good enough where people might actually want to do that -- as I say, by finishing up some of the things that are still undone. Also there are a couple of things that are hardwired to the environment here (particularly, the way that the IP addresses are extracted for DNSBL tests), that I felt that I should make more general before making it open. The latest sources are available online to anybody who wants them, for use in your own environment, for experimentation and trial, but not for redistribution; but indeed if there was some demand I would probably open it up sooner than later. So far nobody has been beating down the door for it (admittedly I haven't really mentioned it in very many places; I think only here and on the bsdi-users list). But yeah, the plan is to make it so that you can modify it and redistribute it. I don't have any kind of hard and fast position on when, though. I'm sure most anyone could convince me to open it up most any time, if there was good reason to do so. mm

1 0

[Dovecot] search functionality
by Cor Bosman 06 Aug '04

06 Aug '04

Hi all, if I give the following command in test32: A004 UID SEARCH CHARSET ISO-8859-1 ALL TEXT {4} Test The response is: * SEARCH A004 OK Search completed. If I say: A004 UID SEARCH CHARSET ISO-8859-1 ALL FROM {4} Test The response is: * SEARCH 217 350 A004 OK Search completed. The RFC says that 'TEXT' is supposed to result in a list of messages where the search string is in either the body or the header. Obviously the string is there in this example, else the FROM search wouldnt have given a result. Tracing the process shows that dovecot never actually checks the email messages for the string. It does for a BODY search but not for a TEXT search. Is this on purpose? Cor

2 1

[Dovecot] dovecot-auth: Aug 04 10:48:29 Fatal: Unknown userdb type 'mysql'
by Alex Low (e-wise) 06 Aug '04

06 Aug '04

Hi, I am trying this way(mailinglist), as I cant find good 'support'/howto/tutorials on the website. I am running Fedora Core II, using postfix with mysql, and I want to use dovecot as imap server. Now I installed Dovecot using dag wieers SRPM, I compiled it with mysql, pgsql; %configure \ --with-ssl="openssl" \ --with-ssldir="%{_datadir}/ssl" \ --with-ldap \ --with-pgsql \ --with-mysql \ --with-cyrus-sasl2 \ --with-rawlog %{__make} %{?_smp_mflags} After compiling it, I installed the rpm. No problem at all. I configure the dovecot.conf like this; #auth = plain digest-md5 #auth_methods = plain digest-md5 auth_userdb = mysql /etc/dovecot-mysql.conf auth_passdb = mysql /etc/dovecot-mysql.conf default_mail_env = maildir:/home/mail/virtual/%d/%n # Use this logfile instead of syslog(). /dev/stderr can be used if you want to # use stderr for logging (ONLY /dev/stderr - otherwise it is closed). log_path = /tmp/dovecot/log1 # For informational messages, use this logfile instead of the default info_log_path = /tmp/dovecot/log2 Then I try run it: [root@octa SPECS]# cat /tmp/dovecot/log1 dovecot-auth: Aug 04 10:48:29 Fatal: Unknown userdb type 'mysql' dovecot: Aug 04 10:48:29 Error: Auth process died too early - shutting down dovecot: Aug 04 10:48:29 Error: child 2118 (auth) returned error 89 imap-login: Aug 04 10:48:29 Fatal: fd_send(-1) failed: Broken pipe dovecot-auth: Aug 04 11:04:39 Fatal: Unknown userdb type 'mysql' dovecot: Aug 04 11:04:39 Error: Auth process died too early - shutting down dovecot: Aug 04 11:04:39 Error: child 11137 (auth) returned error 89 imap-login: Aug 04 11:04:39 Fatal: fd_send(-1) failed: Broken pipe imap-login: Aug 04 11:04:39 Fatal: fd_send(-1) failed: Broken pipe [root@octalys SPECS]# cat /tmp/dovecot/log2 dovecot: Aug 04 10:48:28 Info: Dovecot starting up dovecot: Aug 04 11:04:38 Info: Dovecot starting up [root@octalys SPECS]# Can anyone tell me whats wrong please ? Thank you in advance, Alex

2 1

[Dovecot] Dovecot Courier
by Michael Baird 06 Aug '04

06 Aug '04

Hello, I've been testing dovecot, and it appears to be much faster then courier-imap. I am using the latest .99 version, trying to make the transition from courier to dovecot as smooth as possible. We really only use IMAP via squirrelmail, I think I've got that worked out fine, changing a few settings in squirrelmail as the FAQ instructs and migrating the courier subscriptions to .subscriptions. I've noticed the folders .Trash .Sent are no longer subfolders of the INBOX,, and when I create new folders in a Client, it creates .INBOX.foldername, and a .INBOX. I would really like all folders to be subfolders of .INBOX, I've set dovecot up as the following. default_mail_env = maildir:/var/export/%h/.maildir:INDEX=/var/indexes/%n I've also tried putting the INBOX:/var/export/%h/.maildir in there as well with no luck. I essentially want .INBOX to be .maildir, and any subfolders would be called .Sent or .Trash or whatever, like in courier, is this possible? Regards MIKE

2 1

[Dovecot] Adding mail to dovecot directories
by Chris Dean 03 Aug '04

03 Aug '04

I run mailagent (which is similar to procmail) to filter all my incoming messages. I would like mailagent to put these messages directly into my dovecot server. What I'm doing right now is to create files (one per message) in the "~/mail/.folder-name/new" directory, or in the case of INBOX, in the "~/.mail/new" directory. I have ~/.mail as my maildir. The files created have MH style names: "1", "2", etc. and the names are often reused throughout the day. That is, the file named "1" might be created dozens of times per day with new contents. Is this the right way? Regards, Chris Dean

2 2

[Dovecot] what is the plan for 1.0?
by Farkas Levente 03 Aug '04

03 Aug '04

hi, i'm just look trhough the todo file, but it's rather large. i assume only a small part of it will be finished for 1.0. what is the schedule for 1.0? what kind of features will be included in 1.0? what is in 1.1 etc.. it'd be useful to see in the todo file that what features scheduled for which version. yours. -- Levente "Si vis pacem para bellum!"

2 1

Re: [Dovecot] SSL CA root certificate
by Mail Admin 03 Aug '04

03 Aug '04

Problem solved. In my case I was using the 0.99.10.x release of dovecot, which does not recognize the ssl_ca_file directive. Upgrading to 1.0-test32 was step one. The next step was finding the right format for DST's root certificate. I think the format that finally worked was the format DST distributes for Apache Raven. Thanks! On Mon, 2004-08-02 at 19:47, Zach Bagnall wrote: > It's probably not a matter of getting dovecot to recognise the > certificate, it'll be getting the MUA to recognise the signer. > > When you get the warning, can you click through to the certificate > details and see what it says? Is it showing the signer as DST? Get DST > to confirm that their CA is recognised and trusted by Outlook Express, > Thunderbird, etc. > > Zach. > > On Fri, 30 Jul 2004 13:59:40 -0400, Mail Admin > <postmaster(a)psy.miami.edu> wrote: > > I bought a certificate from Digital Signature Trust which is a well > > known certificate authority. The reason I bought my certificate, was > > so that email clients connecting to my imaps server wouldn't be > > bothered with warnings of unrecognized certificate authority as they > > would see with a self-signed server certificate. However, I haven't > > been able to configure dovecot with my Digital Signature Trust signed > > certificate so that the unrecognized certificate authority warning > > doesn't appear. >

1 0

[Dovecot] [PATCH 0/10] NTLM patchset submission
by Andrey Panin 02 Aug '04

02 Aug '04

Hello all, as I promised some days ago here is NTLM (aka SPA, aka MSN) authentication support patchset. It contains common code in src/lib-ntlm directory, Samba compatible NTLM password scheme and authentication mechanism itself. All patches are against 1.0-test30. Please take a look. Best regards. -- Andrey Panin | Linux and UNIX system administrator pazke(a)donpac.ru | PGP key: wwwkeys.pgp.net

6 27

[Dovecot] SSL CA root certificate
by Mail Admin 02 Aug '04

02 Aug '04

In reading through the mailing list, this question seems to have come up before, but never quite answered. I bought a certificate from Digital Signature Trust which is a well known certificate authority. The reason I bought my certificate, was so that email clients connecting to my imaps server wouldn't be bothered with warnings of unrecognized certificate authority as they would see with a self-signed server certificate. However, I haven't been able to configure dovecot with my Digital Signature Trust signed certificate so that the unrecognized certificate authority warning doesn't appear. I have the root certificate for Digital Signature Trust, but I don't know where to put it so that dovecot will use it. I tried appending the CA root certificate onto my server's certificate file with no success. The answer here is not, load my server's certificate into thunderbird or outlook express, because that is exactly what I'm trying to avoid by purchasing my certificate from a recognized authority. Help. Thanks, Derek

3 2

[Dovecot] Patch: fix $-terminated MCF
by Joshua Goodall 31 Jul '04

31 Jul '04

p/t_strdup_until wasn't returning a terminated string: Index: src/lib/strfuncs.c =================================================================== RCS file: /home/cvs/dovecot/src/lib/strfuncs.c,v retrieving revision 1.41 diff -u -p -r1.41 strfuncs.c --- src/lib/strfuncs.c 18 Jul 2004 01:44:59 -0000 1.41 +++ src/lib/strfuncs.c 31 Jul 2004 08:43:35 -0000 @@ -154,6 +154,7 @@ char *p_strdup_until(pool_t pool, const mem = p_malloc(pool, size + 1); memcpy(mem, start, size); + mem[size] = '\0'; return mem; } Noticed while testing $-terminated modular crypt strings, because I didn't (and still don't) understand the reason for line 65 of password-scheme.c; ... /* stop at next '$' */ p = strchr(p+3, '$'); if (p != NULL) *password = t_strdup_until(*password, p); ... and I have ln -s 'J' /etc/malloc.conf on freebsd 5-current, so malloc'd memory isn't zeroed, causing a segfault. Is there some system that appends dollar signs to MCF formats? The commit message for r1.3 of password-scheme.c doesn't explain. Joshua. -- Joshua Goodall "as modern as tomorrow afternoon" joshua(a)roughtrade.net - FW109

2 2

[Dovecot] Too many open files with test32
by Jens Gutzeit 31 Jul '04

31 Jul '04

Hi Timo and others, I'm using test32 since today and I'm getting this error once every 2 hours or so: dovecot: Jul 30 20:21:26 Error: IMAP(jens(a)gutzeit.at): open(/var/mail/data/jens/jens(a)gutzeit.at/maildir/.INBOX.Gentoo.Security/dovecot-uidlist) failed: Too many open files dovecot: Jul 30 20:21:26 Error: IMAP(jens(a)gutzeit.at): file maildir-uidlist.c: line 147 (maildir_uidlist_deinit): assertion failed: (!UIDLIST_IS_LOCKED(uidlist)) The problem is not specific to this mailbox. I hadn't this problem with the stable releases and I've also not set any special limits for the dovecot processes. I'm using a grsec pathed kernel (linux 2.6.7), the kern log says: grsec: attempted resource overstep by requesting 1024 for RLIMIT_NOFILE against limit 1024 by /usr/local/libexec/dovecot/imap[imap:19114] uid/euid:1011/1011 gid/egid:448/448, parent /usr/local/sbin/dovecot[dovecot:7799] uid/euid:0/0 gid/egid:0/0 Does dovecot really need more then 1024 filedescriptors or is it a bug? If you need more information just ask. best regards, Jens

3 4

[Dovecot] 0.99.10.9 released
by Timo Sirainen 31 Jul '04

31 Jul '04

v0.99.10.9 2004-07-31 Timo Sirainen <tss(a)iki.fi> - MySQL compiling got broken in last release - More PostgreSQL reconnection fixing

1 0

[Dovecot] mailsync: NO Unexpected EOF
by SAiello＠Jentoo.com 31 Jul '04

31 Jul '04

Hello, I am trying to migrate off a MS Exchange 5.0 server. I am using mailsync (http://www.linux-france.org/prj/imapsync/) to copy the files to a Dovecot server, version 0.99.10.7. For particular messages I get the following error: Couldn't append msg #114081 (Subject:[RE: balh blah]) to folder INBOX: Error trying to append: 826 NO Unexpected EOF I think this is Dovecot, complaining about the message text that imapsync is trying to append/write. If this is Dovecot, is there any setting I can set to fix this?

2 5

[Dovecot] 1.0-test32
by Timo Sirainen 31 Jul '04

31 Jul '04

http://dovecot.org/test/ Ok, another one. Fixes somewhat rare crashes with transaction log. mbox won't deadlock anymore. read-only mboxes work finally .. I hope .. and then the one compilation fix in lib-ntlm. Updated the Dovecot serving public mailing list archives, hopefully this version stays working instead of just returning internal error after a while.

2 2

[Dovecot] Patch for 0.99.10.8
by Jaldhar H. Vyas 31 Jul '04

31 Jul '04

I uploaded 0.99.10.8 to Debian but I needed the patch below to get it to compile. --- dovecot-0.99.10.8.orig/src/auth/db-mysql.h +++ dovecot-0.99.10.8/src/auth/db-mysql.h @@ -1,7 +1,8 @@ #ifndef __DB_MYSQL_H #define __DB_MYSQL_H -#include <mysql.h> +#include <mysql/mysql.h> +#include <mysql/errmsg.h> struct mysql_connection; struct mysql_request; -- Jaldhar H. Vyas <jaldhar(a)debian.org> La Salle Debain - http://www.braincells.com/debian/

2 3

[Dovecot] patch for test31 compile problem
by Cor Bosman 30 Jul '04

30 Jul '04

If you grab test31 you might want to apply this small patch. *** dovecot-1.0-test31/src/lib-ntlm/ntlm-message.c Fri Jul 30 05:00:19 2004 --- ../dovecot-1.0-test31/src/lib-ntlm/ntlm-message.c Fri Jul 30 09:23:42 2004 *************** *** 76,83 **** va_start(args, buffer_offset); do { - type = va_arg(args, int); const char *data; memset(&info, 0, sizeof(info)); write_le16(&info.type, type); --- 76,83 ---- va_start(args, buffer_offset); do { const char *data; + type = va_arg(args, int); memset(&info, 0, sizeof(info)); write_le16(&in

1 0

Re: [Dovecot] dovecot mounts user home dir?
by Timo Sirainen 30 Jul '04

30 Jul '04

On 29.7.2004, at 11:38, Peter Evans wrote: > TM (offmct(a)yahoo.com) wrote: >> Why does dovecot mount the user home directory >> whenever the user checks his email (either pop or imap)? > >> Is there a way to disable this? > > Ask the system nicely, its not dovecot per se, > its the system doing things when dovecot becomes > the user for the duration of the check. I don't think simply changing user id for process does that. It's more likely because of this code in src/master/mail-process.c: /* NOTE: if home directory is NFS-mounted, we might not have access to it as root. Change the effective UID temporarily to make it work. */ if (reply->uid != master_uid && seteuid(reply->uid) < 0) i_fatal("seteuid(%s) failed: %m", dec2str(reply->uid)); ret = chdir(full_home_dir); if (reply->uid != master_uid && seteuid(master_uid) < 0) i_fatal("seteuid(%s) failed: %m", dec2str(master_uid)); /* If user's home directory doesn't exist and we're not trying to chroot anywhere, fallback to /tmp as the mails could be stored elsewhere. */ Dovecot just wants to set current directory to user's home directory as that's the most logical location. I hadn't thought about any automounters.. One way to fix it would be to not use home directories in userdb at all, instead set the "mail" setting in it. Then Dovecot would chdir to /tmp. Another fix would be to just delete the code above and make it always chdir to /tmp. Maybe there should be a setting for this? ..

1 0

[Dovecot] 1.0-test31
by Timo Sirainen 30 Jul '04

30 Jul '04

http://dovecot.org/test/ Fixed mbox corruption in some cases where it wrote headers over beginning of message body. Fixed recent flags to work correctly with mbox. Fixed LSUB command to send LSUB replies instead of LIST replies. Then there's NTLM support from Andrey (which I hopefully didn't break) and dovecotpw utility from Joshua. And then some generic status report: For last few weeks I've been trying to make all network I/O non-blocking but that work is going quite slowly. This means that IMAP and POP3 commands which send lots of data to client must be able to stop processing if output buffer is getting full and continue later. Not very difficult, but a bit boring to implement.. This would allow in future to make a single process handle multiple IMAP connections for same user. Although that might not be such a good idea since there's still lock waits and SEARCH command can take a long time.. Anyway, it makes the code less kludgy. Maybe in future we'll have non-blocking lock waits and file I/O too. Adding some support for threading might not be a bad idea either, as long as it doesn't require adding locks all over the place (threads would perform searches, threading, sorting, etc.). Oh, and another thing it enables is processing multiple commands simultaneously. IMAP supports that, although I don't know if any clients do it. So for example a client could send: 1 fetch 1:* envelope 2 status mailbox (unseen) Then Dovecot would process the fetch command until it's output blocks, then it would send the status reply in the middle of it and then again continue the fetching. The nice thing with this is that client can do some "urgent" requests in the middle of some long running commands without the need to create multiple connections to server.

1 0

[Dovecot] 0.99.10.8 released
by Timo Sirainen 30 Jul '04

30 Jul '04

v0.99.10.8 2004-07-30 Timo Sirainen <tss(a)iki.fi> + LDAP support compiles now with Solaris LDAP library - IMAP BODY and BODYSTRUCTURE replies were wrong for MIME parts which didn't contain Content-Type header. - MySQL and PostgreSQL auth didn't reconnect if connection was lost to SQL server - Linking fixes for dovecot-auth with some systems - Last fix for disconnecting client when downloading mail longer than 30 seconds actually made it never disconnect client. Now it works properly: disconnect when client hasn't read _any_ data for 30 seconds.

1 0

[Dovecot] md5 password is not working
by Farkas Levente 30 Jul '04

30 Jul '04

hi, i setup a new mail server (dovecot-0.99.10.7) with ldap authentication (openldap-2.1.29-2). everything works properly until i switch the user's password from crypt to md5 in the ldap server (of course in this case in the ldap server it stores es {MD5}.... but dovecot gives such error messages: ----------------------- dovecot-auth: Jul 29 17:30:08 Info: ldap(lfarkas(a)x.com): password mismatch ----------------------- it it possible to use dovecot with openldap's md5 password? should I hav to change anything in dovecot's config file if i'd like to use other encrypt schema than crypt? thanks in advance. -- Levente "Si vis pacem para bellum!"

2 1

Re: [Dovecot] Re: Newbie: fetchmail -> procmail -> IMAP (Dovecot) -> MUA?
by Marcus Rueckert 30 Jul '04

30 Jul '04

On 2004-07-29 22:54:12 +0100, David Marsh wrote: > [Unreadable in Outlook, here's why: http://viewport.co.uk/outlook ] something like that sucks. it really makes me consider not to help people. > What do I need to do to configure it? > > I haven't touched the mailserver since installing SuSE, mailservers tend > to frighten me (not least with worry as to what can go wrong if I mess > up!) depends on your needs the comments are very helpfull. and look in the printed manuals or the pdf versions of it. > > 6. chkconfig dovecot on > > I was going to ask what that does, but the man page explains all. > Ah, so *that*'s the right way to fiddle with /etc/init.d/ entries.. yes. it will check dependencies of services e.g. darix -- irssi - the client of the smart and beautiful people http://www.irssi.de/

1 0

[Dovecot] Problems compiling PHP --with-imap - can't find rfc822.h
by Chris Weiss 29 Jul '04

29 Jul '04

I'm trying to add webmail (IMP/HORDE) to my OpenBSD 3.5 mail server (Procmail/Amavid/SA/DCC/Razor/Dovecot 0.99.10.7), which means adding PHP and several other libraries. I'm building PHP 4.3 from the ports tree and, as per the IMP/HORDE readme files, added --with-imap to the makefile. Makeing PHP barfs with a "Cannot find rfc822.h. Please check your IMAP installation." error. I did some digging around and this seems to be part of Courier-IMAP and Mutt, but not part of Dovecot. Can this header file just be grabbed from Courier or Mutt and dropped into /usr/include? Is there something else that's got to be done here?

3 2

[Dovecot] dovecot mounts user home dir?
by TM 29 Jul '04

29 Jul '04

Why does dovecot mount the user home directory whenever the user checks his email (either pop or imap)? Is there a way to disable this? I have indicated in the default_mail_env = mbox:/home/%u/:INBOX=/mail/%u:INDEX=MEMORY. The users are in ldap. Windows users' home is in /home/%u so this is ok but unix users' home are in their local computers and are mounted (via automount) at /d1-data/pcname/username. Even if mounted, the users' home directory isn't used by dovecot since nothing gets written to it. The users only checks his pop mail but still, his home directory gets mounted. Is it possible that dovecot won't try to mount the user's home directory whenever the user checks his mail? Thanks a lot. ________________________________________________________________________ Yahoo! Messenger - Communicate instantly..."Ping" your friends today! Download Messenger Now http://uk.messenger.yahoo.com/download/index.html

1 0

[Dovecot] 0.99.10.8-rc1
by Timo Sirainen 29 Jul '04

29 Jul '04

http://dovecot.org/rc/ + LDAP support compiles now with Solaris LDAP library - IMAP BODY and BODYSTRUCTURE replies were wrong for MIME parts which didn't contain Content-Type header. - MySQL and PostgreSQL auth didn't reconnect if connection was lost to SQL server - Linking fixes for dovecot-auth with some systems - Last fix for disconnecting client when downloading mail longer than 30 seconds actually made it never disconnect client. Now it works properly: disconnect when client hasn't read _any_ data for 30 seconds.

1 0

[Dovecot] Errors with a blackberry
by Jeremy Sanders 28 Jul '04

28 Jul '04

Hi - We tried to access a dovecot-0.99.10.7 IMAPS server with a Blackberry 7230. The Blackberry was on loan so we don't have much access to it for testing. We got the following in our logs: Jul 27 12:30:27 xserv imap-login: Login: testuser [xxx.xxx.xxx.xxx] Jul 27 12:30:27 xserv imap(testuser): IndexID mismatch for binary tree file /home/testuser/mail//.imap/INBOX/.imap.index.tree Jul 27 12:30:27 xserv imap(testuser): IndexID mismatch for binary tree file /home/testuser/mail//.imap/INBOX/.imap.index.tree Jul 27 12:30:27 xserv imap(testuser): IndexID mismatch for modify log file /home/testuser/mail//.imap/INBOX/.imap.index.log Apparently the blackberry didn't see the new mail. Has anyone had any luck with such a Blackberry? Thanks Jeremy -- Jeremy Sanders <jss(a)ast.cam.ac.uk> http://www-xray.ast.cam.ac.uk/~jss/ X-Ray Group, Institute of Astronomy, University of Cambridge, UK. Public Key Server PGP Key ID: E1AAE053

2 2

[Dovecot] mbox sync: UID inserted in the middle of mailbox
by Wouter Van Hemel 28 Jul '04

28 Jul '04

Hello, I found this in the logs of a Dovecot v1.0-test29 test server (OpenBSD 2.9, as mentioned in a previous email): Jul 24 05:37:47 myhostname dovecot: IMAP(username): mbox sync: UID inserted in the middle of mailbox /home/username/.mailbox (235 > 234) Jul 24 05:37:52 myhostname dovecot: IMAP(username): file mbox-sync-rewrite.c: line 357 (mbox_sync_read_and_move): assertion failed: (need_space == -mails[idx].space) Jul 24 05:37:52 myhostname dovecot: child 28601 (imap) returned error 1 Is this bad? :) / Wouter Van Hemel

2 2

Re: [Dovecot] Newbie: fetchmail -> procmail -> IMAP (Dovecot) -> MUA?
by Marcus Rueckert 28 Jul '04

28 Jul '04

hi as i created the rpms: my steps to get a working setup: 1. install postfix,fetchmail,dovecot 2. configure postfix via /etc/sysconfig/mail /etc/sysconfig/postfix 3. run SuSEconfig 4. create a selfsigned cert for ssl (script in /usr/share/doc/packages/dovecot) 5. enable ssl in the dovecot config 6. chkconfig dovecot on 7. rcdovecot start 8. configure fetchmail (not a topic on this list) 9. working setup reached at least for system users hope that helps darix -- irssi - the client of the smart and beautiful people http://www.irssi.de/

1 0

[Dovecot] Concerning: in 0.99.10.7 - Maildir: LIST now doesn't skip symlinks
by chris pickert 27 Jul '04

27 Jul '04

TSS/Dovecot: I saw the recent change in the ChangeLog about the 'subtraction' of the listing of symlinks. The point showed(minus): - Maildir: LIST now doesn't skip symlinks Does this truly mean the functionality was removed? I'd tried doing symlink'd maildirs in 99.10.6 w/ no luck and when I saw this change I hoped this was an addition, as it would be great in lieu of Dovecot's lack of ACL/Shared folders. If it was intented to be ADDED in the recent .7 release, it still doesn't work. If it was pulled (which is strange becauase my .6 release didn't do it), why? Are the .conf directives about it I'm missing by chance? (Didn't notice anything) I'm using Dovecot in combo with horde/imp and it's amazingly faster than courier-imap or uwash-imap, well done! What about the aforementioned ACL/Shared folders? I'm getting into a crux that I may need it and courier-imap-/-cyrus-imap will do my trick but, dovecot smokes them on performance! (Especially with horde/imp's preview/info stuff) Thanks! -- Chris Pickert

5 10

Re: [Dovecot] Newbie: fetchmail -> procmail -> IMAP (Dovecot) -> MUA?
by Lars E. Pettersson 27 Jul '04

27 Jul '04

On Tue, 2004-07-27 at 19:08, David Marsh wrote: > Unfortunately, I don't know how to do this part! > Can anybody offer any advice? A short description on how I did this can be found at my web page: http://www.sm6rpz.se/mailserver.html I use Fedora Core 2, but I do not think that will matter, it should work for SuSE also I think. Lars -- Lars E. Pettersson <lars(a)homer.se> http://www.sm6rpz.se/

1 0

[Dovecot] weakness in hash salt generation
by Joshua Goodall 27 Jul '04

27 Jul '04

Dovecot has routines for password hashing; two of these, crypt_generate and md5_generate, both use sizeof(salt_chars) when reducing a random string to salt. I became suspicious when I noted that all salts generated are composed only of "./01". Unfortunately salt_char is declared static const char * rather than static const char [], and so sizeof(salt_chars) is the size of a pointer. Recommend: diff -u -r1.8 password-scheme.c --- password-scheme.c 30 May 2004 03:57:15 -0000 1.8 +++ password-scheme.c 23 Jul 2004 17:05:36 -0000 @@ -15,7 +15,7 @@ # include <openssl/sha.h> #endif -static const char *salt_chars = +static const char salt_chars[] = "./0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz"; static buffer_t *schemes_buf; joshua. -- Joshua Goodall "as modern as tomorrow afternoon" joshua(a)roughtrade.net - FW109

4 8

[Dovecot] bug in LSUB command
by Geo Carncross 27 Jul '04

27 Jul '04

RFC 2060 section 7.2.2 and 7.2.3 says the "The LIST response occurs as a result of a LIST command." and "The LSUB response occurs as a result of an LSUB command." Dovecot presently returns the LIST response for the LSUB command. -- Geo Carncross <geocar(a)internetconnection.net> Internet Connection

2 1

[Dovecot] Local + virtual users using Dovecot 0.99.10.6 (from debian testing)
by Alexander 26 Jul '04

26 Jul '04

Hi, I have configured the MTA (exim4) to put the messages for my local users at /var/mail. If the user does not exist as true unix user, it looks at a postgresql database and if the user exists there, it delivers the message at /var/mail/virtual Example: User fred is a unix user, and peter is a virtual user. If i send a mail to fred(a)mydomain.org, the message is stored at /var/mail/fred (im using exim's append for transport). If i send a mail to peter(a)mydomain.org, the message is stored at /var/mail/virtual/peter With the defaul configuration from debian, dovecot is capable serving the local users mailbox (and its working at the moment). Im using only IMAP (i see there is an option for pop3, but im not interested in that atm). I think i know how to change the config file to serve only virtual users using the postgres module. Can anyone tell me how to serve them both at the same time? As I understand it, what i need is to make dovecot try to validate a user againt the local user database (its using pam for that at the moment), and if it fail, try with postres. But i dont know how (or if its possible at all). Thanks.

2 1

[Dovecot] file index-mail-headers.c: line 408 (index_mail_get_header): assertion failed: (ret != 0)
by Dmitry Khrustalev 26 Jul '04

26 Jul '04

FreeBSD 4.10-RELEASE, dovecot-1.0-test29 crashes on sort and thread commands: Jul 25 15:12:08 owl dovecot: imap-login: Login: dima [81.19.64.101] Jul 25 15:12:26 owl dovecot: IMAP(dima): file index-mail-headers.c: line 408 (index_mail_get_header): assertion failed: (ret != 0) Jul 25 15:12:26 owl dovecot: child 20384 (imap) killed with signal 6 (gdb) bt #0 0x281e0fc4 in kill () from /usr/lib/libc.so.4 #1 0x2822293e in abort () from /usr/lib/libc.so.4 #2 0x8086c73 in i_internal_panic_handler ( fmt=0x8095720 "file %s: line %d (%s): assertion failed: (%s)", args=0xbfbff8cc "\tW\t\b\230\001") at failures.c:374 #3 0x8086827 in i_panic ( format=0x8095720 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:173 #4 0x806d0f9 in index_mail_get_header (_mail=0x80bf41c, field=0x80955ce "Date") at index-mail-headers.c:408 #5 0x806b8fd in index_mail_get_date (_mail=0x80bf41c, timezone=0x0) at index-mail.c:218 #6 0x8059b1c in mail_sort_input (ctx=0x80a1150, mail=0x80bf41c) at imap-sort.c:420 #7 0x80596ae in imap_sort (client=0x80ad180, charset=0x80b1180 "US-ASCII", args=0x80c8010, sort_program=0x80a10d0) at imap-sort.c:252 #8 0x8054ec8 in cmd_sort (client=0x80ad180) at cmd-sort.c:123 #9 0x80560ae in client_handle_input (client=0x80ad180) at client.c:318 #10 0x805614d in _client_input (context=0x80ad180) at client.c:354 #11 0x808a852 in io_loop_handler_run (ioloop=0x80ab040) at ioloop-poll.c:193 #12 0x808a245 in io_loop_run (ioloop=0x80ab040) at ioloop.c:248 #13 0x805bc5b in main (argc=1, argv=0xbfbffbb0, envp=0xbfbffbb8) at main.c:217 (gdb)

3 2

[Dovecot] dovecot.conf: default_mail_env
by Sebastien 26 Jul '04

26 Jul '04

I just installed Dovecot on Debian and everyting seems to be working fine except for the fact that it can't seem to find my mails when I log in. All my mails are stored in the file ~/mail/Inbox. In the dovecot.conf file I put: default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u and it's not working. What is the part: mbox:~/mail/ for ? and what is the part: INBOX=/var/mail/%u for ? I read the documentation but I don't understand. Can anyone help me ?

3 2

[Dovecot] 1.0-test30
by Timo Sirainen 26 Jul '04

26 Jul '04

http://dovecot.org/test/ Mostly just fixes. Fixed some crashes with cache file. Fixed "randomly" occuring mbox parsing problem. Namespace handling was pretty much rewritten. Non-hidden namespaces will also show up in LIST replies now, so if you have eg.: namespace private { prefix = mboxes location = mbox:~/mail } Then clients would show "mboxes" as normal folder. Subscription file handling also changed and will probably change more.. Currently subscription file is specific to the namespace where the mailboxes are. So in above example subscribing to "mboxes/foo" would use ~/mail/.subscriptions file rather than the default. I'm not exactly sure if this is a good idea or not.. It probably needs to be configurable with some subscriptions = yes|no per-namespace setting.

1 0

[Dovecot] imap folders
by Roger D. Vargas 26 Jul '04

26 Jul '04

Until last week I was using old imap daemon, then i installed FEdora Core 2 and it was replaced by dovecot or cyrus. I decided to use dovecot, and managed to configure it. But I still have a problem, the users imap folders (stored in their home dirs) arent visible, only the inbox. How can I recover those folders? -- Roger Durañona Vargas Linux user #180787 A cada momento nos rodea lo desconocido. Es alli donde uno tiene que buscar el conocimiento. Paul Muad'Dib Atreides. Children of Dune

2 1

[Dovecot] Some users cannot read mail: assertion failed
by Robert Munteanu 26 Jul '04

26 Jul '04

Hi all! I am a recent user of dovecot. First of all, the migration from UW-IMAP was definitely worth it. But now I've run into some troubles. Two of my users complain that they can't read their Inboxes, but other folders work fine. The error message I get in the logs look like: lynx imap(gheorghe.bancos): file buffer.c: line 357 (buffer_set_start_pos): assertion failed: (abs_pos <= I_MIN(buf->used, buf->limit)) lynx dovecot: child 1823 (imap) killed with signal 6 The problems have been reported with both MS Outlook and SquirrelMail. What causes this problem and how can I fix it? Thank you, -- Robert Munteanu _______________________________________________________________ Connex scaneaza automat toate mesajele impotriva virusilor folosind Trend Micro VirusWall. Connex automatically scans all messages for viruses using Trend Micro VirusWall. _______________________________________________________________ Nota: Este posibil ca produsul Trend Micro VirusWall sa nu detecteze toti virusii noi sau toate variantele lor. Va rugam sa luati in considerare ca exista un risc de fiecare data cind deschideti fisiere atasate si ca MobiFon nu este responsabila pentru orice prejudiciu cauzat de decizia dvs. Disclaimer: It is possible that the Trend Micro VirusWall product may not be able to detect all new viruses and variants. Please be aware that there is a risk involved whenever opening e-mail attachments to your computer and that MobiFon is not responsible for any damages caused by your decision to do so.

2 6

[Dovecot] paypal link for donations to dovecot webpage?
by security officer 26 Jul '04

26 Jul '04

Paypal link for donations to dovecot webpage? Really good sofware ;) -- Eero

1 0

[Dovecot] Passwords in passwd-file
by Andrew Boothman 25 Jul '04

25 Jul '04

Hi! I'm trying to use MD5 hashed password in a passwd-file (not the system one). I've set auth_userdb = passwd-file /my/passwd/file auth_passdb = passwd-file /my/passwd/file auth.txt additionally describes a syntax like: auth_userdb = passwd-file[34] /my/passwd/file to denote MD5 passwords in the file, but I've been unable to get any combination of using []'s after passwd-file to work. Dovecot complains: "Unknown userdb type". How is it best to store passwords in a passwd-file using Dovecot 0.99.10.7? Ideally I want to use PHP to generate the passwords being entered into the file. Thanks for any pointers! Andrew

2 2

[Dovecot] Bug? 1.0.0-test28 NFS locking problems
by Tim Southerwood 24 Jul '04

24 Jul '04

Hi Slight problem - linux 2.4 running dovecot, Solaris 2.8 home directory server. Full lockd support etc. I had to make the following code patches (at end of mail for clarity) to get dovecot to read the users mbox files at all. 1) fcntl with F_SETLKW will not work against a Solaris 2.8 server as proved with a small test program. Other forms of fcntl (ie F_SETLK) are OK. I noticed there are some code witches, but setting mbox_lock_timeout=0 only seems to knock one of the fcntl's over to F_SETLK 2) O_CREAT | O_EXCL are documented not to work over NFS properly (see man open(2) on linux). So I knocked out the O_EXCL and combined with (1) dovecot will talk over NFS to remote mbox files. THESE ARE NOT VIABLE CODE PATCHES They illustrate a problem I found - they are hackish and totally wrong. I'm not sure of the best way to correct this problem cleanly, so I am just submitting it as a potential bug. Cheers Tim Southerwood ************************************************** --- dovecot-1.0-test28/src/lib/file-lock.c.orig 2004-07-20 14:29:47.000000000 +0100 +++ dovecot-1.0-test28/src/lib/file-lock.c 2004-07-20 14:30:15.000000000 +0100 @@ -38,7 +38,7 @@ fl.l_start = 0; fl.l_len = 0; - while (fcntl(fd, timeout != 0 ? F_SETLKW : F_SETLK, &fl) < 0) { + while (fcntl(fd, timeout != 0 ? F_SETLK : F_SETLK, &fl) < 0) { if (timeout == 0 && (errno == EACCES || errno == EAGAIN)) return 0; --- dovecot-1.0-test28/src/lib-storage/index/mbox/mbox-lock.c.orig 2004-07-20 14:29:54.000000000 +0100 +++ dovecot-1.0-test28/src/lib-storage/index/mbox/mbox-lock.c 2004-07-20 14:30:35.000000000 +0100 @@ -361,7 +361,7 @@ fl.l_start = 0; fl.l_len = 0; - wait_type = max_wait_time == 0 ? F_SETLK : F_SETLKW; + wait_type = max_wait_time == 0 ? F_SETLK : F_SETLK; while (fcntl(ctx->ibox->mbox_fd, wait_type, &fl) < 0) { if (errno != EINTR) { if (errno != EAGAIN && errno != EACCES) ************************************************** and ************************************************** diff -NaurbB dovecot-1.0-test28.orig/src/lib/file-dotlock.c dovecot-1.0-test28/src/lib/file-dotlock.c--- dovecot-1.0-test28.orig/src/lib/file-dotlock.c 2004-06-28 18:28:01.000000000 +0100+++ dovecot-1.0-test28/src/lib/file-dotlock.c 2004-07-20 14:50:33.000000000 +0100 @@ -192,7 +192,7 @@ return -1; } - fd = open(*path_r, O_RDWR | O_EXCL | O_CREAT, 0666); + fd = open(*path_r, O_RDWR | O_CREAT, 0666); if (fd != -1) return fd; diff -NaurbB dovecot-1.0-test28.orig/src/lib-storage/index/maildir/maildir-util.c dovecot-1.0-test28/src/lib-storage/index/maildir/maildir-util.c--- dovecot-1.0-test28.orig/src/lib-storage/index/maildir/maildir-util.c 2004-06-16 01:50:41.000000000 +0100+++ dovecot-1.0-test28/src/lib-storage/index/maildir/maildir-util.c 2004-07-20 14:51:25.000000000 +0100@@ -241,7 +241,7 @@ if (stat(path, &st) < 0 && errno == ENOENT) { /* doesn't exist */ mode_t old_mask = umask(0); - fd = open(path, O_WRONLY | O_CREAT | O_EXCL, mode); + fd = open(path, O_WRONLY | O_CREAT, mode); umask(old_mask); if (fd != -1 || errno != EEXIST) break; diff -NaurbB dovecot-1.0-test28.orig/src/lib-storage/index/mbox/mbox-storage.c dovecot-1.0-test28/src/lib-storage/index/mbox/mbox-storage.c--- dovecot-1.0-test28.orig/src/lib-storage/index/mbox/mbox-storage.c 2004-07-20 14:45:55.000000000 +0100+++ dovecot-1.0-test28/src/lib-storage/index/mbox/mbox-storage.c 2004-07-20 14:49:56.000000000 +0100@@ -386,7 +386,7 @@ int fd; /* make sure inbox file itself exists */ - fd = open(storage->inbox_path, O_RDWR | O_CREAT | O_EXCL, 0660); + fd = open(storage->inbox_path, O_RDWR | O_CREAT, 0660); if (fd != -1) (void)close(fd); @@ -579,7 +579,7 @@ } /* create the mailbox file */ - fd = open(path, O_RDWR | O_CREAT | O_EXCL, 0660); + fd = open(path, O_RDWR | O_CREAT, 0660); if (fd != -1) { (void)close(fd); return 0; diff -NaurbB dovecot-1.0-test28.orig/src/lib-storage/index/mbox/mbox-storage.c.mbox dovecot-1.0-test28/src/lib-storage/index/mbox/mbox-storage.c.mbox--- dovecot-1.0-test28.orig/src/lib-storage/index/mbox/mbox-storage.c.mbox 2004-07-11 22:03:09.000000000 +0100+++ dovecot-1.0-test28/src/lib-storage/index/mbox/mbox-storage.c.mbox 2004-07-20 14:50:58.000000000 +0100@@ -386,7 +386,7 @@ int fd; /* make sure inbox file itself exists */ - fd = open(storage->inbox_path, O_RDWR | O_CREAT | O_EXCL, 0660); + fd = open(storage->inbox_path, O_RDWR | O_CREAT, 0660); if (fd != -1) (void)close(fd); @@ -579,7 +579,7 @@ } /* create the mailbox file */ - fd = open(path, O_RDWR | O_CREAT | O_EXCL, 0660); + fd = open(path, O_RDWR | O_CREAT, 0660); if (fd != -1) { (void)close(fd); return 0; ************************************************** -- Tim J Southerwood Senior Programmer CSG, Dept of Computing, Imperial College, London

4 19

[Dovecot] (no subject)
by Lorenzo Conti 23 Jul '04

23 Jul '04

2 1

[Dovecot] RFE: MD5 encryption with for plain text passwords
by Felix Schwarz 23 Jul '04

23 Jul '04

Hi, due to compatibility issues with mail clients I think I have to use plain text authentication. In order to secure the passwords during their transport I'll use SSL encryption. After reading some documentation I think that I'll have to store the passwords as plain text in the authdb. That is something I dislike very much as it is a (imho) good tradition for unix to store only encrypted passwords for security reasons. I would like to see the possibility in dovecot to store the passwords for plain text authentication md5 encrypted. That should be easy to implement (just one md5 encryption before comparing the given password with the stored one) and could improve security. As this would be an api change it should be made configurable (and in the first versions this setting should default to the actual behavior). How do you like this idea? Maybe I can provide a patch but I won't work on this if you won't include it within dovecot at all. And last but not least I want to thank you for your great support! I really appreciate it! :-) -- Felix

3 2

[Dovecot] CRAM-MD5
by Felix Schwarz 23 Jul '04

23 Jul '04

Hi, after getting dovecot working with PostgreSQL and plaintext passwords I tried to use md5 encrypted passwords with mozilla. www.roughtrade.net/dovecot says that Mozilla only supports CRAM-MD5 and that CRAM-MD5 is included in HEAD. Now I have two questions: 1) Is the md5 hash stored in passdb with cram-md5 the same as in digest-md5? 2) Is a new dovecot stable build planned within the next two weeks (which includes CRAM-MD5)? (I guess the answer is no :-( 3) Are there any dovecot rpms with pgsql and CRAM-md5 supprt? -- Felix

3 3

Re: [Dovecot] Dovecot auth problem on FreeBSD 4.10
by Viren Patel 22 Jul '04

22 Jul '04

> On Thu, 2004-07-22 at 20:35, Viren Patel wrote: >> Hope this helps. Should I send the entire socket.h file? > > Hmm. What would happen if in src/lib/fdpass.c you added: > > #undef CMSG_LEN > #undef CMSG_DATA > > #define CMSG_LEN(l) (sizeof(struct cmsghdr) + (l)) > #define CMSG_DATA(cmsg) ((u_char *)(cmsg) + sizeof(struct cmsghdr)) > > Yes! This did the trick. It seems to be working fine now. Thanks for your help. I can now go on to further testing and imaps/pop3s. I am seriously looking at Dovecot for our production mail server. Viren Patel University of Texas at Austin

2 1

[Dovecot] Dovecot auth problem on FreeBSD 4.10
by Viren Patel 22 Jul '04

22 Jul '04

Hello. I am trying to setup Dovecot on an Alpha running FreeBSD 4.10. I am simply trying the imap/pop3 protocols at this time. But with both protocols the log message I get is: pop3-login: fd_send(5) failed: Bad file descriptor dovecot: child 275 (login) returned error 89 or imap-login: fd_send(5) failed: Bad file descriptor dovecot: child 275 (login) returned error 89 I have tried various combinations of: auth = default|plain|pam auth_userdb = passwd auth_passdb = passwd|shadow|pam|passwd-file but nothing works. What am I doing wrong? Thanks. Viren Patel University of Texas at Austin

5 5

[Dovecot] help: The current command did not succeed. The mail server responded: Invalid mask.
by Ivo Rütsche 22 Jul '04

22 Jul '04

on your mozilla client: go to "Edit" / "Mail & Newsgroups Account Settings" / [your account] / "Server Settings" / "Advanced..." / "IMAP" / "Other Users" make sure your text box is empty (default is "~") bye ivo

1 0

[Dovecot] One final issue
by Tom Ray [Lists] 22 Jul '04

22 Jul '04

Timo- Thanks for all the help. After I changed the permissions to the virtual user I setup I had a few small issues but was able to work through them. Now IMAP is running great. But my new question is, do I need to do anything to get it to work with POP? My server refuses to respond on 110 and I'm wondering if there is something I need to do? I was under the impression that Dovecot can handle both POP/IMAP requests. TIA Tom

3 8

[Dovecot] [PATCH] add LOGIN authentication mechanism
by Andrey Panin 22 Jul '04

22 Jul '04

Hello, attached patch (1.0-test29) adds LOGIN authentication mechanism. Tested with KMail and seems working. Please consider applying. Best regards. P.S. I also have NTLM authentication working and plan to submit it RSN. -- Andrey Panin | Linux and UNIX system administrator pazke(a)donpac.ru | PGP key: wwwkeys.pgp.net

2 1

[Dovecot] Authentification with PostgreSQL
by Felix.Schwarz＠web.de 22 Jul '04

22 Jul '04

Hi all, I found Dag Wieers' Fedora Core 2 rpm on http://dag.wieers.com/packages/dovecot/ and installed it. Now dovecot-auth isn't complaining anymore about an unknown userdb type but I can't get authentication working. /etc/dovecot.conf (...) # Authentication process name. auth = default # plain digest-md5 anonymous auth_mechanisms = plain auth_userdb = pgsql /etc/dovecot-pgsql.conf auth_userdb = pgsql /etc/dovecot-pgsql.conf auth_user = root auth_verbose = yes (...) /etc/dovecot-pgsql.conf connect = host=localhost dbname=xams-dovecot user=dovecot password=hallo default_pass_scheme = PLAIN password_query = SELECT password FROM users WHERE username = '%u' user_query = SELECT home, uid, gid FROM users WHERE username = '%u' If I try to login over imap (no ssl) with Mozilla Mail, authentification will always fail (username: felix(a)schwarz-online.org, password: "hallo"). /var/log/syslog Jul 22 15:48:47 steinchen postgres[2057]: [30-1] DEBUG: forked new backend, pid=2198 socket=10 Jul 22 15:48:47 steinchen postgres[2198]: [31-1] DEBUG: Passwortpaket erhalten Jul 22 15:48:47 steinchen postgres[2198]: [32-1] LOG: Verbindung authorisiert: Benutzer=dovecot Datenbank=xams-dovecot (...) Jul 22 15:51:15 steinchen dovecot(pam_unix)[2210]: check pass; user unknown Jul 22 15:51:15 steinchen dovecot(pam_unix)[2210]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= /var/log/dovecot.log dovecot: Jul 22 15:48:46 Info: Dovecot starting up dovecot-auth: Jul 22 15:51:18 Info: PAM: pam_authenticate(felix(a)schwarz-online.org) failed: Authentication failure $ psql -d xams-dovecot dovecot xams-dovecot-> SELECT password FROM users WHERE username = 'felix(a)schwarz-online.org'; password ---------- hallo xams-dovecot=> SELECT home, uid, gid FROM users WHERE username = 'felix(a)schwarz-online.org'; home | uid | gid ----------+-----+----- /home/fs | 500 | 500 What is wrong? Password encryption? Is there a possibility to see what dovecot gets from Mozilla and what are the expected results of the sql queries? I am stuck as I don't know exactely why authentification failes... thanks for your help -- Felix

3 2

[Dovecot] [PATCH] POP3 CAPA command RFC violation
by Andrey Panin 22 Jul '04

22 Jul '04

Hello, looks like SASL capability reported by dovecot in response to POP3 CAPA command doesn't conforms with rfc2449 which says: Examples: C: CAPA S: +OK Capability list follows S: TOP S: USER S: SASL CRAM-MD5 KERBEROS_V4 S: RESP-CODES S: LOGIN-DELAY 900 S: PIPELINING S: EXPIRE 60 S: UIDL S: IMPLEMENTATION Shlemazle-Plotz-v302 S: . And later: The POP3 AUTH command [POP-AUTH] permits the use of [SASL] authentication mechanisms with POP3. The SASL capability indicates that the AUTH command is available and that it supports an optional base64 encoded second argument for an initial client response as described in the SASL specification. The argument to the SASL capability is a space separated list of SASL mechanisms which are supported. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Dovecot sends SASL capability as list of AUTH=FOO pairs. Looks like copy-paste from IMAP code. Patch attached. Best regards. -- Andrey Panin | Linux and UNIX system administrator pazke(a)donpac.ru | PGP key: wwwkeys.pgp.net

1 0

[Dovecot] namespaces and behaviour of LIST and SELECT with leading ~
by Tim Southerwood 21 Jul '04

21 Jul '04

Hi One weirdness when going through the code: (We are migrating from WU-IMAP and have users with a mixture of ~/IMAP/ and ~/Mail/ for storing mail - but all user INBOX=~/.email thankfully. IMAP client config is even more random and we have 1800 users. I have been playing with namespaces to translate various prefixes ala: default_mail_env = mbox:%h/:INBOX=%h/.email:INDEX=/var/cache/dovecot/%n # Note lack of IMAP ^^^ (So clients can use ~/IMAP or ~/Mail - we have a # historic mixture) full_filesystem_access = no namespace private { separator = / inbox = yes prefix = hidden = no location = mbox:.email } namespace private { separator = / prefix = hidden = no location = mbox:IMAP/ } namespace private { separator = / prefix = IMAP/ hidden = no location = mbox:IMAP/ } namespace private { separator = / prefix = ~/IMAP/ hidden = no location = mbox:IMAP/ } User tstest has INBOX in ~/.email and mail folders in ~/IMAP/ all in mbox format: Here's a sample conversation: * OK dovecot ready. 1 login tstest ******* 1 OK Logged in. 1 list "" % * LIST (\NoInferiors \UnMarked) "/" INBOX * LIST (\NoInferiors) "/" "Trash" * LIST (\NoInferiors) "/" "Queue" * LIST (\NoInferiors) "/" "Sent" * LIST (\NoInferiors) "/" "Drafts" * LIST (\NoInferiors) "/" "Blah" 1 OK List completed. Good 1 list "" IMAP/% * LIST (\NoInferiors) "/" "IMAP/Trash" * LIST (\NoInferiors) "/" "IMAP/Queue" * LIST (\NoInferiors) "/" "IMAP/Sent" * LIST (\NoInferiors) "/" "IMAP/Drafts" * LIST (\NoInferiors) "/" "IMAP/Blah" 1 OK List completed. Good 1 list "" ~/IMAP/% 1 OK List completed. Oops (being caught by mbox_is_valid_mask as prefix begins with ~ and the client supplied prefix is being tested, not the virtual one after namespace prefix substitution) But... 1 select Blah * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted.* 5 EXISTS * 0 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1090326264] UIDs valid * OK [UIDNEXT 6] Predicted next UID 1 OK [READ-WRITE] Select completed. Yes 1 select IMAP/Blah * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted.* 5 EXISTS * 0 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1090326264] UIDs valid * OK [UIDNEXT 6] Predicted next UID 1 OK [READ-WRITE] Select completed. Yes 1 select ~/IMAP/Blah * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted.* 5 EXISTS * 0 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1090326264] UIDs valid * OK [UIDNEXT 6] Predicted next UID 1 OK [READ-WRITE] Select completed. Oo - this works despite the ~ I would argue that with namespace {} directives, the behaviour of SELECT is correct. I would suggest that it may be better to test the final translated path thus: if full_filesystem_access = yes let anything go. else make sure that final translated mail path is identical OR a subpath of the default_mail_env mbox folder path. (INBOX is a special case and can be matched as well) This is a suggestion - what do you think? I'd have a go myself but I don't yet feel competant with the dovecot code. Best wishes Tim -- Tim J Southerwood

2 1

[Dovecot] dovecot-1.0-test27 crash on FETCH
by Wouter Van Hemel 21 Jul '04

21 Jul '04

Hello, I've got a crash with -test27 on a FETCH, just after logging in. Attached are the mailbox (1 message only), logs, sniffed session, testcase and core dump backtrace. If the dovecot.conf is needed, just ask (it's pretty much the default configuration). Maybe this has just been fixed in -test28, in which case you can just delete this email. :) Btw, it's rather irrelevant, but does anybody know a good way to read the qmail alias user's mailbox remotely (imap? The only way seems by assigning a password to the account... Regards, wouter

2 4

[Dovecot] Fatal: Unknown userdb type 'pgsql'
by felix.schwarz＠web.de 21 Jul '04

21 Jul '04

Hello, I'm trying to use postgres authentication with dovecot on a linux system running Fedora Core 2. Installation of dovecot was done by installing the rpm included in the fedora distribution ("yum install dovecot"). from /etc/dovecot.conf auth_userdb = pgsql /etc/dovecot-pgsql.conf auth_passdb = pgsql /etc/dovecot-pgsql.conf but the logs tell me: dovecot: Jul 21 19:28:39 Info: Dovecot starting up dovecot-auth: Jul 21 19:28:40 Fatal: Unknown userdb type 'pgsql' dovecot: Jul 21 19:28:40 Error: Auth process died too early - shutting down dovecot: Jul 21 19:28:40 Error: child 5229 (auth) returned error 89 imap-login: Jul 21 19:28:40 Fatal: fd_send(-1) failed: Broken pipe imap-login: Jul 21 19:28:40 Fatal: fd_send(-1) failed: Broken pipe I think that the fedora rpm was compiled without postgresql support. - Is the information given above sufficient for an educated guess? - Would that lead to the above error message? - What other errors may cause this behavior? - How can I check which authentification types are supported by my dovecot-auth? - Are there any other Fedora rpms compiled with postgres support available on the net? thank you for your help :-) -- Felix

3 3

RE: [Dovecot] Probably a bad idea but.....
by Mark Lidstone 21 Jul '04

21 Jul '04

Hi everyone, Just done some testing and thought I'd share the results. I've successfully moved a few test emails from a Mercury/32 Windows server to Maildirs. I created an IMAP folder for each user ".INBOX.Old\ Mail" and put the email in there. It's accessable via IMAP but does not show up as a new email when the user uses POP3 to collect their email - exactly what I was after (they're all using POP3 at the moment, but I will be pushing them to move to IMAP at a later date). I'm going to copy the rest of the email in one go overnight so if you don't get another email from me on here assume it worked. Thanks for the help Timo. Thanks, Mark Lidstone IT and Network Support Administrator BMT SeaTech Ltd Grove House, Meridians Cross, 7 Ocean Way Ocean Village, Southampton. SO14 3TJ. UK Tel: +44 (0)23 8063 5122 Fax: +44 (0)23 8063 5144 E-Mail: mailto:mark.lidstone@bmtseatech.co.uk Website: www.bmtseatech.co.uk ======================================================================== == Confidentiality Notice and Disclaimer: The contents of this e-mail and any attachments are intended only for the use of the e-mail addressee(s) shown. If you are not that person, or one of those persons, you are not allowed to take any action based upon it or to copy it, forward, distribute or disclose the contents of it and you should please delete it from your system. BMT SeaTech Limited does not accept liability for any errors or omissions in the context of this e-mail or its attachments which arise as a result of Internet transmission, nor accept liability for statements which are those of the author and not clearly made on behalf of BMT SeaTech Limited. ======================================================================== == -----Original Message----- From: Timo Sirainen [mailto:tss@iki.fi] Sent: 21 July 2004 13:58 To: Mark Lidstone Cc: dovecot(a)dovecot.org Subject: Re: [Dovecot] Probably a bad idea but..... On Wed, 2004-07-21 at 14:11, Mark Lidstone wrote: > Mercury stores mail in a similar way to Maildirs, different folders > with separate files for each mail, stored in plaintext RFC822 format. > How sensible would it be to copy the files over from the Mercury > server to users maildirs on a Linux server? > > The filenames are in a different format but I don't know if that would > cause a problem? You'll lose message flags, but as long as the filenames don't contain ':' characters you can just copy them.

1 0

Re: [Dovecot] 1.0.0-test28 Problem with INDEX
by Tim Southerwood 21 Jul '04

21 Jul '04

On Tue, 20 Jul 2004 20:35:04 +0300 Timo Sirainen <tss(a)iki.fi> wrote: > On Tue, 2004-07-20 at 19:13, Tim Southerwood wrote: > > default_mail_env = > > mbox:%h/IMAP/:INBOX=%h/.email:INDEX=/var/cache/dovecot/%n > > > > The INBOX indexes are being built correctly in /var/cache/dovecot, > > but all other indexes for folders are still being built in the > > user's home directory. > > > > I had it working once - but it seems fragile - almost as if the > > config parser is sensitive to context??? Sorry - seems vague, but I > > can't pin this down reliably. > > Have you set full_filesystem_access = yes? That's the only thing that > I can think of that might make it use different directory (and even > then only if you access the mboxes as "~/IMAP/box"). > > OK - I've been look at the code all day and sticking debug statements in. full_filesystem_access = yes will cause the indexes to stick with the mail files and not be based under INDEX=dir. But - using default_mail_env = mbox:%h/:INBOX=%h/.email:INDEX=/var/cache/dovecot/%n # Note lack of IMAP ^^^ (So clients can use ~/IMAP or ~/Mail - we have a # historic mixture) full_filesystem_access = no namespace private { separator = / prefix = hidden = no location = mbox:IMAP/ } namespace private { separator = / prefix = IMAP/ hidden = no location = mbox:IMAP/ } namespace private { separator = / prefix = ~/IMAP/ hidden = no location = mbox:IMAP/ } Will cause the indexes to also stick with the mail files, not use INDEX=dir Bit of a problem with NFS involved. I know I could use INDEX=MEMORY, but I'm worried about what will happen if the machine exhausts it's VM (not impossible with my site). I'm happy to play with this a bit longer if you could give me a hint: where is the path to the index file computed? Cheers Tim -- Tim J Southerwood

1 0

[Dovecot] Probably a bad idea but.....
by Mark Lidstone 21 Jul '04

21 Jul '04

Hi all, I've got a few users I'm trying to migrate from a Mercury Mail server to a dovecot IMAP/POP3 setup. I was hoping to use some sort of imap-copy type script to move email from the Mercury server to dovecot server, but the Mercury box is running so slow it's impossible. Mercury stores mail in a similar way to Maildirs, different folders with separate files for each mail, stored in plaintext RFC822 format. How sensible would it be to copy the files over from the Mercury server to users maildirs on a Linux server? The filenames are in a different format but I don't know if that would cause a problem? Any help gratefully appreciated, Mark Lidstone IT and Network Support Administrator BMT SeaTech Ltd Grove House, Meridians Cross, 7 Ocean Way Ocean Village, Southampton. SO14 3TJ. UK Tel: +44 (0)23 8063 5122 Fax: +44 (0)23 8063 5144 E-Mail: mailto:mark.lidstone@bmtseatech.co.uk Website: www.bmtseatech.co.uk ======================================================================== == Confidentiality Notice and Disclaimer: The contents of this e-mail and any attachments are intended only for the use of the e-mail addressee(s) shown. If you are not that person, or one of those persons, you are not allowed to take any action based upon it or to copy it, forward, distribute or disclose the contents of it and you should please delete it from your system. BMT SeaTech Limited does not accept liability for any errors or omissions in the context of this e-mail or its attachments which arise as a result of Internet transmission, nor accept liability for statements which are those of the author and not clearly made on behalf of BMT SeaTech Limited. ======================================================================== ==

2 1

[Dovecot] Almost there.
by Tom Ray [Lists] 21 Jul '04

21 Jul '04

Hey Timo- I got everything working now that I can log in properly...but I'm have a permissions issue and I'm not sure how to set it..I've been playing with ownership and permissions and I'm still getting this imap(tom(a)testdomain.com): mkdir_parents(/var/spool/mail/indexes/testdomain.com/tom/.imap/INBOX) failed: Permission denied What's that permission/ownership in that folder supposed to be?

2 1

[Dovecot] imap support question
by Tom Allison 21 Jul '04

21 Jul '04

OK, I'm actually trying to write something which interacts with IMAP. I'm trying to run the FETCH command and it goes OK, but I'm wondering how I might be able to call both RFC822.SIZE and BODY[HEADERS.FIELDS(..) in the same call. Right now I'm only able to get this to work with two calls to the server. I was hoping to avoid making two calls. Any suggestions? (I realize it isn't exactly "on topic" for the mailing list, but I can't think of any list I'm on that's even close to the topic)

3 2

[Dovecot] Newbie question: configuration for virtual users
by Rory Campbell-Lange 21 Jul '04

21 Jul '04

Hi! I'm looking forward to deploying dovecot as an IMAP server. I did some research into the various options and it looks like dovecot is the right daemon for me. I'll be using it with Exim. I am running a few tens of users on my server, most of them small numbers of people part of a small company, e.g. example.com. At present I have exim delivering to mbox in each virtual user's mail folder. So, for chris, john and mandy @ example.com, I have /home/example/Mail/ chris john mandy All of the users in example.com run under the same uid and gid (example). I like to separate these 'virtual' users from the real system users for security reasons. I presently serve up these mboxes via teapop, which allows for per-domain configuration. I couldn't find a similar setup after a cursory read of the config file examples on the dovecot website. I'd like some advice on how to support different non-system users under dovecot, ideally storing mail in a similar configuration to above, except (presumably?) that the user files will be under each user name? Thus: /home/example/Mail/ chris/ john/ mandy/ I may use postgresql to store user configuration data if appropriate. Advice gratefully received. Rory -- Rory Campbell-Lange <rory(a)campbell-lange.net> <www.campbell-lange.net>

2 3

[Dovecot] 1.0.0-test28 Problem with INDEX
by Tim Southerwood 20 Jul '04

20 Jul '04

Hi Using this line in dovecot.conf (ignore linewrap) default_mail_env = mbox:%h/IMAP/:INBOX=%h/.email:INDEX=/var/cache/dovecot/%n The INBOX indexes are being built correctly in /var/cache/dovecot, but all other indexes for folders are still being built in the user's home directory. I had it working once - but it seems fragile - almost as if the config parser is sensitive to context??? Sorry - seems vague, but I can't pin this down reliably. Anyone else had problems? Cheers Tim -- Tim J Southerwood Senior Programmer CSG, Dept of Computing, Imperial College, London

2 2

[Dovecot] Idea to enhance migration from UW-Imap
by Klaus Steinberger 20 Jul '04

20 Jul '04

Hello, i want to migrate from UW-Imap to dovecot, but want to avoid changing clients (that would be really hard to do). All my users have their Mailboxes in ~/Mail. My idea would be now to strip off "Mail" from the imap commands, so that both a client which prepends "Mail" as well as one who doesn't would see the same mailboxes. Can somebody give me a hint where in the dovecot source I could do that stripping (at best some central function, so this stripping has to be done just one time). I would be glad to make the changes and then to contribute that change, I just need a hint where in the sources I will find the right place. Sincerly, Klaus Steinberger -- Klaus Steinberger Maier-Leibnitz Labor Phone: (+49 89)289 14287 Am Coulombwall 6, D-85748 Garching, Germany FAX: (+49 89)289 14280 EMail: Klaus.Steinberger(a)Physik.Uni-Muenchen.DE URL: http://www.physik.uni-muenchen.de/~k2/ In a world without Walls and Fences, who needs Windows and Gates

2 2

[Dovecot] 1.0-test29
by Timo Sirainen 20 Jul '04

20 Jul '04

http://dovecot.org/test/ Huh, I almost got stuck with this one. It's boring to do larger rewrites to things that already kind of work. This time it was rewriting how caching headers work. The old way was kind of ugly and it didn't really guarantee the order in which cached headers could be fetched. So there were a few theoretical problems that could have broken things. 0.99.10 didn't support caching headers at all, so it didn't have this problem. I think the new caching code is finally nearly finished. Just a few small things left and it's done. This release also fixes some other crashes and problems. I've been running it nearly an hour now without problems :)

1 0

[Dovecot] Problem with IMAP and MAIL environment
by Luis Miguel Cruz 20 Jul '04

20 Jul '04

Here is the problem: Jul 19 10:40:17 mail1 pop3(master): mbox: Can't create root IMAP folder /home/usuarios/master/mail: Permission denied Jul 19 10:40:17 mail1 pop3(master): MAIL environment missing and autodetection failed (home /home/usuarios/master) Jul 19 10:40:17 mail1 dovecot: child 3528 (pop3) returned error 89 Is there anyway to avoid it? Thanks.

3 5

[Dovecot] [PATCH] fix MD5 code buglet
by Andrey Panin 20 Jul '04

20 Jul '04

Hello, md5_final() function contains minor buglet, it clears first 4 bytes of md5_context instead of whole structure. Patch attached. Best regards. -- Andrey Panin | Linux and UNIX system administrator pazke(a)donpac.ru | PGP key: wwwkeys.pgp.net

1 0

[Dovecot] [PATCH] fix build error with HAVE_MODULES not set
by Andrey Panin 20 Jul '04

20 Jul '04

Hello, attached trivial patch (against 1.0-test28) fixes build error with unset HAVE_MODULES. Error is caused by missing second argument of module_dir_load() stub. Please consider applying. Best regards. -- Andrey Panin | Linux and UNIX system administrator pazke(a)donpac.ru | PGP key: wwwkeys.pgp.net

1 0

[Dovecot] Dovecot LDAP Auth strange mailbox behavior
by Ryan Bloch 19 Jul '04

19 Jul '04

Hello everyone. I have setup a Debian Sarge server, with openldap, postfix, and Dovecot. I have been able to fix all the problems that have been logged thus far, and it seems to work. I am able to use a mail client to login to the pop3 server. The authentication works, and it logs as a successful login, but no messages download. I get a response: No New Messages. I have checked the user's maildir directory, and there are mails sitting in the new directory, so it should download. Anyone have any clues? Thanks in advance, Ryan

3 3

[Dovecot] init script
by Luis Miguel Cruz 19 Jul '04

19 Jul '04

Hi all, Can someone send me or tell me where I can find an init script for dovecot? Thanks.

2 2

[Dovecot] login process died too early
by Adrian Roye 18 Jul '04

18 Jul '04

Hi ! I have dovecot working on a SUSE 9.0 machine. Everything works fine. When I boot, I get this message: snip............. Dovecot starting up Login process died too early-shutting down snap........... rcdovecot status : unused a rcdovecot start starts dovecot. What can I do to start dovecot when I boot up ? Adrian Roye

4 4

[Dovecot] Authentication Problems.
by Tom Ray [Lists] 18 Jul '04

18 Jul '04

Hey- I'm kinda new to Dovecot and I'm trying to do something and it seems I've hit a wall. I put together a server with Fedora Core 2, Exim 4.34, and Dovecot 0.99.10.6 and I need support mail for multiple domains so this is how I have my virtual setup: Virtual Aliases Files: /var/virtualdomains/$domain/etc/aliases Virtual Accounts Passwd File: /var/virtualdomains/$domains/etc/passwd with the following layout: user:passwd:uid:gid:Virtual User:/var/virtualdomains/domain.com/mail/user:/dev/null Virtual Mailboxes: /var/virtualdomains/$domain/mail/$user I got exim working without problem but when I tried to login via IMAP on Dovecot I'm getting 'a001 NO Authentication failed.' Now I have this setup in dovecot.conf: default_mail_env = mbox:/var/virtualdomains//%d/mail/%n/:INBOX=/var/virtualdomains/%d/mail/%n auth_userdb = passwd-file /var/virtualdomains/etc/virtpasswd It's my understanding that Dovecot can't parse out the domain name in the auth_userdb command so I modifed my setup to use just the one password file and modified it to this; user@doman.com:passwd:uid:gid:Virtual User:/var/virtualdomains/domain.com/mail/user:/dev/null Ownership/Group: -rwx------ 1 dovecot dovecot 36 Jul 13 18:41 passwd Is there a setting I have wrong, a step I'm misisng, a permission I don't know about....let me know if there is any other information you might need and I will provide it. TIA Tom Ray

2 3

[Dovecot] SSL Certificates and multiple domain names
by Daniel L. Miller 18 Jul '04

18 Jul '04

How can I have Dovecot either return a different certificate for each domain/hostname or a certificate that supports multiple names? I currently access my imap server through two different hostnames and three domain names. Daniel

4 4

[Dovecot] Testimonial
by Kenneth Porter 16 Jul '04

16 Jul '04

I just switched my main "library" of over 100 mailboxes from UW-IMAP on a gutless wonder with 600 BogoMIPS and 200 MB to a box with 2000 BogoMIPS and 1 GB, and also switched from UW-IMAP under RH7.2 to Dovecot under Fedora Core 2. Using Mulberry on Win2k as the client, it used to take several minutes to check for new mail in all folders. Now it takes just 2-3 seconds. Opening large folders with 100's of messages used to take a dozen seconds or more, and is now down to at most a second or so. IMAP is no longer frustratingly slow. Now to figure out what to do with all my spare time....

1 0

[Dovecot] can't see IMAP folders - Fedora Core 2
by Ralph Brown 15 Jul '04

15 Jul '04

Recently, I upgraded (switched) to Fedora Core 2. Previously, I was running Fedora Core 1, with Cyrus-IMAP, and life was good. Now, I can not see any of my folders. I suspect it is a simple dovecot.conf configuration edit, but i'm not experienced enough with it to make the correct edits. I am using Postfix with Dovecot. My mail directory is; /home/(user)/mail snip from the conf file; --------------------------- You can also limit a width of string by giving the number of max. characters # after the '%' character. For example %1u gives the first character of # username. Some examples: # # maildir:/var/mail/%1u/%u/Maildir # mbox:~/mail/:INBOX=/var/mail/%u # mbox:/var/mail/%d/%n/:INDEX=/var/indexes/%d/%n # #default_mail_env =/home/%u/mail ---------------------------- Thanks in advance for any suggestions. Ralph "Do what ya can...but behave yourself"

4 3

[Dovecot] POP3 fails on non-existent inbox
by Kenneth Porter 14 Jul '04

14 Jul '04

Using the latest RPM (dovecot-0.99.10.5) on Fedora Core 2. I connected to the server by POP3 for a user who'd not yet received email (ever) so she didn't have a spool file in /var/spool/mail, and dovecot was failing on login. I just tested it by removing my own mailbox and see this in maillog: pop3-login: Login: ken [127.0.0.1] pop3(ken): stat() failed with mbox file /var/spool/mail/ken: No such file or directory pop3(ken): stat() failed with mbox file /var/spool/mail/ken: No such file or directory pop3: I/O leak: 0x8050c20 (0) pop3: I/O leak: 0x8084b90 (1) pop3: Timeout leak: 0x8065d00 >From the client, I enter the USER and PASS command and get: +OK Logged in. Connection closed by foreign host.

2 6

[Dovecot] 0.99.10.7 released
by Timo Sirainen 14 Jul '04

14 Jul '04

outlook-pop3-no-nuls didn't actually work in rc1. Works now. v0.99.10.7 2004-07-14 Timo Sirainen <tss(a)iki.fi> + Added outlook-pop3-no-nuls workaround to fix Outlook hang in mails with NULs. + Config file lines can now contain quoted strings ("value ") - If client didn't finish downloading a single mail in 30 seconds, Dovecot closed the connection. This was supposed to work so that if client hasn't read data at all in 30 seconds, it's disconnected. - Maildir: LIST now doesn't skip symlinks

1 0

[Dovecot] Shared folders
by D Canfield 13 Jul '04

13 Jul '04

Several months back shared folders based on ACL's were discussed here, and it was mentioned that support for these had been added to CVS. Since the web site still says shared folders aren't implemented, I just wanted to check and see if the shared folder code is just in CVS for a future, post-1.0 release, or if the code ever made it into any of the 0.99x relases. Thanks DC

2 1

[Dovecot] FreeBSD and MySQL error
by cdmon.com 13 Jul '04

13 Jul '04

Greetings I have been installed dovecot-0.99.10.6 in my FreeBSD 4.10 with WITH_MYSQL=1 , but when I try to configure it to use mysql.conf file: auth_userdb = mysql /usr/local/etc/dovecot-mysql.conf auth_passdb = mysql /usr/local/etc/dovecot-mysql.conf the program gives me the next error: dovecot: Jul 13 10:49:03 Info: Dovecot starting up dovecot-auth: Jul 13 10:49:04 Fatal: Unknown userdb type 'mysql' dovecot: Jul 13 10:49:04 Error: Auth process died too early - shutting down dovecot: Jul 13 10:49:04 Error: child 13659 (auth) returned error 89 Somebody knows why? What I'm doing wrong? It's possible to use MySQL with dovecot in a FreeBSD? Thanks a lot in advanced. -- _____________________ http://www.cdmon.com ¿dominios a 9,95 euros? ¿servidores DNS públicos? ¿se han vuelto locos?

3 2

[Dovecot] [patch] gssapi support
by Colin Walters 13 Jul '04

13 Jul '04

Hi, I've been working on a patch for GSSAPI (Kerberos) support. It seems to work pretty well for authentication (I've tested it with Evolution, fetchmail, and mutt). I have also been working on implementing integrity/confidentiality protection. Unfortunately not many clients support this - the only one I've found really is mutt, which seems to disconnect from the server for some unknown reason not long after a Kerberos-secured conversation. I'm still trying to track that down. But anyways the patch is far along enough that I think it's worthy of review and testing. Some todo items: 0) Track down bug preventing mutt from working 1) Audit integrity proxy a bit more 2) Make sure we're handling mechanisms other than Kerberos 3) Test with more clients

4 15

[Dovecot] 0.99.10.7-rc1
by Timo Sirainen 13 Jul '04

13 Jul '04

http://dovecot.org/rc/ Yet another 0.99 release. If it works, tomorrow comes the real one: + Added outlook-pop3-no-nuls workaround to fix Outlook hang in mails with NULs. + Config file lines can now contain quoted strings ("value ") - If client didn't finish downloading a single mail in 30 seconds, Dovecot closed the connection. This was supposed to work so that if client hasn't read data at all in 30 seconds, it's disconnected. - Maildir: LIST now doesn't skip symlinks Strange that I heard about the 30sec bug yesterday for the first time. It's been there forever. Guess people have fast internet connections nowadays :)

2 4

[Dovecot] postfix patch does not compile on freebsd 4
by Kevin 13 Jul '04

13 Jul '04

i'm trying to use timo's postfix-2.1.2-dovecot-auth.patch on freebsd4 with postfix-2.1.4 the problem is that smtpd_sasl_glue.c tries to include stdint.h which isn't present with fbsd4. is there another lib that'll provide the same functionality? i've tried using inttypes.h but i don't know of any other similar ones stdint is in fbsd5 apparently but i'm still scared of it have any ideas?

2 1

Re: [Dovecot] ldap auth problems
by Karl Latiss 13 Jul '04

13 Jul '04

That didn't seem to help either. In the end I re-compiled the Fedora Core 2 release from SRC RPM and that seems to be working. I'm not sure what the difference is. On Wed, 2004-07-07 at 18:42, Timo Sirainen wrote: > On Mon, 2004-07-05 at 12:17, Karl Latiss wrote: > > [pid 24674] close(8 <unfinished ...> > > [pid 24674] <... close resumed> ) = 0 > > [pid 24674] --- SIGSEGV (Segmentation fault) @ 0 (0) --- > > Process 24674 detached > .. > > Hmm. Doesn't really help. Getting gdb backtrace would show where it > crashes, but I'm not sure if there's any easy way to do it. > > One would be to put sleep(10); to beginning of src/auth/main.c, then > start dovecot and "gdb /usr/local/libexec/dovecot/dovecot-auth pid" > where pid being the running dovecot-auth's process id. then "c" to > continue, wait for crash and "bt" to get backtrace.

1 0

[Dovecot] mailbox problem
by Jean-Francois Theroux 12 Jul '04

12 Jul '04

Hi guys, I use a virtual mailbox setup with dovecot/postfix. Which reside under /virtual. I get an error message which doesn't return anything interesting in Google. I get this: imap(user(a)domain.com): File isn't in mbox format: /virtual/domain.com/user/imapd/Trash I have no idea on how to fix this. I seem to be able to delete messages though. But I'd like to repair this, since I like to have clean logs ;) Thanks for your time, -- Jean-Francois Theroux Systems administrator 514.726.3732 PrivalODC http://www.privalodc.comp

2 1

[Dovecot] 1.0-test28
by Timo Sirainen 12 Jul '04

12 Jul '04

http://dovecot.org/test/ - Fixed some crashes with cache file. THREAD and SORT especially crashed it. - Fixed the SSL infinite looping in login processes - Recent flags are working again with maildir. Almost with mbox too. - Maildir code moves mail into cur/ directory directly if the mail contains flags, so we don't violate maildir spec anymore by placing them into new/ with the flags. Although.. now that I think about it, that breaks recent flags, as only mails in new/ are treated as being recent.. Well, I guess next version implements my another idea for it: Store flags only into index and keep the file in new/, flags will be added when the file is moved to cur/. Non-Dovecot MUAs don't see the flags in the mean time though. - SIGHUPing dovecot master process finally reloads configuration completely and without crashing - Added --exec-mail parameter to dovecot. It can be used to launch imap/pop3 processes with configuration from dovecot.conf - Changed client_workarounds to imap_client_workarounds and pop3_client_workarounds. Added the first pop3 workaround: outlook-no-nuls

1 0

[Dovecot] Debian woody backport of 0.99.10.6 now available on backports.org
by Jaldhar H. Vyas 10 Jul '04

10 Jul '04

Well, the backports.org people finally installed my backport of the latest stable version of dovecot. Please remove the Braincells apt source form /etc/apt/sources.list and add these lines instead. deb http://www.backports.org/debian stable dovecot openldap2 postgresql openssl deb-src http://www.backports.org/debian stable dovecot (If you are using other backports you can merge dovecot etc. into an existing line.) I have also updated the wiki. If there are any other places which mention the old location, please change them. -- Jaldhar H. Vyas <jaldhar(a)debian.org> La Salle Debain - http://www.braincells.com/debian/

1 1

[Dovecot] NUL characters in POP3 conversation cause Outlook to hang
by Matthew Reimer 10 Jul '04

10 Jul '04

We're being bitten an Outlook bug [1,2] that is triggered by a NUL character in a message being sent through POP3. I see that dovecot's imap implementation converts 0x00 to 0x80, but this conversion is not done for POP3. Would it be possible to add an option to do this mapping for POP3 as well? Matt [1] http://xforce.iss.net/xforce/xfdb/15859 [2] http://www.derkeiler.com/Mailing-Lists/NT-Bugtraq/2004-04/0014.html

2 1

[Dovecot] pop3 usernames
by Vlad Mazek 10 Jul '04

10 Jul '04

Hello, I would like to allow users to login as user(a)domain.tld instead of providing their login name; I'm coming from the sendmail/qpopper land and am trying to migrate to postfix/maildir/dovecot one step at a time and I've been able to find a way to do most of what I want except for the above requirement. Do I have to use a SQL server or is there any way to easilly map an email address to a mailbox or even a maildir? Thank you. -Vlad

2 1

[Dovecot] permission problem ??
by Joachim Dostal 09 Jul '04

09 Jul '04

version dovecot-1.0-test27: Jul 9 21:49:07 server dovecot: IMAP(testtest): mprotect() failed with index file /home/testtest/mail/.imap/INBOX/dovecot.index: Permission denied with version 0.99.10.6 i have no such troubles ... ? tx4hlp, joachim

2 3

[Dovecot] Re : Permission denied
by Frédéric Sapin 09 Jul '04

09 Jul '04

Hello Timo, I'm using linux Fedora Core 2. The permissions are : drwxrwxrwt 2 root mail 32 2004-06-16 04:45 /var/spool/mail/ These permissions are made buy the command chmod a+rwxt /var/spool/mail. So if someone wants to erase the /var/spool/mail directory, it's possible unfortunately. If there are theses permissions the user can receive his mails but it's dangerous I think. And if I modify the dovecot.conf file : mail_extra_groups = mail and if the permissions are the initial permission, and if I enter chmod +t /var/spool/mail the user can't receive his mail. Thanks Frederic

4 6

[Dovecot] bug in openssl proxy code (1.0-test24) ?
by Andrey Panin 09 Jul '04

09 Jul '04

Hi all, If client connects to pop3 server, issues STLS command and then drops connection dovecot starts flooding syslog with this message repeated endlessly: Jul 9 14:31:40 smtp dovecot: pop3-login: SSL_accept() syscall failed: EOF [80.254.111.9] Best regards. -- Andrey Panin | Linux and UNIX system administrator pazke(a)donpac.ru | PGP key: wwwkeys.pgp.net

2 3

[Dovecot] passing remote ip to pam
by dean gaudet 09 Jul '04

09 Jul '04

to improve forensic log info i want to set the PAM_RHOST value to the remote ip (which pam logs as rhost=foo in failure messages). i didn't look to see if anything has been done in this way on CVS because i'm still on 0.99.10.6. below is a bit of a hack. in some sense the remote_ip might make more sense in the AUTH_LOGIN_REQUEST_NEW packet rather than the continue packet... but that looked like i'd have to change more code :) btw -- is there anything which stops mech_plain_auth_continue from doing a somewhat unbounded pstrdup if you send "a\0b" for the auth string? -dean diff -rpu dovecot-0.99.10.6.deborig/debian/changelog dovecot-0.99.10.6/debian/changelog --- dovecot-0.99.10.6.deborig/debian/changelog 2004-07-08 18:11:55.000000000 -0700 +++ dovecot-0.99.10.6/debian/changelog 2004-07-08 18:34:40.000000000 -0700 @@ -1,3 +1,9 @@ +dovecot (0.99.10.6-3.dg1) unstable; urgency=low + + * hack a solution to pass PAM_RHOST the remote ip + + -- dean gaudet <dean(a)arctic.org> Thu, 8 Jul 2004 18:34:26 -0700 + dovecot (0.99.10.6-3) unstable; urgency=low * Patched so dovecot follows symlinks to directories again. diff -rpu dovecot-0.99.10.6.deborig/src/auth/auth-login-interface.h dovecot-0.99.10.6/src/auth/auth-login-interface.h --- dovecot-0.99.10.6.deborig/src/auth/auth-login-interface.h 2003-05-18 05:26:28.000000000 -0700 +++ dovecot-0.99.10.6/src/auth/auth-login-interface.h 2004-07-08 18:32:22.000000000 -0700 @@ -1,6 +1,8 @@ #ifndef __AUTH_LOGIN_INTERFACE_H #define __AUTH_LOGIN_INTERFACE_H +#include "network.h" + /* max. size for auth_login_request_continue.data[] */ #define AUTH_LOGIN_MAX_REQUEST_DATA_SIZE 4096 @@ -57,6 +59,8 @@ struct auth_login_request_continue { enum auth_login_request_type type; /* AUTH_LOGIN_REQUEST_CONTINUE */ unsigned int id; + struct ip_addr remote_ip; + size_t data_size; /* unsigned char data[]; */ }; diff -rpu dovecot-0.99.10.6.deborig/src/auth/mech-plain.c dovecot-0.99.10.6/src/auth/mech-plain.c --- dovecot-0.99.10.6.deborig/src/auth/mech-plain.c 2003-05-18 05:26:28.000000000 -0700 +++ dovecot-0.99.10.6/src/auth/mech-plain.c 2004-07-08 18:25:14.000000000 -0700 @@ -21,6 +21,7 @@ mech_plain_auth_continue(struct auth_req size_t i, count, len; auth_request->callback = callback; + auth_request->remote_ip = request->remote_ip; /* authorization ID \0 authentication ID \0 pass. we'll ignore authorization ID for now. */ diff -rpu dovecot-0.99.10.6.deborig/src/auth/mech.h dovecot-0.99.10.6/src/auth/mech.h --- dovecot-0.99.10.6.deborig/src/auth/mech.h 2003-05-18 05:26:28.000000000 -0700 +++ dovecot-0.99.10.6/src/auth/mech.h 2004-07-08 18:31:42.000000000 -0700 @@ -1,6 +1,7 @@ #ifndef __MECH_H #define __MECH_H +#include "network.h" #include "auth-login-interface.h" struct login_connection; @@ -11,6 +12,7 @@ typedef void mech_callback_t(struct auth struct auth_request { pool_t pool; char *user; + struct ip_addr remote_ip; struct login_connection *conn; unsigned int id; diff -rpu dovecot-0.99.10.6.deborig/src/auth/passdb-pam.c dovecot-0.99.10.6/src/auth/passdb-pam.c --- dovecot-0.99.10.6.deborig/src/auth/passdb-pam.c 2003-11-08 06:17:51.000000000 -0800 +++ dovecot-0.99.10.6/src/auth/passdb-pam.c 2004-07-08 18:32:52.000000000 -0700 @@ -166,13 +166,23 @@ static int pam_userpass_conv(int num_msg return PAM_SUCCESS; } -static int pam_auth(pam_handle_t *pamh, const char *user, const char **error) +static int pam_auth(pam_handle_t *pamh, const char *user, + const struct ip_addr *remote_ip, const char **error) { void *item; int status; + const char *addr; *error = NULL; + if ((addr = net_ip2addr(remote_ip)) + && (status = pam_set_item(pamh, PAM_RHOST, addr)) + != PAM_SUCCESS) { + *error = t_strdup_printf("pam_set_item(PAM_RHOST, %s) failed: %s", + addr, pam_strerror(pamh, status)); + return status; + } + if ((status = pam_authenticate(pamh, 0)) != PAM_SUCCESS) { *error = t_strdup_printf("pam_authenticate(%s) failed: %s", user, pam_strerror(pamh, status)); @@ -205,7 +215,8 @@ static int pam_auth(pam_handle_t *pamh, static void pam_verify_plain_child(const char *service, const char *user, - const char *password, int fd) + const char *password, const struct ip_addr *remote_ip, + int fd) { pam_handle_t *pamh; struct pam_userpass userpass; @@ -228,7 +239,7 @@ pam_verify_plain_child(const char *servi str = t_strdup_printf("pam_start(%s) failed: %s", user, pam_strerror(pamh, status)); } else { - status = pam_auth(pamh, user, &str); + status = pam_auth(pamh, user, remote_ip, &str); if ((status2 = pam_end(pamh, status)) == PAM_SUCCESS) { /* FIXME: check for PASSDB_RESULT_UNKNOWN_USER somehow? */ @@ -353,7 +364,7 @@ pam_verify_plain(struct auth_request *re if (pid == 0) { (void)close(fd[0]); - pam_verify_plain_child(service, request->user, password, fd[1]); + pam_verify_plain_child(service, request->user, password, &request->remote_ip, fd[1]); _exit(0); } diff -rpu dovecot-0.99.10.6.deborig/src/imap-login/client-authenticate.c dovecot-0.99.10.6/src/imap-login/client-authenticate.c --- dovecot-0.99.10.6.deborig/src/imap-login/client-authenticate.c 2003-11-24 11:50:55.000000000 -0800 +++ dovecot-0.99.10.6/src/imap-login/client-authenticate.c 2004-07-08 18:21:19.000000000 -0700 @@ -140,7 +140,7 @@ static void login_callback(struct auth_r case 0: /* continue */ ptr = buffer_get_data(client->plain_login, &size); - auth_continue_request(request, ptr, size); + auth_continue_request(request, ptr, size, &client->common.ip); buffer_set_used_size(client->plain_login, 0); break; @@ -270,7 +270,8 @@ static void client_auth_input(void *cont } else { auth_continue_request(client->common.auth_request, buffer_get_data(buf, NULL), - buffer_get_used_size(buf)); + buffer_get_used_size(buf), + &client->common.ip); } /* clear sensitive data */ diff -rpu dovecot-0.99.10.6.deborig/src/login-common/auth-connection.c dovecot-0.99.10.6/src/login-common/auth-connection.c --- dovecot-0.99.10.6.deborig/src/login-common/auth-connection.c 2003-05-26 08:27:13.000000000 -0700 +++ dovecot-0.99.10.6/src/login-common/auth-connection.c 2004-07-08 18:33:38.000000000 -0700 @@ -335,13 +335,21 @@ int auth_init_request(enum auth_mech mec } void auth_continue_request(struct auth_request *request, - const unsigned char *data, size_t data_size) + const unsigned char *data, size_t data_size, + const struct ip_addr *remote_ip) { struct auth_login_request_continue auth_request; /* send continued request to auth */ auth_request.type = AUTH_LOGIN_REQUEST_CONTINUE; auth_request.id = request->id; + if (remote_ip) { + auth_request.remote_ip = *remote_ip; + } + else { + memset(&auth_request.remote_ip, + 0, sizeof(auth_request.remote_ip)); + } auth_request.data_size = data_size; if (o_stream_send(request->conn->output, &auth_request, diff -rpu dovecot-0.99.10.6.deborig/src/login-common/auth-connection.h dovecot-0.99.10.6/src/login-common/auth-connection.h --- dovecot-0.99.10.6.deborig/src/login-common/auth-connection.h 2003-02-09 23:56:23.000000000 -0800 +++ dovecot-0.99.10.6/src/login-common/auth-connection.h 2004-07-08 18:20:58.000000000 -0700 @@ -48,7 +48,8 @@ int auth_init_request(enum auth_mech mec const char **error); void auth_continue_request(struct auth_request *request, - const unsigned char *data, size_t data_size); + const unsigned char *data, size_t data_size, + const struct ip_addr *remote_ip); void auth_abort_request(struct auth_request *request); diff -rpu dovecot-0.99.10.6.deborig/src/pop3-login/client-authenticate.c dovecot-0.99.10.6/src/pop3-login/client-authenticate.c --- dovecot-0.99.10.6.deborig/src/pop3-login/client-authenticate.c 2003-11-24 11:52:09.000000000 -0800 +++ dovecot-0.99.10.6/src/pop3-login/client-authenticate.c 2004-07-08 18:21:32.000000000 -0700 @@ -141,7 +141,7 @@ static void login_callback(struct auth_r case 0: ptr = buffer_get_data(client->plain_login, &size); - auth_continue_request(request, ptr, size); + auth_continue_request(request, ptr, size, &client->common.ip); buffer_set_used_size(client->plain_login, 0); break; @@ -259,7 +259,8 @@ static void client_auth_input(void *cont } else { auth_continue_request(client->common.auth_request, buffer_get_data(buf, NULL), - buffer_get_used_size(buf)); + buffer_get_used_size(buf), + &client->common.ip); } /* clear sensitive data */

2 1

[Dovecot] Permission denied
by Frédéric Sapin 09 Jul '04

09 Jul '04

Hello all, I'm a new user of dovecot and I've got a permission denied problem. I've read the VarMailDotLock wiki paper but there is still a security problem. If I enter : chmod a+rwxt /var/spool/mail it works but I think it's very dangerous to have thaht rights. So I've tried to edit the dovecot.conf file and to change the mail_extra_groups = mail and to change the rights : chmod +t /var/spool/mail but it doesn't work ! The mails are in /var/spool/mail/unix_user_name Could you please help me to configure the /var/spool/mail to have a good security and to allow people to receive their mails ? Thanks Frederic

2 1

[Dovecot] a yum install with mysql support??
by alex＠alution.com 09 Jul '04

09 Jul '04

Hello, Well im guessing i have already answered this question myself. Im using FC1 and installed dovecot the easy way (yum install dovecot) It has stated that it installed version 0.99.10.5 and from what I have looked at in the mailing list archives, this version SHOULD have mysql authentication support. However what I don´t know is if by installing the yum package it will allow this support. Im guessing that I will have to install it the real way, as if I take a look in the logs, it states... ============== dovecot-auth: "Jul 09 00:37:38 "Fatal: Unknown userdb type 'mysql' dovecot: "Jul 09 00:37:38 "Error: Auth process died too early - shutting down dovecot: "Jul 09 00:37:38 "Error: child 31532 (auth) returned error 89 ============== Am i correct in thinking this? Or is there something else a miss?? Thanks Alex

1 0

Re: [Dovecot] 1.0-test26
by Matthew Reimer 09 Jul '04

09 Jul '04

Timo Sirainen wrote: > On 9.7.2004, at 00:57, Mark E. Mallett wrote: > >> On Fri, Jul 09, 2004 at 12:34:04AM +0300, Timo Sirainen wrote: >> >>> http://dovecot.org/test/ >>> >>> - Fixed APPEND hanging if the whole message was sent in one TCP packet >>> (ie. fixes the "Sent mail" hangs) >> >> >> Curious-- how does the application-level code care about TCP packets? > > > It reads all of it into buffer, then later tries to read more even > though everything was already in that buffer so it gets stuck at > waiting. Dovecot's istream-limit wrapper stream specifically was a > problem. It called parent stream's read() function without checking > first if there was already data in it's buffer. > > These wrapper streams have been quite difficult in general. mbox support > is implemented using one of those too and it took quite a while to get > it working correctly. I guess I should write some comments there how > exactly they should be implemented. Is this a problem in 0.99 as well? Matt

2 1

[Dovecot] 1.0-test26
by Timo Sirainen 09 Jul '04

09 Jul '04

http://dovecot.org/test/ - Fixed APPEND hanging if the whole message was sent in one TCP packet (ie. fixes the "Sent mail" hangs) - Some changes in MySQL defaults - Working APOP auth - Fixes/improvements for cache file code. Still isn't as smart as it could, but it seems to work again. The code is nearing a state where plugins could add their own data into cache file.

2 3

Re: [Dovecot] Logging "issue" with PAM authentication
by Steve Johnson 07 Jul '04

07 Jul '04

Great, thanks a lot, solved the problem. No more annoying logs every 2-5 seconds :) Steve Johnson On Wed, 2004-07-07 at 14:39, Ray Miller wrote: > On Wed, Jul 07, 2004 at 02:21:04PM -0400, Steve Johnson wrote: > > > > I've tried with just the following: > > > > auth sufficient /lib/security/$ISA/pam_ldap.so use_first_pass > > password sufficient /lib/security/$ISA/pam_ldap.so use_authtok > > session optional /lib/security/$ISA/pam_ldap.so > > [...] > > In both of these situations, users can't authenticate. Is there > > something I'm doing wrong? I'm not that familiar with pam, so it's a > > very plausible cause! :) > > I'm fairly sure you don't need the password line, but that's not > likely to be causing your problem - more likely it's the use_first_pass > option. Try: > > auth required /lib/security/$ISA/pam_ldap.so > account required /lib/security/$ISA/pam_ldap.so > password required /lib/security/$ISA/pam_deny.so > session required /lib/security/$ISA/pam_ldap.so

1 0

[Dovecot] Peer Config Review
by Eric Kahklen 07 Jul '04

07 Jul '04

I am trying to setup a mail server using Postfix and Squirrelmail. The mail server will ONLY use webmail for access. I will not be using any email clients other than Squirrelmail. I've got the server working in a testing environment. Could people who are dovecot savy look over the config I have set? I've only included the directives that are enabled with no comments. I want a simple but secure backup mail server for about 75 users. Thank you, Eric base_dir = /var/run/dovecot/ protocols = imap login_dir = /var/run/dovecot/login login = imap login_executable = /usr/libexec/dovecot/imap-login mbox_locks = fcntl imap_executable = /usr/libexec/dovecot/imap imap_modules = /usr/lib/dovecot/imap auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = pam auth_executable = /usr/libexec/dovecot/dovecot-auth auth_user = root --

1 0

[Dovecot] Logging "issue" with PAM authentication
by Steve Johnson 07 Jul '04

07 Jul '04

Hi, We currently have a postfix/dovecot setup using nss_ldap with PAM for authentication. Everything is working fine, but there are excessive "error" messages in /var/log/messages that I'd like to prevent from happening. Since auth_userdb defaults to passwd and that our users are not in the passwd file, we get the following message everytime a user logs in: Jul 7 13:34:37 hostname dovecot(pam_unix)[32206]: check pass; user unknown Jul 7 13:34:37 hostname dovecot(pam_unix)[32206]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= We of course also get the input that a user has logged in, in /var/log/maillog: imap-login: Jul 07 13:34:37 Info: Login: username [xxx.xxx.xxx.xxx] I've tried changing auth_verbose to no, and I still get those messages. Is there any way to prevent this from happening? Thanks a lot, Steve Johnson

2 2

[Dovecot] mbox:~/%u-mail/
by justin 07 Jul '04

07 Jul '04

Is it possible to use something like: default_mail_env = mbox:~/%u-mail/:INBOX=/var/mail/%u such that for a user: user1 with a home directory: /home/share the imap files would then be stored in: /home/share/user1-mail/ ???

2 1

[Dovecot] UID Error on Test 24 and 25
by Doug Eubanks 07 Jul '04

07 Jul '04

I started testing Dovecot 1.0 Test 22! I loved the performance improvements, althought dovecot has been very fast for us from the beginning. However, now I am testing test 24 and 25, and I am seeing these errors in the dovecot log and squirrelmail is giving me a ERROR : Connection dropped by imap-server. Query: STATUS "Mailing Lists.SpamAssassin" (MESSAGES UNSEEN RECENT) This is the dovecot error from the log file dovecot: Jul 07 08:52:33 Info: imap-login: Login: admin [208.*.*.*] dovecot: Jul 07 08:52:33 Error: IMAP(admin): file mail-index-view.c: line 286 (_view_lookup_uid_range): assertion failed: (first_uid > 0) dovecot: Jul 07 08:52:33 Error: child 12469 (imap) killed with signal 6 The user I am loggin in with has a uid and gid of 501, not 0! I am using passwd and shadow auth with Maildirs. If anyone has any pointers, they would greatly be appreciated. Sincerely, Doug Eubanks doug(a)simflex.com Post Hoc, Ergo Propter Hoc *** DISCLAIMER *** This e-mail and any attachments thereto may contain information, which is confidential and/or protected by intellectual property rights and are intended for the sole use of the recipient(s) named above. Any use of the information contained herein (including, but not limited to, total or partial reproduction, communication or distribution in any form) by persons other than the designated recipient(s) is prohibited. If you have received this e-mail in error, please notify the sender either by telephone or by e-mail and delete the material from any computer. Thank you for your cooperation.

2 1

[Dovecot] 1.0-test25 with new cache file code
by Timo Sirainen 07 Jul '04

07 Jul '04

http://dovecot.org/test/ Pretty much the only change since test24 is a redesign of how cache file writing works. Reading works as before - without locks. Before (in 1.0-tests, 0.99 was worse) we used to just try to lock it. If it failed, we just didn't update cache. If it didn't fail, the lock could have been kept a long time. For example if a user was downloading a 10MB mail, the lock could have been kept the whole time and no-one else could have modified the cache. The old behaviour wasn't actually too bad, as normally it didn't matter if something couldn't be written to cache. It would have been the next time, all it did was cost some I/O. The new behaviour is more reliable as the locks are kept only a very short time. It works by first writing the updates only into internal 32kB buffer. Once the buffer gets full, or the transaction completes, it's written to disk. When buffer gets full, space is reserved from the cache file for the current transaction. The amount of space is more than is needed for writing the internal buffer, so we don't have to lock the cache file every time the buffer gets full (and so we don't need a huge buffer). Once transaction completes, we lock the cache again and try to free the extra reserved space we have left. If multiple processes weren't updating the cache file at the same time, the freeing should be as simple as decreasing "used_file_size" field in header. Alternatively we'll update a linked list of "holes" in the file. When reserving space, we first try to use those holes instead of appending to end of file. Pointers to new cache records are also written to transaction log at the end of cache transaction. They'll get written to index at next sync after which they become visible to other processes. Each cache record contains a pointer to previous record, so there can be multiple cache records for a single message. The bad thing with the new logic is that nothing prevents two processes from writing the same cache records and so using twice as much space as necessary. But I don't think it's much of a problem. They'll go away at next cache compression. These changes also make it quite simple to make cache file work with shared filesystems. I'd just need to implement some kind of internal caching buffer which remembers what parts of file are read into memory. These changes also make it possible to easily and reliably store X-UIDL headers into cache file, where the POP3 UIDL command could quickly get them. Not in this release yet, though..

3 2

[Dovecot] appenduid?
by Johannes Berg 06 Jul '04

06 Jul '04

Hi, Does dovecot support APPENDUID? If not, would it be possible to add? johannes

2 1

Re: [Dovecot] [PATCH, RFC] add APOP authentication mechanism
by Timo Sirainen 06 Jul '04

06 Jul '04

On 1.7.2004, at 16:26, Andrey Panin wrote: >> + if (strcmp(auth_request->protocol, "POP3")) { >> + if (verbose) >> + i_info("apop(%s): wrong protocol %s", >> get_log_prefix(auth_request), >> + auth_request->protocol); >> + mech_auth_finish(auth_request, NULL, 0, FALSE); >> + return TRUE; >> + } >> >> I don't think there's really any point in checking this? Maybe someone >> really wants to use APOP with another protocol :) > > This will be RFC violation isn't it ? (I'll send a public reply, the last question could need input from others) Well, it's not compatible with any RFC of course, but I don't think it would violate anything? I'd just rather like to avoid unnecessary code bloat. Well, except now that I thought about the logic instead of just the code, there are problems. APOP prevents replay attacks by sending different timestamp in greeting, but you're sending the greeting to dovecot-auth as user input to APOP authentication mechanism. So, a user could simply say "AUTH APOP" and send wanted timestamp as input. One way to fix this would be to disallow APOP mechanism to be used with AUTH command in pop3-login and require that the request was done with POP3 protocol. But I think that's pretty ugly kludge. It also requires that processes connecting to dovecot-auth are trusted, which is something I've tried to avoid as much as possible. So dovecot-auth doesn't really know if it's pop3-login which connects to it.. Better fix would be to get part of the timestamp from dovecot-auth itself. It could send a growing ID number as handshake which would be used as part of the timestamp, and APOP mechanism processing would check that timestamp really contains the ID. So timestamp would be <authid.unixtime@hostname>. That also makes the PID go away, which was another thing I would have suggested. POP3 RFC also says: It is conjectured that use of the APOP command provides origin identification and replay protection for a POP3 session. Accordingly, a POP3 server which implements both the PASS and APOP commands should not allow both methods of access for a given user; that is, for a given mailbox name, either the USER/PASS command sequence or the APOP command is allowed, but not both. But I don't know if there's any nice way to do it, except perhaps by defining APOP password scheme which would actually be plaintext but wouldn't work with anything but APOP authentication. Do any other servers prevent it either?

2 5

[Dovecot] Debian dovecot news
by Jaldhar H. Vyas 04 Jul '04

04 Jul '04

I uploaded 0.99.10.6 to sid. Owing to the importance of the dot lock fix, I've tried to have this pushed to sarge quickly. Let's see how that goes. I've prepared a backport of 0.99.10.6 to woody which should be showing up on www.backports.org soon hopefully. In the meantime, if you desperately need it and don't mind working out dependencies yourself, you can find it at http://www.braincells.com/backports/ I uploaded 1.0test18 to http://src.braincells.com/dovecot-test/ (I'll do test20 tomorrow) I told Timo I'd port dovecot's gnutls support from gnutls7 to gnutls10 but I have absolutely no time for it so if someone would volunteer, contact me, I'd really appreciate it. -- Jaldhar H. Vyas <jaldhar(a)debian.org> La Salle Debain - http://www.braincells.com/debian/

4 7

[Dovecot] index file regeneration?
by Paul Reilly 02 Jul '04

02 Jul '04

Quick question: How does dovecot keep the message headers index file updated? Eg: if my MDA delivers an extra 10 messages while I'm logged in. How does the message index get updated? At what points is it regenerated? Thanks, Paul

2 7

[Dovecot] 1.0-test24 and some mbox benchmarking
by Timo Sirainen 02 Jul '04

02 Jul '04

http://dovecot.org/test/ Again only mbox fixes. I found some more bugs which could have also caused some of the mbox problems that people reported. They were found when I today thought I'd again do a bit of testing with my favourite 1.4GB mbox. Then I thought I might as well see how it compares against UW-IMAP. First a bit of explanations how they work internally: Dovecot 1.0-test24 ------------------ Dovecot works by trying to do everything in one "sync" function. It reads new mails, inserts missing headers, writes header modifications and expunges messages. Dovecot leaves 100 bytes of padding in every mail's headers, which it can use to avoid moving the rest of the file forward when it needs to insert space. However, if there's not enough space (and with new mails there isn't), it needs to do the moving. Moving is done by first reading messages and counting how many bytes we're short. Once we've seen enough padding we'll rewrite those messages. If we read until end of file, we'll grow the file and rewrite the messages. Rewriting is made backwards, so we don't have to do much buffering, and in case the rewriting gets interrupted (crash, power loss, etc.) the data loss is very small, a few kilobytes maximum. UW-IMAP 2004 ------------ UW-IMAP first only reads the mbox with SELECT, rewrite is only triggered by LOGOUT, EXPUNGE and CHECK commands. UW-IMAP also inserts padding, but less than Dovecot. It tries to get added headers to fit into 50 bytes, and what's not used is left as padding. Normally this seems to get it around 15-20 bytes of padding. Perhaps I should shrink it from Dovecot too. Rewriting works by reading the file forward into buffer and writing the changes as needed. This is quite fast, but it means the buffer can grow large, and if the rewrite gets interrupted everything in the buffer gets lost. In my test mbox this would have been 23MB of lost data, but normally much less. Benchmarks ---------- I simply rewrote a 1.4GB mbox containing 361052 mails, Linux kernel mailing list archives from years 96-02. Computer is Athlon XP 2700+ with 1GB of memory. reads/writes were counted using Linux's iostat command. Nothing else was being used in that partition, so the numbers should be accurate. Except UW-IMAP's read count is a few blocks too much because I got tired of waiting it and started looking into the mbox to see how far it had gotten. Read counts could also be somewhat wrong if some of the mbox was already in buffer cache. I tried to trash it anyway by catting 2x4GB of data into /dev/null. Kernel used around 900MB of memory for caching. Total CPU times may also be a bit off, as the computer was being used at the same time. Dovecot 1.0-test24 ------------------ reads : 4007432 blocks = 1956 MB writes: 2947381 blocks = 1439 MB original mbox : 1420611590 B = 2774632 blocks = 1354 MB rewritten mbox: 1472684487 B = 2876336 blocks = 1404 MB indexes : 14452732 B = 28227 blocks = 14 MB 7221164 dovecot.index 10436 dovecot.index.cache 7221132 dovecot.index.log (this will be truncated after a while) - 16064 VSZ, 8012 RSS after SELECT completed - 14MB is mmaped index files - 216kB heap left of which 70kB actually in use - heap usage was 25MB VSZ/RSS constantly while syncing, but allocations were so large that libc used anonymous mmap()s so they got dropped after sync - VSZ peaked at 32MB, most likely because index file(s) were temporarily being mmap()ed more than once - 63.37s user - 16.56s system - 24% cpu - 5:22.75 total UW-IMAP 2004 ------------ Reading: - memory: 70044 VSZ, 67724 RSS - CPU: 7s user, 53s total Totally: reads : 5549640 blocks = 2709 MB writes: 2875581 blocks = 1404 MB original mbox : 1420611590 B = 2774632 blocks = 1354 MB rewritten mbox: 1444411190 B = 2821115 blocks = 1377 MB - 93416 VSZ, 91120 RSS - 2295.81s user - 23.99s system - 96% cpu - 39:57.90 total Notes ----- Not counting Dovecot's indexes UW-IMAP wrote 21MB less. But Dovecot wrote 27MB more padding, so just by shrinking it Dovecot would have written 6MB less data. Also because Dovecot writes the file backwards, it needs to do some extra jumping around and overlapping writes, but I guess OS nicely merged them. I'm not exactly sure why UW-IMAP uses so much CPU for rewriting, but it does and so Dovecot is over 7x faster in total (with 36x less CPU). Dovecot should also support delaying the rewrite. This is mostly useful for POP3 clients which deletes all the mail at logout, so they won't need the rewriting at all. Dovecot also writes all flag changes to disk immediately while UW-IMAP leaves it later to do more at once. That results in less total I/O as well.

1 0

[Dovecot] 1.0-test22 - maildir fixed?
by Timo Sirainen 02 Jul '04

02 Jul '04

http://dovecot.org/test/ Well, remember when I said: > Here you go, maildir syncing problems finally fixed (I hope). Well, > except there's this "new-dir-only syncing" optimization which I'm not > really sure if it works as it should. Just before I found the expunge bug in index, I was trying to fix the new-dir-only syncing because the code looked wrong. Then I figured out the indexing problem and thought maybe this one wasn't broken after all, and then forgot about it. Finally after lots of debugging, I came to same conclusion again. The code was wrong, and cause of the remaining "Maildir sync: UID < next_uid (312 < 3)" errors. So, please try and see if you still can break this release. Other changes include some crashfixes for cache file and fix for mbox which kept constantly rewriting headers for \recent messages if we had selected the mailbox as read-only (EXAMINE, STATUS).

11 30

[Dovecot] building dovecot 1.0 test19 over fc1
by Luis Miguel Cruz 02 Jul '04

02 Jul '04

[root@fc1-devel tmp]# rpmbuild -ta dovecot-1.0-test19.tar.gz error: line 7: Illegal char '-' in version: Version: 1.0-test19 Seems to be an error into the .spec file I am not sure. I will check it. Did anyone get this problem in the past? Thanks.

2 1

[Dovecot] 1.0-test23 and caching decisions
by Timo Sirainen 30 Jun '04

30 Jun '04

http://dovecot.org/test/ mbox fixes mostly. Began some other things, but none of them actually work yet: - Use X-UIDL header in mboxes for POP3 UIDL list - Cache file compression - Some cleverness for cache file for figuring out what to cache Well, I might as well explain the last one now. Users can be divided to three groups: 1. Most users will use only a single IMAP client which caches everything locally. For these users it's quite pointless to do any kind of caching as it only wastes disk space. That might also mean more disk I/O. 2. Some users use multiple IMAP clients which cache everything locally. These could benefit from caching until all clients have fetched the data. After that it's useless. 3. Some clients don't do permanent local caching at all. For example Pine and webmails. These clients would benefit from caching everything. Some locally caching clients might also access some data from server again, such as when searching messages. They could benefit from caching only these fields. After thinking about these a while, I figured out that people who care about performance most will be using the upcoming Dovecot LDA anyway which updates the indexes/cache immediately. In that case even the first user group would benefit from caching the same way as second group. LDA reads the mail anyway, so it might as well extract some information about it and store them into cache. So, group 1. and 2. could be optimally implemented by keeping things cached only for a while. I thought a week would be good. When cache file is compressed, everything older than week will be dropped. But how to figure out if user is in group 3? One quite easy rule would be to see if client is accessing messages older than a week. But with only that rule we might have already dropped useful cached data. It's not very nice if we have to read and cache it twice. Most locally caching clients always fetch new messages (all but body) when they see them. They fetch them in ascending order. Noncaching clients might fetch messages in pretty much any order, as they usually don't fetch everything they can, only what's visible in screen. Some will use server side sorting/threading which also makes messages to be fetched in random order. Second rule would then be that if a session doesn't fetch messages in ascending order, the fetched field type will be permanently cached. So, we have three caching decisions: 1. Don't cache: Clients have never wanted the field 2. Cache temporarily: Clients want this only once 3. Cache permanently: Clients want this more than once Different mailboxes have different decisions. Different fields have different decisions. There are some problems, such as if a client accesses message older than a week, we can't know if user just started using a new client which is just filling it's local cache for the first time. Or it might be a client user hasn't just used for over a week. In these cases we shouldn't have marked the field to be permanently cached. User might also switch clients from non-caching to caching. So we should re-evaluate our caching decisions from time to time. This is done by checking the above rules constantly and marking when was the last time the decision was right. If decision hasn't matched for two months, it's changed. I picked two months because people go to at least one month vacations where they might still be reading mails, but with different clients.

1 0

[Dovecot] Locked index file
by Kevin Cramer 30 Jun '04

30 Jun '04

I have docevot 0.99.10.6 installed on OpenBSD 3.5 and I'm using it with Squirrelmail. I tried to empty my Trash folder and it timed out. It looks like the process or thread died but the lock wasn't removed: Jun 25 09:16:30 plato imap(kevin): Timeout while waiting for release of shared fcntl() lock for index file /home/kevin/Maildir/.Trash/.imap.index How can I free this lock? I have tried stopping and re-starting dovecot already but that didn't help. Also, is there something I should do to prevent this in the future? The OpenBSD package sets the default locking to fcntl for mbox. I'm not sure if that is the setting that also controls the locking mechanism on the index files. Thanks, Kevin

2 3

[Dovecot] ldap auth problems
by Karl Latiss 30 Jun '04

30 Jun '04

I have previously configured dovecot with ldap auth on a fedora setup with no problems. Now, using RHEL 3 with the same config I get: dovecot: Jun 30 17:46:07 Error: Auth process died too early - shutting down dovecot: Jun 30 17:46:07 Error: child 16780 (auth) killed with signal 11 pop3-login: Jun 30 17:46:07 Fatal: fd_send(-1) failed: Broken pipe imap-login: Jun 30 17:46:07 Fatal: fd_send(-1) failed: Broken pipe This doesn't happen when using other kinds of authentication, eg pam The ldap directory is working fine for other apps so I'm pretty sure that's not it. I'm using the rpm from dag's repository and even re-compiled to ensure ldap support is there. Any clues? -- Karl Latiss <karl(a)designit.com.au> designIT

2 1

[Dovecot] 1.0 Maildir/mbox
by Paul Adams 29 Jun '04

29 Jun '04

Just to confirm, and sorry if I've missed this info somewhere in the flurry of messages: dovecot 1.0 will be able to support maildir and mbox users simultaneously? Paul

2 1

Re: [Dovecot] phpGroupWare
by Avery 28 Jun '04

28 Jun '04

I am currently using SQ mail also. Was wondering though about phpGroupWare. Brook Humphrey said: > On Friday 25 June 2004 08:46 pm, Avery wrote: >> Anyone here using phpGroupWare with dovecot? Does anyone know if it is >> possible? >> >> Thanks > I use squirllmail and it works great. > > -- > -~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~- > Brook Humphrey > Mobile PC Medic, 420 1st, Cheney, WA 99004, 509-235-9107 > http://www.webmedic.net, bah(a)webmedic.net, bah(a)linux-mandrake.com > Holiness unto the Lord > -~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~- > > -- Avery

1 0

[Dovecot] Dovecot on Redhat GFS
by Tomi Hakala 28 Jun '04

28 Jun '04

Now that Redhat released GFS to GLP has anyone gotten around to test Dovecot on top of that? -- Tomi Hakala

1 0

[Dovecot] 0.99.10.6 -imap flag update problem still present
by Hauke Fath 28 Jun '04

28 Jun '04

Hi, the email status problem that I reported for Dovecot 0.99.10.5 on June 3rd does still show up in 0.99.10.6. Quoting myself: (1) When new mail is delivered to the inbox, the last read mail(s) change(s) to "unread". Clients: Eudora 6 (Mac), Mozilla 1.6 (NetBSD, Linux, Win XP), MS Outlook. (2) When you attempt to move mails from the inbox to another folder with Mozilla (1.6 on win32, Linux, NetBSD), they are not removed from the inbox, effectively performing a copy instead of a move. And, while I am at it, (3) I see a regular log entry from a MS Outlook 2000 SP 3 Jun 3 10:26:23 bounce imap-login: SSL_read() syscall failed: EOF [130.83.XXX.XXX] The setup here: OS NetBSD 2.0beta, MTA sendmail 8.12.11, LDA maildrop 1.3.9, dovecot 0.99.10.6, OpenSSL 0.9.7d Any ideas? My users are starting to nag... hauke -- Institut für Nachrichtentechnik /~\ The ASCII Ribbon Campaign FG Signalverarbeitung \ / No HTML/RTF in email TU Darmstadt X No Word docs in email Ruf +49-6151-16-3281, Fax -3778 / \ Respect for open standards

2 7

[Dovecot] Mailbox archiving
by Leslie Viljoen 28 Jun '04

28 Jun '04

Hi all! I have a strange problem with Dovecot - deleted messages never seem to get deleted on the server! Deleted messages just seem to get a 'T' at the end of them on the server and remain there, so user mail boxes continue to grow to incredible sizes. Is this a setting I must change somewhere? Must I delete these files manually? Leslie

3 2

[Dovecot] Is Dovecot able to use PostgreSQL to store mailboxes?
by Bill Moran 28 Jun '04

28 Jun '04

Subject says it all. (I'm almost positive this is a FAQ, or that the information is online _somewhere_, but I just spent 20 minutes without finding it ... sorry if I didn't search hard enough) -- Bill Moran Potential Technologies http://www.potentialtech.com

6 8

[Dovecot] passwd + shadow auth problem
by T'aZ 28 Jun '04

28 Jun '04

Hi! here is the problem , i have local users some have shadow password, some not, so i must create two auth one to login via shadow , and one via passwd so here is my config file (stripped comments): protocols = imap imaps pop3 pop3s imap_listen = 192.168.0.2 pop3_listen = 192.168.0.2 imaps_listen = 192.168.0.2 pop3s_listen = 192.168.0.2 login = imap login = pop3 auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = shadow auth_user = root auth_count = 1 auth_verbose = yes auth = truc auth_mechanisms = plain auth_userdb = passwd auth_passdb = passwd auth_verbose = yes if i try a user with shadow, it works, but if i try a user without shadow, it fails in the log with dovecot-auth: shadow(taz): unknown user what's wrong, why doesnt it use the second auth option ? where is my error ? i'm using 0.99.10.6 thanks in advance -- T'aZ |Jabber:taz-007@jabber.org|GPG keyID:E051925D|http://taz.prout.be *They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.* Benjamin Franklin 1759 *Beaucoup,vite,loin,mal.* http://www.cl.cam.ac.uk/~rja14/tcpa-faq.html

2 1

[Dovecot] invalid mask
by Adrian Roye 28 Jun '04

28 Jun '04

Hi ! I still get the message: "The current command did not succeed. The mail server responded: invalid mask" I am using the Netscapes mail client. Adrian

2 1

[Dovecot] phpGroupWare
by Avery 26 Jun '04

26 Jun '04

Anyone here using phpGroupWare with dovecot? Does anyone know if it is possible? Thanks -- Avery

1 0

[Dovecot] Locked index file
by Kevin Cramer 25 Jun '04

25 Jun '04

I have docevot 0.99.10.6 installed on OpenBSD 3.5 and I'm using it with Squirrelmail. I tried to empty my Trash folder and it timed out. It looks like the process or thread died but the lock wasn't removed: Jun 25 09:16:30 plato imap(kevin): Timeout while waiting for release of shared fcntl() lock for index file /home/kevin/Maildir/.Trash/.imap.index How can I free this lock? I have tried stopping and re-starting dovecot already but that didn't help. Also, is there something I should do to prevent this in the future? The OpenBSD package sets the default locking to fcntl for mbox. I'm not sure if that is the setting that also controls the locking mechanism on the index files. Thanks, Kevin

1 0

[Dovecot] Locked index file
by Kevin Cramer 25 Jun '04

25 Jun '04

I have docevot 0.99.10.6 installed on OpenBSD 3.5 and I'm using it with Squirrelmail. I tried to empty my Trash folder and it timed out. It looks like the process or thread died but the lock wasn't removed: Jun 25 09:16:30 plato imap(kevin): Timeout while waiting for release of shared fcntl() lock for index file /home/kevin/Maildir/.Trash/.imap.index How can I free this lock? I have tried stopping and re-starting dovecot already but that didn't help. Also, is there something I should do to prevent this in the future? The OpenBSD package sets the default locking to fcntl for mbox. I'm not sure if that is the setting that also controls the locking mechanism on the index files. Thanks, Kevin

1 0

[Dovecot] IMAP mailing archives back online
by Timo Sirainen 24 Jun '04

24 Jun '04

Read-only mboxes seem to be working nicely now, so I installed latest CVS Dovecot to dovecot.org again to serve them. Allows either ANONYMOUS SASL logins, or plaintext logins with "anonymous" user and empty password.

1 0

[Dovecot] Sym links to subfolders?
by Kevin Cramer 24 Jun '04

24 Jun '04

I just installed dovecot 0.99.10.6 and I'm trying to use symlinks for subfolders. I have my mail in ~/Maildir and I want to make symlinks such as from .Sent to ~/Mail/Sent. All of these folders are maildir and the permissions are correct. I've searched the list and I cannot find anything stating that it should not work. In fact I've seen posts that claim it should work. However, it does not work for me and looking at maildir-list.c around line 101, it appears that it is only checking for directories and not for links. I'm doing this because I have it setup so I can use mutt directly against the maildir folders and so IMAP will work against them. It's worked great for over a year but I want to move it to a different machine and I wanted to switch from courier-imap to dovecot. Can anyone confirm that it works or not? Any ideas on how to address this issue? Thanks, Kevin

2 1

[Dovecot] Re: [ismail] Re: using Dovecot
by Steven Stern 24 Jun '04

24 Jun '04

On Wed, 23 Jun 2004 18:26:01 +0000, "Kelley Reynolds" <kelley(a)insidesystems.net> wrote: > >I've never used dovecot, but I know that those directories aren't what IMAP servers generally expect when looking for a rootfolderpath. > >For example, courier is always 'INBOX', uw-imap is usually but not always 'mail', and sometimes it's just a blank string. My guess is that for you, it's one of those three. If your mail is in a 'mail' directory, I suggest just putting 'mail' and not '~/mail'. > >Kelley Reynolds >President >Inside Systems, Inc > >___________________________________________________________________ I'm going to cross post this to the dovecot list in case someone there has an idea. To bring those people up to speed: I'm evaluating ISMail (www.insidesystems.net) as a replacement for IMP. I'm having problems configuring the IMAP settings to work with Dovecot. === I've got some progress. I set rootmailfolder to "~/mail". When I login to ISMail, it creates the directory ~/inbox as follows: mail Sent Items then dies. If I set rootmailfolder to as "rootmailfolder=" with no argument, it creates .imap INBOX .customflags .imap.index.data .imap.index.tree .imap.index .imap.index.log then dies If I set rootmail folder to "INBOX" INBOX Sent Items .subscriptions .imap INBOX .customflags .imap.index.data .imap.index.tree .imap.index .imap.index.log -- Steve

2 1

[Dovecot] customflags considered a folder?
by Peter Schuller 23 Jun '04

23 Jun '04

Hello, i just switched from courier-imap to dovecot on a machine. The transition was painless except for one issue - when using the "Check mail" feature of kmail, one gets the message: "Unable to get information about folder customflags. The server replied: internal error..." So it looks like the server isn't properly hiding the .customflags file for some reason. I googled and only found one person who had seen something similar, but no solution. This is with dovecot 0.99.10.5. Similarly, 'customflags' does show up as a folder when using mutt. How would I go about preventing this problem? Thanks! -- / Peter Schuller, InfiDyne Technologies HB PGP userID: 0xE9758B7D or 'Peter Schuller <peter.schuller(a)infidyne.com>' Key retrieval: Send an E-Mail to getpgpkey(a)scode.org E-Mail: peter.schuller(a)infidyne.com Web: http://www.scode.org

2 5

[Dovecot] 1.0-test20
by Timo Sirainen 22 Jun '04

22 Jun '04

http://dovecot.org/test/ One more for today :) Again mostly mbox fixes and optimizations. Don't try it with maildir because it crashes with COPY and APPEND commands. This release supports now UIDPLUS extension. It was mostly a side effect of making saving mails store the X-UID header immediately to mbox and adding the mail to index. So, a Dovecot LDA would finally make sense now. Besides keeping indexes updated, it could also ask user's home dir, uid and gid from dovecot-auth. Now, that combined with postfix-dovecot-auth patch, Dovecot would be very simple to install with Postfix :)

2 2

[Dovecot] Compile error
by Greg T. Harber 22 Jun '04

22 Jun '04

On dovecot-1.0-test21: gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../src/lib -I../../src/lib-auth -DPKG_RUNDIR=\""/usr/local/var/run/dovecot"\" -DSBINDIR=\""/usr/local/sbin"\" -I/usr/local/include -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -c ssl-proxy-gnutls.c ssl-proxy-gnutls.c:11:2: #error broken currently ssl-proxy-gnutls.c:310: error: conflicting types for `ssl_proxy_new' ssl-proxy.h:12: error: previous declaration of `ssl_proxy_new' ssl-proxy-gnutls.c: In function `ssl_proxy_new': ssl-proxy-gnutls.c:319: warning: passing arg 2 of `gnutls_transport_set_ptr' makes pointer from integer without a cast ssl-proxy-gnutls.c: In function `read_dh_parameters': ssl-proxy-gnutls.c:417: warning: `gnutls_dh_params_set' is deprecated (declared at /usr/local/include/gnutls/compat8.h:82) ssl-proxy-gnutls.c: In function `read_rsa_parameters': ssl-proxy-gnutls.c:443: warning: `gnutls_rsa_params_set' is deprecated (declared at /usr/local/include/gnutls/compat8.h:77) make[3]: *** [ssl-proxy-gnutls.o] Error 1 On dovecot-0.99.10.6: gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../src/lib -DPKG_RUNDIR=\""/usr/local/var/run/dovecot"\" -DSBINDIR=\""/usr/local/sbin"\" -I/usr/local/include -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -c ssl-proxy-gnutls.c ssl-proxy-gnutls.c: In function `ssl_handshake': ssl-proxy-gnutls.c:280: warning: implicit declaration of function `gnutls_handshake_get_direction' ssl-proxy-gnutls.c: In function `initialize_state': ssl-proxy-gnutls.c:302: warning: implicit declaration of function `gnutls_cert_type_set_priority' ssl-proxy-gnutls.c: In function `ssl_proxy_new': ssl-proxy-gnutls.c:318: warning: passing arg 2 of `gnutls_transport_set_ptr' makes pointer from integer without a cast ssl-proxy-gnutls.c: In function `read_dh_parameters': ssl-proxy-gnutls.c:416: warning: `gnutls_dh_params_set' is deprecated (declared at /usr/local/include/gnutls/compat8.h:82) ssl-proxy-gnutls.c: In function `read_rsa_parameters': ssl-proxy-gnutls.c:442: warning: `gnutls_rsa_params_set' is deprecated (declared at /usr/local/include/gnutls/compat8.h:77) ssl-proxy-gnutls.c: In function `ssl_proxy_init': ssl-proxy-gnutls.c:508: warning: implicit declaration of function `gnutls_certificate_allocate_cred' ssl-proxy-gnutls.c:520: error: void value not ignored as it ought to be ssl-proxy-gnutls.c:523: error: void value not ignored as it ought to be ssl-proxy-gnutls.c: In function `ssl_proxy_deinit': ssl-proxy-gnutls.c:545: warning: implicit declaration of function `gnutls_certificate_free_cred' make[3]: *** [ssl-proxy-gnutls.o] Error 1 Environment: Solaris 8 (2.8) gnutls 1.0.13 gcc -v Reading specs from /usr/local/lib/gcc-lib/sparc-sun-solaris2.8/3.3/specs Configured with: ../configure --disable-nls --with-as=/usr/ccs/bin/as --with-ld=/usr/ccs/bin/ld Thread model: posix gcc version 3.3 Process: # ./configure # make

3 2

[Dovecot] Update: Compile error
by Greg T. Harber 22 Jun '04

22 Jun '04

Offending lines in src/login-common/ssl-proxy-gnutls.c 519 ret = gnutls_certificate_set_dh_params(x509_cred, dh_params); 520 if (ret < 0) 521 i_fatal("Can't set DH parameters: %s", gnutls_strerror(ret)); 522 ret = gnutls_certificate_set_rsa_params(x509_cred, rsa_params); 523 if (ret < 0) 524 i_fatal("Can't set RSA parameters: %s", gnutls_strerror(ret)); Problem: gnutls.h lists these two functions as returning void Solution: remove the ret and the check code Compilation continue but link fails: Undefined first referenced symbol in file gnutls_cert_type_set_priority ../login-common/liblogin-common.a(ssl-proxy-gnutls.o) gnutls_certificate_allocate_cred ../login-common/liblogin-common.a(ssl-proxy-gnutls.o) gnutls_certificate_free_cred ../login-common/liblogin-common.a(ssl-proxy-gnutls.o) gnutls_handshake_get_direction ../login-common/liblogin-common.a(ssl-proxy-gnutls.o) Solution: Add #include "/usr/local/include/gnutls/compat4.h" to ssl-proxy-gnutls.c Successful compile afterwards. -- Greg T. Harber gth(a)cs.sfasu.edu Director, McGee Computing Laboratory 936 468-2508 Department of Computer Science P.O. Box 13063 Stephen F. Austin State University Nacogdoches, TX 75962 USA

1 0

[Dovecot] 1.0-test21
by Timo Sirainen 22 Jun '04

22 Jun '04

http://dovecot.org/test/ Should work again with maildir. - Some bugfixes to indexes (possibly fixing the still persisting maildir sync errrors?) - Enabled cache file again. If client asks about something that can be cached for future, it's done. There's currently no smart logic about when not to do it or when to cache more than was asked for future use. Currently nothing is ever deleted from cache. Currently it's disabled if mmap_disable = yes. - Removed UIDPLUS extension after all. It needs more thinking with maildir, because for performance reasons new messages are given UIDs once at the end transaction rather than separately for each one. So, the UID would have to be 0 temporarily until transaction is committed. But the current API make the new messages visible without syncing, and then the sequences don't match anymore and we can't get the UIDs. So, this one needs thinking, mostly from API designing point of view.

8 25

[Dovecot] LDAP Bind
by Hervé Commowick - NewSports 22 Jun '04

22 Jun '04

hi all 2 Questions : - how not using the authentication bind feature of ldap server ? i rewrite checkpassword-ldap recently to use in bincimap server, and it take 3 lines to do this, so i don't understand how you don't use it. it is more powerful and more secure than retrieve pasword from the base and use crypto api to compare it. - is the dovecot server support the IMAPdir feature like bincimap or not ? thx for this great software, who replace my imap and pop3 server when it support that :) Vr.

3 6

[Dovecot] Delete message
by Marius Stan 22 Jun '04

22 Jun '04

Hello, I'm seeing that our favourite pop3 server only deletes the messages upon logoff: dele 1 +OK Marked to be deleted. quit +OK Logging out, messages deleted. Connection closed by foreign host. This is causing me some trouble with a certain webmail app. Is there a way I can instruct Dovecot to immediatelly delete a message ? 10x, Marius

2 1

[Dovecot] proxy plugin
by Timo Sirainen 22 Jun '04

22 Jun '04

I've updated the proxy plugin at http://dovecot.org/patches/1.0/quota.c. It doesn't exactly work, even against latest CVS Dovecot as it crashes in save/copy, but it shows how it's basically going to work. Pretty ugly to do objects with C, but works.. If you're interested about writing support for some specific quota backend (maildir++, sql, ..), now would be a good time to begin :) Well, the reason it crashes is because it needs to find out the message's size, but Dovecot doesn't yet really like being asked about messages that haven't been committed to index. I guess that needs to change, hopefully won't require too large changes. I think I'm going to merge mail-index-view and mail-index-transaction into same thing..

1 1

[Dovecot] I/O Leak?
by Paul McMurphy 22 Jun '04

22 Jun '04

Is the I/O leak message normal? (from syslog) Jun 22 02:12:39 xbox pop3(paul): lstat(/var/mail/Maildir/paul/INBOX/cur) failed: Permission denied Jun 22 02:12:39 xbox pop3(paul): lstat(/var/mail/Maildir/paul/INBOX/cur) failed: Permission denied Jun 22 02:12:39 xbox pop3: I/O leak: 0x8050ce0 (0) Jun 22 02:12:39 xbox pop3: I/O leak: 0x8084b10 (1) Jun 22 02:13:22 xbox pop3-login: Login: paul [192.168.1.10] Jun 22 02:13:23 xbox pop3(paul): lstat(/var/mail/Maildir/paul/INBOX/cur) failed: Permission denied Jun 22 02:13:23 xbox pop3(paul): lstat(/var/mail/Maildir/paul/INBOX/cur) failed: Permission denied Jun 22 02:13:23 xbox pop3: I/O leak: 0x8050ce0 (0) Jun 22 02:13:23 xbox pop3: I/O leak: 0x8084b10 (1) Oh... and any hints on the permissions problem would be ok also. ;) Debian 1.0.1 / dovecot 0.99.10.6-1 Thanks!

2 1

[Dovecot] The Status: header is forced
by Olivier Tharan 21 Jun '04

21 Jun '04

Hi, I started testing dovecot for our next POP/IMAP server (nearing production state), and noticed that the Status: header is always added, with a value of 'O' or 'RO'. This happens in `lib-index/mbox/mbox-rewrite.c'. This does not seem to happen in the Maildir case. Is the Status: header really needed in every case? This breaks mutt which displays mails with a 'O' flag instead of 'N'. My dovecot is 0.99.10.4 (FreeBSD port), but the behavior is still the same in the CVS version. -- olive

3 6

[Dovecot] 1.0-test19
by Timo Sirainen 21 Jun '04

21 Jun '04

http://dovecot.org/test/ I'm finally using this release myself with mboxes. So far no crashes or corruption. :) - several mbox fixes and optimizations - maildir syncing fix - solaris fixes - create mbox root dir if it doesn't exist

2 3

[Dovecot] 0.99.10.6 released
by Timo Sirainen 20 Jun '04

20 Jun '04

Since no-one have complained about previous RCs, I guess it's release time. Since -rc2 I added the ioloop.c assert fix, and 64bit Solaris fix. Here's the full change summary again: v0.99.10.6 2004-06-20 Timo Sirainen <tss(a)iki.fi> + SHA1 password support using OpenSSL crypto library + mail_extra_groups setting + maildir_stat_dirs setting + Added NAMESPACE capability and command - Autocreate missing maildirs (instead of crashing) - Fixed occational crash in maildir synchronization - Fixed occational assertion crash in ioloop.c - Fixed FreeBSD compiling issue - Fixed issues with 64bit Solaris binary

2 1

[Dovecot] Re: [dovecot-cvs] dovecot/src/lib fdpass.c,1.28,1.29
by Charlie Allom 20 Jun '04

20 Jun '04

Will this perhaps fix these? imap-login: Jun 15 12:28:16 Panic: file ioloop.c: line 90: assertion failed: (i o->fd <= current_ioloop->highest_fd) dovecot: Jun 15 12:28:16 Error: child 17987 (login) killed with signal 6 imap-login: Jun 15 13:14:58 Panic: file ioloop.c: line 90: assertion failed: (i o->fd <= current_ioloop->highest_fd) dovecot: Jun 15 13:14:58 Error: child 13002 (login) killed with signal 6 On Tue, Jun 15, 2004 at 02:42:25AM +0300, cras(a)procontrol.fi wrote: > Update of /home/cvs/dovecot/src/lib > In directory talvi:/tmp/cvs-serv11171 > > Modified Files: > fdpass.c > Log Message: > Solaris fix by Tim Hurman > > > > Index: fdpass.c > =================================================================== > RCS file: /home/cvs/dovecot/src/lib/fdpass.c,v > retrieving revision 1.28 > retrieving revision 1.29 > diff -u -d -r1.28 -r1.29 > --- fdpass.c 1 Dec 2003 19:07:34 -0000 1.28 > +++ fdpass.c 14 Jun 2004 23:42:23 -0000 1.29 > @@ -31,12 +31,20 @@ > #include <sys/uio.h> > > #ifndef CMSG_SPACE > -# define CMSG_ALIGN(len) \ > +# if defined(_CMSG_DATA_ALIGN) && defined(_CMSG_HDR_ALIGN) /* for Solaris */ > +# define CMSG_ALIGN(len) _CMSG_DATA_ALIGN(len) > +# define CMSG_SPACE(len) \ > + (_CMSG_DATA_ALIGN(len) + _CMSG_HDR_ALIGN(sizeof(struct cmsghdr))) > +# define CMSG_LEN(len) \ > + (_CMSG_HDR_ALIGN(sizeof(struct cmsghdr)) + (len)) > +# else > +# define CMSG_ALIGN(len) \ > (((len) + sizeof(size_t) - 1) & ~(sizeof(size_t) - 1)) > -# define CMSG_SPACE(len) \ > +# define CMSG_SPACE(len) \ > (CMSG_ALIGN(len) + CMSG_ALIGN(sizeof(struct cmsghdr))) > -# define CMSG_LEN(len) \ > +# define CMSG_LEN(len) \ > (CMSG_ALIGN(sizeof(struct cmsghdr)) + (len)) > +# endif > #endif > > #ifdef SCM_RIGHTS > -- .signature 0x14AA7941

2 4

[Dovecot] 0.99.10.5 released
by Timo Sirainen 19 Jun '04

19 Jun '04

One more bugfix since rc2: - Maildir: synchronization might have sometimes set wrong flags to messages, or crash completely Quite rare because we were lucky before :) And list of all the changes one more time: v0.99.10.5 2003-12-27 Timo Sirainen <tss(a)iki.fi> + MySQL authentication, patch by Matthew Reimer + --with-moduledir configure option - mbox: APPEND reversed given \Draft and \Deleted flags - mbox: "LF not found" errors happened sometimes when X-IMAPbase header was updated. Possibly corrupted mbox sometimes. Thanks to Fabrice Bellet for finding this bug. - Custom flags couldn't be unset - Maildir: make sure ":2," is appended to filename when moving mails from new/ to cur/. - Maildir: synchronization might have sometimes set wrong flags to messages, or crash completely - Maildir: RENAME xx inbox.xx didn't result as uppercased ".INBOX.xx" directory which then couldn't be accessed - Don't crash with RAND_bytes() error messages anymore. This mostly happened with Fedora/RedHat.

6 13

[Dovecot] 1.0-test17
by Timo Sirainen 19 Jun '04

19 Jun '04

http://dovecot.org/test/ Just mbox fixes since 1.0-test16. The logic is simpler and more correct now. Can anyone break it anymore? I actually tested it a while with Evolution and several mailboxes and it didn't break at least immediately. :) Now maybe a few more days and I dare trying this thing myself with my real mboxes (yes, I'm still using them). Dovecot mailing list archives could soon be served with 1.0-tests too, as soon as I get support for read-only mboxes working again (storing and comparing MD5 summed headers).

5 17

[Dovecot] 1.0-test18
by Timo Sirainen 19 Jun '04

19 Jun '04

http://dovecot.org/test/ Again mostly just mbox fixes. The good thing is that the code is only getting cleaner and more understandable with every release. But I think it's clean enough now that this release should work :) It also has checkpassword passdb support. Supporting it as userdb isn't yet implemented. I think I'll make some generic caching thingy, so that if passdb is same as userdb, they both could be queried from database in one query. Probably by allowing pass_query/pass_filter to return them.

1 0

[Dovecot] 0.99.10.6-rc1 released
by Timo Sirainen 18 Jun '04

18 Jun '04

http://dovecot.org/rc/ Fixes the crashes people had been getting more often with 0.99.10.5. Also included all the patches in dovecot.org/patches/old: - SHA1 passwords - mail_extra_groups setting (Debian people can finally fix #185335 :) - autocreate missing maildirs (and don't crash) - maildir_stat_dirs setting If no problems are found within few days this will simply be renamed to 0.99.10.6.

3 5

[Dovecot] 0.99.10.6-rc2
by Timo Sirainen 18 Jun '04

18 Jun '04

http://dovecot.org/rc/ Since rc1: - Changed a few comments in dovecot-example.conf - Changed a few error messages. Most importantly: "Internal error occured. Error report written to server log." .. maybe that would get more people to look for the real error in the log file :) - Added NAMESPACE command - Fixed SHA1 compiling issue - Fixed FreeBSD compiling issue

1 0

[Dovecot] dovecot startup failure - dovecot-auth unable to open passwd-file
by Stephen Hillier 18 Jun '04

18 Jun '04

Hi all, I'm stuck on getting dovecot to work for 2 days. Here's the logfile entries from the startup process(es) dovecot: Jun 18 14:48:43 Info: Dovecot starting up dovecot-auth: Jun 18 14:48:44 Fatal: Can't open passwd-file /var/run/dclogin/mail-passwd: No such file or directory dovecot: Jun 18 14:48:44 Error: Auth process died too early - shutting down dovecot: Jun 18 14:48:44 Error: child 7313 (auth) returned error 89 imap-login: Jun 18 14:48:44 Fatal: fd_send(-1) failed: Broken pipe pop3-login: Jun 18 14:48:44 Fatal: fd_send(-1) failed: Broken pipe The strange thing is, the file I've specified does exist -- i created it manually -- and the 1 entry in that file is this: steve:s13fj3NHakds.:10001:5000::/var/run/dovecot/home/steve:/sbin/nologin::~/Mail/:INBOX=/var/spool/mail/steve What's even stranger -> every time I try to startup dovecot, the passwd-file that is seen to be "missing" gets deleted!!!! why??? Here's a copy of my current (broken) conf: base_dir = /var/run/dovecot/ protocols = imap imaps pop3 pop3s ssl_disable = yes log_path = /var/log/maillog login_dir = /var/run/dclogin login_chroot = no login = imap login_executable = /usr/libexec/dovecot/imap-login login_user = doveauth login_process_per_connection = yes login_processes_count = 5 login = pop3 login_executable = /usr/libexec/dovecot/pop3-login first_valid_uid = 10000 last_valid_uid = 20000 first_valid_gid = 5000 last_valid_gid = 5100 default_mail_env = mbox:~/Mail/:INBOX=/var/spool/mail/%u mbox_locks = fcntl imap_executable = /usr/libexec/dovecot/imap pop3_executable = /usr/libexec/dovecot/pop3 auth = default auth_mechanisms = plain digest-md5 auth_userdb = passwd-file /var/run/dclogin/mail-passwd auth_passdb = passwd-file /var/run/dclogin/mail-passwd auth_executable = /usr/libexec/dovecot/dovecot-auth auth_verbose = yes I'm sure I did something silly in my conf that's causing the problem but I'm not sure what that might be. Thanks in advance for any and all help. Steve. ______________________________________________________________________ Post your free ad now! http://personals.yahoo.ca

2 1

[Dovecot] Info: Internal login failure:
by Nico De Beer - MWEB 18 Jun '04

18 Jun '04

I get the following error on auth with mysql on pop3 what am i missing or doing wrong mysql config file db_host = localhost #db_port = 3306 db_unix_socket = /var/lib/mysql/mysql.sock db = ADMIN db_user = mailmaster db_passwd = ******** db_client_flags = 0 default_pass_scheme = PLAIN password_query = SELECT MAILBOX_PASSWORD AS password FROM MAIL WHERE MAILBOX_USERNAME = '%n' AND MAILBOX_DOMAIN = '%d' #user_query = SELECT MAILBOX_ROOT AS home,uid,gid FROM MAIL WHERE MAILBOX_USERNAME = '%n' and MAILBOX_DOMAIN='%d' dovecot config file base_dir = /var/run/dovecot/ protocols = imap pop3 imap_listen = * pop3_listen = * ssl_disable = yes log_path = /var/log/dovecot_log info_log_path = /var/log/dovecot_info_log log_timestamp = "%b %d %H:%M:%S " login_dir = /var/run/dovecot/login login = imap login_executable = /usr/local/libexec/dovecot/imap-login login_user = dovecot login_process_size = 16 login_process_per_connection = yes login_processes_count = 3 login_max_processes_count = 128 login_max_logging_users = 256 login = pop3 max_mail_processes = 1024 verbose_proctitle = no first_valid_uid = 500 #last_valid_uid = 0 default_mail_env = maildir:/home/mail/%d/%n/Maildir mail_cache_fields = MessagePart client_workarounds = oe6-fetch-no-newmail:outlook-idle: mailbox_check_interval = 300 mailbox_idle_check_interval = 30 mail_save_crlf = yes mail_read_mmaped = no maildir_copy_with_hardlinks = yes mbox_locks = dotlock fcntl mbox_read_dotlock = yes mbox_lock_timeout = 120 mbox_dotlock_change_timeout = 30 umask = 0077 mail_drop_priv_before_exec = no imap_executable = /usr/local/libexec/dovecot/imap imap_process_size = 256 pop3_executable = /usr/local/libexec/dovecot/pop3 pop3_process_size = 256 auth = default auth_mechanisms = plain auth_passdb = mysql /usr/local/etc/dovecot-mysql.conf auth_user = mailmaster auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ Are you ready for Telkom's 10-digit dialling? To find out how this will affect your Internet connection in the not too distant future, go to www.mweb.co.za/ten

2 1

[Dovecot] Maildir + Evolution
by mkortela＠cc.hut.fi 18 Jun '04

18 Jun '04

I don't know if this is an Evolution bug or not, but when I use the maildir format with Dovecot 0.99.10p2 (from OpenBSD packages collection) and connect to it from Evolution 1.4 using IMAP, Evolution displays subfolders incorrectly. It actually does not show any subfolders, only root folders with names like "Folder.Subfolder" and "Folder.Subfolder.Subsubfolder". There's no such problem when using traditional mailboxes. Is this an Evolution bug or one of Dovecot's? I had thought the IMAP protocol should act the same no matter which mail dir structure was used... -- Mikko Kortelainen mkortela(a)cc.hut.fi

3 2

[Dovecot] Add SSL to Dovecot & SquirrelMail
by Eric Kahklen 18 Jun '04

18 Jun '04

I am relatively new to setting up mail servers and wondered how difficult it would be to add SSL to my current Dovecot & SquirrelMail setup. Would I just add SSL to the squirrelmail directory under appache with my certificate? Does Dovecot need any changes to the configuration? I have it working fine without SSL. Thanks, Eric

1 0

[Dovecot] IMAP and webmail applications
by Tom Allison 18 Jun '04

18 Jun '04

I've been hunting around for a webmail application other than squirrelmail for reasons that really don't matter. But I'm seeing that a lot of these applications tend to sometimes access servers via IMAP, but they always seem to have a touch more information needed than might be for an IMAP session. An example is openwebmail. It authenticates very similar to how dovecot authenticates, with a userdb and passdb specifications. It reads directly off the disk for some of it's activities. As for squirrelmail, they seem to want a lot of information regarding the mail architecture (mbox, maildir, folder locations...) and I don't really see where this could come into play with an IMAP implimentation. So, not actually having read all 82 pages of RFC 2060 (but I did print them!), I'm trying to see what I might miss if I were to attempt a web mail application that was based entirely upon IMAPv4 with the only information known prior to connection is the server name. Kind of like my mail client. Will I get into trouble with mail directories/folders if I start accessing different IMAP servers other than dovecot? Can I discover this without any hints from the user? I'm not sure exactly what I'm asking for here, other than some thoughts on what I might have to watch out for or do without (when comparing to squirrelmail as an example). I know I'll have to do something different if someone wants an addressbook, but I'm not there yet.

5 6

[Dovecot] 1.0-test16 - nearing usable state
by Timo Sirainen 18 Jun '04

18 Jun '04

http://dovecot.org/test/ Here you go, maildir syncing problems finally fixed (I hope). Well, except there's this "new-dir-only syncing" optimization which I'm not really sure if it works as it should. The bug really was in index code as I was beginning to suspect. The good thing is that while trying to figure it out over the last several weeks I thought of many other potential problems (race conditions) which got fixed. Those would have been much harder to find than this one :) Finally I thought I'd stop looking at the code and just begin dumping tons of debugging data to see where exactly it goes wrong. After few hours of debugging I figured out it was because message was being removed from index but not from maildir. 5 hours of sleep later I woke up, thought a while, figured out where it must be, got up, half an hour more debugging and found it. :) Code merging two UID range buffers into one was buggy, inserting one line of code fixed it. So .. Maybe I'll finally start using this myself now. The next important problems seem to be some random error messages about index locking timeouts and some asserts in some situations.

3 2

Re: [Dovecot] IMAP and webmail applications
by durango99 18 Jun '04

18 Jun '04

i thought squirrelmail would be way too much of an overkill for my needs also but i went for it. i'm using debian and i got the squirrelmail package installed and working within 15 minutes. what really makes life easy is that squirrelmail comes with a configuration utility (squirrelmail-configure). it was very easy to get things configured without worry about a lot of conf files :) i also like the many plugins that people have created for squirrelmail. it's also very simple to add these plugins into squirrelmail using squirrelmail-configure. i had originally been ssh and mutt to check my mail, but i decided it be nice to have a web front-end and squirrelmail /apache /dovecot /procmail /spamassassin /gotmail /getmail /fetchyahoo have been a good mix for me. the hardest part for me was figuring out procmail and not squirrelmail :) my 2 cents, dan > I've been hunting around for a webmail application other than > squirrelmail for reasons that really don't matter. > > But I'm seeing that a lot of these applications tend to sometimes access servers via IMAP, but they always seem to have a touch more information needed than might be for an IMAP session. > > An example is openwebmail. It authenticates very similar to how dovecot authenticates, with a userdb and passdb specifications. It reads directly off the disk for some of it's activities. > > As for squirrelmail, they seem to want a lot of information regarding the mail architecture (mbox, maildir, folder locations...) and I don't really see where this could come into play with an IMAP implimentation. > > So, not actually having read all 82 pages of RFC 2060 (but I did print them!), I'm trying to see what I might miss if I were to attempt a web mail application that was based entirely upon IMAPv4 with the only information known prior to connection is the server name. Kind of like my mail client. > > Will I get into trouble with mail directories/folders if I start accessing different IMAP servers other than dovecot? Can I discover this without any hints from the user? > > I'm not sure exactly what I'm asking for here, other than some thoughts on what I might have to watch out for or do without (when comparing to squirrelmail as an example). I know I'll have to do something different if someone wants an addressbook, but I'm not there yet. >

1 0

[Dovecot] shared authentication
by Kevin 16 Jun '04

16 Jun '04

whats the recommended way to share a user auth info between dovecot and postfix? sasldb seems like it could work but nobody really seems to like using the giant mass that is sasl. i also cant find any information on actually getting dovecot to use sasl past the configure options. i looked at timo's patch for postfix to use dovecot-auth but it doesnt apply correctly on the 2.1 branch. so what are people using to share passwords between the two without using the system passwd?

3 3

[Dovecot] POP3 LAST command?
by Christian Balzer 16 Jun '04

16 Jun '04

Hello, any plans to support this in the future? Seems the inability to use LAST breaks that Yahoo remote mailbox slurper thing, not that I care too much about that, but some mail clients might miss it as well. ;) Regards, Christian Balzer -- Christian Balzer Network/Systems Engineer NOC chibi(a)gol.com Global OnLine Japan/Fusion Network Services http://www.gol.com/

4 4

[Dovecot] Return (revenge?) of the "pop-lock".
by Christian Balzer 16 Jun '04

16 Jun '04

Hello, The users here have been migrated to the new mail system with dovecot 0.99.10.5 (Debian package) on the backends. Storage is maildir, only pop3 access for now. I see very seldom occurrences (compared to the session wide pop lock of qpopper on the old system) like this: --- Jun 16 14:35:52 mb01 pop3(user(a)gol.com): Timeout while waiting for release of exclusive fcntl() lock for index file /mail/spool/mb01/9ef/f73/af.user/.INBOX/.imap.index --- These are people with slow connections and at least one large mail in the box, with their client aborting w/o terminating the session properly. I presume the timeout for this is hardcoded, as all the config parameters for timeouts are mbox related, rite? Regards, Christian Balzer -- Christian Balzer Network/Systems Engineer NOC chibi(a)gol.com Global OnLine Japan/Fusion Network Services http://www.gol.com/

2 2

[Dovecot] /var/mail dotlocking workaround
by Timo Sirainen 16 Jun '04

16 Jun '04

I added "mail_extra_groups" setting which can be used to give imap/pop3 process access to additional groups. So what this means is if you set it to "mail" you can finally remove o-w access from /var/mail directory. Leaving the sticky bit could still be a good idea, so there's no way users to be able to delete each others inboxes. Here's a patch against 0.99.10.5: http://dovecot.org/patches/mail-extra-groups.diff

1 0

[Dovecot] dovecot non-local users
by Tom Allison 16 Jun '04

16 Jun '04

From the docs: System without local users -------------------------- <snip> Having one uid per user would mean that in case of a security hole in Dovecot, the user still couldn't read other peoples mails. Use this if possible. ----- I don't quite understand this one. If you aren't a local user, what's the uid all about? Do I do something like: create a user for mydomain in /etc/passwd (eg: user:domain_dude, home:/var/dovecot) with a valid home/uid/gid. Plug in the uid/gid/home for domain_dude in the authentication and have a data structure of /var/dovecot/%d/%n/Maildir or %h/%d/%d/Maildir where %h = "/var/dovecot" via /etc/passwd. Something like that?

2 1

[Dovecot] review of my configuration
by Tom Allison 16 Jun '04

16 Jun '04

Over the last week I've set up dovecot and imap and imaps support. I've even tried to break it but it's been doing very well. Now I'm trying to set up a webmail interface. Rather than use the common squirrelmail, I thought I would try openwebmail. Mainly because it's written in perl, of which I am a big fan. However, I ran into some errors in openwebmail that actually may tie back to dovecot. Here's how: dovecot configuration userdb = /etc/passwd passdb = pgsql.... ---this allows me to use the $HOME, uid, gid from the passwd file and not have to carry two copies of it (/etc/passwd and pgsql) However, under openwebmail I don't seem to have this option as they are really determined to require a home, uid, gid for each user that logs in. As witnessed by the following line: Tue Jun 15 20:23:34 2004 - [31572] (unknown) tallison - userinfo error - auth_pgsql.pl, ret -3, Can't execute SQL statement: ERROR: column "uid" does not exist Sure looks familiar doesn't it? (see, it's relevant!) Since I was thinking that maybe it might be interesting to do some email set up to support multiple domains and users some day, and I want to try out the openwebmail sooner than that. I'm getting the impression that it might be easier if I just made the leap today and started to reconfigure everything for multiple domain hosting and all the cool stuff. Now, I can probably muddle through this without too much internal damage. But I keep getting stuck on one point. How can I filter the delivery of email like I do with procmail, when I am delivering mail to many users, none of whom have a /etc/passwd entry? Are there any alternative ideas on how to do this?

1 0

[Dovecot] cvs changelog
by Geo Carncross 15 Jun '04

15 Jun '04

FEI: the CVS changelog is no longer updating. cras's commits look like this: date: YYYY-MM-DD HH:MM:SS +TZDD; author cras; state Exp; lines +1 -0 but cvs2cl.pl (2.50) demands: date: YYYY/MM/DD HH:MM:SS; author cras; state: Exp; lines +1 -0 cvs2cl.pl version 2.55 still can't parse these lines. I patched my cvs2cl.pl so I could still follow dovecot, but I'm not certain these changes actually belong in cvs2cl.pl --- /s/2.55-orig/cvs2cl.pl 2004-06-15 18:58:54.000000000 +0000 +++ /s/2.55/cvs2cl.pl 2004-06-15 18:59:14.000000000 +0000 @@ -2286,7 +2286,7 @@ my ($year, $mon, $mday, $hours, $min, $secs, $author, $state, $rest) = $line =~ - m!(\d+)/(\d+)/(\d+)\s+(\d+):(\d+):(\d+);\s+ + m!(\d+)[/-](\d+)[/-](\d+)\s+(\d+):(\d+):(\d+)(?:.*?);\s+ author:\s+([^;]+);\s+state:\s+([^;]+);(.*)!x or die "Couldn't parse date ``$line''"; die "Bad date or Y2K issues"

2 1

[Dovecot] SSL problems with imap-login
by Terje Rosten 15 Jun '04

15 Jun '04

I am using dovecot-0.99.10.5-1 on RHEL 3 for x86-64: $ uname -a Linux localhost 2.4.21-15.ELsmp #1 SMP Thu Apr 22 00:09:01 EDT 2004 x86_64 x86_64 x86_64 GNU/Linux The client is Horde-2.2.5/IMP-3.2 on Fedora Core 2 on i386. At random imap-login fails with the following error message: $ grep imap /var/log/maillog: Jun 15 18:01:08 anne imap-login: Login: terjeros [10.0.0.1] Jun 15 18:01:17 anne imap-login: Login: terjeros [10.0.0.1] Jun 15 18:15:25 anne imap-login: Login: terjeros [10.0.0.1] Jun 15 18:15:25 anne imap-login: SSL_accept() failed: error:1409C041:SSL routines:SSL3_SETUP_BUFFERS:malloc failure [10.0.0.1] Jun 15 18:15:47 anne imap-login: Login: terjeros [10.0.0.1] Jun 15 18:15:47 anne imap-login: SSL_accept() failed: error:1409C041:SSL routines:SSL3_SETUP_BUFFERS:malloc failure [10.0.0.1] Jun 15 18:16:00 anne imap-login: Login: terjeros [10.0.0.1] Jun 15 18:16:00 anne imap-login: SSL_accept() failed: error:1409C041:SSL routines:SSL3_SETUP_BUFFERS:malloc failure [10.0.0.1] Jun 15 18:16:25 anne imap-login: Login: terjeros [10.0.0.1] Jun 15 18:17:35 anne imap-login: Login: terjeros [10.0.0.1] Jun 15 18:19:43 anne imap-login: SSL_accept() failed: error:1409C041:SSL routines:SSL3_SETUP_BUFFERS:malloc failure [10.0.0.1] Jun 15 18:52:01 anne imap-login: Login: terjeros [10.0.0.1] Jun 15 18:52:01 anne imap-login: SSL_accept() failed: error:1409C041:SSL routines:SSL3_SETUP_BUFFERS:malloc failure [10.0.0.1] Jun 15 18:52:31 anne imap-login: Login: terjeros [10.0.0.1] Jun 15 18:52:53 anne imap-login: Login: terjeros [10.0.0.1] Jun 15 18:53:33 anne imap-login: Login: terjeros [10.0.0.1] Jun 15 18:54:30 anne imap-login: SSL_accept() failed: error:1409C041:SSL routines:SSL3_SETUP_BUFFERS:malloc failure [10.0.0.1] The box has plenty of memory: $ free | grep Mem Mem: 4016976 3696888 320088 0 731608 2279704 Any ideas? OpenSSL or dovecot issue? - Terje

2 2

[Dovecot] flat file mailbox formats
by Timo Sirainen 15 Jun '04

15 Jun '04

I've tried to write the new mbox code in a way that it could be moved into generic flat-file library with mbox-specific code being implemented on top of that. The code would be useful for all formats that require modifying message headers to store the metadata. How many such are there? I suppose all such formats could be implemented by separating mails into 3 logical parts: - header ("From ...\n") - mail data (headers and body) - footer ("\n") Except keeping a separate header and footer is kind of annoying, my current code uses: - mail separator ("\nFrom ...\n") - first message header's skip counter: how many characters to remove from mail separator for the first message (1, for \n before the "From ..") - last message's footer Somewhat uglier, but I think all needed formats could be implemented with it? It's also simper and more efficient to implement.. Besides mbox, I know at least two variations which are used: AAAA-box: - I remember seeing this somewhere years ago, but I'm not sure if it's still used or if it has a real name.. - separator is four ^A characters (ascii 1) and LF - header skip counter is 5 - last message footer would be the same ^A^A^A^A\n dotbox: - mails are stored in SMTP format, ie. lines beginning with '.' are prefixed with another '.'. the '.' prefixes will have to be removed for IMAP, so this isn't as simple as others to implement. - separator is ".\n" - header skip counter is 2 - last message footer is ".\n" Any thoughts?

2 1

[Dovecot] dovecot + Fedora core 1
by Pablo Endres 15 Jun '04

15 Jun '04

Hi, I've installed dovecot-0.99.10.5 using the rpm from Dag Wieers, but when I start it all I get is nothing (but none of the processes are running). I checked the config file and set it up (I'm trying to use it with mysql support, but it doesn't work with traditional config) Any ideas -- Pablo Endres <epablo(a)comvoz.com> ComVoz Communications USA: +1 954 343-2085 Ext 199 Venezuela: +58 212 7713195 Ext 199 Colombia: +57 1 3256840 Ext 199

3 2

[Dovecot] Shared folders?
by Villalovos, John L 15 Jun '04

15 Jun '04

I haven't seen any info on this so I thought I'd ask. Is there support for shared IMAP folders? Quite a few people at work subscribe to the Linux Kernel Mailing List. I thought it would make more sense if there could be a shared LKML folder that they all could use. This would save disk space. Is this posssible? If so how? I am also looking into the idea of doing a local newsgroup of the mailing list but I don't have a news server software setup at the moment. John

3 2

[Dovecot] 1.0-test15 released
by Timo Sirainen 15 Jun '04

15 Jun '04

http://dovecot.org/test/ Maildir code is still having syncing trouble. I thought about fixing mbox code for a chance - if the same problems happen with it too then I at least know that the problems are in indexes instead of maildir syncing itself. So, the biggest change in 1.0-test15 is a new fully functional superfast mbox code. If you can make it corrupt your mboxes I'd like to know about that. I haven't tested it too much yet, but I haven't seen corruption for a while anymore. Superfast as in: - Syncing and modifying the mbox is done in one integrated loop, no more passing through the whole mbox multiple times. - If we know the mbox is synced and we need to modify it, we directly jump to the message(s) needing modification and change only them. This means that with upcoming Dovecot LDA the mbox never needs to be fully parsed. As long as you're not expunging old messages, mboxes with sizes of even gigabytes should be no problem. Still a few remaining issues though: - It gets to infinite loop with 0 sized message body. I'll fix this soon - Recent counters are broken - mbox lock should be kept two extra seconds after syncing. that is required so that we can be sure no-one else has modified the mbox (ie. mtime changes every time) - APPEND command doesn't yet update indexes directly, so they still trigger a full sync - keywords aren't implemented - UW-IMAP style "FOLDER INTERNAL DATA" message is almost supported.. but not quite yet. We're going to use it if it exists, but we won't insert one ourself. This also brings to my mind supporting some other flatfile formats.. Well, I'll write another mail about that.

1 0

[Dovecot] PAM_RHOST item
by Tom Alsberg 15 Jun '04

15 Jun '04

A little problem, which is bugging me: when using PAM authentication, Dovecot (0.99.5) does not set the PAM_RHOST item, so the PAM modules cannot know who the client is. We need this for some PAM module doing access control. Changing passdb-pam.c to pam_set_item it seems trivial, but I'm bugged as to how to get the client name from there. It seems not to be available in the auth_request strut or anything from there. I tried even adding an upwards reference from there to the struct client *, but then I see that there are three structs named client and two structs named auth_request, and somehow I got into trouble of passing it cleanly. Any help or guidance for it is greatly appreciated. (I know Dovecot 0.99 is not really under development and such stuff is done in Dovecot 1.0 now, but that's not yet stable and for now we're using 0.99 where it would help). Thanks, -- Tom -- Tom Alsberg - hacker (being the best description fitting this space) Web page: http://www.cs.huji.ac.il/~alsbergt/ DISCLAIMER: The above message does not even necessarily represent what my fingers have typed on the keyboard, save anything further.

2 1

[Dovecot] password and mysql ?
by Javi Pardo (DAKOTA) 15 Jun '04

15 Jun '04

Hello i am postfix and dovecot with the authentication with the password file of system is possible added virtual domains with mysql? with the two metods? regards dakota(a)dakotabcn.net Administrador Servidor dakotabcn.net LINUX Registrered USER 93707 :) P.o Box 579 08913 Badalona (Barcelona) SPAIN firmas GnuPG en http://pgp.escomposlinux.org/ dakota(a)menta.net || dakota(a)escomposlinux.org - Equipos PIV 2.2 Ghz - 1.5 Gb RAM - W-XP Pro Dual Xeon 2.8Ghz - 1 Gb Ram - Linux Fedora Core 1 Firma para spammers: test(a)spamout.com.ar (no usar!!!)

2 1