search for: insance

...ot creates a new mail based on the vacation rules. *This one* fail. It is injected in the main postfix instance, which is wrong in this case. I tried to start dovecot with an additional environment MAIL_CONFIG=/etc/postfix-instance2 and enabled alternate_config_directories in main.cf of the first insance. ( http://www.postfix.org/postconf.5.html#alternate_config_directories ) I also configured the userdb to return an extrafield userdb_mail_config=/etc/postfix-instance2. But all produce strance postfix errors I never saw in my last 6 years as postfix-admin. Would it be possible to configure doveco...

...t; Hi > > ANyone to answer specifically ? > > Q1 : get_last_uid -> Is this the last UID indexed (which may be not the greatest value), or the gratest value (which may not be the latest) (the code of existing plugins is unclear about this, Solr looks for the greatest for insance) > > Q2 : WHen Indexing an email, the data is not passed by "build_key". Why so ? What is the link with "build_more" ? > > Q3 : Searching/Lookup : THe fheader in which to llok for (must be a least among "cc, to, from, subject, body") is not appear...

and finally , for fts_backend_xxxx_lookup_multi, why is that backend dependent ? Would- nt the below function below be the same for any backend ? Waiting fro your feedback on all those questions Thank you JM ----------------- static int fts_backend_xapian_lookup_multi(struct fts_backend *_backend, struct mailbox *const boxes[], struct mail_search_arg *args, enum fts_lookup_flags flags,

...te: > > Hi > > ANyone to answer specifically ? > > Q1 : get_last_uid -> Is this the last UID indexed (which may be not the greatest value), or the gratest value (which may not be the latest) (the code of existing plugins is unclear about this, Solr looks for the greatest for insance) All the mails are always supposed to be indexed from the beginning to the last indexed mail. If there's a gap, indexer first indexes all the missing mails. So the latest UID is supposed to be the greatest UID. (Supporting out-of-order indexing would be rather difficult to keep track of.) &gt...

...; wrote: > Hi > > ANyone to answer specifically ? > > Q1 : get_last_uid -> Is this the last UID indexed (which may be not the greatest value), or the gratest value (which may not be the latest) (the code of existing plugins is unclear about this, Solr looks for the greatest for insance) > All the mails are always supposed to be indexed from the beginning to the last indexed mail. If there's a gap, indexer first indexes all the missing mails. So the latest UID is supposed to be the greatest UID. (Supporting out-of-order indexing would be rather difficult to keep track of.)...

Hi ANyone to answer specifically ? Q1 : get_last_uid -> Is this the last UID indexed (which may be not the greatest value), or the gratest value (which may not be the latest) (the code of existing plugins is unclear about this, Solr looks for the greatest for insance) Q2 : WHen Indexing an email, the data is not passed by "build_key". Why so ? What is the link with "build_more" ? Q3 : Searching/Lookup : THe fheader in which to llok for (must be a least among "cc, to, from, subject, body") is not appearing in the 'struct'...

...he last UID indexed (which may be not the </div> <div> greatest value), or the gratest value (which may not be the latest) (the </div> <div> code of existing plugins is unclear about this, Solr looks for the </div> <div> greatest for insance) </div> <div> All the mails are always supposed to be indexed from the beginning to </div> <div> the last indexed mail. If there's a gap, indexer first indexes all the </div> <div> missing mails. So the latest UID is supposed to...

...i >> >> ANyone to answer specifically ? >> >> Q1 : get_last_uid -> Is this the last UID indexed (which may be not the greatest value), or the gratest value (which may not be the latest) (the code of existing plugins is unclear about this, Solr looks for the greatest for insance) > > All the mails are always supposed to be indexed from the beginning to the last indexed mail. If there's a gap, indexer first indexes all the missing mails. So the latest UID is supposed to be the greatest UID. (Supporting out-of-order indexing would be rather difficult to keep track...

...;dovecot at dovecot.org> wrote: Hi ANyone to answer specifically ? Q1 : get_last_uid -> Is this the last UID indexed (which may be not the greatest value), or the gratest value (which may not be the latest) (the code of existing plugins is unclear about this, Solr looks for the greatest for insance) All the mails are always supposed to be indexed from the beginning to the last indexed mail. If there's a gap, indexer first indexes all the missing mails. So the latest UID is supposed to be the greatest UID. (Supporting out-of-order indexing would be rather difficult to keep track of.) Q2 :...

...answer specifically ? >> >> Q1 : get_last_uid -> Is this the last UID indexed (which may be not the >> greatest value), or the gratest value (which may not be the latest) (the >> code of existing plugins is unclear about this, Solr looks for the >> greatest for insance) >> All the mails are always supposed to be indexed from the beginning to >> the last indexed mail. If there's a gap, indexer first indexes all the >> missing mails. So the latest UID is supposed to be the greatest UID. >> (Supporting out-of-order indexing would be r...

...gt; > ANyone to answer specifically ? > > Q1 : get_last_uid -> Is this the last UID indexed (which may be not the > greatest value), or the gratest value (which may not be the latest) (the > code of existing plugins is unclear about this, Solr looks for the > greatest for insance) > All the mails are always supposed to be indexed from the beginning to > the last indexed mail. If there's a gap, indexer first indexes all the > missing mails. So the latest UID is supposed to be the greatest UID. > (Supporting out-of-order indexing would be rather difficult...