Email rules - Revision history

Huynhhuyphong at 08:35, 12 April 2012

2012-04-12T08:35:14Z

← Older revision		Revision as of 08:35, 12 April 2012
Line 32:		Line 32:

	<br>		<br>

			{\| cellspacing="0" cellpadding="2" border="1" width="875" style="border-collapse:collapse; border:1px solid #010101" class="tableintopic"
			\|- align="left" valign="top"
			\| bgcolor="#C0C0C0" width="292" style="border:1px solid #010101;" \|
			'''Index'''

			\| bgcolor="#C0C0C0" width="116" style="border:1px solid #010101;" \|
			'''Data type'''

			\| bgcolor="#C0C0C0" width="467" style="border:1px solid #010101;" \|
			'''Value'''

			\|- align="left" valign="top"
			\| width="292" style="border:1px solid #010101;" \|
			<span class="normalise">EMAIL_FROM</span>

			\| width="116" style="border:1px solid #010101;" \|
			<span class="normalise">string</span>

			\| width="467" style="border:1px solid #010101;" \|
			<span class="normalise">The sender's email address</span>

			\|- align="left" valign="top"
			\| width="292" style="border:1px solid #010101;" \|
			<span class="normalise">EMAIL_TO_RESOURCE_ID</span>

			\| width="116" style="border:1px solid #010101;" \|
			<span class="normalise">Number</span>

			\| width="467" style="border:1px solid #010101;" \|
			<span class="normalise">The resource ID of the resource to which the email is delivered</span>

			\|- align="left" valign="top"
			\| width="292" style="border:1px solid #010101;" \|
			<span class="normalise">EMAIL_TO_ADDRESSES</span>

			\| width="116" style="border:1px solid #010101;" \|
			<span class="normalise">string</span>

			\| width="467" style="border:1px solid #010101;" \|
			<span class="normalise">The recipients' email addresses, including Cc recipients'.</span>

			\|- align="left" valign="top"
			\| width="292" style="border:1px solid #010101;" \|
			<span class="normalise">EMAIL_HEADERS</span>

			\| width="116" style="border:1px solid #010101;" \|
			<span class="normalise">string</span>

			\| width="467" style="border:1px solid #010101;" \|
			<span class="normalise">The headers of the email</span>

			\|- align="left" valign="top"
			\| width="292" style="border:1px solid #010101;" \|
			<span class="normalise">EMAIL_SUBJECT</span>

			\| width="116" style="border:1px solid #010101;" \|
			<span class="normalise">string</span>

			\| width="467" style="border:1px solid #010101;" \|
			<span class="normalise">The subject of the email</span>

			\|- align="left" valign="top"
			\| width="292" style="border:1px solid #010101;" \|
			<span class="normalise">EMAIL_CONTENT</span>

			\| width="116" style="border:1px solid #010101;" \|
			<span class="normalise">string</span>

			\| width="467" style="border:1px solid #010101;" \|
			<span class="normalise">The content of the email</span>

			\|}

			'''Example : ''' On the workflow using for adding the journal basing on the email content :

			array emailparameter=Workflow_getParameters();

			string fromemail = emailparameter[EMAIL_FROM];

			number parentResourceId = emailparameter[EMAIL_TO_RESOURCE_ID];

			string toemail = emailparameter[EMAIL_TO_ADDRESSES];

			string headeremail = emailparameter[EMAIL_HEADERS];

			string headeremail = emailparameter[EMAIL_SUBJECT];

			string contentemail = emailparameter[EMAIL_CONTENT];

			addJournal(197653,6, "Comment",convertToString(emailparameter));

	[[Category:Accounts]]		[[Category:Accounts]]

Cg_pham at 04:48, 4 January 2012

2012-01-04T04:48:45Z

