STATUS
- Alpha code is written and compiling now. (attached)
- I would like to start testing. However, there is an error when
starting dovecot (git) :
Error: Couldn't load required plugin
/usr/lib/dovecot/lib21_fts_xapian_plugin.so: dlopen() failed:
/usr/lib/dovecot/lib21_fts_xapian_plugin.
On 11 Jan 2019, at 21.23, Joan Moreau via dovecot wrote:
>
> The below patch resolves the compilation error
>
> $ diff -p compat.h compat.h.joan
> *** compat.h 2019-01-11 20:21:00.726625427 +0100
> --- compat.h.joan 2019-01-11 20:14:41.729109919 +0100
> *** struct iovec;
> *** 202,2
Did you remember to load fts first?
mail_plugins =$mail_plugins fts fts_xapian
Aki
On 12 January 2019 at 10:37 Joan Moreau via dovecot <
dovecot@dovecot.org> wrote:
STATUS
The change of "Extern C" suggested by Timo actually solved the situation
Now, further question :
I put a "i_warning" at each of my functions, and I see in the log :
Jan 12 10:33:27
indexer-worker(j...@grosjo.net)<30970>:
Warning: fts_backend_xapian_alloc
Jan 12 10:33:27
indexer-worker(j...@
Sorted this out. sorry for noise
On 2019-01-12 11:39, Joan Moreau wrote:
The change of "Extern C" suggested by Timo actually solved the situation
Now, further question :
I put a "i_warning" at each of my functions, and I see in the log :
Jan 12 10:33:27
indexer-worker(j...@grosjo.net)<30
On 12/31/2018, 5:22:48 AM, Ignacio García wrote:
> A totally different approach (that is imap-server agnostic), providing
> that you're setting up those new accounts with temporary passwords
> (which you know), before users change their passwords to their liking:
> you could also use imapsync (
THank you
Now, for the results
I see the member of fts_result is :
ARRAY_TYPE(seq_range) definite_uids;
I have the UID as a aray of uint32_t *
How to put my UIDs into this "definite_uids" ? Obviously this is not a
simple array/pointer. How to say someting similar to
result->definite_uids
additionally, my logic is that the backend stores one databalse per
mailox in /xapian-indexes (in the "root" dir of the user), the name od
the database is the GUID of the mailbox
For INBOX, that works perfectly, and database is properly createdm and
backed starts indexing all emails
For othe
On 2018-11-09 07:40, André Rodier wrote:
On 2018-11-09 05:25, Aki Tuomi wrote:
This seems to have nothing to do with master account or not. Does this
happen if you try to open the virtual mailbox again?
Aki
On 09 November 2018 at 00:13 André Rodier wrote:
Hello,
I am running dovecot 2.2.3
Op 11/01/2019 om 21:07 schreef Larry Rosenman:
do you use both fts-solr and tika by chance?
I doubt it. The original post is about Lucene and it fails in the Lucene
code. The FTS Solr + Tika problem is caused in Dovecot lib-http.
Regards,
Stephan.
On Fri, Jan 11, 2019 at 11:19 AM Fírv
On Sat, 2019-01-12 at 19:11 +, André Rodier via dovecot wrote:
> On 2018-11-09 07:40, André Rodier wrote:
> > On 2018-11-09 05:25, Aki Tuomi wrote:
> > > This seems to have nothing to do with master account or not. Does this
> > > happen if you try to open the virtual mailbox again?
> > >
> >
Ok, thanks for the info.
Hadn't read the whole thread.
On Sat, Jan 12, 2019 at 1:30 PM Stephan Bosch wrote:
>
> Op 11/01/2019 om 21:07 schreef Larry Rosenman:
> > do you use both fts-solr and tika by chance?
>
> I doubt it. The original post is about Lucene and it fails in the Lucene
> code. Th
Op 11/01/2019 om 16:05 schreef Dominik Menke:
Hello Gerald,
that did the trick, thank you very much!
--Dominik
On 1/11/19 10:54 AM, Gerald Galster wrote:
Hi Dominik,
I have set ssl = required in 10-ssl.conf globally but no ssl here:
service managesieve-login {
inet_listener sieve {
Op 11/01/2019 om 15:27 schreef subscription1:
I made a mistake when I moved dovecot to a new server and only
specified mail_location instead of mail_home
All I have in 10-mail.conf is
-
mail_location = maildir:/home/vmail/mailboxes/%d/%n
All emails for the few accounts
Op 11/01/2019 om 15:13 schreef Marc Roos:
imaptest host=mail04.local port=143 user=xxx pass=xxx mbox=test.mbox
[Fri Jan 11 15:09:14 2019] imaptest[7634]: segfault at 1354ff0 ip
01354ff0 sp 7ffed5d8f558 error 15
[Fri Jan 11 15:09:22 2019] imaptest[7635]: segfault at 2267ff0 ip
0
Please, unsubscribe me.
I really don't want to read this.
12.01.2019 22:47, Stephan Bosch пишет:
>
> Op 11/01/2019 om 15:13 schreef Marc Roos:
>> imaptest host=mail04.local port=143 user=xxx pass=xxx mbox=test.mbox
>>
>> [Fri Jan 11 15:09:14 2019] imaptest[7634]: segfault at 1354ff0 ip
>>
I somehow fixed the folder issue. (seems some unix rights after too many
tests)
Getting back on the "fts_results" structure:
I am trying:
I_ARRAY_INIT(&(RESULT->DEFINITE_UIDS),R->SIZE);
I_ARRAY_INIT(&(RESULT->MAYBE_UIDS),0);
uint32_t uid;
for(i=0;isize;i++)
{
try
{
uid=atol(back
Op 11/01/2019 om 02:52 schreef Jacky:
Hi,
Just found out that Postfix does not implement/support the AUTH=sender
parameter.
So, back to Dovecot, can we use variables in the
submission_relay_user =
submission_relay_password =
No, that is not supported. :/
then Dovecot will forward the
Op 06/01/2019 om 17:05 schreef Stephan Bosch:
Op 31/12/2018 om 06:32 schreef Laz C. Peterson:
Hello Sami, yes, see below.
We run Dovecot at a different versions, mainly 2.2.10 (CentOS),
2.2.22 (Ubuntu) and now 2.2.36 (CentOS). The issue is weird, because
it only happened after the update
Op 12/01/2019 om 23:08 schreef Stephan Bosch:
Op 06/01/2019 om 17:05 schreef Stephan Bosch:
Op 31/12/2018 om 06:32 schreef Laz C. Peterson:
Hello Sami, yes, see below.
We run Dovecot at a different versions, mainly 2.2.10 (CentOS),
2.2.22 (Ubuntu) and now 2.2.36 (CentOS). The issue is
For reference: if you put ssl=yes there, the TLS layer is established
immediately. However, the standard ManageSieve protocol does not support
that (not currently anyway): only the establishment of the TLS layer
using the STARTTLS command is part of the standard. That is why your
clients fail t
21 matches
Mail list logo
