No, it is NOT in OWA.. which means it would be parsing the mail to get
the flag. What I have found is that someone has to have modify rights on
the email to 'flag' it and as such have attached two email examples. One
without the flag and one with. The problem I had is that as the mailbox
is IMAP I had to send two emails because as I suck down the eMail via
IMAP it does not seem to get updated. I opened it up with vi and tried
to find the 'categories' field but not much luck. Their did not seem to
be any differences. Their HAS to be some way I can 'see' these stupid
flags. (I would like to set them also but If I have to revert to Outlook
to set a flag I will)
On Mon, 2005-03-21 at 16:39 -0500, JP Rosevear wrote:
> On Mon, 2005-03-21 at 15:19 -0500, Jeremey Wise wrote:
> > Just wanted to post more details I just received for those willing to
> > help:
> >
> > **********************
> > The other group uses the "Categories" field within Outlook to mark an
> > email
> > accordingly. We can do this as well, using one of the default
> > categories (or we can decide what kind of category we want to use and
> > implement it on the server)
>
> To start the ball rolling here, is this category stuff even available
> when using straight OWA in a web browser?
>
> -JP
--
Call if you have any questions,
Jeremey Wise
[EMAIL PROTECTED]
Office: (440)-519-6006
Cell: (216)-647-1121
MCSE,CNE,CSE
From [EMAIL PROTECTED] Mon Mar 21 16:44:42 2005
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Received: from DCEX3.pios.com ([172.25.15.150]) by pioushqmail1.pios.com
with Microsoft SMTPSVC(5.0.2195.6713); Mon, 21 Mar 2005 16:44:42 -0500
MIME-Version: 1.0
Content-Type: text/html; charset="US-ASCII"
Received: from 172.27.17.97 ([172.27.17.97]) by DCEX3.pios.com
([172.25.15.150]) with Microsoft Exchange Server HTTP-DAV ; Mon, 21 Mar
2005 21:44:42 +0000
Received: from wizej by dcex3.pios.com; 21 Mar 2005 16:45:03 -0500
Return-Path: <[EMAIL PROTECTED]>
X-Mailer: Evolution 2.0.1
X-OriginalArrivalTime: 21 Mar 2005 21:44:43.0126 (UTC)
FILETIME=[3125D160:01C52E5F]
Content-Class: urn:content-classes:message
Subject: test -With flag
Date: Mon, 21 Mar 2005 16:45:02 -0500
Message-ID: <[EMAIL PROTECTED]>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: test -With flag
Thread-Index: AcUuXzE79irzu9tlRR2kQP+68OxYQg==
From: "Wise, Jeremey" <[EMAIL PROTECTED]>
To: "IA_SOLUTION" <[EMAIL PROTECTED]>
X-Evolution-Source: imap://[EMAIL PROTECTED]/
Content-Transfer-Encoding: 8bit
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.0.6487.1">
<TITLE>test -With flag</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>test -With flag</FONT>
</P>
<P><FONT SIZE=2>-- </FONT>
<BR><FONT SIZE=2>Thanks,</FONT>
</P>
<P><FONT SIZE=2>Jeremey Wise</FONT>
<BR><FONT SIZE=2>[EMAIL PROTECTED]</FONT>
</P>
<P><FONT SIZE=2>All opinions or information expressed here are personal in
nature and do</FONT>
<BR><FONT SIZE=2>not reflect the official position of Agilysys Inc.</FONT>
</P>
</BODY>
</HTML>From [EMAIL PROTECTED] Mon Mar 21 16:44:24 2005
Received: from DCEX3.pios.com ([172.25.15.150]) by pioushqmail1.pios.com
with Microsoft SMTPSVC(5.0.2195.6713); Mon, 21 Mar 2005 16:44:24 -0500
Received: from 172.27.17.97 ([172.27.17.97]) by DCEX3.pios.com
([172.25.15.150]) with Microsoft Exchange Server HTTP-DAV ; Mon, 21 Mar
2005 21:44:24 +0000
Received: from wizej by dcex3.pios.com; 21 Mar 2005 16:44:44 -0500
Subject: test -Without flag
From: Jeremey Wise <[EMAIL PROTECTED]>
To: IA_SOLUTION <[EMAIL PROTECTED]>
Content-Type: text/plain
Date: Mon, 21 Mar 2005 16:44:43 -0500
Message-Id: <[EMAIL PROTECTED]>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.1
Return-Path: [EMAIL PROTECTED]
X-OriginalArrivalTime: 21 Mar 2005 21:44:24.0752 (UTC)
FILETIME=[26322B00:01C52E5F]
X-Evolution-Source: imap://[EMAIL PROTECTED]/
Content-Transfer-Encoding: 8bit
test -Without flag
--
Thanks,
Jeremey Wise
[EMAIL PROTECTED]
All opinions or information expressed here are personal in nature and do
not reflect the official position of Agilysys Inc.
