search for: premselaar

Is the CONTROLDIR directive only available (undocumented as it may be) in the 1.0 series? I'm currently using 0.99.13 and I didn't find CONTROLDIR with grep. Thanks alan

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've spent the past couple of hours trying to figure this out by checking the wiki and googling, but haven't come up with anything that works yet. I just installed dovecot 1.0.14 with the quota-rewrite (1.09) patch and i'm trying to get the quota overridden via a passwd-file type userdb. I had 1.0.13 without the new quota style patched

I've been browsing the wiki and thru my mail-list archives but haven't found an answer. does/can dovecot 0.99.x support authenticating with a SASL database? I'll be setting up a new mail server for my offices using Sendmail/MIMEDefang/ClamAV/etc with dovecot as the IMAP server. I'm not familiar at all with LDAP. I know that sendmail will authenticate to a SASL database and

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Just to give some more information about this: Apparently some of our POP3 users are saying that when they checked for new mail this morning that all the mail that was saved on the server was downloaded again as unread mail. I followed the guidelines in the wiki [1] with regards to upgrading from 0.99 to 1.0, made sure the .subscriptions and

Hi! My mail server (ubuntu breezey badger) is connected by ADSL and has a dynamic address. I have noticed that, every day after the IP address changes, dovecot is no longer reachable from the net. Iguess this is because dovecot doesn't register this change and continues to listen on a non-existing interface/address. I'm trying to solve this problem by putting a script in /etc/ppp/ip-up/

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've just installed 1.0beta9 on my RHEL 3 system and am still getting the problems with the quota-fs returning "invalid argument". I think i've traced the problem down to differences in the quota versions based on the <sys/quota.h> files on RHEL 3 compared to FC3. on the system itself i'm using v2 quotas (with aquota.user

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've been running 0.99.13 on RHEL 3 for over a year now and finally decided to upgrade to the 1.0 series. unfortunately, I only have one RHEL 3 machine which is my production machine. So, while doing all my preliminary testing I was doing so on a FC 3 machine. I got everything to a stage where I felt comfortable doing the upgrade but I'm

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've setup a test machine and have been playing with dovecot-1.0beta7 and dovecot-lda in preparation for a migration from 0.99.x series. (hopefully with the ability to support imap-quotas) anyways, i've got it all compiled fine (as far as I can tell) and following the directions on the wiki for setting up dovecot LDA with sendmail. (I've

I have blocked some pop3 user sessions: Dec 8 00:03:38 xxxxxx pop3-login: Disconnected: user=<johndoe> Is there a way of sending a message to a user that constantly tries to establish a block pop3 session? Example: From: noreply at mysite.com Subject: Your POP3 session Message: Hello, Your POP3 session is blocked; please contact systemmanagement -- -------------- next part

I've recently installed dovecot 0.99.10.5 on a redhat 7.3 machine. Everything seems to be running fine and smoothly for the most part, however in the past few days I've seen a couple of duplicate emails (and so have a few of my users) which don't appear to have been processed twice by sendmail. also, on one of my IMAP sub-folders my mail client (mozilla thunderbird version 0.6+

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 OK. So, I got over some of the segfault problems I was having with dovecot 1.0beta7 and have even downloaded and installed the latest CVS version which is properly providing quota information to thunderbird (although Mail.app doesn't show the quota details) now i've also downloaded the CVS version of dovecot-LDA and have run autogen.sh and

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thanks to code provided by Geo Carncross, I was able to determine what the problem was with v2 quota support on RHEL 3 using ext3 filesystems. I've included a patch file for quota-fs.c <sys/quota.h> on RHEL 3 sets _LINUX_QUOTA_VERSION to 1 if it's not defined by default. I copied <sys/quota.h> to ./sysquota.h and edited it to