similar to: More documentation

I'm trying to use this to test an IMAP server I'm developing (I picked the nightly up from the link on the wiki page at http://www.imapwiki.org/ImapTest/Installation). With one client using the mailbox dovecot-crlf (http://www.dovecot.org/tmp/dovecot-crlf) I get messages like: Error: test at npsl.co.uk[67]: 1035253882.5041.34.camel at hurina: Header From changed 'Timo Sirainen

Hi Dovecot: 2.2.19.rc2 OS: CentOS Linux release 7.1.1503 (Core) FS: XFS Problem: Dovecot it does not include line breaks in the letter. Bug or feautre? Message size in fs: 1125 bytes Message: From cras at irccrew.org Tue Jul 23 19:39:23 2002 Received: with ECARTIS (v1.0.0; list dovecot); Tue, 23 Jul 2002 19:39:23 +0300 (EEST) Return-Path: <cras at irccrew.org> Delivered-To: dovecot

Hi, just started using dovecot on FreeBSD. Nice and easy to configure :-) I then wanted to browse the dovecot mailing list, so, according to http://dovecot.procontrol.fi/mailinglists.html: IMAP archives available from dovecot.procontrol.fi, either use ANONYMOUS authentication or give anonymous as username and empty password. I was using a patched sylpheed that doesn't support

> >Message: 2 >Date: Wed, 18 Jun 2003 13:21:08 +0200 (CEST) >From: Andreas Aardal Hanssen <dovecot at andreas.hanssen.name> >Subject: Re: [Dovecot] Multiple auth howto >To: Dovecot mailing list <dovecot at procontrol.fi> >Message-ID: > <Pine.LNX.4.44.0306181319060.29812-100000 at shusaku.troll.no> >Content-Type: TEXT/PLAIN; charset=US-ASCII > >On

0.99.9 should really be released soon. There's been quite a lot of important fixes since 0.99.8.1. There's still some recent counter strangeness, but it wasn't perfect before either. mbox still doesn't necessarily notice flag changes unless they're written into index file (ie. non-Dovecots and Dovecot without index files). But it wasn't perfect before either.

It finally seems to be working. I've done some testing now and it seems to be working fine. If you have time, see if you can get it to break (especially with INDEX=memory or by manually modifying the maildir). The UIDs are kept in Courier-compatible dovecot-uidlist file (so "mv courierimapuiddb dovecot-uidlist" should work). The great thing about this code is that we never wait for

On Fri, 2003-01-17 at 14:15, Timo Sirainen wrote: > On Thu, 2003-01-16 at 03:31, james broermann wrote: > > pine still doesn't want to work. It does detect that the server is using > > plain text passwords. I'll try the sniffer and see what turns up. > > Whops, you're right. I've tested pine only with digest-md5 > authentication before. Looks like my

http://dovecot.procontrol.fi/test/ - Hopefully OpenSSL is fixed :) - We sometimes produced invalid ENVELOPE with 8bit headers. That could really have broken things (broke it in test12). So, what's left is to make PAM work well..

http://dovecot.procontrol.fi/test/ Again major maildir syncing updates: - uidlist file is accessed and rewritten a lot less often now than before - mail duplicates are detected and handled properly by renaming them to new base name - message flag updates and expunging before did two full syncs for cur/ directory. now it does only one. - some fixes to syncing in read-only / out-of-quota

Hi all, This is probably a silly question, but I have a problem. I've had to move my users maildirs from: maildir:/home/%u/.Maildir To maildir:/data/mail/%u I've updated the MTA to put mail to the correct place and it's working fine. I've also changed the dovecot.conf file and restarted dovecot and I thought that would be all I needed to do. However, the users are getting

http://dovecot.procontrol.fi/test/ I think I've fixed the problems that were corrupting indexes with the new code. It happened every time you had expunged some messages and new messages arrived. I think this release might actually work :) disable_plaintext_auth = yes will be default from now on. It allows plaintext authentication from localhost (127.*, ::1) however. I just figured out

first, thx for --with-storages=maildir second, there is a problem when user exceed their quota < status INBOX (messages) > NO Internal error [2003-05-06 15:35:56] in logfile: imap(user): Can't create directory /var/mail/user/.INBOX: Disk quota exceeded 'user' is not able to get list of messages and delete some of them :( third, in logfile: imap(user2): maildir flags

Lots of bounces from you, I'm moving this subscription to new address.. On Wed, 2003-07-09 at 22:15, mailman-bounces at procontrol.fi wrote: > The attached message was received as a bounce, but either the bounce > format was not recognized, or no member addresses could be extracted > from it. This mailing list has been configured to send all > unrecognized bounce messages to the

Fixed all the reported bugs. Changed PAM service to "dovecot". Anything left? http://dovecot.procontrol.fi/rc/

(Logging in to anonymous at dovecot.procontrol.fi) CVS password: cvs [login aborted]: connect to dovecot.procontrol.fi:2401 failed: Connection refused cvs [checkout aborted]: connect to dovecot.procontrol.fi:2401 failed: Connection refused Was the CVS server taken down? -- Jesse Peterson / jesse at pixeltechs.com

Just tried Dovecot with 85k mails from Linux kernel mailing list, total of 357MB. I mostly wanted to see if the new binary tree file works well. And it does :) Nothing gets slowed down after deleting messages all around the mailbox. I tried several things with Dovecot, UW-IMAPd and Courier. You'll see that Dovecot is faster in everything else except raw I/O which is a bit strange, have to

There are constantly pretty basic questions in this list (and in my inbox) about how to get user authentication work correctly. This means that the documentation how it all works is either bad, or people don't find it easily. Any ideas how to improve it? I did this now: - Documentation link in dovecot.org now points directly to Wiki, so people don't go read the outdated documents

It works for me. I don't know why it wouldn't work for you. Looking at the autoindexing code I don't see how it could be possible that it works for saving but not copying. > On 10 Sep 2015, at 21:05, Larry Rosenman <larryrtx at gmail.com> wrote: > > Is there a fix coming for this, Timo? Or is it a longer term issue? > > On Mon, Sep 7, 2015 at 5:23 PM, Larry

On 23/06/15 13:10, Steffen Kaiser wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Tue, 23 Jun 2015, lejeczek wrote: >> On 23/06/15 09:32, Steffen Kaiser wrote: >>> On Mon, 22 Jun 2015, lejeczek wrote: >>>> On 22/06/15 09:43, Steffen Kaiser wrote: >>>>> On Mon, 22 Jun 2015, lejeczek wrote: >>>>>> On 22/06/15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 23 Jun 2015, lejeczek wrote: > On 23/06/15 09:32, Steffen Kaiser wrote: >> On Mon, 22 Jun 2015, lejeczek wrote: >>> On 22/06/15 09:43, Steffen Kaiser wrote: >>>> On Mon, 22 Jun 2015, lejeczek wrote: >>>>> On 22/06/15 09:16, lejeczek wrote: >>>>>> >>>>>> to=<me