I'm running the Debian-packaged GridEngine 6.2u4 on a smallcluster here, and I've recently discovered a problem with e-mailnotifications -- the system is defaulting to sending these to"<user>@<submit-host>", but these mails are getting stuck.

There actually is a mail relay on the cluster subnet, but itonly accepts mail for local delivery. The actual nodes run"nullmailer", and are set up to default to a domainwhich the mail relay recognizes as "local".

The problem is that this default local domain does notcorrespond to the names of the submit hosts -- consequentlythe mail relay is blocking these messages.

A work-around is for users to put "#$ -M <username>"(or "#$ -M <username>@<local-domain>") in their scripts.A more automatic set-up could be achieved if I set up anan interior DNS server for my cluster subnet with MXrecords for the submit hosts that would translate them tothe mail relay's local domain.

But what I really want is for SGE to get it right inthe first place -- I'd like the default e-mails to beaddressed to either just <username>, or<username>@<prescribed-domain-independent-of-submit-host>.

Post by reidacI'm running the Debian-packaged GridEngine 6.2u4 on a smallcluster here, and I've recently discovered a problem with e-mailnotifications -- the system is defaulting to sending these toThere actually is a mail relay on the cluster subnet, but itonly accepts mail for local delivery. The actual nodes run"nullmailer", and are set up to default to a domainwhich the mail relay recognizes as "local".The problem is that this default local domain does notcorrespond to the names of the submit hosts -- consequentlythe mail relay is blocking these messages.A work-around is for users to put "#$ -M <username>"A more automatic set-up could be achieved if I set up anan interior DNS server for my cluster subnet with MXrecords for the submit hosts that would translate them tothe mail relay's local domain.But what I really want is for SGE to get it right inthe first place -- I'd like the default e-mails to beaddressed to either just <username>, or

you have two options:

a) use an SGE mail-wrapper

b) adjust the domain in e.g. postfix:

$ cat sender_canonical/^(.*@).*$/ ${1}domain.example.invalid

(main.cf must be changed from hash to regexp for sender_canonical, no postmap necessary)

Post by reidacI'm running the Debian-packaged GridEngine 6.2u4 on a smallcluster here, and I've recently discovered a problem with e-mailnotifications -- the system is defaulting to sending these toThere actually is a mail relay on the cluster subnet, but itonly accepts mail for local delivery. The actual nodes run"nullmailer", and are set up to default to a domainwhich the mail relay recognizes as "local".The problem is that this default local domain does notcorrespond to the names of the submit hosts -- consequentlythe mail relay is blocking these messages.A work-around is for users to put "#$ -M <username>"A more automatic set-up could be achieved if I set up anan interior DNS server for my cluster subnet with MXrecords for the submit hosts that would translate them tothe mail relay's local domain.But what I really want is for SGE to get it right inthe first place -- I'd like the default e-mails to beaddressed to either just <username>, or

a) use an SGE mail-wrapper$ cat sender_canonical(main.cf must be changed from hash to regexp for sender_canonical, no postmap necessary)

Post by reidacHi all --I'm running the Debian-packaged GridEngine 6.2u4 on a smallcluster here, and I've recently discovered a problem with e-mailnotifications -- the system is defaulting to sending these to

I've gotten this to work with Postfix on both the head node and computenodes.

Post by reidacThere actually is a mail relay on the cluster subnet, but itonly accepts mail for local delivery. The actual nodes run"nullmailer", and are set up to default to a domainwhich the mail relay recognizes as "local".

At a minimum, you'll need to configure the MTA on the head node to relaymail for the cluster subnet. Unless, of course, your nodes can connectdirectly to an external mail server...

The relevant bits of my psotfix conf...

on the head node main.cf:

# Set the domainmydomain = domain.commyorigin = $myhostname

#Relay for these networks:mynetworks = 127.0.0.0/8 10.5.0.0/23

# Now, send all outbound mail, including that# which is relayed elsewhere. The brackets mean# do *NOT* check MX records for the mail server;# just send to this host. Period.relayhost = [mailrelay.domain.com]

On the compute nodes:

mydomain = cluster.domain.commyorigin = $mhostname

# Send all mail *ONLY* to the head node for relaying.relayhost = [10.5.0.1]

Also make sure that you set postfix to listen on the correct interfaces.

Post by reidacThe problem is that this default local domain does notcorrespond to the names of the submit hosts -- consequentlythe mail relay is blocking these messages.A work-around is for users to put "#$ -M <username>"A more automatic set-up could be achieved if I set up anan interior DNS server for my cluster subnet with MXrecords for the submit hosts that would translate them tothe mail relay's local domain.

You could tell users to add this to their respective ~/.sge_request files,but that's a poor workaround, not a solution.

Post by reidacBut what I really want is for SGE to get it right inthe first place -- I'd like the default e-mails to beaddressed to either just <username>, orIs this possible?

I think that SGE is pretty simple when it comes to mail handling--itjust passes what it is given off to the mail subsystem. If that doens'twork correctly, SGE won't either.

Post by reidacThere actually is a mail relay on the cluster subnet, but itonly accepts mail for local delivery. The actual nodes run"nullmailer", and are set up to default to a domainwhich the mail relay recognizes as "local".

--Dave LoveAdvanced Research Computing, Computing Services, University of LiverpoolAKA ***@gnu.org