Re: problem in setting up proxy

Hi! First of all, can you provide output of 'doveconf -n'? It's much cleaner to read and shows what's really there? Aki On 22.1.2019 17.57, Ted wrote: > Hello, > > We're having difficulty with our updated cluster of dovecot servers > accessing the email storage on the NFS mounts.  It seems

Re: debian10+dovecot-2.2.33.2

Maybe you should try 2.2.36? Aki On 22.1.2019 16.47, Maciej Milaszewski IQ PL wrote: > Hi > I have little problem with debian10 and dovecot 2.2.33.2 > > ps -ax > 21815 ?    S  0:00 dovecot/pop3-login director > 21816 ?    S  0:00 dovecot/pop3-login director > 21817 ?    S 

problem in setting up proxy

Hello, We're having difficulty with our updated cluster of dovecot servers accessing the email storage on the NFS mounts.  It seems index files get corrupted when 2 backend mailservers access the same account, and from documentation setting up a director proxy in front of the backup servers.  I'm

debian10+dovecot-2.2.33.2

Hi I have little problem with debian10 and dovecot 2.2.33.2 ps -ax 21815 ?    S  0:00 dovecot/pop3-login director 21816 ?    S  0:00 dovecot/pop3-login director 21817 ?    S  0:00 dovecot/pop3-login director 21818 ?    S  0:00 dovecot/pop3-login director 21819 ?

Re: Moving messages between servers with different configurations

Hi, not easily. You can always limit dsync to a single folder with -m folder, but then again it's designed to make 1:1 copy so you would need to rename the synced folder afterwards. Sami > On 22 Jan 2019, at 17.55, Marc Roos wrote: > > > This pulls over the whole test mailbox, but I need

RE: Having temp mdbox files, what to do with them?

I assume yes because the X-Universally-Unique-Identifier, I can all find in the original mailbox. >Can I delete these because doveadm is only purging from source, when it >is confirmed they are correctly at the destination? > > >[@ storage]# ls -ac1rt >m.554 >m.569 >m.564 >m.559

Having temp mdbox files, what to do with them?

Can I delete these because doveadm is only purging from source, when it is confirmed they are correctly at the destination? [@ storage]# ls -ac1rt m.554 m.569 m.564 m.559 m.561 .temp.1548002572.P1969Q0M313023.mail03 .temp.1548002572.P1969Q1M313023.mail03 .temp.1548002572.P1969Q2M313023.mail03

RE: Moving messages between servers with different configurations

This pulls over the whole test mailbox, but I need it to be stored in a different mailbox, of course that is now possible to move from the local test to the local INBOX/test2. But then I might aswell scp the mbox in the first place. Should we conclude that it is not possible with a single

Re: Moving messages between servers with different configurations

Hi, try running this on the NEW dovecot server: doveadm backup -u uid -R tcp:192.168.10.43:542 to pull the messages from old server. Sami > On 22 Jan 2019, at 16.52, Marc Roos wrote: > > > > Hi Martin, > > I feel a bit like an idiot, but I have been trying with copy, so I do > not lose

RE: Moving messages between servers with different configurations

Hi Martin, I feel a bit like an idiot, but I have been trying with copy, so I do not lose any message when testing. But I can't get them to copy. I do indeed have same uid and gid. [@~]# doveadm mailbox status -S 192.168.10.43:542 -u testuser -t messages test messages=43 [@~]# doveadm

Re: Moving messages between servers with different configurations

Hi, doveadm [-Dv] move [-S socket_path] -u user destination [user source_user] search_query Moving all mails from mailbox INBOX/test on serverA to mailbox Archive/2017 on local serverB. + destination Archive/2017 must exist + Limitation: source_user and testuser must share the same UID and

Encoding input

Hi Are data inputs of fts_backend_update_build_more(struct fts_backend_update_context *_ctx, const unsigned char *data, size_t size) already converted to UTF8 ? Thanks

Re: Changing the imaps port #

Another possible thing, I don't know what the bug is or if it is fixed, but few years ago Thunderbird (on CentOS 7) for me refused to connect to Port 993 or Port 465 if I used a self-signed certificate even though the same certificate worked when using STARTTLS and port 143 and 587. The error

Re: Changing the imaps port #

Comcast DNS servers enforce dnssec, AT does not (last I checked). If by chance your zone has DNSSEC enabled but mis-configured then it is possible the domain name you use for the dovecot server is not resolving because of a dnssec validation failure. I have never heard of comcast or any ISP

Re: Solr -> Xapian ?

To get back on thi "build_more" function: this is what I receive: (see below) 2 poitns : the header name seems to be added at the end of the *data. not always, why so ? where is the body ? Jan 22 08:25:50 gjserver dovecot[20984]: indexer-worker(j...@grosjo.net)<20998>: