search for: schupbach

>> New subscriber here. I noticed that the FTS index is not used in compound searches. >> Is this expected? Tested in 2.0.0 and 2.0.8: > >Yep. It's been in TODO for a while. I know this thread is quite old, but we have the same issue with v2.0.14 and squat. Would this issue also affect the Solr FTS backend? Thanks, Nikolai.

Hi Timo, We have encountered an issue today with a number of migrations. Some customers have mailboxes on the source IMAP server that look like this: 3 LIST "" * * LIST () "." "INBOX" * LIST () "." "INBOX.Statements" * LIST () "." "INBOX.Draft" * LIST () "." "INBOX.Drafts" * LIST () "."

Timo, There is a problem with the dsync POP3 migration plugin when syncing a large INBOX. What happens is dsync establishes a connection to the POP3 server at the beginning of the sync, but then it sits there idle until it's used to sync the UIDLs. On a very large inbox with many thousands of messages it will be idle for longer than a POP3 server's idle timeout setting. When the UIDL

I'm seeing the following error in our logs when removing mailboxes (we are using mdbox and dovecot 2.1.8): Aug 1 20:03:36 msgsrv dovecot: imap(test at test.com): Error: stat(/mailstore/domains/test.com/test/mdbox/mailboxes/Spam) failed: Operation not permitted Aug 1 20:03:36 msgsrv dovecot: imap(test at test.com): Mailbox deleted: Spam When I run truss against the process it appears the

I'm working on migrating IMAP users from Mirapoint Message Servers to Dovecot servers. The Mirapoint IMAP server uses INBOX as a namespace for private mailboxes. I created the same namespace in Dovecot, but when I migrate mailboxes dsync seems to ignore/miss the namespace on Mirapoint and I end up with all mailboxes under a INBOX.INBOX hierarchy. Mirapoint Source Server

I have been having a heck of a time trying to setup samba with "security = share" I have the following shares and related config files defined yet windows 95/98 clients get password rejected when trying to connect to the shares. However I have found that if I call the share the same as the user in the valid user parameter the can connect fine. I have tried the "username map"