search for: amfs

Logs: Jun 5 06:02:25 bubba dovecot: imap(dmiller at amfes.com)<25877><IjkkJZOKPvKsOk9d>: Opening DB (RO) /var/mail/amfes.com/dmiller/sdbox/xapian-indexes/db_f2857830c70c844e2f1d00003bc41c5f Jun 5 06:02:25 bubba dovecot: imap(dmiller at amfes.com)<25877><IjkkJZOKPvKsOk9d>: FTS Xapian: FLAG=AND Jun 5 06:02:25 bubba dovecot: imap(dmiller at

Yes, latest git version. The logs show (as I read them) returned results - yet nothing shows in the client. The logs look the same (with different numbers) when querying "regular" folders - but results are shown in clients. -- Daniel On June 6, 2019 12:16:08 AM Joan Moreau <jom at grosjo.net> wrote: > Hi > Are you using the latest git version ? > WHich part exactly

Hi Are you using the latest git version ? WHich part exactly of your logs relates to "virtual folders do not work" ? On 2019-06-05 13:08, Daniel Miller via dovecot wrote: > Logs: > > Jun 5 06:02:25 bubba dovecot: imap(dmiller at amfes.com)<25877><IjkkJZOKPvKsOk9d>: Opening DB (RO)

For my primary namespace this is working fine - thanks to the developers! It also appears to work great for shared folders as well. But my virtual folders aren't returning results - at least not to the client. The logs show FTS Xapian opening several DB files and getting results - but nothing is being returned to client. Is this a config issue on my side or is this a current limitation of

Attempting to delete a folder from within the trash folder using Thunderbird. I see the following in the log: Jan 25 15:36:22 bubba dovecot: imap(dmiller at amfes.com): Panic: file mailbox-list-fs.c: line 156 (fs_list_get_path): assertion failed: (mailbox_list_is_valid_pattern(_list, name)) Jan 25 15:36:22 bubba dovecot: imap(dmiller at amfes.com): Error: Raw backtrace:

Trying to clean up the last of the corruption caused by my own stupidity. I now have two mailboxes for one user that give errors such as: doveadm(fax at amfes.com): Error: zlib.read(/var/mail/amfes.com/fax/mdbox/storage/m.9): gz trailer has wrong CRC value at 20065618 doveadm(fax at amfes.com): Error: read(/var/mail/amfes.com/fax/mdbox/storage/m.9) failed: Invalid argument (uid=238)

What did I do wrong to make this happen? "doveadm(dmiller at amfes.com): Debug: fts: Indexes disabled for namespace 'shared/%n/'" doveadm -D fts rescan -u dmiller at amfes.com doveadm(root): Debug: Loading modules from directory: /usr/local/lib/dovecot doveadm(root): Debug: Module loaded: /usr/local/lib/dovecot/lib01_acl_plugin.so doveadm(root): Debug: Module loaded:

doveadm search -u dmiller at amfes.com text xyzxyz doveadm(dmiller at amfes.com): Panic: file istream-limit.c: line 79 (i_stream_limit_seek): assertion failed: (v_offset <= lstream->v_size) doveadm(dmiller at amfes.com): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x3ca8a) [0x7fcf3daaca8a] -> /usr/local/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x32)

It's apparent I have some level of corruption in my mailboxes - something to do with the combination of mdbox, sis, and zlib. I should note that I know I have a mix of compressed and raw messages - if that makes any difference in identifying the problems. I think I need to somehow regenerate the mailboxes with issues. Is there a suggestion for how to accomplish this? Should I perhaps use

Hey Everyone, I just found a slight problem with the "read_body" method in raw_post_data_fix.rb. This line: # Fix for Safari Ajax postings that always append \000 content.chop! if content[-1] == 0 This causes problems with Flash AMF binary format. As AMF always appends a \000 to the stream as well. I''m the developer over at RubyAMF and have been running into problems with AMF

