Re: [Dovecot] b13 Compile error on Solaris 10 (Sparc)
[EMAIL PROTECTED] wrote: > All betas so far have compiled without problems on my setup, but something > breaks in b13. > > This problem occurs with both make and gmake. > > Below are outputs from make and gmake. Exactly same thing here, Solaris 10 x86, with Sun CC 12 and gcc. Tomi
Re: [Dovecot] live and backup auth database
John Lyons wrote: Is there a way of setting dovecot to use two mysql authentication databases, either in a live/failover format or a round robin method. Yes, just provide as many MySQL hosts as you wish in "sql.conf" "connect = host=mysql1 host=mysql2 dbname=mail user=dovecot .." MySQL hosts are queried in round-robin fashion. Tomi
Re: [Dovecot] Webmail Recommendation
Peter Sparkes wrote: Hi, I want to install webmail. I am using Dovecot with Exim4. Recommendations requested please. RoundCube is nice, but development is slow http://roundcube.net/ @mail is very good, has optional user management module also. @mail is commercial but then again it is the best webmail I have seen sofar. http://atmail.com/ Tomi
Re: [Dovecot] v1.1.beta14 released (Compile Error)
Timo Sirainen wrote: On 20.1.2008, at 19.40, Jerry Yeager wrote: Undefined symbols: "_posix_fallocate", referenced from: _file_set_size in liblib.a(file-set-size.o) Fixed: http://hg.dovecot.org/dovecot/rev/6c868e7fe7b2 You can also fix it by removing HAVE_POSIX_FALLOCATE from config.h Same problem and fix applies to Solaris 10. Tomi
Re: [Dovecot] corrupted index?
Gary Funck wrote: On 02/02/08 12:27:14, Ronald MacDonald wrote: Where does Dovecot put the INDEX? My problem disappeared as soon as I set INDEX=MEMORY. Does this mean that as long as the dovecot server is long-running that it will cache indexes into local memory? Or is the index kept in memory only for the per-client connection? Only for per connection. Store indexes on local disk if you wish to have persistent indexes but avoid problems with NFS. Do something like this mail_location = maildir:~/Maildir:INDEX=/var/lib/dovecot/%u Tomi
Re: [Dovecot] Scheduled folder purging
Pietro wrote: Thanks a lot Ronald. Is there any issue I must consider about dovecot indexes? Dovecot will log an warning but nothing much else, so it is pretty safe. Tomi -Pietro. 2008/2/18, Ronald MacDonald <[EMAIL PROTECTED]>: On 18/02/2008, Pietro <[EMAIL PROTECTED]> wrote: Hi all. I'm looking for a way to empty user's trash folder. Can message deletion or folder purging be scheduled? Thanks in advance. -Pietro. Of course. Run a cron job to search, for example, for files older than a certain date. Delete all files in /cur which are older than 30 days: /usr/bin/find /home/vmail/*/.Junk/cur -mtime +30 -type f -daystart -exec rm '{}' \; Hope that helps. Kind regards, Ronald. -- Ronald MacDonald http://www.rmacd.com/ 0777 235 1655
Re: [Dovecot] v1.1.rc1 released
Timo Sirainen wrote: Finally the first v1.1 release candidate. Please test so we can have a fully stable v1.1.0 release. v1.1.betas are already running in a few large installations, so I don't expect there to be many bugs left. So far it's been smooth ride for me, upgraded from 1.0.10 last night. Quick specs of my setup * Solaris 10 x86 * Compiled with Sun Studio 12 * Maildir storage on ZFS * Dovecot indexes on compressed ZFS * MySQL 5 as user data backend * Postfix with Dovecot SASL and Dovecot Deliver * Plugins in use: quota, imap quota, fts, fts squat * Users ~30 * Clients in use: Thunderbird, RoundCube Webmail, Nokia smartphones Tomi
Re: [Dovecot] 1.1rc1: Maximum number of mail processes exceeded
Ralf Hildebrandt wrote: So how can I raise the filedescriptor limit above 1024 (linux-2.6.24.2, Debian)? In /etc/security/limits.conf, set ## domain typeitemlimit * softnofile 8192 * hardnofile 8192 And in /etc/profile do ulimit -HSn 8192 Log out from shell and log back in and you have new settings in effect. Tomi
Re: [Dovecot] Unexpected behaviour when deleteing a big mailbox
Timo Sirainen wrote: xfs is a lot slower than ext3 with maildir at least in my tests. Do you have 'dir_index' option enabled on ext3? Tomi
Re: [Dovecot] 1.0.rc29 released
Jeff A. Earickson wrote: My one concern about dovecot is the "feeping creaturism" in the code. Why does it have to be an LDA? That is what procmail is for. And designing your own mailbox format (dbox?) seems dangerous too. Both features were done for paying customer. Dovecot LDA is lot more than procmail is, for example, how would you implement a proper out of office reply only using procmail? You also have great performance benefits when using Dovecot LDA over procmail, indexing for both Maildir and mbox and header padding for mbox. Tomi
Re: [Dovecot] Problems using GFS2 and clustered dovecot
On Thu, 2007-04-05 at 09:58 +0100, David Craigon wrote: > I am trying to use dovecot. I've got a GFS2 shared volume on two servers > with dovecot running on both. On one server at a time, it works. Do you have mmap disabled? Tomi
Re: [Dovecot] Memory Errors
Paul Hamby wrote: I just loaded 1.0.0 on a new box and am getting the following errors periodically. Run memtest86, I bet you have faulty memory or CPU. Tomi
Re: [Dovecot] High CPU utilization on Solaris 10
Peter Eriksson wrote: We also saw a lot of pollsys() calls when trussing it. We haven't had time to debug it further though. I tried compiling the source file that calculates the ioloop timeout using "-O" instead of "-fast" but that didn't make any difference. If you are using Sun Studio 12 compile all with "-xtarget=native -xO3" and see if it helps for your high CPU usage, for me it did. Tomi
Re: [Dovecot] v1.1.beta1 released
Timo Sirainen wrote: http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta1.tar.gz Cannot compile this on Solaris 10 with Sun Studio 12. cc -DHAVE_CONFIG_H -I. -I. -I../.. -I/opt/csw/mysql5/include/mysql -I/opt/csw/include -xO3 -xtarget=native -xc99 -I/opt/csw/include-c istream-seekable.c source='istream-tee.c' object='istream-tee.o' libtool=no \ DEPDIR=.deps depmode=none /bin/bash ../../depcomp \ cc -DHAVE_CONFIG_H -I. -I. -I../.. -I/opt/csw/mysql5/include/mysql -I/opt/csw/include -xO3 -xtarget=native -xc99 -I/opt/csw/include-c istream-tee.c "istream-tee.c", line 102: void function cannot return value "istream-tee.c", line 172: void function cannot return value cc: acomp failed for istream-tee.c gmake[4]: *** [istream-tee.o] Error 2 gmake[4]: Leaving directory `/opt/src/dovecot-1.1.beta1/src/lib' gmake[3]: *** [all] Error 2 gmake[3]: Leaving directory `/opt/src/dovecot-1.1.beta1/src/lib' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/opt/src/dovecot-1.1.beta1/src' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/opt/src/dovecot-1.1.beta1' gmake: *** [all] Error 2 Tomi
Re: [Dovecot] What is your dovecot setup?
Timothy Murphy wrote: I'd be really grateful if someone running a dovecot IMAP (or IMAPS) server could tell me exactly how their email folders are arranged. A while back when I was running mid-size Dovecot installation on which mail spool was arranged something like /san/%LUN/domain/%UID/inbox Indexes were at /var/lib/dovecot/%LUN/domain/%UID/ or thereabouts. Currently I am running just a small personal server where I use ~/Maildir/. What is the mail_location setting in /etc/dovecot.conf ? mail_location = maildir:~/Maildir:INDEX=/var/spool/dovecot/%u Homes are on RAID-5 (compressed ZFS), INDEX location is on RAID-10 (also compressed ZFS). Does the client see an inbox folder? Yes. If so, what directory on the server contains these email messages? Standard Maildir locations ~/Maildir/new for unread messages ~/Maildir/cur for read messages Tomi
Re: [Dovecot] Dovecot + OCFS2
Jon Blazquez wrote: The system works fine but when there are mailing lists the load increases dramatically. Any suggestions? First thing that I would do is to reduce number of concurrent deliver processes. I have no clue how this is done with Sendmail but with Postfix one could adjust deliver process "maxproc" value in master.cf. Tomi
Re: [Dovecot] Released v1.1.beta3
Sergey wrote: Hi Timo I've triedt to compile v1.1.beta3 on OpenSolaris (x86) with SunStudio 12. options invalid; UNIX 03 and POSIX.1-2001 applications require the use of c99" export CFLAGS="-x03 -xtarget=native -xc99" ./configure ..etc.. Your optimization flags may vary. Tomi