similar to: RE: Locking problem

I am trying to sync a set of maildir folders from a dovecot server and a different imap server on a different host. Using a perl tool called imapsync. The tool says the following about the two servers capabilities: >From capability : IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN LISTEXT LIST-SUBSCRIBED To capability : IMAP4rev1 UIDPLUS CHILDREN NAMESPACE

I am trying to setup dovecot imap on a test Solaris 8 box. I have dovecot POP3S running fine on another box, but I want to switch to IMAP. I see a successful login with a message like: Mar 8 13:22:47 sws601.mcsun.local imap-login: [ID 457029 mail.info] Login: sunuser1 [192.168.1.17] Then the Mozilla Mail client gets a message that the server disconnected. It appears to be from a segfault on

I have read and read the dovecot docs on maildir folders and think that this is what I want. However, the MUA programs that I use, SylpheedClaws, Evolution, Mozilla seem to react differently to how I setup the folders. Is there a good FAQ on this subject somewhere? I think that I want to setup a virtual domain and am looking for documents. Alex

I realized that my last message about locking gave bad information -- or rather, very little information. Here's my setup: - Home directories and user login information are located on an Xserve running Mac OS X 10.2.6. Home directories are split between 2 different directories -- /Users and /Students. Home dirs are exported via NFS to the mail server. User login info is shared via LDAP

Hi all: We're planning to deploy a large e-mail system storing maildirs in a NAS system through NFS. One of the options we're thinking on is using Dovecot+EXIM. As far as I've read in both project's documentation, both services implement locking allowing multiple servers to access the same maildirs in order to distribute the service load. However, I can't find any information

Seems you got the hash wrong... You probably mean 4a1e2e8e85ad5d4ab43496a5f3cd6b7ff6ac5955, which fixes a memory leak, but does not release sync lock. Interesting if this commit fixes the issue. Looking at the sync code, where the lock is made / released, there is only one commit recently, which is 8077d714e11388a294f1583e706152396972acce and that one creates home directory if missing. Would

Hi, [Formatting is a bit rough, replying from a trimmed digest email] > Message: 1 > Date: Fri, 6 Apr 2018 15:04:35 +0200 > From: Michael Grimm <trashcan at ellael.org> > To: Dovecot Mailing List <dovecot at dovecot.org> > Subject: Re: 2.3.1 Replication is throwing scary errors > Message-ID: <E7E7A927-68F8-443F-BA59-E66CED8FE878 at ellael.org> >

Hi all, New to the mailing lists but have joined up because of above */2.3.1 Replication is throwing scary errors /*Brief system configuration ??? MX1 - Main ??? ??? Freebsd 11.1-Release-p9 ??? ??? Hosted on a Vultr VM in Sydney AU ??? ??? MTA = Postfix 3.4-20180401 ??? ??? Dovecot = 2.3.1 ??? ??? File system = ufs ??? MX2 - Backup ??? ??? Freebsd 11.1-Release-p9 ??? ???? Running on

Hi Reuben, thank you for digging into this issue reported by some users, now. I wonder if there are users out there using master/master replication with 2.3.1 dovecot that do *NOT* observe the errors mentioned in this thread? Please report, please. And, pleas have a closer look for It would be interesting to know if these failures are seen by a subset of users, only. And please have a look

Hi Friends! An opinion. I would like to facilitate the configuration of one's mail client (desktop or mobile) to my users server. Some time ago I asked the same question and you suggested me to use "Automx". So I started of good will and I looked for the Automx documentation. And here the problems started as I found several inconsistencies, even parameters (in official

Hi Andy, Funny you say that - I've been testing this very problem for some time today to narrow down the commits where I think the problem started occurring. So far I have been able to roll forward to commit from git: 74ef8506dcb946acc42722683e49fdcb964eed19 >> "doveadm: Unref header search context after use" . So far I have been running on that code for a few hours

... when the MUA has issued a FETCH? ? I am a Dovecot newbie ... so please bear with me if this is obvious. Basically what I am trying to do is process the mail body (in my own specific way) before Dovecot serves it up to the MUA. I want to do it as a transient operation in memory. So think of the scenario as ... ? - the MUA issues a FETCH ? - Dovecot intercepts the FETCH ? - Dovecot internally

Hi everyone, My goal is to sample from a two-dimensional grid. Consider the following example of code: n.grid <- 500 muA.grid <- seq(-4,4, length=n.grid) muB.grid <- seq(-4,4, length=n.grid) mu.p <- matrix(NA, nrow=n.grid, ncol=n.grid) for(i in 1:n.grid){ for(j in 1:n.grid){ mu.p[i,j] <- dnorm(muA.grid[i], 0, 1)*dnorm(muB.grid[j], 0, 0.5) } } mu.p <-

Hi folks, I have configured a public folder as described on the Wiki (more or less; see below), but in TB3 I see the "Public" folder grayed out. I cannot subscribe. Toggling the subscriptions flag doesn't help. What did I miss here? Any helpful comment would be highly appreciated. If this is a TB3 problem: Which MUA would you suggest? Regards Harri

Dear All, I have few question regarding dovecot configuration for specific need which are as follows:- 1. I have IMAP folder with the name Sent Mail and i want whenever client uses any MUA to send mail from my server his mail must be kept in server's IMAP folder which is Sent Mail instead of local Sent folder. 2. Whenever user configures account in MUA, MUA automatically

After solving a problem with a sweet little application I discovered (more on that below), I wanted to get some feedback about a potential enhancement for IMAP: standardized, MUA independant, server-side sorting. Currently, there are two basic solutions for sorting: handle it during delivery or handle it in the MUA. However, if you handle it in the MUA, you lose some of the client

Hi all I am missing something on the the pop3 "leave messages" rationale. Although the UIDL feature solves for the MUA the problem "whch mails should be downloaded", how the duration that these mails should be kept on server, say 10 days for one MUA and 20 days for another MUA for the same account, is resolved on the server? thanks in advance -- ????????? ???????????

Hi All, I've read a bit about this but don't really see a full solution anywhere. Has anyone actually got a good fix for this? Telling a user they are over quota then not allowing them to delete anything does seem the height of perversion. =) Question is - is this even a problem for the IMAP server? Or should the MUA be detecting over quota problems and then issuing the right

I'm wondering what I'd need to do to get the "important" flag set on an incoming message according to a pre-specified header. I know the problem of this not being a "joined-up" feature in standard email, but in practice many MUAs set headers like X-priority etc, and IMAP has an "important" flag that is the obvious mapping. I'm not really sure where

Trying to figure out how to convert an existing mbox system to maildir Below is my dovecot.conf file. Tried adding this at the bottom of the file and nothing happens. plugin { convert_mail = mbox:/vhome/%d/home/%n:INBOX=/vhome/%d/home/%n/INBOX convert_skip_broken_mailboxes=yes } What am I doing wrong? ## Dovecot 1.0 configuration file # '#' character and everything after it is