- dovecot - dovecot.org

[Dovecot] Problem with users home...
by websafe 27 Apr '05

27 Apr '05

Hi :) I hope this short example shows what problem I have: # returns users homedir from /etc/passwd grep user1 /etc/passwd | cut -d':' -f6 # result: /home/group-subdir/user1 And the logfile... #maillog imap-login: Login: user1 [192.168.0.253] imap(user1): mkdir(/home/user1/Maildir/.Trash) failed: No such file or directory Why Dovecot tries to create /home/user1/Maildir/.Trash and NOT /home/group-subdir/user1/Maildir/.Trash as in /etc/passwd ??? Is there any solution? I'm running 0.99.14 # cat /etc/dovecot.conf ssl_disable = yes disable_plaintext_auth = no login = imap verbose_proctitle = yes default_mail_env = maildir:/home/%u/Maildir auth = default auth_mechanisms = plain auth_userdb = passwd /etc/passwd auth_passdb = shadow /etc/shadow auth_user = root Thanks in advance, -- websafe

3 2

[Dovecot] Mozilla Thunderbird 1.0 and Dovecot/IMAP problem.
by websafe 27 Apr '05

27 Apr '05

If you notice problems with your imap folders and "Lost transaction logfile" when connecting Dovecot (0.99 / 1.0-testXX) via IMAP, upgrade to Thunderbird 1.02. This should help. -- websafe

1 0

[Dovecot] Track when user last checked mail
by Del Stoliker 27 Apr '05

27 Apr '05

First off I've just got to say thanks. We just upgraded from UW to Dovecot migrating from mbox to maildir. Wow, what a difference! Load average used to hang around 5.0 during business hours and could get up to 20+ on a bad day. Now we rarely break 1.0! I'm wondering if there's a way to keep track of the last time a user checked their email and whether they checked it using POP or IMAP. We're trying to gather statistics on what protocols our users use and find accounts that haven't been checked for a long time. We used to be able to do some of this with the finger command and the user's mbox. I found a script called "mfinger" that works better with Maildir, but it's designed for Courier. Any ideas? Thanks!

6 6

[Dovecot] docecot and procmail?
by Dan Stromberg 27 Apr '05

27 Apr '05

Is dovecot still considered unreliable when combined with NFS? Is this true for mbox only, or Maildir as well? If dovecot Is still considered unreliable with NFS, how about having a dovecot mode that would chain into procmail for delivery, so that dovecot doesn't (necessarily) have to reinvent that wheel? Thanks!

4 4

[Dovecot] Why is "UIDVALIDITY changed" fatal?
by Chris Wakelin 27 Apr '05

27 Apr '05

I've got several users testing Dovecot IMAP at the moment, but some of them are also accessing their mail via UW-IMAP at other times. (I've warned them about accessing the same folder simultaneously via UW-IMAP and Dovecot!) In addition, we have special folders "AutoSpam" and "Trash" that pruned using Washington's "mailutil" automatically every so often. Of course, Dovecot's indexes will become invalid in such cases, but they seem to get rebuilt automatically OK. However, in some cases UW-IMAP seems to change the UIDVALIDITY value (not sure why!) and when Dovecot tries to sync it notices this and gives up with a fatal error on opening that folder. Opening the folder a second time is then OK. I was wondering why Dovecot can't just rebuild the indexes silently in such cases (which seems to be done by returning "0" from the mbox_sync_loop() routine)? Best Wishes, Chris --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+-- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

3 11

[Dovecot] Basic configuration problem "not a directory"
by Einar Flesaker 26 Apr '05

26 Apr '05

