|
Posted by Alex Duggleby on August 1, 2006, 2:58 am
Please log in for more thread options Hi Jeff,
thanks! So I suppose the Standard Outlook IFilter isn't configurable?
Because basically we would be rewriting the Filter just to include a few more
Attributes to the index.
And if I remember right, it is not recommended to write IFilter using the
.netFX, instead we should use unmanaged components?
Or does anyone know of a third-party IFilter that IS configurable?
Regards,
Alex
"Jeff R." wrote:
> Excellent question. I dunno.
>
> The issue is that the IFilter responsible for parsing email has been written
> to use Outlook's field list. Now if the fields have been extended by a
> third party program, there is no way for the IFilter to know the new fields
> exist, thus they are not parsed.
> If you or the third party software company were to put out an Ifilter for
> the modified email, then there is a good chance that WDS would add those
> fields to the index. That is assuming there is a way to map those fields to
> the index schema...
>
> hth,
>
> Jeff
>
> > Hi,
> >
> > Consider an application that adds a number of Custom (User) Properties to
> > mails in Outlook (for example MyProperty1).
> >
> > Is there a way (or will there be a way in the future) to use Windows
> > Desktop
> > Search to search by these properties? Is there a way to let WDS index
> > these
> > properties aswell? As an example I would like to find all Mails that have
> > the
> > MyProperty1 property set, and have the MyProperty1 Value = 'foo*'.
> >
> > Is that possible?
> >
> > Thanks in advance,
> > Alex
>
>
>
| 
XML Sitemap