Horde development mailing list

Kevin M. Myer | 2 Nov 2005 23:07

Re: [imp] Searching an IMAP mail store with Imp [SOLVED]

Quoting Michael M Slusarz <slusarz <at> mail.curecanti.org>:

> Quoting Jan Schneider <jan <at> horde.org>:
>
>> This seems to become a common issue, see also
>> http://bugs.horde.org/ticket/?id=2828
>>
>> Maybe we should make this configurable?
>
> Is there a way to determine this via the 'capability' command?
>

I don't think so.  I think the only way to catch it would be to do a 
search - if the result is NO, it could mean that charset isn't 
supported.  But a NO also could mean that search criteria isn't 
supported as well..  If you can think of a simple search with valid 
criteria, then the results of that search could be used to determine if 
a given charset is supported or not, otherwise, the results would be 
ambigious.  Kevin
-- 
Kevin M. Myer
Senior Systems Administrator
Lancaster-Lebanon Intermediate Unit 13  http://www.iu13.org

--

-- 
Horde developers mailing list - Join the hunt: http://horde.org/bounties/
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: dev-unsubscribe <at> lists.horde.org

(Continue reading)

headers

Michael M Slusarz | 3 Nov 2005 19:23

Re: [imp] Searching an IMAP mail store with Imp [SOLVED]

Quoting "Kevin M. Myer" <kevin_myer <at> iu13.org>:

> Quoting Michael M Slusarz <slusarz <at> mail.curecanti.org>:
>
>> Quoting Jan Schneider <jan <at> horde.org>:
>>
>>> This seems to become a common issue, see also
>>> http://bugs.horde.org/ticket/?id=2828
>>>
>>> Maybe we should make this configurable?
>>
>> Is there a way to determine this via the 'capability' command?
>>
>
> I don't think so.  I think the only way to catch it would be to do a
> search - if the result is NO, it could mean that charset isn't
> supported.  But a NO also could mean that search criteria isn't
> supported as well..  If you can think of a simple search with valid
> criteria, then the results of that search could be used to determine if
> a given charset is supported or not, otherwise, the results would be
> ambigious.  Kevin

Try what I just committed (you will need an up-to-date version of both 
IMP and HEAD).  Turns out that the search command MUST output (among 
other items) the phrase 'BADCHARSET' if a search is performed with a 
charset that it does not support.

michael

_______________________________________

(Continue reading)

headers

Marc Jauvin | 3 Nov 2005 21:02

Re: [imp] Searching an IMAP mail store with Imp [SOLVED]

Michael, where did you get this Information? I checked the RFCs, and I 
found this (ref. http://www.ietf.org/rfc/rfc2060.txt):

6.4.4.  SEARCH Command

   Arguments:  OPTIONAL [CHARSET] specification
               searching criteria (one or more)

   Responses:  REQUIRED untagged response: SEARCH

   Result:     OK - search completed
               NO - search error: can't search that [CHARSET] or
                    criteria
               BAD - command unknown or arguments invalid

But I don't see the "BADCHARSET" error.

--marc

Michael M Slusarz <slusarz <at> mail.curecanti.org> wrote:

> Quoting "Kevin M. Myer" <kevin_myer <at> iu13.org>:
>
>> Quoting Michael M Slusarz <slusarz <at> mail.curecanti.org>:
>>
>>> Quoting Jan Schneider <jan <at> horde.org>:
>>>
>>>> This seems to become a common issue, see also
>>>> http://bugs.horde.org/ticket/?id=2828
>>>>

(Continue reading)

headers

Michael M Slusarz | 3 Nov 2005 22:15

Re: [imp] Searching an IMAP mail store with Imp [SOLVED]

Quoting Marc Jauvin <marc <at> r4l.com>:

> Michael, where did you get this Information? I checked the RFCs, and I
> found this (ref. http://www.ietf.org/rfc/rfc2060.txt):
>
> 6.4.4.  SEARCH Command
>
>   Arguments:  OPTIONAL [CHARSET] specification
>               searching criteria (one or more)
>
>   Responses:  REQUIRED untagged response: SEARCH
>
>   Result:     OK - search completed
>               NO - search error: can't search that [CHARSET] or
>                    criteria
>               BAD - command unknown or arguments invalid
>
>
> But I don't see the "BADCHARSET" error.

RFC 2060 is obsolete.  RFC 3501 now controls.

michael

_______________________________________
Michael Slusarz [slusarz <at> curecanti.org]

--

-- 
Horde developers mailing list - Join the hunt: http://horde.org/bounties/
Frequently Asked Questions: http://horde.org/faq/

(Continue reading)

headers

Marc Jauvin | 4 Nov 2005 04:32

Re: [imp] Searching an IMAP mail store with Imp [SOLVED]

Doh! 8)

Michael M Slusarz <slusarz <at> mail.curecanti.org> wrote:

> Quoting Marc Jauvin <marc <at> r4l.com>:
>
>> Michael, where did you get this Information? I checked the RFCs, and I
>> found this (ref. http://www.ietf.org/rfc/rfc2060.txt):
>>
>> 6.4.4.  SEARCH Command
>>
>>   Arguments:  OPTIONAL [CHARSET] specification
>>               searching criteria (one or more)
>>
>>   Responses:  REQUIRED untagged response: SEARCH
>>
>>   Result:     OK - search completed
>>               NO - search error: can't search that [CHARSET] or
>>                    criteria
>>               BAD - command unknown or arguments invalid
>>
>>
>> But I don't see the "BADCHARSET" error.
>
> RFC 2060 is obsolete.  RFC 3501 now controls.
>
> michael
>
> _______________________________________
> Michael Slusarz [slusarz <at> curecanti.org]

(Continue reading)