March 2006 - dovecot - dovecot.org

Re: [Dovecot] Can I install in the following fashion?
by Lior Okman 07 Mar '06

07 Mar '06

On 3/7/06, Stewart Dean <sdean(a)bard.edu> wrote: > if you run configure --help, you will see this (and more): > > Installation directories: > > --prefix=PREFIX install architecture-independent files in PREFIX > > [/usr/local] > > --exec-prefix=EPREFIX install architecture-dependent files in EPREFIX > > [PREFIX] > > > > By default, `make install' will install all the files in > > `/usr/local/bin', `/usr/local/lib' etc. You can specify > > an installation prefix other than `/usr/local' using `--prefix', > > for instance `--prefix=$HOME'. > > > I see now I missed something so I will redefine my request. If I invoke > configure with: > --prefix=/usr/local/dovecot-bld/<timestamp> > --eprefix=/usr/local/dovecot-bld/<timestamp> > where /usr/local/dovecot-bld/<timestamp> is a directory > Q1: Will I have everything in that one directory so that by tar'ing and > untar'ing that one directory I can tar up everything necessary to run > dovecot on another machine with the same OSlevel/patches/OpenSSL. Will > dovecot be able to reference everything it needs? Assuming all the external shared objects on both systems are in the same place, I don't see why not. > I notice that > > --oldincludedir=DIR C header files for non-gcc [/usr/include] > > will not be there. Will that be a problem? I'm not sure, but I think this setting is used for compile time - it's where dovecot expects to find include files, it doesn't mean that anything will be installed there. If you're really concerned, then use "make -n install", and go over the commands that make would have run, you will be able to see exactly where everything goes. Or you could run "make install" inside a chroot jail. I also seem to recall that I saw a script somewhere that could trace the "make install" procedure and print exactly where it puts everything. It was being used for converting .tar.gz "make-based-installations" to rpms. > Q2: Will dovecot not be able to find system resources it needs? Dovecot should be able to find everything it needs, assuming the configuration files are ok. > Tar'ing up a directory is doable. RPM'ing hundreds of files scattered > here and there, perhaps referenced by others, perhaps with new > additions/deletions you don't know about sounds like an heroic task. Tar`ing a directory is doable, but doesn't lend itself well to reusing components and sane system management. When you use RPM/DPKG for manging your configuration, each package you install is responsible for its own files and nothing more. The packaging system makes sure that nothing conflicts or overwrites existing files. If you accidently untar a file with bad configuration files in it, they will probably overwrite your existing configuration. RPM/DPKG will save your old configuration files. Tar can't help you verify that what you installed is what is actually running. RPM -verify can make sure that no trojan has been installed instead of a file provided in an RPM file. And the list goes on and on. > Does anybody see how simple it is to upgrade UWImap with its one binary? Just as long as there is only one binary. AFAIK, UWImap doesn't support configuration files, on the assumption that the sysadmin probably doesn't know enough to create a valid configuration. The downshot of that is that there is a limit to what you can do with UWImap's one binary :-) Lior > > Lior Okman wrote: > > Looking at the debianized version, the bulk of the files are placed in > > € > > or under /usr/lib/dovecot, with all of the configuration files in > > € > > /etc/dovecot, and relevant binaries under /usr/bin and /usr/sbin. > > € > > > > € > > However, reading from the comment in the begining of the default > > € > > dovecot.conf file, you can probably compile your own version of > > € > > dovecot where you specify the following parameters to configure: > > € > > "--prefix=/usr --sysconfdir=/etc --localstatedir=/var > > € > > --with-ssldir=/etc/ssl". > > € > > Just make sure to replace all the paths with where you want to install > > € > > this version of dovecot. > > € > > > > € > > Lior > > € > > > > € > > On 3/7/06, Stewart Dean <sdean(a)bard.edu> wrote: > > € > > > >> Hmmm, hadn't thought of RPM. But I would like a direct answer to my > >> > > € > > > >> question, which was: Can I just tar up everything in a dovecot-only > >> > > € > > > >> prefix directory (defined in the invocation of configure) when the make > >> > > € > > > >> and make install is done, and then untar/extract it in a directory of > >> > > € > > > >> the same name over on another machine with the same OS, patches and > >> > > € > > > >> OpenSSL? Are there Dovecot dependencies outside prefix directory. > >> > > € > > > > € > > > >> My OS is AIXV5.3 maintenance/tech level 4. There is no distro RPMs for > >> > > € > > > >> same, so I am building it myself. > >> > > € > > > > € > > > >> Lior wrote: > >> > > € > > > >>> The problem you are describing is solved with tools like RPM and DEB. > >>> > > € > > > > € > > > >>> You can install/remove an entire package with a single command, you > >>> > > € > > > >>> can verify the installation with a single command, you can safetly > >>> > > € > > > >>> upgrade with a single command, and safetly revert to an older version > >>> > > € > > > >>> with a single command. > >>> > > € > > > > € > > > >>> These tools allow you to find out exactly which file belongs to what > >>> > > € > > > >>> package, and they prevent conflicting files from two different > >>> > > € > > > >>> packages from being installed. Not to mention (almost) automatic (at > >>> > > € > > > >>> least on debian) dependency resolving for packages. > >>> > > € > > > > € > > > >>> If you're using Debian, you can just "apt-get install dovecot-imap > >>> > > € > > > >>> dovecot-pop", and have the dpkg handle all of the issues you > >>> > > € > > > >>> mentioned. If you're using an RPM based distro- try yum or apt-rpm. > >>> > > € > > > > € > > > >>> Lior > >>> > > € > > > > € > > > > € > > > >> Timothy White wrote: > >> > > € > > > >>>> If you're using Debian, you can just "apt-get install dovecot-imap > >>>> > > € > > > >>>> dovecot-pop", and have the dpkg handle all of the issues you > >>>> > > € > > > >>>> mentioned. If you're using an RPM based distro- try yum or apt-rpm. > >>>> > > € > > > > € > > > > € > > > >>> And there is nothing stopping you making a deb package, from a newer > >>> > > € > > > >>> version of dovecot, that Debian has, AND, duplicating the server, so > >>> > > € > > > >>> you can do a test upgrade... Of course, with any upgrade, someone will > >>> > > € > > > >>> notice something ;-) > >>> > > € > > > > € > > > >>> Tim > >>> > > € > > > >>> -- > >>> > > € > > > >>> Linux Counter user #273956 > >>> > > € > > > > € > > > > € > > > >> -- > >> > > € > > > >> ==== > >> > > € > > > >> Stewart Dean, Unix System Admin, Henderson Computer Resources > >> > > € > > > >> Center of Bard College, Annandale-on-Hudson, New York 12504 > >> > > € > > > >> sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035 > >> > > € > > > > € > > > > € > > > > -- > ==== > Stewart Dean, Unix System Admin, Henderson Computer Resources > Center of Bard College, Annandale-on-Hudson, New York 12504 > sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035 > >

1 0

Re: [Dovecot] Can I install in the following fashion?
by Stewart Dean 07 Mar '06

07 Mar '06

if you run configure --help, you will see this (and more): > Installation directories: > --prefix=PREFIX install architecture-independent files in PREFIX > [/usr/local] > --exec-prefix=EPREFIX install architecture-dependent files in EPREFIX > [PREFIX] > > By default, `make install' will install all the files in > `/usr/local/bin', `/usr/local/lib' etc. You can specify > an installation prefix other than `/usr/local' using `--prefix', > for instance `--prefix=$HOME'. > > For better control, use the options below. > > Fine tuning of the installation directories: > --bindir=DIR user executables [EPREFIX/bin] > --sbindir=DIR system admin executables [EPREFIX/sbin] > --libexecdir=DIR program executables [EPREFIX/libexec] > --datadir=DIR read-only architecture-independent data [PREFIX/share] > --sysconfdir=DIR read-only single-machine data [PREFIX/etc] > --sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com] > --localstatedir=DIR modifiable single-machine data [PREFIX/var] > --libdir=DIR object code libraries [EPREFIX/lib] > --includedir=DIR C header files [PREFIX/include] > --oldincludedir=DIR C header files for non-gcc [/usr/include] > --infodir=DIR info documentation [PREFIX/info] > --mandir=DIR man documentation [PREFIX/man] I see now I missed something so I will redefine my request. If I invoke configure with: --prefix=/usr/local/dovecot-bld/<timestamp> --eprefix=/usr/local/dovecot-bld/<timestamp> where /usr/local/dovecot-bld/<timestamp> is a directory Q1: Will I have everything in that one directory so that by tar'ing and untar'ing that one directory I can tar up everything necessary to run dovecot on another machine with the same OSlevel/patches/OpenSSL. Will dovecot be able to reference everything it needs? I notice that --oldincludedir=DIR C header files for non-gcc [/usr/include] will not be there. Will that be a problem? Q2: Will dovecot not be able to find system resources it needs? Tar'ing up a directory is doable. RPM'ing hundreds of files scattered here and there, perhaps referenced by others, perhaps with new additions/deletions you don't know about sounds like an heroic task. Does anybody see how simple it is to upgrade UWImap with its one binary? Lior Okman wrote: > Looking at the debianized version, the bulk of the files are placed in > € > or under /usr/lib/dovecot, with all of the configuration files in > € > /etc/dovecot, and relevant binaries under /usr/bin and /usr/sbin. > € > > € > However, reading from the comment in the begining of the default > € > dovecot.conf file, you can probably compile your own version of > € > dovecot where you specify the following parameters to configure: > € > "--prefix=/usr --sysconfdir=/etc --localstatedir=/var > € > --with-ssldir=/etc/ssl". > € > Just make sure to replace all the paths with where you want to install > € > this version of dovecot. > € > > € > Lior > € > > € > On 3/7/06, Stewart Dean <sdean(a)bard.edu> wrote: > € > >> Hmmm, hadn't thought of RPM. But I would like a direct answer to my >> > € > >> question, which was: Can I just tar up everything in a dovecot-only >> > € > >> prefix directory (defined in the invocation of configure) when the make >> > € > >> and make install is done, and then untar/extract it in a directory of >> > € > >> the same name over on another machine with the same OS, patches and >> > € > >> OpenSSL? Are there Dovecot dependencies outside prefix directory. >> > € > > € > >> My OS is AIXV5.3 maintenance/tech level 4. There is no distro RPMs for >> > € > >> same, so I am building it myself. >> > € > > € > >> Lior wrote: >> > € > >>> The problem you are describing is solved with tools like RPM and DEB. >>> > € > > € > >>> You can install/remove an entire package with a single command, you >>> > € > >>> can verify the installation with a single command, you can safetly >>> > € > >>> upgrade with a single command, and safetly revert to an older version >>> > € > >>> with a single command. >>> > € > > € > >>> These tools allow you to find out exactly which file belongs to what >>> > € > >>> package, and they prevent conflicting files from two different >>> > € > >>> packages from being installed. Not to mention (almost) automatic (at >>> > € > >>> least on debian) dependency resolving for packages. >>> > € > > € > >>> If you're using Debian, you can just "apt-get install dovecot-imap >>> > € > >>> dovecot-pop", and have the dpkg handle all of the issues you >>> > € > >>> mentioned. If you're using an RPM based distro- try yum or apt-rpm. >>> > € > > € > >>> Lior >>> > € > > € > > € > >> Timothy White wrote: >> > € > >>>> If you're using Debian, you can just "apt-get install dovecot-imap >>>> > € > >>>> dovecot-pop", and have the dpkg handle all of the issues you >>>> > € > >>>> mentioned. If you're using an RPM based distro- try yum or apt-rpm. >>>> > € > > € > > € > >>> And there is nothing stopping you making a deb package, from a newer >>> > € > >>> version of dovecot, that Debian has, AND, duplicating the server, so >>> > € > >>> you can do a test upgrade... Of course, with any upgrade, someone will >>> > € > >>> notice something ;-) >>> > € > > € > >>> Tim >>> > € > >>> -- >>> > € > >>> Linux Counter user #273956 >>> > € > > € > > € > >> -- >> > € > >> ==== >> > € > >> Stewart Dean, Unix System Admin, Henderson Computer Resources >> > € > >> Center of Bard College, Annandale-on-Hudson, New York 12504 >> > € > >> sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035 >> > € > > € > > € > -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

1 0

[Dovecot] dspam plugin mailing list?
by Johannes Berg 07 Mar '06

07 Mar '06

Hi, Every once a while I get mail about my dspam plugin. While that's great (tells me people are using it or at least like the idea), sometimes I think the discussions then should be accessible to others. I'm thinking of setting up a new mailing list for it so answers get archived, are searchable, and I don't necessarily have to reply to everything. I'm not sure if that's feasible though, there probably aren't *that* many users, and sometimes the questions are more dovecot questions. Would anyone on this list (esp. Timo of course) mind if I were to note on the plugin page that discussion and questions should be sent to this (the dovecot) mailing list? I'll still be reading here and answering questions, of course, but then if something crops up that's more dovecot than plugin related it's at the right place already, or if I'm off for a few days and someone else knows the answer... If there are any objections I'll just set up a private mailing list instead and ask anyone interested to join (it'd be very low volume I guess) :) johannes

2 2

[Dovecot] mbox sync: UID inserted in the middle of mailbox...
by Simon Bowden 07 Mar '06

07 Mar '06

Hi, We're getting a lot of errors like this: Mar 7 10:02:35 imapserver dovecot: imap(user1): mbox sync: UID inserted in the middle of mailbox /home/user1/mail/mail/INBOX.Trash (8 > 2, seq=2,idx_msgs=6) We have several hundred people using the server, and at least 22 have had this error in the past 24 hours. The numbers at the end change between each user, which I guess you'd expect. I was able to make the errors go away for one user by removing the index files (rm -rf ~/mail/.imap/INBOX), so I'm guessing they were corrupt. However, the problem with this is that: 1) It requires user intervention 2) The symptom is that they aren't seeing any new mail in the affected mailbox. I had thought that the indexing stuff would not *give up*, but would reindex a directory if there was a problem. Anyone able to help? Some info on our setup: /home/user is nfs-mounted. We allow them to configure their mbox/maildir type and location, but obviously this is only relating to mbox ones. Here's the config file, stripped of comments and blank lines: ==================== protocols = imap imaps ssl_cert_file = /etc/ssl/certs/imapd.cert ssl_key_file = /etc/ssl/private/imapd.pem ssl_ca_file = /etc/ssl/certs/cacert.pem log_timestamp = "%Y-%m-%d %H:%M:%S " login_processes_count = 6 first_valid_uid = 40 mail_extra_groups = default_mail_env = mbox:~/mail/:INBOX=~/.incoming-mail mmap_disable = yes mail_drop_priv_before_exec = yes protocol imap { mail_executable = /usr/local/mail/imap-wrapper imap_client_workarounds = outlook-idle delay-newmail tb-extra-mailbox-sep } protocol pop3 { } auth default { mechanisms = plain gssapi passdb pam { args = session=yes * } userdb passwd { } user = root } plugin { } ==================== /usr/local/mail/imap-wrapper is just a script that lets them configure the setup a bit (effectively change value of MAIL, and some namespace stuff), ultimately running /usr/lib/dovecot/imap. The nfs mount options on the home directory mount are: rw,hard,intr,rsize=8192,wsize=8192,nosuid,nodev,vers=3,proto=udp Thanks! Cheers, - Simon

2 1

[Dovecot] Dovecot as a smart IMAP proxy
by Timo Sirainen 07 Mar '06

07 Mar '06

Do you see a use for an IMAP proxy where the proxy would be able to execute hooks which modify mail contents, such as transparent encrypting/decrypting mails, or maybe some virus-filtering? It would need at least some kind of IMAP command/reply parsing capabilities, so it might be able to do all kinds of other things. Maybe one potential use case would be Cyrus Murder-like proxying to multiple IMAP servers to distribute the mailboxes. But that might be done better as an imap process plugin, or maybe as IMAP mail storage backend. Anyway, the reason I'm asking this is because I was asked to add mail encryption/decryption capabilities to Dovecot's IMAP proxy, but I'm not sure what would be the best way to handle this. In any case it would be a plugin or a new binary which is executed instead of imap binary, but can I do it in a way that would actually be useful for Dovecot project in general?

8 14

[Dovecot] [IMAP] Strange! No problem when I import mails from local to server.
by Xueron Nee 07 Mar '06

07 Mar '06

Hi, All: I hava just post a question that says when I move mail from one folder to another, mails were holded in the tmp directory of the target folder. I try to move mails from server to local and then, move them from the local folder to the server side folder, it works fine :) I refresh the tmp directory and could see tmp files created-unlinked, and all mail imported to the target folder currectly. What's the problem when I move mails between server-side folders? -- Xueron Nee <xueron(a)gmail.com>

1 0

[Dovecot] [IMAP] mails holded in tmp directory
by Xueron Nee 07 Mar '06

07 Mar '06

Version: 1.0.beta3 OS: Redhat AS 4 I use the cvs version of Dovecot to run my IMAP server. When I move some mails from one folder to another, only 1 or 2 mails are moved, while others were holded in the tmp directory of the target folder. So, what's the matter? I use becky and Outlook as client, and both of the two have the same problem. Thanks :) -- Xueron Nee <xueron(a)gmail.com>

1 0

[Dovecot] Shared Folders (1.0beta3)
by Timothy White 07 Mar '06

07 Mar '06

A few quick questions, as documentation seems to be sparse. * Is there a way to force a shared folder to be subscribed to? If I am using SquirrelMail I have a plugin to do that, but not if they are using another IMAP client. * Are there some sort of ACL's on shared folders, so that I can (hopefully with a sql backend), allow different users different permissions on the folder? * Is it a bug that we can't subscribe to the shared folder, only to it's sub folders? (and is there a way to work around this, i.e. if the shared folder isn't really a Maildir, but it's sub folders are? Other than that, so far, my glimpse at 1.0beta3 is looking very good, and came at the right time, as I was thinking I might need to use Cyrus for the project I'm working on atm... Thanks Tim -- Linux Counter user #273956

2 2

RE: [Dovecot] getting lock error
by Bas van den Dikkenberg 07 Mar '06

07 Mar '06

Thanx fot the tip this solves problem with pop3 but not with imap With imap I get imap(basweb(a)dikkenberg.net): Mar 07 00:32:35 Error:mailstore/vmail/dikkenberg.net/basweb/.subscriptions failed with subscription file file_wait_lock(): No locks available I'm running redhat enterprise linux 4.0 with dovecot 0.99.11 but redhat doesn't provide the new version yet with up2date is there an rpm so I can update? Met vriendelijk groet, Bas van Dikkenberg GISkit bv BFVD1-RIPE Tel: +3130-6340430 Fax: +3130-6342433 Prive Tel: +3130-6372769 Mob: +316-52384841 -----Oorspronkelijk bericht----- Van: dovecot-bounces(a)dovecot.org [mailto:dovecot-bounces@dovecot.org] Namens Timo Sirainen Verzonden: maandag 6 maart 2006 21:55 Aan: Bas van den Dikkenberg CC: dovecot(a)dovecot.org Onderwerp: Re: [Dovecot] getting lock error On Mon, 2006-03-06 at 09:11 +0100, Bas van den Dikkenberg wrote: > I’m getting this error for al my users does anybody know wat the > problem is and how i can fix it > > pop3(bas(a)giskit.nl): Mar 06 09:10:37 Error: file_wait_lock() failed > with index file /mailstore/vmail/giskit.nl/bas/.INBOX/.imap.index: No > locks available First of all, use 1.0betas instead of 0.99.x. Then read NFS section in http://wiki.dovecot.org/QuickConfiguration

1 0

[Dovecot] using mbox but, can't create subfolders
by blaq b0x 07 Mar '06

07 Mar '06

Hi, I'm using mbox format w/ dovecot 1.0b3. I tried moving over my mail from a uw-imap server. Everything works fine except I can't create subfolders. Is there something I'm doing wrong or is this a limitation of dovecot? How can I fix this? Thanks, --------------------------------- Yahoo! Mail Bring photos to life! New PhotoMail makes sharing a breeze.

2 3