search for: vitalwerk

For the life of me I can't get dsync to work. Please help! Remote server runs dovecot out of /usr/local/dovecot2. Everything makes sense until this line: dsync-local(djonas at vitalwerks.com): Error: Invalid mailbox input from worker server: Invalid mailbox first_recent_uid The local uid is 8989 and the remote uid is 89. I added "first_valid_uid = 89" to the local conf but to no avail. Local version is 2.0.12, remote is 2.0.1. # dsync -Dv -u djonas at vitalwerks.com...

Recently we changed Postfix to use Dovecot for our SASL authentication and we ran into trouble with some of our clients having extraneous spaces at the end of their usernames. The quick fix was to add a space to username_chars. The slightly longer fix was a pretty simple patch to Dovecot. I put the trimming in auth_request_fix_username. I didn't think it warranted a full strfuncs

Hello Everyone, I have the opportunity to do a new mail system build out for about 20k email boxes over a few hundred domains. I already run a system like this, but this time I can do it right :). My thought on storage is to have a 12 drive JBOD system attached via SAS to a 3ware 9690SA raid controller. Drives would be RAID'd (10 or 5) to appear as one for message storage. Dovecot would run

Is --with-file-offset-size no longer supported in 1.1? # ./configure \ --prefix=/usr/local/dovecot-1.1 \ --with-mysql \ --with-file-offset-size=32 \ --with-ioloop=best \ --with-pop3d \ --with-ssl \ --with-deliver \ ... checking for _FILE_OFFSET_BITS value needed for large files... 64 ... Install prefix ...................... : /usr/local/dovecot-1.1 File

Hello everyone, I've been working with the quota plugin, attempting to use the dict backend. It seems the sql dict class is not getting loaded. I dropped a couple lines in dict_class_lookup(dict.c) and it seems the only class that gets loaded is "proxy". Any idea how to get the sql driver to load in the quota/dict module? My authentication goes through the sql module and is working

We have a plethora of accounts for which we would like to enable CRAM-MD5 but their passwords are stored as MD5 hashes. Is there anything we can do? Can we take a linux MD5 hashed password (e.g. $1$fac330ee$wd6Tll...) and convert it to dovecot's CRAM-MD5 format (e.g. {CRAM-MD5}b3f297...)? Thanks!

Hello, Is there a way of locking a mailbox, effectively making it read-only to IMAP clients? I've read through http://wiki2.dovecot.org/ACL. I created dovecot-acl with the content "owner lr" in .INBOX which seems to keep me from copying messages into the folder, but not out. I have the plugin configured correctly, it seems, since MYRIGHTS command shows the correct value: 30

I'm in the process of migrating a large number of maildirs to a 3rd party dovecot server (from a dovecot server). Tests have shown that using imap to sync the accounts doesn't preserve the uidl for pop3 access. My current attempt is to convert the maildir to mbox and add an X-UIDL header in the process. Run a second dovecot that serves the converted mbox. But dovecot's docs say,

It appears that using dovecot to proxy to nginx imap proxy doesn't work. >From tcpdump and browsing the source it appears dovecot sends, C CAPABILITY\r\nL LOGIN <user> <pass>\r\n and nginx only responds to the CAPABILITY command. Is this a problem with dovecot sending the two commands without waiting for the first to complete or is it nginx's trouble with not handling it

When using dovecot (2.1.5) sasl with postfix (2.8.4) behind nginx smtp proxy I am seeing a ton of errors of the form: postfix/smtpd[7731]: warning: unknown[192.168.0.6]: SASL LOGIN authentication failed: Connection lost to authentication server Nothing is printed by dovecot in the logs regarding the error. It seems that dovecot just hung up on postfix. (side note: no, can't use xclient

Hello, I have a mailbox with an ungodly number of small messages in it. When new messages are delivered lmtp kicks up an error like the one below. I tried raising the vsz_limit for lmtp but that didn't see to help. Any ideas (besides deleting 400k messages)? Thanks! dovecot: lmtp(6068, user at example.com): Error: mmap() failed with file

Since an upgrade to 2.0.1 from 1.2.x we're seeing this on (mostly) large mailboxes (Maildir) Sep 4 11:27:25 dovecot: dict: mysql: Connected to 192.168.dd.dd (accounts) ... Sep 4 11:27:46 kelly-a dovecot: lda(u1 at example.com):): msgid=<123 at xxx>: saved mail to INBOX Sep 4 11:27:47 dovecot: dict: Error: sql dict: commit failed: Not connected to database Sep 4 11:27:47 dovecot:

On startup of dovecot 1.1b2 I seem to have some permission trouble. Dovecot was configured with --prefix=/usr/local/dovecot-1.1 for testing purposes while dovecot 1.0.2 is in production. # cd /usr/local/dovecot-1.1/sbin/ # ./dovecot -F -c ../etc/dovecot.conf Enet_connect_unix(/usr/local/dovecot-1.1/var/run/dovecot/dict-server) failed: Permission denied # ls -la

Upon upgrading from 1.0.2 to 1.1rc4 I see this error for many of our users: Getting size of message UID=1 failed Couldn't init INBOX: Can't sync mailbox: Messages keep getting expunged Logging in with IMAP I would see a bunch of messages with no subject or time and blank bodies (usine horde/imp). Removing dovecot.index.log, dovecot.index.log.2, or dovecot-uidlist fixes the problem

I upgraded from 1.1 to 1.2 a couple months ago and now we are seeing this: Aug 20 05:34:38 kelly dovecot: auth(default): auth workers: Auth request was queued for 7 seconds, 10 left in queue ... Aug 20 05:34:38 kelly dovecot: auth(default): BUG: Worker sent reply with id 53, expected 54 Aug 20 05:34:38 kelly dovecot: auth(default): worker-server(xxx at example.com,dd.dd.dd.dd): Aborted: Worker

Currently running 1.0.2 with 1.1b1 listening on a different port. On first pop3 login on 1.1b1 I received an immediate disconnect (I was testing with telnet) with the log entries below. Subsequent logins work fine. Other accounts that I tried did not have the same problem. So this is probably isolated to some bad indexes or something, but I thought I should let Timo know. Regards, David Here

When using proxy_maybe CRAM-MD5 authentication fails when the connection is proxied. Is this expected behavior? Is proxy_maybe too simplified for this case? We're using SQL so I could rewrite the query with IFs to fake proxy_maybe and return the password as NULL and nologin as Y, but if it works that way couldn't it work with proxy_maybe? This works: password_query = \ SELECT NULL AS

We're using the SQLite backend for authentication of Postfix SASL. When the db is replaced we HUP dovecot to close and reopen its connection. During this time it appears the socket file is removed and Postfix rejects the authentication attempt. From the logs: Jun 3 00:23:02 xxx dovecot: dovecot: SIGHUP received - reloading configuration Jun 3 00:23:02 xxx postfix/smtpd[14746]: warning:

Hello, I've been working with the quota plugin(s) the past few days and have been having some real trouble. Only a few entries are appearing in the database, a couple more when I restarted dovecot. None of the current entries were being updated either. I think I've tracked it down to somewhere in the dict backend. I put in a few i_info() statements and recompiled. A few queries get