← Older revision		Revision as of 04:48, 4 January 2012
Line 1:		Line 1:
	~~[[Category:Accounts]]~~

			=== Email rules ===

	~~===~~Email rules~~===~~		Email rules can be accessed from the accounts dialog. Any email rule must belong to a main account. Accounts can although have multiple rules.

	~~Email rules can be accessed from the accounts dialog. Any email rule must belong to a main account. Accounts can although have multiple rules~~.		[[Image:8086.png\|800px\|Emailrules581-1]]

	~~[[Image:8086~~.~~png\|800px\|Emailrules581-1]]~~		Click add to create a new email rule and edit to modify an existing rule. This will open the following dialogue.

	~~Click add to create a new email rule and edit to modify an existing rule. This will open the following dialogue~~.		[[Image:8087.png\|530px\|Emailrules581-2]]

	~~[[Image:8087~~.~~png\|530px\|Emailrules581~~-~~2]]~~		Each rule has some criteria which you can define to specify for which e-mails the rule will apply. And it has some actions to define what will happen to the emails for which the criteria applies. If an incoming e-mail meets the criteria of one rule, the action is applied.

	~~Each rule has some~~ criteria ~~which you can define to specify~~ for ~~which~~ e-mails the ~~rule will apply~~. ~~And it has some actions to define what will happen~~ to the ~~emails~~ for ~~which~~ the criteria ~~applies~~. ~~If an incoming~~ e-mail ~~meets~~ the ~~criteria of one~~ rule, the ~~action is applied~~.		The criteria that exists for selecting e-mails for a rule are; To e-mail, From e-mail, Subject, Message and Header contains. It is only for the To E-mail where an exact match is required. For the other rules the inserted string just needs to be part of the tested e-mail. If e.g. Subject for the rule is "Coca" then all e-mails with "Coca-Cola" in subject will also fulfill this criteria. The Header contains field is for advanced users who know how the hidden "codes" in e-mail headers look. An example of a  header criteria could be "x-sender: kiima@ozonic.com" or "X-ExchangeSecure-AntiSpam: spam". This would mean that all headers containing the keys "x-sender" where value looks like %kiima@ozonic.com% and key "X-ExchangeSecure-AntiSpam" where value looks like %spam% will fulfill this rule. To add multiple rules for "header contains" please place each rule in a separate line in the text box.

	~~The criteria that exists for selecting e-mails for a rule are; To e-mail~~, ~~From e-~~mail~~, Subject, Message and Header contains. It~~ is ~~only for the To E-mail where an exact match is required. For the other rules the inserted string just needs~~ to ~~be part of the tested e-mail~~. ~~If e.g~~. Subject ~~for~~ the ~~rule is~~ "~~Coca~~" then ~~all~~ e-~~mails with "Coca-Cola" in subject~~ will ~~also fulfill this criteria~~. ~~The Header contains field is for advanced users who know how~~ the ~~hidden "codes" in~~ e-mail ~~headers look. An example of a header criteria could be "x~~-~~sender: kiima@ozonic.com" or "X-ExchangeSecure-AntiSpam: spam". This would mean that all headers containing the keys "x-sender" where value looks like %kiima@ozonic.com%~~ and key ~~"X-ExchangeSecure-AntiSpam" where value looks like %spam% will fulfill this rule. To add multiple rules for "header contains" please place each rule in a separate line~~ in the ~~text box~~.		In the above dialogue example, if an incoming mail is sent to support@vietnam.catglobe.com and in the Subject field includes the string "[Spam]", then the e-mail will be moved to the Inbox of the ARCHIVE resource. As you can see we can combine a number of different rules based on whom the e-mail is to, whom an e-mail is from, and what key words are found in the subject and message areas.

	~~In the above dialogue example, if an incoming mail is sent to support@vietnam.catglobe.com and~~ in the ~~Subject field includes the string "[Spam]", then the e-mail will be moved to the Inbox of the ARCHIVE resource~~. ~~As you can see we can combine a number of different rules based on whom the e-mail is to, whom an e-mail is from, and what key words~~ are ~~found~~ in ~~the subject and message areas.~~		Distribution rules offer 6 different types of actions (chosen in the Type dropdown). These are explained in turn below>

	~~Distribution rules offer 6 different types of actions~~ (~~chosen in the Type dropdown~~). ~~These are explained in turn below>~~		'''Move:''' When choosing this type, you will be asked to choose a mailfolder (typically inbox) of another resource to which incoming emails caught by this rule should be moved to.

	'''~~Move~~:''' When choosing this type, you will be asked to choose a mailfolder (typically inbox) of another resource to which incoming emails caught by this rule should be ~~moved~~ to.		'''Copy:''' If you want to leave a copy in the original resource, but still want a copy another place, you can use this type. When choosing this type, you will be asked to choose a mailfolder (typically inbox) of another resource to which incoming emails caught by this rule should be copied to.

	'''~~Copy~~:''' If you want ~~to leave a copy in~~ the ~~original resource, but still want a copy another place, you can use~~ this ~~type. When choosing this type, you will~~ be ~~asked~~ to ~~choose a mailfolder (typically inbox) of~~ another ~~resource to which incoming emails caught by~~ this rule ~~should be copied~~ to.		'''Forward:''' If you want the incoming email caught by this rule to be forwarded to another email address, then use this rule. The stated email does not need to exist in the Catglobe system.

	'''~~Forward~~:''' If you ~~want~~ the incoming email caught by this rule ~~to be forwarded to another email address, then use this rule. The stated email does not need to exist in the Catglobe system~~.		'''Reply:''' When choosing this type, you will be asked to specify the mail template to be used for the reply email. An email reply will then automatically be returned for any incoming email caught by this rule.

	'''~~Reply~~:''' When ~~choosing~~ this type, ~~you will be asked to specify the mail template to be used for the reply email. An email reply will then automatically be returned for~~ any ~~incoming~~ email caught ~~by this rule~~.		'''Delete:''' When you choose this type, any email caught will immediately get deleted. Good way to handle spammail.

	'''~~Delete~~:''' ~~When~~ you choose this ~~type, any email caught~~ will ~~immediately get deleted~~. ~~Good way~~ to ~~handle spammail~~.		'''Execute CGScript:''' This is a more advanced - but nonetheless extremely smart option. This rule offers you to choose a workflow or tabulation script. When an email with this keyword is received by Catglobe then the chosen script will be run. The SMS message will exist in context of the script and can thus be used to insert into e.g. a task or project.

	'''Execute CGScript:''' This is a more advanced - but nonetheless extremely smart option. This rule offers you to choose a workflow or tabulation script. When an email with this keyword is received by Catglobe then the chosen script will be run. The SMS message will exist in context of the script and can thus be used to insert into e.g. a task or project.		<br>

	~~Back to:~~ [[ ~~Email~~ ]]		[[Category:Accounts]]
	~~__NOTOC__~~
	~~<!-- imported from file: 3304.htm-->~~

