A question on how FTS is implemented with regards to shared & virtual
mailbox. In particular - with Solr. Does Dovecot treat each shared and
virtual mailbox as completely independent - which means Solr would
reindex each appearance independently?
If that's the case, has any thought been give
Sorry for the re-post - just want to make sure you saw this:
#0 0x7fddaf597c37 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1 0x7fddaf59b028 in __GI_abort () at abort.c:89
#2 0x7fddaf9c0c86 in default_fatal_finish (type=,
status=status@entry=0)
Just a quickie: why is "Connection queue full" logged under Info, instead
of something like error? Or at least have the word 'error' in it?
Seems like a pretty error-ish thing to happen. Anything that causes the
connection to fail from the server side should show up in a grep -i for
error. I.e. I
I have a major dsync headache which I am hoping someone can help me
with.
I have to migrate mails from a 'namespace/inbox/prefix=INBOX.' server to
a 'namespace/inbox/prefix=' server.
So I'm trying
# dsync -o 'namespace/inbox/prefix=' sync -1 -f -u x...@xx.com tcp:1.2.3.4
It works fine for so
* Aki Tuomi :
> > Still there in auto11
> >
> Yes, we have not gotten round fixing it. Did you remove < from the path?
Of course :)
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Charité - Universitätsmedizin Berlin
Campus Benjamin Franklin
Hindenburgdamm 30 | D-12203 Berl
On 23.03.2017 11:59, Ralf Hildebrandt wrote:
> * Ralf Hildebrandt :
>
>> Mar 20 16:10:17 mproxy dovecot: master: Dovecot v2.2.devel (a39b5b2)
>> starting up for imap
>> Mar 20 16:10:26 mproxy dovecot: auth: Error:
>> imapc(exchange-imap.charite.de:993): Couldn't initialize SSL context: Can't
>
* Ralf Hildebrandt :
> Mar 20 16:10:17 mproxy dovecot: master: Dovecot v2.2.devel (a39b5b2) starting
> up for imap
> Mar 20 16:10:26 mproxy dovecot: auth: Error:
> imapc(exchange-imap.charite.de:993): Couldn't initialize SSL context: Can't
> verify remote server certs without trusted CAs (ssl_c
Thanks for the advice, sadly the VM hoster uses Qemu with an ancient crappy
kernel and does not offer any way to move upwards to 16.04 with dovecot
2.2.22.
All I could do is try to force the 16.04 packages into the 14.04 system,
which would likely add more problems than solve these :/
Stefan
2017
2.2.9 is rather old. Updating to a more recent version could help.
Aki
On 23.03.2017 10:48, Kein Name wrote:
> Hello List,
>
> I am running an Ubuntu 14.04.5 LTS Server with Dovecot 2.2.9, only local
> filesystems and authentication done via mysql backend.
> Server is a Strato Virtual Server run
Hello List,
I am running an Ubuntu 14.04.5 LTS Server with Dovecot 2.2.9, only local
filesystems and authentication done via mysql backend.
Server is a Strato Virtual Server running
2.6.32-042stab120.11 #1 SMP Fri Mar 10 16:52:50 MSK 2017 i686 i686 i686
GNU/Linux
Sometimes I see errors in the log
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 23 Mar 2017, Robert Moskowitz wrote:
On 03/23/2017 12:15 AM, Rob McAninch wrote:
On Mar 22, 2017, at 23:53, Robert Moskowitz wrote:
It is mentioned here
http://wiki.dovecot.org/ConfigFile
Debian Jessie has the last line of dovecot.conf
sysctl kernel.core_pattern usually indicates where cores are placed. If
it says 'core' you are probably not gonna find it.
Aki
On 22.03.2017 18:11, Daniel Miller wrote:
> Where would I find the core file? I'm not finding anything obvious.
>
> The replicator path is /usr/local/libexec/dovecot/re
12 matches
Mail list logo