ManualEmailConfig - Revision history

Jbrandt at 17:27, 19 May 2022

2022-05-19T17:27:50Z

← Older revision		Revision as of 13:27, 19 May 2022
Line 62:		Line 62:

	Fetchmail or Getmail can be used to fetch email from a inbox using IMAP or POP. An example configuration for Fetchmail can be seen below:		Fetchmail or Getmail can be used to fetch email from a inbox using IMAP or POP. An example configuration for Fetchmail can be seen below:

	set daemon 0		set daemon 0
	# PID files are more useful for forking systemd services. But fetchmail will		# PID files are more useful for forking systemd services. But fetchmail will
Line 98:		Line 99:
	Lastly you will need a cronjob to pull your inbox periodically		Lastly you will need a cronjob to pull your inbox periodically
	`/1 * * * root /usr/bin/getmail --fetchmailrc /opt/rt4/etc/fetchmailrc --quiet`		`/1 * * * root /usr/bin/getmail --fetchmailrc /opt/rt4/etc/fetchmailrc --quiet`

			If you use MS Office 365 or Google (Gmail) for email, basic authentication (username/password) is no longer allowed. See [[Integrating_RT_Email_with_Google_Mail_(Gmail)]] for details on setting up getmail. [https://metacpan.org/pod/App::wsgetmail App-wsgetmail] is an option for fetching email from MS Office 365.

	----		----
	Prev: [[ManualApacheConfig]] --- Up: [[UserManual]] --- Next: [[ManualBasicAdministration]]		Prev: [[ManualApacheConfig]] --- Up: [[UserManual]] --- Next: [[ManualBasicAdministration]]
	[[Category:RT User Manual]]		[[Category:RT User Manual]]
	[[Category:RT44]]		[[Category:RT44]]

Blaine at 18:49, 2 April 2019

2019-04-02T18:49:42Z

← Older revision		Revision as of 14:49, 2 April 2019
Line 101:		Line 101:
	Prev: [[ManualApacheConfig]] --- Up: [[UserManual]] --- Next: [[ManualBasicAdministration]]		Prev: [[ManualApacheConfig]] --- Up: [[UserManual]] --- Next: [[ManualBasicAdministration]]
	[[Category:RT User Manual]]		[[Category:RT User Manual]]
			[[Category:RT44]]

Craigkai at 14:31, 22 March 2019

2019-03-22T14:31:11Z

Craigkai at 14:27, 22 March 2019

2019-03-22T14:27:10Z

← Older revision		Revision as of 10:27, 22 March 2019
Line 103:		Line 103:

	Lastly you will need a cronjob to pull your inbox periodically		Lastly you will need a cronjob to pull your inbox periodically
			`/1 * * * root /usr/bin/getmail --fetchmailrc /opt/rt4/etc/fetchmailrc --quiet`
	/1 * * * root /usr/bin/getmail --fetchmailrc /opt/rt4/etc/fetchmailrc --quiet
	----		----
	Prev: [[ManualApacheConfig]] --- Up: [[UserManual]] --- Next: [[ManualBasicAdministration]]		Prev: [[ManualApacheConfig]] --- Up: [[UserManual]] --- Next: [[ManualBasicAdministration]]
	[[Category:RT User Manual]]		[[Category:RT User Manual]]

Craigkai at 14:26, 22 March 2019

2019-03-22T14:26:43Z

← Older revision		Revision as of 10:26, 22 March 2019
Line 101:		Line 101:
	mda '/opt/rt4/bin/rt-mailgate --url https://rt.mycompany.com --queue "support" --action correspond'		mda '/opt/rt4/bin/rt-mailgate --url https://rt.mycompany.com --queue "support" --action correspond'
	idle		idle

			Lastly you will need a cronjob to pull your inbox periodically

			/1 * * * root /usr/bin/getmail --fetchmailrc /opt/rt4/etc/fetchmailrc --quiet
	----		----
	Prev: [[ManualApacheConfig]] --- Up: [[UserManual]] --- Next: [[ManualBasicAdministration]]		Prev: [[ManualApacheConfig]] --- Up: [[UserManual]] --- Next: [[ManualBasicAdministration]]
	[[Category:RT User Manual]]		[[Category:RT User Manual]]

Craigkai at 14:24, 22 March 2019

2019-03-22T14:24:58Z

← Older revision		Revision as of 10:24, 22 March 2019
Line 63:		Line 63:
	Fetchmail or Getmail can be used to fetch email from a inbox using IMAP or POP. An example configuration for Fetchmail can be seen below:		Fetchmail or Getmail can be used to fetch email from a inbox using IMAP or POP. An example configuration for Fetchmail can be seen below:
	set daemon 0		set daemon 0

	# PID files are more useful for forking systemd services. But fetchmail will		# PID files are more useful for forking systemd services. But fetchmail will
	# always write one. Since the service runs fetchmail as the apache user,		# always write one. Since the service runs fetchmail as the apache user,
	# www-data, we need to give fetchmail a path that it has write permission to.		# www-data, we need to give fetchmail a path that it has write permission to.
	#set pidfile '/opt/rt4/var/run/fetchmail-rtir.pid'		#set pidfile '/opt/rt4/var/run/fetchmail-rtir.pid'

	poll "IP_OF_MAIL_SERVER" proto imap port 993		poll "IP_OF_MAIL_SERVER" proto imap port 993
	user "rt@mycompany.com" password "password"		user "rt@mycompany.com" password "password"
Line 87:		Line 87:
	# messgae		# messgae
	# auth password		# auth password

	# IMAP supports flags on individual messages to indicate the		# IMAP supports flags on individual messages to indicate the
	# message status. The 'Seen' flag indicates that the message has		# message status. The 'Seen' flag indicates that the message has
Line 98:		Line 98:
	# ignore 'Seen' flags and download all messages.		# ignore 'Seen' flags and download all messages.
	# fetchall		# fetchall

	mda '/opt/rt4/bin/rt-mailgate --url https://rt.mycompany.com --queue "support" --action correspond'		mda '/opt/rt4/bin/rt-mailgate --url https://rt.mycompany.com --queue "support" --action correspond'
	idle		idle
	----		----

	Prev: [[ManualApacheConfig]] --- Up: [[UserManual]] --- Next: [[ManualBasicAdministration]]		Prev: [[ManualApacheConfig]] --- Up: [[UserManual]] --- Next: [[ManualBasicAdministration]]
	[[Category:RT User Manual]]		[[Category:RT User Manual]]

Craigkai at 14:24, 22 March 2019

2019-03-22T14:24:25Z

Show changes

Blaine at 23:57, 21 March 2019

2019-03-21T23:57:30Z

Admin: 5 revisions imported

2016-04-06T20:14:27Z

5 revisions imported

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

207.75.165.174: newaliases path, add a hash in front of some comments in code preformat mode

2011-10-10T14:28:53Z

newaliases path, add a hash in front of some comments in code preformat mode

← Older revision		Revision as of 10:28, 10 October 2011
Line 45:		Line 45:
	The URL will be the URL for RT's web interface, such as http://issues.bestpractical.com/, [http://fsck.com/rt/ =]; whatever is the root of your RT install.		The URL will be the URL for RT's web interface, such as http://issues.bestpractical.com/, [http://fsck.com/rt/ =]; whatever is the root of your RT install.

	3) Stop and start your mail server, so it picks up your configuration changes. With sendmail or postfix (possibly others), you usually also need to type the command "newaliases" to get the server to recognize the new aliases.		3) Stop and start your mail server, so it picks up your configuration changes. With sendmail or postfix (possibly others), you usually also need to type the command "newaliases" to get the server to recognize the new aliases. If this command is unrecognized, it's probably not in your default path; a common location is "/usr/sbin/newaliases".

	4) Change the password. The default root password for the web interface is password, as installed. Changing this should be the first thing you do after installation.		4) Change the password. The default root password for the web interface is password, as installed. Changing this should be the first thing you do after installation.
