[ILUG] Dovecot

[Timothy Murphy]

On Sat 08 Sep 2007, Pete McEvoy wrote:

> > What I don't understand is how exactly the client program
> > (kmail in my case, thunderbird in yours) causes dovecot on the server
> > to update its indices.
>
> Whats the default_mail_env setting? dovecot -n is a convenient way to
> check.

Thanks for your response.
I don't see any setting for default_mail_env in /etc/dovecot.conf .
The output of dovecot -n on my server is
-------------------------------------
[root at alfred tim]# dovecot -n
# 1.0.3: /etc/dovecot.conf
info_log_path: /var/log/dovecot
protocols: imap imaps
listen: *:143
ssl_listen: *:993
login_dir: /var/run/dovecot/login
login_executable: /usr/libexec/dovecot/imap-login
mail_location: maildir:~/Mail/inbox
auth default:
  passdb:
    driver: pam
  userdb:
    driver: passwd
-------------------------------------

> On the dovecot list you mentioned using fetchmail and uucp to grab mail,
> where does it then put it?
> Are the two locations the same?

As far as I can see, on my server
procmail ensures that everything ends up in ~/Mail/inbox .
Could I add something in .procmailrc
to tell dovecot to update itself whenever something comes through?
Or could I run a cron job to tell dovecot to update every 5 minutes,
or whatever.

What I don't understand is what exactly causes dovecot to update
its indices, if everything is running properly.

My dovecot log file does not seem to contain anything interesting.
It just consists of entries like
-------------------------------------
Sep 08 16:47:49 Info: imap-login: Login: user=<tim>, method=PLAIN, 
rip=79.12.132.123, lip=192.168.1.1, TLS
Sep 08 19:24:22 Info: IMAP(tim): Disconnected: Logged out
Sep 08 23:43:03 Info: imap-login: Login: user=<tim>, method=PLAIN, 
rip=82.61.177.211, lip=192.168.1.1, TLS
-------------------------------------