Hi, I've been struggling with getting dovecot up and running the last hour, but I seem to be stuck. When logging in (which I can do successfully) my connection is dropped, and the following is outputted to my dovecot log: dovecot: Apr 26 09:56:52 Fatal: chdir(/bin/false) failed with uid 513: Not a directory dovecot: Apr 26 09:56:52 Error: child 27345 (imap) returned error 89 .. But I'm certain the relevant directories exist. Relevant configuration details are as follows: * [dovecot.conf] valid_chroot_dirs = /var/spool/vmail default_mail_env = maildir:/var/spool/vmail/$d/%n/ * [passwd sample] einar@domain.com::513:513:/var/spool/vmail/domain.com/:/bin/false:: * [directory listing] [root@server einar]# pwd /var/spool/vmail/domain.com/einar [root@server einar]# ls -l totalt 12 drwx------ 2 virtmail virtmail 4096 apr 26 07:27 cur drwx------ 2 virtmail virtmail 4096 apr 26 08:48 new drwx------ 2 virtmail virtmail 4096 apr 26 08:48 tmp I'd be very grateful for any assistance, any ideas of what might be wrong. Is there any easy way to see the relevant directory that /bin/false exits on? -Einar-

3 7

[Dovecot] many instances om imap and imap-login
by Jon 26 Apr '05

26 Apr '05

Hi, Im using dovecote as my IMAP interface. However i do have a lot of imap instances. its only 7 user using the system as i get this. please advice. 1230 ? S 0:00 imap-login 1309 ? S 0:00 imap-login 1387 ? S 0:00 imap-login 1388 ? S 0:00 imap-login 1389 ? S 0:00 imap-login 1390 ? S 0:00 imap-login 1391 ? S 0:00 imap-login 1399 ? S 0:00 imap 1400 ? S 0:00 imap 1401 ? S 0:00 imap 1402 ? S 0:00 imap 1406 ? S 0:00 imap 1442 ? S 0:00 imap 1636 ? S 0:00 imap 1637 ? S 0:00 imap-login 1638 ? S 0:00 imap-login 1640 ? S 0:00 imap 1683 ? S 0:00 imap-login 1684 ? S 0:00 imap-login 1685 ? S 0:00 imap-login 1686 ? S 0:00 imap-login 1687 ? S 0:00 imap-login 1689 ? S 0:00 imap-login 1692 ? S 0:00 imap 1693 ? S 0:00 imap 1697 ? S 0:00 imap 1698 ? S 0:00 imap 1699 ? S 0:00 imap 1701 ? S 0:00 imap 1914 ? S 0:00 imap 1916 ? S 0:00 imap 1965 ? S 0:00 imap-login 1968 ? S 0:00 imap 1969 ? S 0:00 imap 1971 ? S 0:00 imap-login 1974 ? S 0:00 imap-login 1980 ? S 0:00 imap-login 1981 ? S 0:00 imap-login 2068 ? S 0:00 imap 2069 ? S 0:00 imap 2071 ? S 0:00 imap 2072 ? S 0:00 imap-login 2079 ? S 0:00 imap 2157 ? S 0:00 imap-login 2158 ? S 0:00 imap-login 2159 ? S 0:00 imap-login 2160 ? S 0:00 imap-login 2161 ? S 0:00 imap-login 2162 ? S 0:00 imap-login 2332 ? S 0:00 imap 2337 ? S 0:00 imap 2338 ? S 0:00 imap 2339 ? S 0:00 imap 2340 ? S 0:00 imap 2341 ? S 0:00 imap-login 2342 ? S 0:00 imap-login 2386 ? S 0:00 imap 2387 ? S 0:00 imap-login 3095 ? S 0:00 imap 3096 ? S 0:00 imap-login /jon

3 2

Re: [Dovecot] many instances om imap and imap-login
by Dominic Marks 26 Apr '05

26 Apr '05

