Hi all,
I am having real trouble when attempting to patch dovecot 1.2 to include the
Pidgeonhole sieve support on my CentOS 5.6 x64 mail server. I am relatively new
to the programming side of linux, but I am not having a lot of luck when trying
to get this thing to compile.
Here's what happen
Jan-Frode Myklebust writes:
IMHO it would be great if we could both provision and un-provision users
without having the provisioning system mess with files in the
filesystem. Provisioning new users works fine since dovecot will create
all files/directories on first login, but I haven?t found th
Hey guys,
I'm wondering what the best way is to be backwards compatible with
Courier mailbox formats and not duplicate mailbox trees with Dovecot.
Is anyone doing this right now?
My Dovecot 2.0.13 is configured as follows for Namespaces:
namespace {
inbox = yes
location =
prefix =
Hi all!
I want create a large IMAP server setup where dovecot is listening on multiple
interfaces and needs
a different default realm on each interface. I'm using dovecot 2.0.5 on
FreeBSD9 and authenticate
against a LDAP database.
I found an old mail thread from 2007 that said I'm basically scre
Hi,
recently I debugged some load and performance and 'log out' problems and
found an error in the dovecot logs:
Error: pipe() failed: Too many open files
Googling around and reading some posts led to the conclusion, that my
problem is a bug, which will not be removed.
So I'm thinking of upgrad
IMHO it would be great if we could both provision and un-provision users
without having the provisioning system mess with files in the
filesystem. Provisioning new users works fine since dovecot will create
all files/directories on first login, but I haven´t found the tools to
un-provison them. I s