I see the following history in my log during message delivery: Mar 1 13:35:09 mailserver postfix/pickup[21464]: 5FAFC2A002: uid=0 from=<root> Mar 1 13:35:09 mailserver postfix/cleanup[21526]: 5FAFC2A002: message-id=<20090301213509.5FAFC2A002 at mailserver.amfeslan.local> Mar 1 13:35:09 mailserver postfix/qmgr[21429]: 5FAFC2A002: from=<root at mailserver.amfeslan.local>,

I've completed my mailbox rebuild - theoretically I should be free of corruption. I used dsync to export from mdbox to maildir (so should be clean) then used a virtual machine with Dovecot to import back to mdbox in another location. So...theoretically I should be free of all corruption now... Running an fts update - "doveadm search text -u user at domain.com xyzzyx" works on

Having a problem with a mailbox. I've been trying to rebuild - but doveadm force-resync crashes. This is mdbox with sis. doveadm purge -u dmiller at amfes.com doveadm(dmiller at amfes.com): Panic: file istream.c: line 466 (i_stream_grow_buffer): assertion failed: (stream->max_buffer_size > 0) doveadm(dmiller at amfes.com): Error: Raw backtrace:

What options are available for remote storage, i.e. storage devices directly mounted on the machine running Dovecot? I've seen discussions of NFS usage - but my experiences with NFS in times past have been poor. CIFS has worked well for me for non-mail use - would this be suitable? Or is there another method I've not considered? -- Daniel

Continuing to see errors on this with some new messages. Is it possible this has anything to do with zlib plugin, or possibly having a mix of zlib compressed & uncompressed messages with mdbox? I recently added zlib to deliver plugin list. -- Daniel L. Miller, VP - Engineering, SET AM Fire & Electronic Services, Inc. [AMFES] dmiller at amfes.com 702-312-5276

I'm trying to run an SEM, but I keep getting the following error message. In sem.default(ram = ram, S = S, N = N, param.names = pars, var.names = vars, : Could not compute QR decomposition of Hessian. Optimization probably did not converge. I have 4 latent variables (plant, AMF, abiotic, and soilAgg) with 2 or 4 indicator variables for each latent variable.My model is specified as: >

My next bonehead maneuver - was more of the first! location = virtual:/var/mail/%%d/%%n/mdbox/mailboxes/virtual was adapted from my definition for my shared namespace. Which was intended to share OTHER users - which is why the '%%' prefixes are used. Changing to: location = virtual:/var/mail/%d/%n/mdbox/mailboxes/virtual Now I can actually view something! But I still have a

Any ideas on what I need to check or should post to help find the problem? -- Daniel On 2015-06-20 14:50, dmiller at amfes.com wrote: > The first bonehead maneuver seems to be: > location = virtual:/var/mail/%%d/%%n/mdbox/virtual > I'm thinking it should be: > location = virtual:/var/mail/%%d/%%n/mdbox/mailboxes/virtual > > But...it didn't seem to make a

Where I used to be able to access the server without incident, I can no longer receive mail on the mobile device. I'm seeing this in the server log: Nov 27 23:45:05 bubba dovecot: imap-login: Login: user=<dmiller at amfes.com>, method=PLAIN, rip=173.117.196.198, lip=192.168.0.72, mpid=17422, TLS Nov 27 23:45:07 bubba dovecot: imap(dmiller at amfes.com): Error: FETCH [1.2] for

Just upgraded to a new Solr, so I did a full re-index. Saw some of these friendly messages: doveadm(csmith at amfes.com): Error: zlib.read(/var/mail/amfes.com/csmith/mdbox/storage/m.20): gz trailer has wrong CRC value at 28579617 doveadm(csmith at amfes.com): Error: read(zlib(/var/mail/amfes.com/csmith/mdbox/storage/m.20)) failed: Invalid argument doveadm(csmith at amfes.com): Error: