Microsoft Exchange Server - Revision history

Jkuehlthau: /* Exchange Origin */

2017-04-05T13:58:42Z

Exchange Origin

← Older revision		Revision as of 13:58, 5 April 2017
Line 3:		Line 3:
	**This is used if you want to read from another mailbox other than your own. You enter here a comma-seperated list of mailboxes to read from. If this feature is not being used it can be left blank. You must be granted Read permissions by the other users for this to work correctly.		**This is used if you want to read from another mailbox other than your own. You enter here a comma-seperated list of mailboxes to read from. If this feature is not being used it can be left blank. You must be granted Read permissions by the other users for this to work correctly.
	*Query String		*Query String
	The Query String accepts a date, and is only used to filter for records greater than or equal to the date you supply. So just put a date in there “1/1/2017” and it should just bring back messages newer than that.		**The Query String accepts a date, and is only used to filter for records greater than or equal to the date you supply. So just put a date in there “1/1/2017” and it should just bring back messages newer than that.

	==Sample Origin Filters==		==Sample Origin Filters==

Jkuehlthau at 13:58, 5 April 2017

2017-04-05T13:58:32Z

← Older revision		Revision as of 13:58, 5 April 2017
Line 1:		Line 1:
	=Exchange Origin=		=Exchange Origin=
			*Mailboxes
			**This is used if you want to read from another mailbox other than your own. You enter here a comma-seperated list of mailboxes to read from. If this feature is not being used it can be left blank. You must be granted Read permissions by the other users for this to work correctly.
			*Query String
			The Query String accepts a date, and is only used to filter for records greater than or equal to the date you supply. So just put a date in there “1/1/2017” and it should just bring back messages newer than that.

	==Sample Origin Filters==		==Sample Origin Filters==
	Query strings in the EWS Managed API and EWS are interpreted as a subset of AQS syntax. AQS strings are composed of either values or keyword/value pairs, separated by a colon (:).		Query strings in the EWS Managed API and EWS are interpreted as a subset of AQS syntax. AQS strings are composed of either values or keyword/value pairs, separated by a colon (:).

Jkuehlthau at 16:33, 4 March 2015

2015-03-04T16:33:47Z

← Older revision		Revision as of 16:33, 4 March 2015
Line 1:		Line 1:
	=Exchange Origin=		=Exchange Origin=
	==Sample ~~Contact~~ Origin Filters==		==Sample Origin Filters==
	Query strings in the EWS Managed API and EWS are interpreted as a subset of AQS syntax. AQS strings are composed of either values or keyword/value pairs, separated by a colon (:).		Query strings in the EWS Managed API and EWS are interpreted as a subset of AQS syntax. AQS strings are composed of either values or keyword/value pairs, separated by a colon (:).
	<source lang="xml">		<source lang="xml">
Line 6:		Line 6:
	</source>		</source>
	When a value is specified without a keyword, all indexed properties are searched for the value. If a keyword is paired with a value, the keyword specifies a property to search for the corresponding value. See: https://msdn.microsoft.com/en-us/library/office/dn579420(v=exchg.150).aspx		When a value is specified without a keyword, all indexed properties are searched for the value. If a keyword is paired with a value, the keyword specifies a property to search for the corresponding value. See: https://msdn.microsoft.com/en-us/library/office/dn579420(v=exchg.150).aspx

	~~I'm not sure if this criteria is the same for other Exchange folders or not.~~

Jkuehlthau at 04:42, 4 March 2015

2015-03-04T04:42:21Z

← Older revision		Revision as of 04:42, 4 March 2015
Line 1:		Line 1:
	=Exchange Origin=		=Exchange Origin=
	==Sample Origin Filters==		==Sample Contact Origin Filters==
	Query strings in the EWS Managed API and EWS are interpreted as a subset of AQS syntax. AQS strings are composed of either values or keyword/value pairs, separated by a colon (:).		Query strings in the EWS Managed API and EWS are interpreted as a subset of AQS syntax. AQS strings are composed of either values or keyword/value pairs, separated by a colon (:).
	<source lang="xml">		<source lang="xml">
Line 6:		Line 6:
	</source>		</source>
	When a value is specified without a keyword, all indexed properties are searched for the value. If a keyword is paired with a value, the keyword specifies a property to search for the corresponding value. See: https://msdn.microsoft.com/en-us/library/office/dn579420(v=exchg.150).aspx		When a value is specified without a keyword, all indexed properties are searched for the value. If a keyword is paired with a value, the keyword specifies a property to search for the corresponding value. See: https://msdn.microsoft.com/en-us/library/office/dn579420(v=exchg.150).aspx

			I'm not sure if this criteria is the same for other Exchange folders or not.

Jkuehlthau: /* Sample Origin Filters */

2015-03-04T04:23:41Z

Sample Origin Filters

← Older revision		Revision as of 04:23, 4 March 2015
Line 2:		Line 2:
	==Sample Origin Filters==		==Sample Origin Filters==
	Query strings in the EWS Managed API and EWS are interpreted as a subset of AQS syntax. AQS strings are composed of either values or keyword/value pairs, separated by a colon (:).		Query strings in the EWS Managed API and EWS are interpreted as a subset of AQS syntax. AQS strings are composed of either values or keyword/value pairs, separated by a colon (:).
	<source lang="~~bash~~">		<source lang="xml">
	keyword:value		keyword:value
	</source>		</source>
	When a value is specified without a keyword, all indexed properties are searched for the value. If a keyword is paired with a value, the keyword specifies a property to search for the corresponding value. See: https://msdn.microsoft.com/en-us/library/office/dn579420(v=exchg.150).aspx		When a value is specified without a keyword, all indexed properties are searched for the value. If a keyword is paired with a value, the keyword specifies a property to search for the corresponding value. See: https://msdn.microsoft.com/en-us/library/office/dn579420(v=exchg.150).aspx

Jkuehlthau at 04:22, 4 March 2015

2015-03-04T04:22:46Z

← Older revision		Revision as of 04:22, 4 March 2015
Line 5:		Line 5:
	keyword:value		keyword:value
	</source>		</source>
	When a value is specified without a keyword, all indexed properties are searched for the value. If a keyword is paired with a value, the keyword specifies a property to search for the corresponding value.		When a value is specified without a keyword, all indexed properties are searched for the value. If a keyword is paired with a value, the keyword specifies a property to search for the corresponding value. See: https://msdn.microsoft.com/en-us/library/office/dn579420(v=exchg.150).aspx
	See: https://msdn.microsoft.com/en-us/library/office/dn579420(v=exchg.150).aspx

Jkuehlthau at 04:22, 4 March 2015

2015-03-04T04:22:32Z

← Older revision		Revision as of 04:22, 4 March 2015
Line 6:		Line 6:
	</source>		</source>
	When a value is specified without a keyword, all indexed properties are searched for the value. If a keyword is paired with a value, the keyword specifies a property to search for the corresponding value.		When a value is specified without a keyword, all indexed properties are searched for the value. If a keyword is paired with a value, the keyword specifies a property to search for the corresponding value.
			See: https://msdn.microsoft.com/en-us/library/office/dn579420(v=exchg.150).aspx

Jkuehlthau: Created page with "=Exchange Origin= ==Sample Origin Filters== Query strings in the EWS Managed API and EWS are interpreted as a subset of AQS syntax. AQS strings are composed of either values o..."

2015-03-04T04:22:08Z

Created page with "=Exchange Origin= ==Sample Origin Filters== Query strings in the EWS Managed API and EWS are interpreted as a subset of AQS syntax. AQS strings are composed of either values o..."

New page

=Exchange Origin=
==Sample Origin Filters==
Query strings in the EWS Managed API and EWS are interpreted as a subset of AQS syntax. AQS strings are composed of either values or keyword/value pairs, separated by a colon (:).
<source lang="bash">
keyword:value
</source>
When a value is specified without a keyword, all indexed properties are searched for the value. If a keyword is paired with a value, the keyword specifies a property to search for the corresponding value.