Line 53:		Line 53:
	To configure a mail transfer agent (postfix) to post tickets to RT3 on a separate server ....		To configure a mail transfer agent (postfix) to post tickets to RT3 on a separate server ....

	(download and un-tar RT)		#(download and un-tar RT)
	./configure		./configure
	make sbin-install		make sbin-install
Line 66:		Line 66:
	The link to RT is now configured. However, the rt-mailgate script is a perl script which requires support. On a fresh [[SuSE]] 9.3 server install, the following was needed to provide the necessary perl libraries (someone with deeper knowledge may know of a more restrictive set of libraries, but these worked).		The link to RT is now configured. However, the rt-mailgate script is a perl script which requires support. On a fresh [[SuSE]] 9.3 server install, the following was needed to provide the necessary perl libraries (someone with deeper knowledge may know of a more restrictive set of libraries, but these worked).

	(install gcc and glibc, if necessary)		#(install gcc and glibc, if necessary)
	perl -MCPAN -eshell (to configure CPAN)		perl -MCPAN -eshell (to configure CPAN)
	perl -MCPAN -e 'install("LWP")'		perl -MCPAN -e 'install("LWP")'

← Older revision		Revision as of 10:31, 22 March 2019
Line 63:		Line 63:
	Fetchmail or Getmail can be used to fetch email from a inbox using IMAP or POP. An example configuration for Fetchmail can be seen below:		Fetchmail or Getmail can be used to fetch email from a inbox using IMAP or POP. An example configuration for Fetchmail can be seen below:
	set daemon 0		set daemon 0

	# PID files are more useful for forking systemd services. But fetchmail will		# PID files are more useful for forking systemd services. But fetchmail will
	# always write one. Since the service runs fetchmail as the apache user,		# always write one. Since the service runs fetchmail as the apache user,
	# www-data, we need to give fetchmail a path that it has write permission to.		# www-data, we need to give fetchmail a path that it has write permission to.
	#set pidfile '/opt/rt4/var/run/fetchmail-rtir.pid'		#set pidfile '/opt/rt4/var/run/fetchmail-rtir.pid'

	poll "IP_OF_MAIL_SERVER" proto imap port 993		poll "IP_OF_MAIL_SERVER" proto imap port 993
	user "rt@mycompany.com" password "password"		user "rt@mycompany.com" password "password"
