Tomas Kuliavas wrote:
>
> If your primary searches are in headers, try dovecot.
>
One more thing about dovecot. http://wiki.dovecot.org/Plugins/FTS
--
View this message in context:
http://old.nabble.com/search-questions-tp26869730p26887961.html
Sent from the squirrelmail-users mailing list a
Courier IMAP does not have any longterm cache or options are somewhere in
install docs. I think it caches only UIDs.
IMAP SEARCH CHARSET UTF-8 BODY "a" times (uncached search and cached in
memory):
1000 messages - 7592,02/368,79 ms
2500 messages - 25291,5/1116,46 ms
5000 messages - 51136,95/2183
Courier imap
we use qmail toaster
but not the default squirrelmail installation
we install it separately
rajesh
>
>
> Rajesh M-3 wrote:
>>
>> hi
>>
>> we use the latest stable version of squirrelmail Version: 1.4.19
>>
>> we tried it on an account with around 15000 emails and when we login th
Rajesh M-3 wrote:
>
> hi
>
> we use the latest stable version of squirrelmail Version: 1.4.19
>
> we tried it on an account with around 15000 emails and when we login the
> inbox lists out the emails very quickly -- excellent performance
>
> however under search -- it times out and gives imap
hi
we use the latest stable version of squirrelmail Version: 1.4.19
we tried it on an account with around 15000 emails and when we login the
inbox lists out the emails very quickly -- excellent performance
however under search -- it times out and gives imap server error, in most
cases of search
>>> SquirrelMail version:
>>> 1.5.2 [SVN]
>>
>> There's your SM version. You should probably start by downloading a
>> fresh copy of a 1.5.2SVN snapshot.
>
> Ok, downloaded the current SVN just now, installed, copied over the
> config file and set data/ to be correct.
It would be better, at least
On Nov 12, 2008, at 3:33 PM, Paul Lesniewski wrote:
>> SquirrelMail version:
>> 1.5.2 [SVN]
>
> There's your SM version. You should probably start by downloading a
> fresh copy of a 1.5.2SVN snapshot.
Ok, downloaded the current SVN just now, installed, copied over the
config file and set data
On Wed, Nov 12, 2008 at 2:38 PM, Scott Haneda <[EMAIL PROTECTED]> wrote:
> On Nov 12, 2008, at 1:05 PM, Paul Lesniewski wrote:
>
>> On Wed, Nov 12, 2008 at 12:40 PM, Scott Haneda
>> <[EMAIL PROTECTED]> wrote:
>>> On Nov 12, 2008, at 12:15 PM, Paul Lesniewski wrote:
>>>
On Wed, Nov 12, 2008 at
On Nov 12, 2008, at 1:05 PM, Paul Lesniewski wrote:
> On Wed, Nov 12, 2008 at 12:40 PM, Scott Haneda
> <[EMAIL PROTECTED]> wrote:
>> On Nov 12, 2008, at 12:15 PM, Paul Lesniewski wrote:
>>
>>> On Wed, Nov 12, 2008 at 2:26 AM, Scott Haneda <[EMAIL PROTECTED]>
>>> wrote:
I am using the curren
On Wed, Nov 12, 2008 at 12:40 PM, Scott Haneda <[EMAIL PROTECTED]> wrote:
> On Nov 12, 2008, at 12:15 PM, Paul Lesniewski wrote:
>
>> On Wed, Nov 12, 2008 at 2:26 AM, Scott Haneda <[EMAIL PROTECTED]>
>> wrote:
>>> I am using the current development version of SM, when I do a search
>>> on all folde
On Nov 12, 2008, at 12:15 PM, Paul Lesniewski wrote:
> On Wed, Nov 12, 2008 at 2:26 AM, Scott Haneda <[EMAIL PROTECTED]>
> wrote:
>> I am using the current development version of SM, when I do a search
>> on all folders, with the other fields set to any of the options, I
>> get
>> the error be
On Wed, Nov 12, 2008 at 2:26 AM, Scott Haneda <[EMAIL PROTECTED]> wrote:
> I am using the current development version of SM, when I do a search
> on all folders, with the other fields set to any of the options, I get
> the error below, can someone suggest a fix on my end, or is this a
> known issue
I am using the current development version of SM, when I do a search
on all folders, with the other fields set to any of the options, I get
the error below, can someone suggest a fix on my end, or is this a
known issue in SM?
ERROR
ERROR: Bad or malformed request.
Query: FETCH (BODY.PEEK[HEA
13 matches
Mail list logo