On Tuesday 26 April 2005 15:19, you wrote: > Thanks for extensive answer. > > I will look into all your suggestions. Please keep the mailing list in the response, it allows other people to provide advice, follow the conversation, and you get, hopefully, complete solutions stored in the archives waiting for Google to index. > Answers to you questions: > > Are the mailboxes being accessed via Webmail?: > yes they can but arent at the moment (squirrelmail) Webmail can cause lots of extra connections to me made. > What Mail application are your users using?: > Thunderbird 1.0.2 Don't have much experience with this client, although it works when I've tried it. Others may be able to provide experience here. > Have you checked what state the connections are in?: > Do you mean of they are connected or not? when I run top I do see > instances called IMAP owned by each user so I asume they are connected mail# netstat -f inet -p tcp | grep imap tcp4 0 0 mailserver.imap client01.1386 ESTABLISHED tcp4 0 0 mailserver.imap client02.1344 ESTABLISHED tcp4 0 0 mailserver.imap client01.1108 ESTABLISHED tcp4 0 0 mailserver.imap client03.54607 ESTABLISHED mail# netstat -a -f inet -p tcp | grep "*.imap*" tcp4 0 0 *.imaps *.* LISTEN tcp4 0 0 *.imap *.* LISTEN FreeBSD 5.4 with a few Outlook and KMail clients. > /jon > > Dominic Marks said the following on 2005-04-26 16:11: > >On Tuesday 26 April 2005 14:58, Jon wrote: > >>Hi, > >> > >>Im using dovecote as my IMAP interface. However i do have a lot of imap > >>instances. its only 7 user using the system as i get this. please advice. > > > >Having lots of processes running isn't automatically a bad thing, but you > > do > > > >seem to have quite a lot of imap and imap-login processes, so: > >>From a dovecot.conf on a server I run being used by about 7 people: > > > > (Comments are from dovecot-sample.conf) > > > ># 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 = no > > > >So if security is less of a concern than having many processes running, > > you should set this to no. > > > ># 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 = 1 > > > >I set this low because I don't need the extra processes. > > > ># 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 > > > >You might want to set this to something like 4? > > > ># 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 > > > >Probably no need to worry about this. > > > >>1230 ? S 0:00 imap-login > >> 1309 ? S 0:00 imap-login > > > > <snip> > > > >> 2387 ? S 0:00 imap-login 3095 ? S 0:00 imap > >> 3096 ? S 0:00 imap-login > >> > >>/jon > > > >Other things to think about: > > > >Are the mailboxes being accessed via Webmail? > >What Mail application are your users using? > >Have you checked what state the connections are in? > > > >HTH, -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK.

1 0

[Dovecot] can't chroot "auth process" (dovecot-1.0-test68)
by John Wong 26 Apr '05

26 Apr '05

OS: OpenBSD/i386 dovecot: dovecot-1.0-test68 dovecot can not start, when i chroot "auth process" can i defined the "auth-work.XXX" unix socket path?? mail.log ----------------------------------------- Dovecot v1.0-test68 starting up auth(default): mysql: Connected to (null) (mail) Auth process died too early - shutting down auth(default): net_connect_unix(/var/dovecot//auth-work.12922) failed: No such file or directory child 12922 (auth) returned error 89 ----------------------------------------- dovecot.conf ----------------------------------------- base_dir = /var/dovecot/ protocols = imap imaps pop3 pop3s ssl_cert_file = /etc/ssl/certs/mail.crt ssl_key_file = /etc/ssl/private/mail.key ssl_parameters_file = /var/dovecot/ssl-parameters.dat disable_plaintext_auth = no login_dir = /var/dovecot/login login_user = _dovecot login_processes_count = 1 valid_chroot_dirs = /var/spool/postfix/var/mail mail_debug = yes default_mail_env = maildir:%h mmap_no_write = yes protocol imap { } protocol pop3 { } auth_verbose = yes auth_debug = yes auth default { mechanisms = plain passdb sql { args = /etc/dovecot-sql.conf } userdb static { args = uid=32765 gid=32765 home=/var/spool/postfix/var/mail/%u/./ } user = _dovecot-auth chroot = /var/spool/postfix } -----------------------------------------------------------

1 0

[Dovecot] whoson support
by Simon Dick 26 Apr '05

26 Apr '05

Is anyone working on integrating whoson support into dovecot? I would do it myself but currently I'm short on time and will need that support, anyone got any tips? :) -- Simon Dick <simon(a)advantage-interactive.com>

1 0

[Dovecot] 1.0-stable update
by Timo Sirainen 26 Apr '05

26 Apr '05

Just a note, I backported some larger mbox changes from 1.0-test67. Hopefully works, but if you're going to try it test it well first :) Should fix some issues related to X-IMAP/X-IMAPbase header handling and maybe some other mbox related problems as well.

3 6

[Dovecot] configuration problem: maildir folders and messages not found
by Bram Mertens 26 Apr '05

26 Apr '05

Hi Perhaps I've been going too far OT in my previous thread or perhaps I just didn't explain my problem clear enough so forgive me for trying again. I have configured fetchmail to fetch my mail from my ISP's POP3-server. I have set up procmail to filter messages and deliver all non-filtered messages to the folder ".IN-catchall/" in "$HOME/Maildir" After sending some test messages the "Maildir" folder in my home-folder looks like: m8ram@medion:~$ tree -a Maildir Maildir |-- .IN-catchall | |-- cur | |-- new | | `-- 1114356268.8424_0.medion | `-- tmp |-- .IN-testing | |-- cur | |-- new | | |-- 1114354955.6900_0.medion | | `-- 1114356175.8292_0.medion | `-- tmp |-- .INBOX | |-- .IN-testing | | |-- cur | | |-- new | | | |-- 1114354955.6900_0.medion | | | `-- 1114356175.8292_0.medion | | `-- tmp | |-- .imap.index | |-- .imap.index.data | |-- .imap.index.log | `-- .imap.index.tree |-- .customflags |-- IN-catchall |-- cur |-- new `-- tmp 16 directories, 11 files Because I have been using the mbox format to test dovecot so far I had to modify my dovecot configuration but no matter what I try none of the messages above appear in evolution or thunderbird. Can anybody tell me what I need to add/remove/change in my config? I'm running: m8ram@medion:~$ /usr/sbin/dovecot --version 0.99.14 on debian testing /etc/dovecot/dovecot.conf contains the following: protocols = imap login = imap login = pop3 mail_extra_groups = mail default_mail_env = maildir:/%h/Maildir auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = pam auth_user = root When using mbox I used: default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u I also tried the following for maildir: default_mail_env = maildir:~/Maildir default_mail_env = maildir:/home/%u/Maildir But neither worked. TIA Bram -- # Mertens Bram "M8ram" <bram-mertens(a)linux.be> Linux User #349737 # # debian testing kernel 2.6.8-1-686 i686 512MB RAM # # 13:39:03 up 30 days, 19:52, 13 users, load average: 0.49, 0.50, 0.39 #

2 4

[Dovecot] ldap uid with static gid problem
by Farkas Levente 26 Apr '05

26 Apr '05

hi, i'd like to use dovecot to authenticate from ldap. in ldap each user has it's uniq uid and gid. unfortunately with postfix we can't use uniq uid/gid since in this case we have ot create all user's home in advance. so we decided to use uniq uid and a common gid in postfix since in this case postfix can create new users maildir and deliver new mails. so i'd like to use everyone's own uid in dovecot, but a common gid (same as in postfix). but how can i do so? i read the wiki, but the problem is if i use: auth_userdb = ldap /etc/dovecot-ldap.conf then i have to define ldap attrib name in dovecot-ldap.conf: user_attrs = mail,,,uid,uidNumber,gidNumber what should i use in the last field in user_attrs? or it's not possible with dovecot to define this? i'd be very said in this case:-( any advice? thanks in advance. yours. -- Levente "Si vis pacem para bellum!"

2 1

[Dovecot] libexecdir and localstatedir problem
by Marten Lehmann 26 Apr '05

26 Apr '05

Hello, I'd really like to define the finale libexecdir and localstatedir through the configure-script. But the Makefiles are rewriting them. Not $libexecdir is used, but $pkglibexecdir. And $pkglibexecdir is always defined as $libexecdir/dovecot. But I don't want this trailing "/dovecot". Same with localstatedir. I want dovecot to use a certain path. But to this path, a "run/dovecot" is appended. I surely could build some patchfiles to change the Makefiles. But it would be easier, if you could add a new directive --pgklibexecdir to the configure-script. I don't know where the "run/dovecot" is defined, but it would also be very fine to set it in the configure-script (specially when upgrading to new releases) instead of defining them all in the dovecot.conf (base_dir, login_dir). Regards Marten

2 5

[Dovecot] 1.0-test68 released
by Timo Sirainen 26 Apr '05

26 Apr '05

http://dovecot.org/test/ Recommended update, has had a lot of testing today. No new big features. Changes: - LDAP authentication should work finally? - Some header lookup fixes that should fix sort/threading issues - Don't crash with 0-byte size mboxes - Transaction log fixes. Also rotate .log file to .log.2 file, allowing more history and less "transaction log file lost" messages. - SEARCHing multiple headers might have crashed - mbox: When first message was expunged we might have gotten "uid-last unexpectedly lost" errors. - recent flag counter wasn't updated in index file header always even if the recent flags were removed - UIDVALIDITY changes are handled more transparently - Added --rundir configure option (not actually tested, does it work? :) - etc.

6 12

[Dovecot] INBOX can't be deleted
by Marten Lehmann 26 Apr '05

26 Apr '05

Hi, surely it can't and it shouldn't. I'm just wondering why a check for "INBOX" is done in src/imap/cmd-delete.c AND src/lib-storage/index/maildir/maildir-storage.c. The first is clear because it gives an imap-error to the client. But for which case is the check in maildir-sorage.c? Just to be absolutely sure? The reason for me to ask is, because I need to disable deletions for five folders: Drafts, Infected, Junk, Sent and Trash. A certain webmail-interface and spamfilter will rely on these folders, so nobody shall be able to delete or rename them. First I placed the checks in cmd-delete.c. Should I place them in maildir-storage.c additionally? In normal circumstance, the check in maildir-storage.c should never be reached, right? Regards Marten

2 1

[Dovecot] Dovecot Stable (or: When is 1.0 coming to a server near you?)
by Rich West 26 Apr '05

26 Apr '05

I'm mainly just curious, but what version of dovecot is considered to be stable enough to be running in a production environment? We're running the 0.99.13 version shipped with FC3 and, while experiencing great performance gains over UW-IMAP, we have hit a couple of snags here and there (random and infrequent characters at the beginning of a mailbox, periodic duplication of a message here and there, etc). I figure we should upgrade to something a bit more current, but I am not sure what the "recommended" verion would be.. Also, perhaps more important, what's the roadmap to getting 1.0 finalized? What's the timeframe? :-) -Rich

2 1

[Dovecot] -test68, -stable and ldap
by Thomas Hummel 25 Apr '05

25 Apr '05

Hello Timo, Thanks to your patches, LDAP authentication now works with -test68. However, I'm still experiencing a segmentation fault with today's snapshot of -stable, as shown in the following gdb backtrace. [I'm still running FreeBSD 5.3] Can you see where it comes from ? Is it because the ldap new code (as in -test68) hasn't been backported into -stable yet ? Thank you, -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Pôle informatique - systèmes et réseau -- (gdb) n 186 userdb_preinit(); (gdb) n 187 passdb_preinit(); (gdb) n Program received signal SIGSEGV, Segmentation fault. auth_cache_parse_key (query=0x0) at auth-cache.c:39 39 for (; *query != '\0'; query++) { (gdb) bt full #0 auth_cache_parse_key (query=0x0) at auth-cache.c:39 str = (string_t *) 0x806a100 key_seen = '\0' <repeats 255 times> key = 0 '\0' #1 0x08055456 in passdb_ldap_preinit (args=0x8075100 "/usr/local/dovecot/etc/dovecot-ldap.conf") at passdb-ldap.c:237 conn = (struct ldap_connection *) 0x8078010 #2 0x08054b8d in passdb_preinit () at passdb.c:152 p = (struct passdb_module **) 0x8068914 name = 0x806b078 "ldap" args = 0x806891c "ÒP\006\b\bT\005\bdT\005\bxT\005\bøR\005\b\204S\005\bíQ\006\b" #3 0x0805108b in main (argc=1, argv=0x806a100) at main.c:187 No locals. (gdb) --

1 0

[Dovecot] HA heartbeat scripts
by Nigel Metheringham 25 Apr '05

25 Apr '05

Has anyone worked with getting dovecot to work in a HA cluster using heartbeat? If so do you have any magic startup scripting or other special sauce? [I'll be playing with this over the next couple of days, although concentrating on pop for our requirements. I can post any scripting I produce] Nigel. -- [ Nigel Metheringham Nigel.Metheringham(a)InTechnology.co.uk ] [ - Comments in this message are my own and not ITO opinion/policy - ]

1 0

[Dovecot] Limiting IP range access
by Luigi Rosa 25 Apr '05

25 Apr '05

First of all, MANY compliments for this fantastic software. Now the question: is it possibile to limit the access to dovecot (or a single service) to a specified range of IPs? Basically, I am thinking about an IP-based ACL. Thankyou in advance. Ciao, luigi -- A beer delayed is a beer denied.

4 3

[Dovecot] Quota
by Timo Sirainen 25 Apr '05

25 Apr '05

If anyone's interested about implementing quota code for Dovecot (there were a few of you before! :), now it's finally your chance to do it quite easily. With the API changes committed today to CVS, it's now much easier to write plugins that modify mail-storage behavior. So, I finally fixed my half-working quota plugin that had been lying there for a while. It implements the RFC2087 quota commands for IMAP, a generic quota API that should allow pretty much any kind of quota implementation, and the actual quota limit checking for saving and copying mails. As an example there's an implementation which just scans through all files in a directory and sums their sizes. Currently it can be made to work only when starting from command line, eg.: export QUOTA=~/mail:storage=1024 export MODULE_DIR=/usr/local/lib/dovecot/imap ./imap The QUOTA variable is passed to the quota implementation. In this case quota-dirsize reads it, figures out that ~/mail is the directory where to count the files, and 1024kB is the maximum for quota. I think I'll change the master process code so that any unrecognized varibles that come from userdb are fed to imap/pop3 processes. That way you could simply make the userdb return the quota value (and set other user-specific settings as well). Available from: http://dovecot.org/patches/1.0/quota.tar.gz Unpack under dovecot/src, compile command is at the beginning of quota-plugin.c I'm still wondering where this code should be placed. Maybe the core implementation should be built into Dovecot, while the different quota implementations would be plugins? ..And even better would be if Dovecot's build process was modified so that it's possible to specify with configure script what to compile in and what to compile as plugins.. Anyway, comments welcome, Maildir++ implementation welcome, other implementations welcome as well :)

3 8

[Dovecot] File isn't in mbox format - Couldn't open INBOX
by Rich West 24 Apr '05

24 Apr '05

While I saw another thread on the list similar to the issue I was experiencing (http://dovecot.org/pipermail/dovecot/2005-February/006168.html) I was wondering if there was a way around this problem (the thread simply suggested upgrading, but are the later version (specifically the 1.0-test releases) ready for prime time?)... We're periodically having this with some users (not sure what client they are using, but I am pretty sure it is MS Outlook) where the inbox is in near perfect shape except for some extra characters at the beginning of the file. POP or IMAP delivery fails with an error stating "File isn't in mbox format - Couldn't open INBOX". It looks like those characters are of a previous message that was not completely removed from the file, and those characters seem to throw everything out of wack.. It's easily correctable by removing the bogus characters from the beginning of the file, but that gets annoying quickly.. -Rich

4 7

[Dovecot] about filtering and dovecot
by Bram Mertens 24 Apr '05

24 Apr '05

Hi I would like to set up a local mailserver but I'm getting lost with all the available options. As I have already decided to use dovecot I hope someone here will be able to point me to the right docs/HOWTO's/... Here's my wish-list: 1) download mail from my ISP's POP3-server 2) scan with spamassassin 3) scan with ClamAV 4) filter messages (mailing lists/sender/...) 5) store messages in dovecot 6) be able to read messages on my desktop (where all of the above will be running) and on my laptop 7) be able to send messages (currently using evolution) from both my desktop and laptop so sent messages are stored in dovecot (the idea is to be able to see all sent messages on both PC's) I have already created a test-account om my ISP's POP3-server, installed and configured fetchmail and dovecot. Exim has been installed as well but I haven't touched it's configuration yet. Running fetchmail manually collects the mail and stores it in /var/mail/m8ram where dovecot finds it. So I would like to know (how to find out) how I can achieve 2), 3), 4) and 7). I have looked around and have discovered that there are many programs that can do some or all of this. But I haven't been able to figure out how to get them to work with dovecot. e.g. I don't understand what I would have to change to dovecot's config if exim or procmail or whatever moves certain messages to different folders (or even where these folders would be created). Perhaps I'm missing a HOWTO that explains all this, if so please let me know. TIA Bram -- # Mertens Bram "M8ram" <bram-mertens(a)linux.be> Linux User #349737 # # debian testing kernel 2.6.8-1-686 i686 512MB RAM # # 12:40:02 up 26 days, 18:53, 9 users, load average: 0.56, 0.46, 0.29 #

