EmailInterface - Revision history

Phanousk: /* Configuring notification scrips */

2023-09-05T11:24:54Z

Configuring notification scrips

← Older revision		Revision as of 07:24, 5 September 2023
Line 114:		Line 114:

	'''NOTE:''' Information vital for scrip debugging. Mainly "what mail was initiated by what script". Mail header '''RT-Message-ID''' or '''Message-ID''' is the source of many usefull information. It's being created in <tt>lib/RT/Interface/Email.pm</tt> as this:		'''NOTE:''' Information vital for scrip debugging. Mainly "what mail was initiated by what script". Mail header '''RT-Message-ID''' or '''Message-ID''' is the source of many usefull information. It's being created in <tt>lib/RT/Interface/Email.pm</tt> as this:
	<source lang="perl"~~><pre~~>		<source lang="perl">
	sub GenMessageId {		sub GenMessageId {
	my %args = (		my %args = (
Line 129:		Line 129:
	return "<rt-". $RT::VERSION ."-". $$ ."-". CORE::time() ."-". int(rand(2000)) .'.'		return "<rt-". $RT::VERSION ."-". $$ ."-". CORE::time() ."-". int(rand(2000)) .'.'
	. $ticket_id ."-". $scrip_id ."-". $sent ."@". $org .">" ;		. $ticket_id ."-". $scrip_id ."-". $sent ."@". $org .">" ;
	}</source~~></code~~>		}</source>
	So you can easily form this mail header recognize what scrip in what ticket is responsible for the mail.		So you can easily form this mail header recognize what scrip in what ticket is responsible for the mail.

2023-09-05T11:23:24Z

add description of Message-ID: mail header

@@ Line 112: / Line 112: @@
 * [[ScripAction]] - basics on creating a new actions
 * [[NotificationsTuning]] - very good article on tuning notifications
 == Other ==

2018-05-16T19:48:38Z

← Older revision		Revision as of 15:48, 16 May 2018
Line 1:		Line 1:

	== T's config file ==		== RT's config file ==

	You should start configuration from [[SiteConfig\|SiteCo]], all options are briefly described in the main config template, so here we'll try to add additional information that will help you understand importance of each option. As it's not complete description then you '''MUST''' always read description in the main config file.		You should start configuration from [[SiteConfig\|SiteCo]], all options are briefly described in the main config template, so here we'll try to add additional information that will help you understand importance of each option. As it's not complete description then you '''MUST''' always read description in the main config file.

2016-11-15T17:46:55Z

Updated broken link to archive.org copy

← Older revision		Revision as of 13:46, 15 November 2016
Line 49:		Line 49:
	* [[ManualInstallation]]		* [[ManualInstallation]]
	* [[Qmail]] - Using Qmail Aliases w/ RT		* [[Qmail]] - Using Qmail Aliases w/ RT
	* [http://www.geert.triple-it.nl/node/rt_procmail.html Using Procmail to deliver RT-mail to queues]		* [http://web.archive.org/web/20070703225014/http://www.geert.triple-it.nl/node/rt_procmail.html Using Procmail to deliver RT-mail to queues]
	* [[EximConfig]]		* [[EximConfig]]
	* [[EximConfigVirtualDomain]]		* [[EximConfigVirtualDomain]]

2016-04-06T20:08:53Z

15 revisions imported

← Older revision		Revision as of 16:08, 6 April 2016
(No difference)

2015-03-10T06:54:39Z

← Older revision		Revision as of 02:54, 10 March 2015
Line 1:		Line 1:
	~~This is all is about [[MTAs]] and handling of incoming and transferring outgoing emails.~~

	~~Configuring email flow in RT is one of most important part to get effective RT instance. Effective configuration of notifications can improve performance of your team multiple times.~~		== T's config file ==

	= ~~Incoming mail gateway configuration~~ =

	~~== RT~~'s config file ==

	You should start configuration from [[SiteConfig\|SiteCo]], all options are briefly described in the main config template, so here we'll try to add additional information that will help you understand importance of each option. As it's not complete description then you '''MUST''' always read description in the main config file.		You should start configuration from [[SiteConfig\|SiteCo]], all options are briefly described in the main config template, so here we'll try to add additional information that will help you understand importance of each option. As it's not complete description then you '''MUST''' always read description in the main config file.

2015-03-10T06:53:25Z

RT's config file

← Older revision		Revision as of 02:53, 10 March 2015
Line 7:		Line 7:
	== RT's config file ==		== RT's config file ==

	You should start configuration from [[SiteConfig]], all options are briefly described in the main config template, so here we'll try to add additional information that will help you understand importance of each option. As it's not complete description then you '''MUST''' always read description in the main config file.		You should start configuration from [[SiteConfig\|SiteCo]], all options are briefly described in the main config template, so here we'll try to add additional information that will help you understand importance of each option. As it's not complete description then you '''MUST''' always read description in the main config file.

	Very '''important''' options are OwnerEmail, RTAddressRegexp and NotifyActor.		Very '''important''' options are OwnerEmail, RTAddressRegexp and NotifyActor.

2014-03-11T13:13:01Z

Loops prevention

← Older revision		Revision as of 09:13, 11 March 2014
Line 28:		Line 28:

	'''$RTAddressRegexp''' (regular expression) - used to prevent RT from ending up in a loop within itself, for example when '''$ParseNewMessageForTicketCcs''' is enabled. This can get complicated if there are several names for the server; for this reason, it's recommended you place your RT email addresses into a namespace such as <code>rt-foo\@example.com</code>, <code>rt-bar\@example.com</code>, etc. to make this as straightforward as possible.		'''$RTAddressRegexp''' (regular expression) - used to prevent RT from ending up in a loop within itself, for example when '''$ParseNewMessageForTicketCcs''' is enabled. This can get complicated if there are several names for the server; for this reason, it's recommended you place your RT email addresses into a namespace such as <code>rt-foo\@example.com</code>, <code>rt-bar\@example.com</code>, etc. to make this as straightforward as possible.
			#See also [[RTAddressRegexp]] which describes how to write this regular expression.
	See also [[RTAddressRegexp]] which describes how to write this regular expression.

	=== Attachments handling ===		=== Attachments handling ===

2012-10-20T19:34:18Z

Sending via SMTP server

← Older revision		Revision as of 15:34, 20 October 2012
Line 111:		Line 111:
	* [[mailx]] - Sending outgoing email from RT to a remote smtp-server instead of a local MTA		* [[mailx]] - Sending outgoing email from RT to a remote smtp-server instead of a local MTA
	** mailx is a poor option. It will always override your /Content-Type/ headers, and so can't properly handle email attachments as it will replace the /multipart/mime; boundary=xxxxxx/ header with /text/plain/. -- comment from a user		** mailx is a poor option. It will always override your /Content-Type/ headers, and so can't properly handle email attachments as it will replace the /multipart/mime; boundary=xxxxxx/ header with /text/plain/. -- comment from a user
	* [[msmtp]] is a great option. It's very easy to use, supports attachments, TLS~~, and more~~.		* [[msmtp]] is a great option. It's very easy to use, supports attachments, TLS.

	== Configuring notification scrips ==		== Configuring notification scrips ==

2012-05-27T05:37:01Z

RT's mail gate