[Dovecot] Update Dovecot index files on maildrop delivery?
Hi all, is there some easy way to inform Dovecot about a new delivery, which has happened after postfix invoked maildrop, so the index files would be updated?
On Sex, 15 Jan 2010, Kārlis Repsons wrote:
is there some easy way to inform Dovecot about a new delivery, which has happened after postfix invoked maildrop, so the index files would be updated?
That's exactly the task for which dovecot deliver was made.
-- Eduardo M KALINOWSKI eduardo@kalinowski.com.br
On Friday 15 January 2010 12:20:05 Eduardo M KALINOWSKI wrote:
On Sex, 15 Jan 2010, Kārlis Repsons wrote:
is there some easy way to inform Dovecot about a new delivery, which has happened after postfix invoked maildrop, so the index files would be updated?
That's exactly the task for which dovecot deliver was made. But maybe you could also post a short info on how should deliver be called?
I read that "The Dovecot LDA, called deliver, is a local delivery agent which takes mail from an MTA and delivers it to a user's mailbox, while keeping Dovecot index files up to date." However in my case maildrop seems to be in the place of deliver. Would it work if maildrop had deliver called by xfilter with the options appended, then followed by "to /dev/null"?
On Sex, 15 Jan 2010, Kārlis Repsons wrote:
On Friday 15 January 2010 12:20:05 Eduardo M KALINOWSKI wrote:
On Sex, 15 Jan 2010, Kārlis Repsons wrote:
is there some easy way to inform Dovecot about a new delivery, which has happened after postfix invoked maildrop, so the index files would be updated?
That's exactly the task for which dovecot deliver was made. But maybe you could also post a short info on how should deliver be called?
I read that "The Dovecot LDA, called deliver, is a local delivery agent which takes mail from an MTA and delivers it to a user's mailbox, while keeping Dovecot index files up to date." However in my case maildrop seems to be in the place of deliver.
Would it work if maildrop had deliver called by xfilter with the options appended, then followed by "to /dev/null"?
I don't know maildrop, so I can't tell if this would work. But the
idea is to use deliver instead of maildrop, unless you need something
that only maildrop can do.
In this case, I'd leave things as they are and not worry about
indexes. When the mail folder is opened next time dovecot will notice
the new messages and update the indexes.
-- <Mercury> knghtbrd: Eww, find a better name, the movie sucked.. <G> <Knghtbrd> Mercury: The engine is better than the movie
Eduardo M KALINOWSKI eduardo@kalinowski.com.br
On Friday 15 January 2010 14:44:07 Eduardo M KALINOWSKI wrote:
On Sex, 15 Jan 2010, Kārlis Repsons wrote:
On Friday 15 January 2010 12:20:05 Eduardo M KALINOWSKI wrote:
On Sex, 15 Jan 2010, Kārlis Repsons wrote:
is there some easy way to inform Dovecot about a new delivery, which has happened after postfix invoked maildrop, so the index files would be updated?
That's exactly the task for which dovecot deliver was made.
But maybe you could also post a short info on how should deliver be called?
I read that "The Dovecot LDA, called deliver, is a local delivery agent which takes mail from an MTA and delivers it to a user's mailbox, while keeping Dovecot index files up to date." However in my case maildrop seems to be in the place of deliver. Would it work if maildrop had deliver called by xfilter with the options appended, then followed by "to /dev/null"?
I don't know maildrop, so I can't tell if this would work. But the idea is to use deliver instead of maildrop, unless you need something that only maildrop can do.
In this case, I'd leave things as they are and not worry about indexes. When the mail folder is opened next time dovecot will notice the new messages and update the indexes.
But I think, client MUA will not be timely notified of the new mail, which might happen for one together with index updating (wouldn't it?)...
On Fri, 2010-01-15 at 14:56 +0000, Kārlis Repsons wrote:
In this case, I'd leave things as they are and not worry about indexes. When the mail folder is opened next time dovecot will notice the new messages and update the indexes.
But I think, client MUA will not be timely notified of the new mail, which might happen for one together with index updating (wouldn't it?)...
Not really. Dovecot notices the new/ directory's mtime changed so it'll go look inside it.
participants (3)
-
Eduardo M KALINOWSKI
-
Kārlis Repsons
-
Timo Sirainen