If I do the following:

search tweeters "chickadee"

I get over 550 lines containing chickadee, Chickadee, or CHICKADEE for me,
so I do think the case of the search term _is_ ignored, as per
the documentation.

The other issue, for all of us who strive to seek improvements in
services and software, is to hope that CREN (Listproc's developer) will
eventually implement the return of individual messages (and/or their
identity) that satisfy the SEARCHes (similar to the way LISTSERV on
VM/CMS systems does with its SEARCH command), rather than just the
lines, and leaving it to the subscriber to GET the entire logs with
contain those messages

Several people have implemented full-text searchable WWW-based Hypermail
servers to handle listserver discussion messages. They subscribe the
server to the discussion list, and the messages get archived, indexed,
searchable, and retrievable as individual messages from there. It's an
ok alternative, but it would be nice to package everything under one
cover.

Peter