similar to: what defines dovecot LOG perms?

Backported from CVS HEAD to branch_1_0. You can get it as a patch from http://dovecot.org/patches/1.0/quota-rewrite.diff New features include support for multiple quota roots, so you could have eg. per-user quota and a larger domain quota (although no backend actually supports this yet..). The more important feature is that you can configure specific mailboxes to have a bit more space available

what's the correct format for setting per-user override quotas in a passwd-file? in my "dovecot.conf", i've: protocol imap { mail_plugins = quota imap_quota mail_plugin_dir = /usr/local/dovecot-plugins/imap plugin { quota = maildir:storage=10240 # 10 MB quota limit } in my "imap_user_file", i've: passdb passwd-file { args =

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, building OPENSSH v4.3p2 on OSX 10.4.7, all's fine (config, nake, install, exec) out-of-the-box. so, to be clear, this is NOT a blocker, by any stretch ... that said, however ... if, instead of a don't-monkey-with-it build, prior to ./configure, i: autoreconf -i -f then, a subsequent: ./configure \ --prefix=/usr/local/openssh \

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi all, per the exim docs @: http://exim.org/exim-html-4.62/doc/html/spec_html/ch36.html a cyrus_sasl authenticator driveer is 'included' in exim core. given that Dovecot has become a very attractive alternative for an increasing number of folks, and there's a patch against exim 4.43 here:

-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 hi, i've dovecot-cvs up on osx. logging in with virtual users is working. so far so good. i'm attempting to build sieve support now. after: % cd /usr/ports/dovecot/dovecot-sieve % glibtoolize -f -c % autoreconf -i -f configure.in: installing `./install-sh' configure.in: installing `./missing' src/Makefile.am:

hi, i'm running dovecot branch_10 cvs on OSX 10.4.7 w/ exim 4.63. i'd like to use Dovecot's SASL as an auth backend to exim, instead of Cyrus-SASL. @ dovecot's sasl page: http://wiki.dovecot.org/Sasl i know there's a patch against exim 4.43: http://www.exim.org/eximwiki/AuthenticatedSmtpUsingDovecot that, purportedly, enables EXIM to use dovecot's SASL as an

Hello, I'm new to dovecot. I just installed it a few days ago on FreeBSD via the ports and got it up and running without too much trouble. Although yesterday I turned on the SSL/TLS features and tried to get secure connections to work. I don't get any error messages when launching dovecot, I saw it successfully create the SSL parameters after first enabling the feature yet I

hi, i've dovecot cvs 10branch installed on OSX 10.4.7. when i login from my MUA (in this example, Mulberry), functionally all looks OK. BUT, i *do* see one error in the log output, dovecot: Aug 27 20:43:25 Error: IMAP(testuser at mydomain.com): Sending log messages too fast, throttling.. Is this an imap error? or is it 'just' the error of logging too fast? if the latter, what

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi matthias, reading the dovecot wiki page: http://wiki.dovecot.org/Quota that, apparently, you last edited (created?): Quota (last edited 2006-06-13 15:27:38 by MatthiasAndree) i note: " plugin { # 10 MB quota limit quota = maildir:storage=10240 # 1000 messages quota limit quota = maildir:messages=1000 # 10 MB + 1000

-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 bldg dovecot cvs branch_1_0 on osx, i'm seeing a sensitivity to order in protocol statements. e.g., on launch: THIS WORKS FINE: protocol lda { sendmail_path = /usr/local/exim/bin/exim ... plugin { quota = maildir:storage=10240 # 10 MB quota limit } } but, THIS DOES NOT protocol lda { ... plugin { quota =

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, i build mysql (currently v5.0.22) on OSX 10.4.7 w/ threading enabled. i.e., i build the reentrant libs: libmysqlclient_r.dylib rather than the 'usual': libmysqlclient.dylib currently, to make Dovecot 'play nice' and recognize the reentrant libs, I: perl -pi -e

-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 hi, i've built dovecot latest cvs on OSX 10.4.7. i'm making a 1st attempt @ trying/failing to get TLS operation up-n-running ... my install's OK: Install prefix ...................... : /usr/local/dovecot File offsets ........................ : 64bit I/O loop method ..................... : poll File change notification method

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, i've Dovecot 10branch head built on on OSX 10.4.7. i've also exim 4.63 configured for use with dovecot's AUTH. on local delivery via exim -> dovecot LDA, i see two errors: (1) dovecot_lda transport output: dyld: Library not loaded: /usr/local/ssl/lib/libssl.0.9.8.dylib (2) Child process of dovecot_lda transport (running

i'm setting up for virtual_users w/ maildir. i have in my dovecot.conf: auth default { passdb passwd-file { args = /etc/dovecot/imapd.passwd } userdb static { args = static uid=300 gid=300 home=/var/dovecot/mail mail=maildir:/var/dovecot/mail/%d/%n/Maildir nice=10 } } default_mail_env = maildir:/var/dovecot/mail/%d/%n/Maildir:INDEX=/var/dovecot/indexes/%d/%n in

-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 hi all, i have two OSX boxes set up for ssh via pubkey auth only. i'm setting up rsync comms for the first time. i have rsyncd running on box A. no-auth rsync from box B to/from box A's rsyncd works as expected. rsync@B to/from rsyncd@A using pubkey-auth'd-ssh trasport: rsync --verbose --stats --recursive -e "ssh -F

hi all, does dovecot.conf support the definition/use of user variables? e.g., in principle, my_DIR = /path/to/something/ then, default_mail_env = maildir:${my_DIR}/%d/Accounts/%1u/%u/Maildir or, for that matter, default_mail_env = blahblah then, namespace private { ... location = $default_mail_env ... i finallly figured out --

... of a correctly formatted QUOTA spec in/for a static userdb. That's all I'm askin' for! i've tried a bunch of variants. the most recent two: user at domain.com:{PLAIN}testpass:::::: quota=maildir:storage=4096 user at domain.com:{PLAIN}testpass:::::: maildir:storage=4096 *none* (so far ...) work to override the spec in dovecot.conf. no errors in the logs; rather, simply:

hi all, has anyone had any success in getting the current dovecot cvs-lda's implementation of CyrusSIEVE responding to a ManageSIEVE client? in particular, i'm hoping that one can use, e.g., Mulberry's Client- & Server-side sieve editor: <http://www.cyrusoft.com/sieve/sievescreens.html> if i telnet to my dovecot box's sieve port ( = 2000) i get no response at

hi all, i've dovecot TLS working correctly w/ locally generated *RSA* CA cert, domain privkey & self-signed domain cert. to that end, my dovecot.conf includes: ssl_key_file = /var/Security/mail.testdomain.com.privkey.rsa.pem ssl_cert_file = /var/Security/mail.testdomain.com.cert.rsa.pem ssl_ca_file =

hi all, "uncle"! i've thrown up my hands with cyrus, and am looking for a 'better alternative' ... i'm brand new to dovecot (haven't even built it yet ...), and have spent the last while reading through the LIST archives here. apart from the TECHNICAL aspects, which seem _more_ than adequate/competitive, i'm most attracted by a comment abt this