> I have to deploy an Email Server based on Cyrus IMAP, Postfix and
> LDAP. This is no problem, I have done it before.However our customer
> requests for a web based tool for administering user accounts and
> quotas.
>
> We found tools capable of administering accounts in the LDAP Server
> (ie LDAP
I have to deploy an Email Server based on Cyrus IMAP, Postfix and
LDAP. This is no problem, I have done it before.However our customer
requests for a web based tool for administering user accounts and
quotas.
We found tools capable of administering accounts in the LDAP Server
(ie LDAPmyADMIN)
I saw this problem the first time I enabled replication on a machine
hosting all the IT support staff the University of Michigan. Plenty
of large mailboxes there!
My solution (such as it is) was to reduce the wasteful amount of
space sync_server was allocating per message:
--- cyrus-imap
Andreas Winkelmann wrote:
Ok, please remove the "LOGIN" Mechanism from sasl_mech_list.
# Authentication configuration
sasl_pwcheck_method: saslauthd
sasl_mech_list: PLAIN LOGIN
"LOGIN" is not able to do authorization (-a cyrus -u user). Only PLAIN and
DIGEST-MD5 can do that. Because you use
Ok, so this isn't a memory leak as such, but...
When sync_client has a large folder to send (for
the sake of far too many hours of me trying to
make this work let's just say it's 180,000
messages), then it just sends a single
"UPLOAD [lastuid] [lastappenddate]" followed by
every single message on
