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,
On Fri Aug 10 10:10:21 2012, Timo Sirainen wrote:
On 10.8.2012, at 20.05, David Jonas wrote:
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
On 8/10/12 10:10 AM, Timo Sirainen wrote:
On 10.8.2012, at 20.05, David Jonas wrote:
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
On Wed May 2 06:41:00 2012, Gilles Albusac wrote:
I would like to configure Dovecot for POP3S proxying all users from the
Internet to the internal Exchange Mail Server.
Unless I'm missing something with your request, you don't need dovecot.
Any ssl proxy can do that for you, such as stunnel
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
On 12/29/11 5:35 AM, Timo Sirainen wrote:
On 22.12.2011, at 3.52, David Jonas wrote:
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
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
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
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
On 6/3/11 7:25 AM, Timo Sirainen wrote:
On Thu, 2011-05-26 at 23:25 -0700, David Jonas wrote:
dsync-local(djo...@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
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(djo...@vitalwerks.com): Error: Invalid mailbox input from
worker server: Invalid mailbox first_recent_uid
The local uid is
On 1/12/11 , Jan 12, 11:46 PM, Stan Hoeppner wrote:
David Jonas put forth on 1/12/2011 6:37 PM:
I've been considering getting a pair of SSDs in raid1 for just the
dovecot indexes. The hope would be to minimize the impact of pop3 users
hammering the server. Proposed design is something like 2
On 1/12/11 , Jan 12, 9:53 AM, Marc Perkel wrote:
I just replaced my drives for Dovecot using Maildir format with a pair
of Solid State Drives (SSD) in a raid 0 configuration. It's really
really fast. Kind of expensive but it's like getting 20x the speed for
20x the price. I think the big gain
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!
On 9/8/10 , Sep 8, 8:05 AM, Timo Sirainen wrote:
On Tue, 2010-09-07 at 18:07 -0700, David Jonas wrote:
Well, see if this helps:
http://hg.dovecot.org/dovecot-2.0/rev/902f008f17cf
The patch didn't seem to make a difference. I'm still seeing the error.
If you have any ideas on debugging I'm
On 9/9/10 , Sep 9, 12:23 PM, David Jonas wrote:
On 9/8/10 , Sep 8, 8:05 AM, Timo Sirainen wrote:
On Tue, 2010-09-07 at 18:07 -0700, David Jonas wrote:
Well, see if this helps:
http://hg.dovecot.org/dovecot-2.0/rev/902f008f17cf
The patch didn't seem to make a difference. I'm still seeing
On 9/7/10 , Sep 7, 11:56 AM, Timo Sirainen wrote:
On Sat, 2010-09-04 at 12:17 -0700, David Jonas wrote:
Sep 4 11:27:47 dovecot: dict: Error: sql dict: commit failed: Not
connected to database
Hmm. dict process thinks that all of its SQL connections are in use.
Although why that happens
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(u...@example.com):): msgid=1...@xxx:
saved mail to INBOX
Sep 4 11:27:47 dovecot:
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:
On 6/3/10 , Jun 3, 9:45 AM, Jerrale Gayle wrote:
On 6/3/2010 12:35 PM, David Jonas wrote:
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
On 6/3/10 , Jun 3, 10:16 AM, William Blunn wrote:
On 03/06/2010 17:35, David Jonas wrote:
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
On 6/3/10 , Jun 3, 11:17 AM, William Blunn wrote:
On 03/06/2010 19:08, David Jonas wrote:
On 6/3/10 , Jun 3, 10:16 AM, William Blunn wrote:
On 03/06/2010 17:35, David Jonas wrote:
We're using the SQLite backend for authentication of Postfix SASL.
When
the db is replaced we HUP
On 01/22/2010 10:15 AM, Brandon Davidson wrote:
We've thought about enabling IP-based session affinity on the load
balancer, but this would concentrate the load of our webmail clients, as
well as not really solving the problem for users that leave clients open
on multiple systems.
Webmail
On 11/21/2009 06:15 PM, Thomas wrote:
Close TB. Delete your .msf to recreate indexes. Start TB again and let
it re-index (it will take a while). Then everything should be fine. If
not do a bug report.
I submitted a bug report before I saw your post (Tested in TB3.0rc1,
On 11/20/09 , Nov 20, 11:13 AM, Charles Marcus wrote:
On 11/20/2009, Charles Sprickman (sp...@bway.net) wrote:
It is very good compared to TB2. However, the exact problem the OP
described still exists in 3.0b4. I've had the folks I setup with TB3
bugging the hell out of me about the all
On 8/24/09 , Aug 24, 11:10 AM, Timo Sirainen wrote:
On Thu, 2009-08-20 at 08:03 -0700, David Jonas wrote:
Aug 20 05:34:38 kelly dovecot: auth(default): BUG: Worker sent reply
with id 53, expected 54
http://hg.dovecot.org/dovecot-1.2/rev/0827941c0e7c fixes it, I think.
Applied
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
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
Timo Sirainen wrote:
On Nov 19, 2008, at 8:14 PM, David Jonas wrote:
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?
Fails how?
We're using SQL so I could rewrite the query
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
Timo Sirainen wrote:
On Fri, 2008-05-16 at 00:48 -0700, David Jonas wrote:
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
Cassidy Larson wrote:
If you're using MySQL for your database driver you can easily use the TRIM()
function in your query to strip off leading and ending whitespace
characters. I do that and a LCASE() to
forcehttp://dev.mysql.com/doc/refman/5.0/en/string-functions.html#function_trimthe
usernames
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
Timo Sirainen wrote:
On Fri, 2008-05-16 at 00:48 -0700, David Jonas wrote:
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
Timo Sirainen wrote:
I finally figured out what's happening:
v1.0 writes expunges as plain expunged records to dovecot.index.log
file. v1.1 treats such records as expunge requests, while the actual
expunging is done by writing another expunged (ext) record.
With v1.1 dovecot.index file isn't
Timo Sirainen wrote:
I finally figured out what's happening:
v1.0 writes expunges as plain expunged records to dovecot.index.log
file. v1.1 treats such records as expunge requests, while the actual
expunging is done by writing another expunged (ext) record.
With v1.1 dovecot.index file isn't
Timo Sirainen wrote:
On Mon, 2008-05-05 at 17:46 -0700, David Jonas wrote:
Anyway, this fixes the problem:
http://hg.dovecot.org/dovecot-1.1/rev/b776f2b8d827
Well, it looked good but pop3 processes started accumulating and pretty
soon the load was over 50. No errors were getting logged. strace
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
Timo Sirainen wrote:
On Fri, 2008-05-02 at 14:57 -0700, David Jonas wrote:
Is --with-file-offset-size no longer supported in 1.1?
No. I thought no-one cared, and I found this nice AC_SYS_LARGEFILE
autoconf macro that did all the work for me, so I decided to use it.
Hmm. I guess it would
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
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
Timo Sirainen wrote:
On Fri, 2007-09-28 at 16:12 -0700, David Jonas wrote:
Sep 28 15:51:14 kelly-a dovecot: POP3([EMAIL PROTECTED])[8112]: Fixed index
file /home/vmail/x/x.com/xxx/Maildir/dovecot.index: first_recent_uid
0 - 1
Fixed now: http://hg.dovecot.org/dovecot/rev/392a49f0c69a
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
Marcin Michal Jessa wrote:
Russell E. Meek wrote:
Quoting Ken A [EMAIL PROTECTED]:
I'm switching from a pop3 only dovecot install to a pop3/imap install
and I'm wondering how many connections every 100 'normal' imap users
might have/keep open? I'm wondering if I need to tweak any o/s related
Timo Sirainen wrote:
On 25.7.2007, at 0.09, David Jonas wrote:
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
Jasper Bryant-Greene wrote:
On Tue, Jul 24, 2007 at 02:09:23PM -0700, David Jonas wrote:
SELECT current FROM quota WHERE ...
513965019
BEGIN
INSERT INTO quota (current, ...
COMMIT
?? (error_r appears to be (null))
Unrelated to the original post, but the above would appear
Jasper Bryant-Greene wrote:
On Tue, Jul 24, 2007 at 02:46:11PM -0700, David Jonas wrote:
Jasper Bryant-Greene wrote:
On Tue, Jul 24, 2007 at 02:09:23PM -0700, David Jonas wrote:
SELECT current FROM quota WHERE ...
513965019
BEGIN
INSERT INTO quota (current, ...
COMMIT
?? (error_r
Frank Cusack wrote:
On May 23, 2007 11:54:20 AM -0700 Marc Perkel [EMAIL PROTECTED] wrote:
IMAP establishes a connection between the client and the server. Wouldn't
it be great if it could be a conduit to let custom Thunderbird plugins
talk to custom server application over the IMAP
David Lee wrote:
We do some routine logfile (syslog) gathering and analysis. I've been
looking at extending this to parse the syslog output of dovecot. Hmmm...
...
For instance:
1. All lines, including the deliver, to begin dovecot:;
2. The IMAP(): Disconnected to become imap:
49 matches
Mail list logo
