Emailing - Revision history

PeterThorpe: /* Introduction */

2019-11-14T08:49:46Z

‎Introduction

Jw297: /* Introduction */

2019-01-07T08:56:01Z

‎Introduction

Jw297: /* Introduction */

2019-01-07T08:29:14Z

‎Introduction

Jw297: /* Introduction */

2019-01-04T14:45:33Z

‎Introduction

Jw297: /* Introduction */

2019-01-04T14:44:55Z

‎Introduction

Rf at 11:44, 16 March 2017

2017-03-16T11:44:59Z

Rf at 09:47, 16 March 2017

2017-03-16T09:47:19Z

Rf: Created page with "= Introduction = This is mainly about emailing users when their jobs are finished. Only an easy workable solution is presented and it relies on gmail servers and having a sp..."

2017-03-16T09:46:56Z

Created page with "= Introduction = This is mainly about emailing users when their jobs are finished. Only an easy workable solution is presented and it relies on gmail servers and having a sp..."

New page

= Introduction =

This is mainly about emailing users when their jobs are finished.

Only an easy workable solution is presented and it relies on gmail servers and having a special gmail address.

On the frontend, first focus on the followinng file:
/etc/postfix/main.cf

Look for the '''relayhost''' parameter. We will set it as follows:

relayhost = [smtp.gmail.com]:587

This means that postfix will outsource most of the email subtasks to gmail's servers. Though this may sound easy, it also means one must comply with gmail rules which can be quite stringent (i.e. require more work in setting up) in terms of security. Something to get right is TLS and SASL.

For TLS, first of all let's get a good certificate. One that works is:
Equifax_Secure_CA.pem

Which may be found in
/etc/ssl/certs

We can copy it over into a new name to create
/etc/postfix/cacert.pem

Then we want to get the following lines into '''main.cf''':
smtp_use_tls = yes
smtp_tls_CAfile = /etc/postfix/cacert.pem

Now for SASL. We need to create a fil called
sasl_passwd

put all the gmail user and password details. I.e.
[smtp.gmail.com]:587 <gmail_address> <password>

A hash of this must be generated. Postfix has its own hasher, so it can be done as follows:
postmap sasl_passwd

You should get a new file called
sasl_passwd.db

after this operation.

Now main.cf needs to be told about all of this , so the following shoudl be included.

smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtp_sasl_security_options = noanonymous

This should get you most of the way there.

← Older revision		Revision as of 08:49, 14 November 2019
Line 7:		Line 7:

	in this case we want the mailer to be /usr/sbin/ssmtp		in this case we want the mailer to be /usr/sbin/ssmtp
		+
		+	/usr/sbin/ssmtp
		+
		+
		+	source /usr/sbin/ssmtp
		+	/usr/sbin/ssmtp start

	Then rolled out the following config to all of the nodes:		Then rolled out the following config to all of the nodes:

@@ Line 1: / Line 1: @@
 = Introduction =
-Works on Marvin. Nodes throwing an "Unable to set UseSTARTTLSCert="YES"" error.
+Works on Marvin. Nodes throwing an "Unable to set UseSTARTTLSCert="YES"" error but I suspect the real issue is that the nodes can't ping the mailhost server. Likely solution is setting up marvin as a mailhost/redirector and sending the email to marvin to forward onwards.
 Need to set the command used for email for each node usin g

@@ Line 1: / Line 1: @@
 = Introduction =
-Miracle done by Joe, Jan 2019.
+Works on Marvin. Nodes throwing an "Unable to set UseSTARTTLSCert="YES"" error.
 Need to set the command used for email for each node usin g

← Older revision		Revision as of 14:45, 4 January 2019
Line 66:		Line 66:
	# added cert PT 2018 0928		# added cert PT 2018 0928
	TLS_CA_FILE=/etc/pki/tls/certs/ca-bundle.crt		TLS_CA_FILE=/etc/pki/tls/certs/ca-bundle.crt
		+
		+
		+	It may be possible to make the output neater. Links for later reference
		+	http://gridengine.org/pipermail/users/2011-June/001140.html
		+	https://gridengine.markmail.org/search/?q=sge+mail+header+ben#query:sge%20mail%20header%20ben+page:1+mid:azhmwbsrn62akprk+state:results

@@ Line 1: / Line 1: @@
 = Introduction =
-This is mainly about emailing users when their jobs are finished.
+Miracle done by Joe, Jan 2019.
-Only an easy workable solution is presented and it relies on gmail servers and having a special gmail address.
+Need to set the command used for email for each node usin g
-On the frontend, first focus on the followinng file:
+in this case we want the mailer to be /usr/sbin/ssmtp
-Look for the '''relayhost''' parameter. We will set it as follows:
+Then rolled out the following config to all of the nodes:
-  relayhost = [smtp.gmail.com]:587
+ # /etc/ssmtp.conf -- a config file for sSMTP sendmail.
-This means that postfix will outsource most of the email subtasks to gmail's servers. Though this may sound easy, it also means one must comply with gmail rules which can be quite stringent (i.e. require more work in setting up) in terms of security. Something to get right is TLS and SASL.
+ # See the ssmtp.conf(5) man page for a more verbose explanation of the
-For TLS, first of all let's get a good certificate. One that works is:
+ # available options.
-  Equifax_Secure_CA.pem
-−
-Which may be found in
+ # The person who gets all mail for userids < 500
-  /etc/ssl/certs
+ # Make this empty to disable rewriting.
+ root=marvin-mail@st-andrews.ac.uk
-We can copy it over into a new name to create
-  /etc/postfix/cacert.pem
+ # The place where the mail goes. The actual machine name is required
+  # no MX records are consulted. Commonly mailhosts are named mail.domain.com
-Then we want to get the following lines into '''main.cf''':
+ # The example will fit if you are in domain.com and your mailhub is so named.
-  smtp_use_tls = yes
+  mailhub=mailhost.st-andrews.ac.uk
-  smtp_tls_CAfile = /etc/postfix/cacert.pem
+ # Example for SMTP port number 2525
-Now for SASL. We need to create a file called
+  # mailhub=mail.your.domain:2525
-  sasl_passwd
+ # Example for SMTP port number 25 (Standard/RFC)
+ # mailhub=mail.your.domain
-put all the gmail user and password details. I.e.
+  # Example for SSL encrypted connection
-  [smtp.gmail.com]:587 <gmail_address> <password>
+  # mailhub=mail.your.domain:465
-−
-A hash of this must be generated. Postfix has its own hasher, so it can be done as follows:
+ # Where will the mail seem to come from?
-  postmap sasl_passwd
+ #RewriteDomain=
-−
-You should get a new file called
+ # The full hostname
-  sasl_passwd.db
+ Hostname=marvin.st-andrews.ac.uk
-−
-after this operation.
+  # Set this to never rewrite the "From:" line (unless not given) and to
+ # use that address in the "from line" of the envelope.
-Now '''main.cf''' needs to be told about all of this , so the following shoudl be included.
+ FromLineOverride=YES
-−
-  smtp_sasl_auth_enable = yes
+ # Use SSL/TLS to send secure messages to server.
-  smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
+ UseTLS=YES
- smtp_sasl_security_options = noanonymous
+ UseSTARTTLSCert=YES
+  # added PT 201809
-This should get you most of the way there.
+ UseSTARTTLS=YES