[imapfilter-devel] Matching problem with imapfilter and Exchange IMAP

[Hans-Werner Hilse]

Hi David, Bernd, John and all those others on this quiet list ;-),

On Mon, 31 Mar 2008 10:40:29 -0500
David DeSimone <fox at verio.net> wrote:

> Bernd Kuemmerlen <bkuemmer at gmx.net> wrote:
> > even though I have thought I had tackled all the problems using
> > imapfilter with Exchange IMAP, I have found a new problem.
> 
> Your efforts are noble, but, I believe, ultimately futile.
> 
> My opinion:
> 
> Microsoft only implemented the Basic functionality of IMAP.  They want
> it to be only useful for reading mail, nothing else.  This way they can
> claim to be "open standards compliant"

Well, they indeed don't offer too much -- especially w/ regard to
proper indication what exactly they offer ;-)

But being forced onto an Exchange server as well and being highly
dissatisfied with the offered filtering (and FWIW: spam scanning)
functionality. So I found imapfilter and it served quite well -- in the
end. My configuration is a bit special in that sense that I don't use
much of imapfilter's rich repertoire of functions. In my case, I've
come to rely only on the full headers and body of new mails and stopped
bothering with the servers' functionality. As an example, I've attached
my configuration, verbosely commented. Basically, I wrote my own
filtering mechanism using Lua built-in regular expressions. Since I
decided to download the full messages, I didn't see much sense in
further relying on server side search facilities. And I wanted to
download the full messages anyway in order to feed them into a spam
scanning mechanism that *I* trust in. After fighting with false
positives for about a week, I dropped any effort to use the Exchange
based spam filter (I heard the Outlook-built-in is better, but that
doesn't really help...).

The attached sample config uses my patch for using IMAP IDLE, posted
here (it still works on newer versions of imapfilter, I think):
http://lists.hellug.gr/pipermail/imapfilter-devel/2007/000514.html
If the patch is not present, the script must be reconfigured in the end
section (it has commented out alternatives).

Sorry for not actually bringing a problem to this list and not really
answering the original question, but I thought an exemplary use case
from a matching environment might be nice here :-)

-hwh
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imapfilter-config.lua
Type: application/octet-stream
Size: 3634 bytes
Desc: not available
URL: <http://lists.hellug.gr/pipermail/imapfilter-devel/attachments/20080331/99403df5/attachment.obj>