Line 86:		Line 84:
	# authentication failures, which might eliminate this error		# authentication failures, which might eliminate this error
	# messgae		# messgae
	~~# auth password~~

	# IMAP supports flags on individual messages to indicate the		# IMAP supports flags on individual messages to indicate the
	# message status. The 'Seen' flag indicates that the message has		# message status. The 'Seen' flag indicates that the message has
Line 98:		Line 94:
	# ignore 'Seen' flags and download all messages.		# ignore 'Seen' flags and download all messages.
	# fetchall		# fetchall

	mda '/opt/rt4/bin/rt-mailgate --url https://rt.mycompany.com --queue "support" --action correspond'		mda '/opt/rt4/bin/rt-mailgate --url https://rt.mycompany.com --queue "support" --action correspond'
	idle		idle

	Lastly you will need a cronjob to pull your inbox periodically		Lastly you will need a cronjob to pull your inbox periodically
	`/1 * * * root /usr/bin/getmail --fetchmailrc /opt/rt4/etc/fetchmailrc --quiet`		`/1 * * * root /usr/bin/getmail --fetchmailrc /opt/rt4/etc/fetchmailrc --quiet`

← Older revision		Revision as of 19:57, 21 March 2019
Line 13:		Line 13:
	perldoc /<path to installed program>/rt-mailgate		perldoc /<path to installed program>/rt-mailgate

	(For Debian, the default path is /usr/bin.) The rt-mailgate program is installed in /opt/~~rt3~~/bin by default, so that command will probably be, more specifically:		(For Debian, the default path is /usr/bin.) The rt-mailgate program is installed in /opt/rt4/bin by default, so that command will probably be, more specifically:

	perldoc /opt/~~rt3~~/bin/rt-mailgate		perldoc /opt/rt4/bin/rt-mailgate

	unless you've moved your install (not build) directory.		unless you've moved your install (not build) directory.
Line 23:		Line 23:
	Add the following lines to /etc/aliases (or your local equivalent such as /etc/mail/aliases):		Add the following lines to /etc/aliases (or your local equivalent such as /etc/mail/aliases):

	rt: "\|/opt/~~rt3~~/bin/rt-mailgate --queue general --action correspond --url http://localhost/rt"		rt: "\|/opt/rt4/bin/rt-mailgate --queue general --action correspond --url http://localhost/rt"

	rt-comment: "\|/opt/~~rt3~~/bin/rt-mailgate --queue general --action comment --url http://localhost/rt"		rt-comment: "\|/opt/rt4/bin/rt-mailgate --queue general --action comment --url http://localhost/rt"

	(Replace /opt/~~rt3~~ by your RT installation path and http://localhost/rt by the URL of your RT installation on your webserver)		(Replace /opt/rt4 by your RT installation path and http://localhost/rt by the URL of your RT installation on your webserver)

	'''NOTE:''' When you add the above each alias entry should be all one line; make sure you include the quotes.		'''NOTE:''' When you add the above each alias entry should be all one line; make sure you include the quotes.
Line 37:		Line 37:
	The queue name may have spaces. <code>rt-mailgate</code> works as well with them, but do not forget to escape these spaces by enclosing the queue name in single quote:		The queue name may have spaces. <code>rt-mailgate</code> works as well with them, but do not forget to escape these spaces by enclosing the queue name in single quote:

	my-queue: "\|/opt/~~rt3~~/bin/rt-mailgate --queue 'My Queue' --action correspond --url http://localhost/"		my-queue: "\|/opt/rt4/bin/rt-mailgate --queue 'My Queue' --action correspond --url http://localhost/"

	If you are using the default sendmail included in most redhat distro's you will most likely need to copy (cp) rt-mailgate to /etc/smrsh or create a symbolic link and change /opt/~~rt3~~/bin above to /etc/smrsh or sendmail will complain. These sendmails will only execute programs as alias targets which have been blessed by placing them in a special directory. This is not necessary for Exim or postfix.		If you are using the default sendmail included in most redhat distro's you will most likely need to copy (cp) rt-mailgate to /etc/smrsh or create a symbolic link and change /opt/rt4/bin above to /etc/smrsh or sendmail will complain. These sendmails will only execute programs as alias targets which have been blessed by placing them in a special directory. This is not necessary for Exim or postfix.

	You'll choose from "--action correspond" and "--action comment" depending on whether the mail should be resent to the requestor. If you want the requestor to see it, choose correspond; if you want to keep it from the requestor, choose comment.		You'll choose from "--action correspond" and "--action comment" depending on whether the mail should be resent to the requestor. If you want the requestor to see it, choose correspond; if you want to keep it from the requestor, choose comment.
Line 51:		Line 51:
	You '''can''' have the mail gateway on your MX or some other server and have it talk to RT via HTTP. For more details, see [[InstallMailgateOnly]].		You '''can''' have the mail gateway on your MX or some other server and have it talk to RT via HTTP. For more details, see [[InstallMailgateOnly]].

	To configure a mail transfer agent (postfix) to post tickets to ~~RT3~~ on a separate server ....		To configure a mail transfer agent (postfix) to post tickets to RT4 on a separate server ....

	#(download and un-tar RT)		#(download and un-tar RT)