Phamngocsonopenid at 04:50, 26 April 2011

2011-04-26T04:50:55Z

← Older revision		Revision as of 04:50, 26 April 2011
Line 1:		Line 1:
	[[Category:~~HelpBooks~~]]		[[Category:Accounts]]

Catglobe: jrfconvert import

2011-03-07T08:50:28Z

jrfconvert import

New page

[[Category:HelpBooks]]

===Email rules===

Email rules can be accessed from the accounts dialog. Any email rule must belong to a main account. Accounts can although have multiple rules.

[[Image:8086.png|800px|Emailrules581-1]]

Click add to create a new email rule and edit to modify an existing rule. This will open the following dialogue.

[[Image:8087.png|530px|Emailrules581-2]]

Each rule has some criteria which you can define to specify for which e-mails the rule will apply. And it has some actions to define what will happen to the emails for which the criteria applies. If an incoming e-mail meets the criteria of one rule, the action is applied.

The criteria that exists for selecting e-mails for a rule are; To e-mail, From e-mail, Subject, Message and Header contains. It is only for the To E-mail where an exact match is required. For the other rules the inserted string just needs to be part of the tested e-mail. If e.g. Subject for the rule is "Coca" then all e-mails with "Coca-Cola" in subject will also fulfill this criteria. The Header contains field is for advanced users who know how the hidden "codes" in e-mail headers look. An example of a header criteria could be "x-sender: kiima@ozonic.com" or "X-ExchangeSecure-AntiSpam: spam". This would mean that all headers containing the keys "x-sender" where value looks like %kiima@ozonic.com% and key "X-ExchangeSecure-AntiSpam" where value looks like %spam% will fulfill this rule. To add multiple rules for "header contains" please place each rule in a separate line in the text box.

In the above dialogue example, if an incoming mail is sent to support@vietnam.catglobe.com and in the Subject field includes the string "[Spam]", then the e-mail will be moved to the Inbox of the ARCHIVE resource. As you can see we can combine a number of different rules based on whom the e-mail is to, whom an e-mail is from, and what key words are found in the subject and message areas.

Distribution rules offer 6 different types of actions (chosen in the Type dropdown). These are explained in turn below>

'''Move:''' When choosing this type, you will be asked to choose a mailfolder (typically inbox) of another resource to which incoming emails caught by this rule should be moved to.

'''Copy:''' If you want to leave a copy in the original resource, but still want a copy another place, you can use this type. When choosing this type, you will be asked to choose a mailfolder (typically inbox) of another resource to which incoming emails caught by this rule should be copied to.

'''Forward:''' If you want the incoming email caught by this rule to be forwarded to another email address, then use this rule. The stated email does not need to exist in the Catglobe system.

'''Reply:''' When choosing this type, you will be asked to specify the mail template to be used for the reply email. An email reply will then automatically be returned for any incoming email caught by this rule.

'''Delete:''' When you choose this type, any email caught will immediately get deleted. Good way to handle spammail.

'''Execute CGScript:''' This is a more advanced - but nonetheless extremely smart option. This rule offers you to choose a workflow or tabulation script. When an email with this keyword is received by Catglobe then the chosen script will be run. The SMS message will exist in context of the script and can thus be used to insert into e.g. a task or project.

Back to: [[ Email ]]
__NOTOC__