6 9

RE: [Dovecot] IMAP EXPUNGE disconnect/box hang - Fedora Core 2, Squirrelmail and Evolution
by Schettino, John Charles 24 Apr '05

24 Apr '05

Well, I just built and installed the 1.0 stable w/o tags version from source, and so far, it's not hanging/crashing the system - if this is the fix, I'm all over it :D Context: this is my problem: Correction: I'm running yum.log:03/07/05 05:48:28 Updated: dovecot 0.99.14-1.1.fc2.rf.i386 - Sorry about that. I'm a bit befuddled by this behavior. I've been using dovecot for close to a year, and recently the Fedora Core 2 Update: dovecot-0.99.13-4.FC2 build came in via yum. Since then I occasionally get this EXPUNGE disconnect error. When the error hits, the box does not crash but I can no longer log in*, nor start any new processes. I happen to have gkrellm running and I see a slow but steady climb in the # of processess. The only way to recover the box is to do a hard reset, as I cannot log in, nor su - to do a shutdown. In one case I happened to have a root shell open, and I still could not do a shutdown. Any ideas as to what I should do with this? As long as I don't expung everything is fine, but when I do expunge (move something or a filter runs in squirrelmail, or Action/Expunge in Evolution) sometimes it works fine, sometimes I get this error and a weird zombie state. It was all rock solid before this new version. Suggestions welcome - I don't seem to be getting any logging when it goes bad, perhaps I can up the log level? I'm more then happy to build the current dovecot from source, and if I should post this to some Fedora list, point me at it :D

3 3

[Dovecot] Dovecot LDA with sieve scripting
by Timo Sirainen 23 Apr '05

23 Apr '05

I also placed dovecot-lda-0.1.tar.gz in http://dovecot.org/test/. It's also in dovecot-lda module in CVS. It's based on the same deliver binary that exists in Dovecot's sources, but I've also plugged in CMU Sieve (mostly because it was the easiest one to plug in). The code could be much prettier, but it works anyway :) I think at some point I'm going to try to make the Sieve stuff a plugin on top of the normal delivery binary. (Dovecot in general should have some pretty plugin architecture, so you could just unpack them in some directory then do ./configure --with-builtin-plugins=quota-maildir,lda-sieve --with-external-plugins=sql,ldap,quota-sql) configure needs --with-dovecot=../dovecot-1.0-test68 option. So, usage goes like I mentioned in my previous mail (uhm. should put it into README): http://dovecot.org/list/dovecot/2005-March/006512.html Sieve script is assumed to be in ~/.dovecot.sieve file. It's automatically compiled to ~/.dovecot.sievec whenever timestamp changes. If it doesn't exist, mail is stored normally into INBOX.

1 0