similar to: Renumbering UID on messages

I am getting lots of these error messages in the log file, any idea why? vsz_limit = 512M Dec 14 00:50:12 lmtp(it at wenn.com)(it at wenn.com): Error: mmap_anon(211079168) failed: Cannot allocate memory -- The information contained in or attached to this email is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not

Dovecot 2.0.13 Centos 5.4 x86_64 2.6.18-164.9.1.el5 (on ESXi) OS/Logs on local storage, /home all on NFS server for datastore (NFS Store Centos 5.5 x86_64 2.6.18-194.11.1.el5) Thunderbird 3.1.10 on XP/W7 Desktops We are seeing a werid issue where there is a delay of up to a few mins in seeing label updates on messages. I have confirmed that Thunderbird is sending the update to the server with

It seems that when you run ./configure with --with-solr it does not check for deps libcurl and libexpat. When we compiled it silently went though and still compiled without a problem then missed installing solr. Maybe im missing something? -- The information contained in or attached to this email is intended only for the use of the individual or entity to which it is addressed. If you are not

I have found that if you the fts_solr plugin is listed after Zlib it will cause an indexing problem where any message that was compressed with Zlib is submitted to solr without being uncompressed. The order of the plugins is important. Not sure if this can be fixed but im trying to add a wiki note. -- The information contained in or attached to this email is intended only for the use of the

Am 2016-12-18 um 22:50 schrieb Ricardo Branco: > I am having a problem with Horde due to large variations in email UID > for a few users. > At one time they were receiving thousands of emails a day, they have > deleted all these messages but because they still have early emails in > the mailbox the UID range from start to now is massive. > We use Horde webmail and it creates an

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 15 Jul 2014, Ricardo Branco wrote: > Attached files > > Nick Edwards wrote, On 15/07/2014 10:19: >> you need to show doveconf -n >> and what you have in the master.conf for dovecot >> >> On 7/15/14, Ricardo Branco <ricardo at wenn.com> wrote: >>> I have been trying looking though all the wiki

Mail server runs centos 6.9 and so does the nfs servers, it is using nfsv3 on mount, underlining fs is xfs. On 9 October 2017 23:00:42 BST, Tom Talpey <tom at talpey.com> wrote: >What OS are you running doveadm on, and what type of NFS server is >hosting the storage? > >One possibility on (much) older NFS servers is that some of them refuse >to extend a file when setting the

I am getting lots of these messages in my imapd.log or while I am doing mailbox operations on the terminal. All my mailboxes are stored on NFS and ive set the nfs locking params in the config, only one mailserver accessing this share. Any ideas why this would be happening? doveadm(ops): Error:

Solr 7 returns JSON by default but fts_solr requires XML. Would be good to have wt=xml added to the query to force it to xml all the time, this would prevent errors if solr has not had xml set as default for index. Dovecot 2.2.36 Centos 6 *Doveadm Request:* doveadm search -u caroline at covermg.com TEXT smith doveadm(caroline at covermg.com): Error: fts_solr: Invalid XML input at 1:0: not

HI all, Is there a renumbering function in R? I would like to renumber the following id numbers *Input file * Id Father Mother 123 0 0 124 0 0 125 123 124 126 123 0 127 125 126 128 0 127 130 123 125 *Output* Id Father Mother 1 0 0 2 0 0 3 1 2 4 1 0 5 3 4 6 0 7 7 1 2 Any help is highly appreciated in Advance Val K [[alternative HTML version deleted]]

On Fri, 22 Jul 2005, David McBride wrote: > Package: dovecot-imapd > Version: 0.99.14-1 > Severity: important > > Hi, > > I think I've identified a bug in Dovecot 0.99.14 as packaged and > distributed by Debian Sarge. I believe the bug lies in the original > Dovecot source, not with any modifications made by Debian. > > Specifically, this bug deals with

Is there a way to force dovecot to reprocess a user account to refile the m.* files based on new config for max file size. Ive got one account at 22k files due to a 2M split.

We have multiple logins assigned to single mailboxes, so we can give one login to different devices. Does this cause a problem with mailbox guids in solr or is the ID stored within the indexes and not related to username.

Is there a way when using doveadm to search a users mailbox to disable using solr plugin (without changing config file). We have found that solr does not work well with certain search types and reverting to non solr searching works much better.

On Aug 13, 2012, at 8:34 AM, Sergei Larin <slarin at codeaurora.org> wrote: > Andy, > > Yes, this is what Arnold has suggested also, and from this point it looks > like it should work, but it will require parsing the bundle every time we > care to know whether this is a real use or a conditional def. This might > become awkward... but I guess I should provide a better

I have referred to the wiki and the RFC, but I still can't find the exact answer I'm looking for. From what I know, Dovecot uses the IMAP standard of 32 bit integers to uniquely identify messages. After a message is deleted from the mbox, can this UID ever be reissued to a new message or is that UID retired? What about after the 2 billion limit is reached? Thanks!

Andy, Jacob, I have ported Hexagon MI scheduler to use the new scheduler infrastructure, but one of my tests triggers an assert in LiveInterval update. On the surface it does not make much sense to me, so I wonder if this is something you readily recognize, before I try to prop it open... The assert is: lib/CodeGen/LiveInterval.cpp:266: llvm::LiveRange*

On 2018-06-07, Ricardo Branco <ricardo.branco at wenn.com> wrote: > Solr 7 returns JSON by default but fts_solr requires XML. > > Would be good to have wt=xml added to the query to force it to xml all the time, this would prevent errors if solr has > not had xml set as default for index. This is already done in Dovecot 2.3.x, the same patch works in 2.2.x.

I have been trying looking though all the wiki documents to setup LMTP. It now seems to all be connected except that it keeps saying that the user is not recognised when postfix sends to LMTP, it sends the full recipent email address but seems that on the dovecot side it is unable to work with this. I have checked the userdb and made sure its using %n but alas it still does not work. Currently

Andy, Lang, Thanks for the suggestion. I have spent more time with it today, and I do see some strange things in liveness update. I am not at the actual cause yet, but here is what I got so far: I have the following live ranges when I start scheduling a region: R2 = [0B,48r:0)[352r,416r:5)... R3 = [0B,48r:0)[368r,416r:5)... R4 = [0B,32r:0)[384r,416r:4)... R5 = [0B,32r:0)[400r,416r:4)...