Fany, Are you able to send us some of the lines from the /var/log/maillog file which indicateds why the email server is rejecting the email? Thankyou
-----Original Message----- From: Fany Pages [mailto:fpa...@udio.cujae.edu.cu] Sent: 05 October 2016 16:30 To: slurm-dev <slurm-dev@schedmd.com> Subject: [slurm-dev] Re: Send notification email Thanks anyway. All the best. Fany -----Mensaje original----- De: John Hearns [mailto:john.hea...@xma.co.uk] Enviado el: miércoles, 5 de octubre de 2016 11:20 Para: slurm-dev Asunto: [slurm-dev] Re: Send notification email Fany, You are correct. I understand this a bit better now. My answer I am afraid is that you will have to ask your corporate IT people to allow email from this address. I recently dealt with a similar case at a university. The mail servers were refusing to accept mail from the cluster head node, as it did not have a reverse DNS access. I n the end we had to configure email to go via an Office365 server! Other people on the list may be able to offer a better solution though. -----Original Message----- From: Fanny Pagés Díaz [mailto:fpa...@citi.cu] Sent: 05 October 2016 15:45 To: slurm-dev <slurm-dev@schedmd.com> Subject: [slurm-dev] Re: Send notification email Yes, I refer to the external network IP cluster is not valid out, my domain is not registered (@ cluster.citi.cu) therefore is not in the MX records, so when I relay in my postfix, my corporate mail server refuses mails go out of my internal network. I think that's what is happening. I'm wrong? -----Mensaje original----- De: John Hearns [mailto:john.hea...@xma.co.uk] Enviado el: miércoles, 5 de octubre de 2016 10:17 Para: slurm-dev Asunto: [slurm-dev] Re: Send notification email Fany, Many clusters which have an internal network which is a private network. However the other interface on the cluster head node, which is normally called the 'external' interface can have a real, proper IP address on your external network. It will therefore be able to send email. The cluster compute nodes can be configured to 'relay' email via the head node. -----Original Message----- From: Fanny Pagés Díaz [mailto:fpa...@citi.cu] Sent: 05 October 2016 15:13 To: slurm-dev <slurm-dev@schedmd.com> Subject: [slurm-dev] Re: Send notification email Hi, Thanks for your answer. My HPC cluster does not have a real IP segment, it is a test cluster. Therefore it not recognized in the external network. So, I need try to another way. All the best, Fany -----Mensaje original----- De: Christopher Samuel [mailto:sam...@unimelb.edu.au] Enviado el: martes, 4 de octubre de 2016 18:43 Para: slurm-dev Asunto: [slurm-dev] Re: Send notification email On 03/10/16 23:39, Fanny Pagés Díaz wrote: > I have a slurm running in the same HPC cluster server, but I need send > all notification using my corporate mail server, which running in > another server at my internal network. I not need use the local > postfix installed at slurm server. The most reliable solution will be to configure Postfix to send emails via the corporate server. All our clusters send using our own mail server quite deliberately. We set: relayhost (to say where to relay email via) myorigin (to set the system name to its proper FQDN) aliasmaps (to add an LDAP lookup to rewrite users email to the value in LDAP) But really this isn't a Slurm issue, it's a host config issue for Postfix. All the best, Chris -- Christopher Samuel Senior Systems Administrator VLSCI - Victorian Life Sciences Computation Initiative Email: sam...@unimelb.edu.au Phone: +61 (0)3 903 55545 http://www.vlsci.org.au/ http://twitter.com/vlsci Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Employees of XMA Ltd are expressly required not to make defamatory statements and not to infringe or authorise any infringement of copyright or any other legal right by email communications. Any such communication is contrary to company policy and outside the scope of the employment of the individual concerned. The company will not accept any liability in respect of such communication, and the employee responsible will be personally liable for any damages or other liability arising. XMA Limited is registered in England and Wales (registered no. 2051703). Registered Office: Wilford Industrial Estate, Ruddington Lane, Wilford, Nottingham, NG11 7EP Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Employees of XMA Ltd are expressly required not to make defamatory statements and not to infringe or authorise any infringement of copyright or any other legal right by email communications. Any such communication is contrary to company policy and outside the scope of the employment of the individual concerned. The company will not accept any liability in respect of such communication, and the employee responsible will be personally liable for any damages or other liability arising. XMA Limited is registered in England and Wales (registered no. 2051703). Registered Office: Wilford Industrial Estate, Ruddington Lane, Wilford, Nottingham, NG11 7EP Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Employees of XMA Ltd are expressly required not to make defamatory statements and not to infringe or authorise any infringement of copyright or any other legal right by email communications. Any such communication is contrary to company policy and outside the scope of the employment of the individual concerned. The company will not accept any liability in respect of such communication, and the employee responsible will be personally liable for any damages or other liability arising. XMA Limited is registered in England and Wales (registered no. 2051703). Registered Office: Wilford Industrial Estate, Ruddington Lane, Wilford, Nottingham, NG11 7EP
