Re: [Dovecot] Getting Postfix Admin's DB to work with Postfix's/Dovecot's MySQL DB
Antoine Nguyen [ngu.anto...@gmail.com] wrote: You can take a look at Modoboa (http://modoboa.org/). It includes a web user interface to create users and a simple webmail. We just installed vimbadmin and are quite happy with it (although removed some annoying crap from the footer) It's very easy to migrate from a postfixadmin-like database and it uses modern web interface tools and techniques which provide a more professional look and feel. The drawback of course is the complex javascript environment surrounding it. http://www.opensolutions.ie/open-source/vimbadmin
[Dovecot] Thunderbird caching problem
Using a fairly simple dovecot config (which obviously needs some max limit
tweaking) we have problems with IMAP synchronization between thunderbird
clients.
Two TB clients in the same IMAP mailbox will, from time to time, show different
views of the same INBOX folders, when TB caching is enabled. The only fix is
to right-click on the folder, go to Properties and use the Repair Folder
option which repairs the local TB .msf cache file.
Is there any server-side fix/workaround that would keep TB from regularly going
out-of-sync ? This happens with TB3 and newer versions, in concert with either
dovecot 1 or 2.
The obvious fix is to disable TB local caching, which unfortunately also
disables certain search features and can be a pain for large mailboxes.
# dovecot -n
# 2.0.13: /etc/dovecot/dovecot.conf
doveconf: Warning: service auth { client_limit=4096 } is lower than required
under max. load (7168)
doveconf: Warning: service anvil { client_limit=2048 } is lower than required
under max. load (3075)
# OS: OpenBSD 5.0 amd64 ffs
auth_default_realm = dovecot.org
auth_mechanisms = plain digest-md5 cram-md5 apop
auth_username_translation = :@
default_client_limit = 2048
default_internal_user = _dovecot
default_login_user = _dovenull
default_process_limit = 1024
disable_plaintext_auth = no
first_valid_gid = 125
first_valid_uid = 125
mail_location = maildir:/mail/%d/%n/
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope encoded-character
vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy
include variables body enotify environment mailbox date
mbox_write_locks = fcntl
mmap_disable = yes
passdb {
args = /etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
plugin {
sieve = ~/.dovecot.sieve
sieve_dir = ~/sieve
sieve_global_path = /etc/dovecot/default.sieve
}
protocols = imap pop3 lmtp sieve
service auth {
unix_listener auth-userdb {
user = mail
}
}
service managesieve-login {
inet_listener sieve {
port = 4190
}
inet_listener sieve_deprecated {
port = 2000
}
}
ssl_cert = /etc/balls/balls-cert.pem
ssl_key = /etc/balls/balls-key.pem
userdb {
args = /etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
protocol lda {
mail_plugins = sieve
}
protocol imap {
imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags
mail_max_userip_connections = 50
}
protocol pop3 {
mail_max_userip_connections = 50
pop3_client_workarounds = outlook-no-nuls oe-ns-eoh
pop3_save_uidl = yes
pop3_uidl_format = %v-%u
}
Re: [Dovecot] Thunderbird caching problem
Dave McGuire [mcgu...@neurotica.com] wrote: On 08/31/2011 02:59 PM, Chris Cappuccio wrote: Using a fairly simple dovecot config (which obviously needs some max limit tweaking) we have problems with IMAP synchronization between thunderbird clients. Two TB clients in the same IMAP mailbox will, from time to time, show different views of the same INBOX folders, when TB caching is enabled. The only fix is to right-click on the folder, go to Properties and use the Repair Folder option which repairs the local TB .msf cache file. Is there any server-side fix/workaround that would keep TB from regularly going out-of-sync ? This happens with TB3 and newer versions, in concert with either dovecot 1 or 2. I ran into exactly this problem as well, it is infuriating. A workaround was discussed here awhile back. Sticking this in the protocol imap block of dovecot.conf solved the problem completely: imap_capability = IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT CHILDREN NAMESPACE UIDP LUS LIST-EXTENDED I18NLEVEL=1 ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS Interesting..How do I know that I really should be announcing all of these capabilities given my current dovecot version and config? With the config I posted, here's what I send out now * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] Blahfart
[Dovecot] web interface for user creation/vacation
What are the best web interfaces for user/domain management, perhaps one that also allows individual users to edit vacation msgs? Right now I'm using a postfixadmin based mysql control panel. Curious what is the better stuff out there that people are using with dovecot/sieve these days? Are there any decent front-ends to setup/manage per-user sieve filters?
[Dovecot] Max OS X 10.5 Mail + Dovecot
Hi, People using the new OS X mail client are unable to connect to the unsigned dovecot-mkcert.sh certificate on my Dovecot installations. Turning off SSL fixes the problem. Is there any way to make it work automatically, or do I just have to get the certificates signed? Has anyone figured this one out before? Thanks, Chris
Re: [Dovecot] Max OS X 10.5 Mail + Dovecot
Well the symptom is that the OS X mail client just times out. It talks to port 993 on the server for a while, but just shows the user a moving icon. Eventually it complains the mail server didn't respond. 10.3 and 10.4 work fine, strangely enough. It times out as it's checking connection to the mail server. I did upgrade from dovecot 1.0 to 1.1 without doing much of any config changes on the dovecot side. But other clients work fine... Actually I just realized while watching tcpdump that Mail.app is testing port 25 after 993. So it may be a Postfix SSL failure of some sort. Chris Peter Giessel [EMAIL PROTECTED] wrote: On Friday, December 05, 2008, at 10:45AM, Chris Cappuccio [EMAIL PROTECTED] wrote: People using the new OS X mail client are unable to connect to the unsigned dovecot-mkcert.sh certificate on my Dovecot installations. Turning off SSL fixes the problem. Is there any way to make it work automatically, or do I just have to get the certificates signed? Has anyone figured this one out before? I have an unsigned SSL certificate with Dovecot and connect fine using OSX.5's Mail.app. What do you mean, unable to connect? Do you really mean unable to connect, or do you mean, an error message comes up every time they try to connect? If its the latter complaint, please see this document: http://support.apple.com/kb/TA22383 I know it says 10.3 Mail, but the steps to follow are essentially unchanged between 10.3 and 10.5.
[Dovecot] Stopping imap synchronization on spool failure
Is there any way to tell an IMAP client to not synchronize/delete old mail through IMAP? Let's say that recent events cause a mail spool to not exist, but people may still want to see old messages that are already cached on their machines.
