Possible to remove/control e-mail domain for cluster notifications?

[reidac]

Hi all --

I'm running the Debian-packaged GridEngine 6.2u4 on a small
cluster here, and I've recently discovered a problem with e-mail
notifications -- 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 it
only accepts mail for local delivery. The actual nodes run
"nullmailer", and are set up to default to a domain
which the mail relay recognizes as "local".

The problem is that this default local domain does not
correspond to the names of the submit hosts -- consequently
the 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 an
an interior DNS server for my cluster subnet with MX
records for the submit hosts that would translate them to
the mail relay's local domain.

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

Is this possible?

Thanks.

-- A.
--
Dr. Andrew C. E. Reid
Physical Scientist, Computer Operations Administrator
Center for Theoretical and Computational Materials Science
National Institute of Standards and Technology, Mail Stop 8555
Gaithersburg MD 20899 USA
***@nist.gov

------------------------------------------------------
http://gridengine.sunsource.net/ds/viewMessage.do?dsForumId=38&dsMessageId=301655

To unsubscribe from this discussion, e-mail: [users-***@gridengine.sunsource.net].

[reuti]

Hi,

Post by reidac
I'm running the Debian-packaged GridEngine 6.2u4 on a small
cluster here, and I've recently discovered a problem with e-mail
notifications -- the system is defaulting to sending these to
There actually is a mail relay on the cluster subnet, but it
only accepts mail for local delivery. The actual nodes run
"nullmailer", and are set up to default to a domain
which the mail relay recognizes as "local".
The problem is that this default local domain does not
correspond to the names of the submit hosts -- consequently
the 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 an
an interior DNS server for my cluster subnet with MX
records for the submit hosts that would translate them to
the mail relay's local domain.
But what I really want is for SGE to get it right in
the first place -- I'd like the default e-mails to be
addressed 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)

-- Reuti

Post by reidac
Is this possible?
Thanks.
-- A.
--
Dr. Andrew C. E. Reid
Physical Scientist, Computer Operations Administrator
Center for Theoretical and Computational Materials Science
National Institute of Standards and Technology, Mail Stop 8555
Gaithersburg MD 20899 USA
------------------------------------------------------
http://gridengine.sunsource.net/ds/viewMessage.do?dsForumId=38&dsMessageId=301655

------------------------------------------------------
http://gridengine.sunsource.net/ds/viewMessage.do?dsForumId=38&dsMessageId=301657

To unsubscribe from this discussion, e-mail: [users-***@gridengine.sunsource.net].

[reidac]

Post by reuti
Hi,

Post by reidac
I'm running the Debian-packaged GridEngine 6.2u4 on a small
cluster here, and I've recently discovered a problem with e-mail
notifications -- the system is defaulting to sending these to
There actually is a mail relay on the cluster subnet, but it
only accepts mail for local delivery. The actual nodes run
"nullmailer", and are set up to default to a domain
which the mail relay recognizes as "local".
The problem is that this default local domain does not
correspond to the names of the submit hosts -- consequently
the 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 an
an interior DNS server for my cluster subnet with MX
records for the submit hosts that would translate them to
the mail relay's local domain.
But what I really want is for SGE to get it right in
the first place -- I'd like the default e-mails to be
addressed 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)

Thanks Reuti -- a wrapper is probably pretty simple, I'll try that
first.

-- A.
--
Dr. Andrew C. E. Reid
Physical Scientist, Computer Operations Administrator
Center for Theoretical and Computational Materials Science
National Institute of Standards and Technology, Mail Stop 8555
Gaithersburg MD 20899 USA
***@nist.gov

------------------------------------------------------
http://gridengine.sunsource.net/ds/viewMessage.do?dsForumId=38&dsMessageId=301660

To unsubscribe from this discussion, e-mail: [users-***@gridengine.sunsource.net].

[hawson]

Hi Andrew,

Post by reidac
Hi all --
I'm running the Debian-packaged GridEngine 6.2u4 on a small
cluster here, and I've recently discovered a problem with e-mail
notifications -- the system is defaulting to sending these to

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

Post by reidac
There actually is a mail relay on the cluster subnet, but it
only accepts mail for local delivery. The actual nodes run
"nullmailer", and are set up to default to a domain
which the mail relay recognizes as "local".

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

The relevant bits of my psotfix conf...

on the head node main.cf:

# Set the domain
mydomain = domain.com
myorigin = $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.com
myorigin = $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 reidac
The problem is that this default local domain does not
correspond to the names of the submit hosts -- consequently
the 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 an
an interior DNS server for my cluster subnet with MX
records for the submit hosts that would translate them to
the 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 reidac
But what I really want is for SGE to get it right in
the first place -- I'd like the default e-mails to be
addressed to either just <username>, or
Is this possible?

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

[fx]

Post by hawson
I've gotten this to work with Postfix on both the head node and compute
nodes.

Does postfix work on the compute nodes without a daemon somehow? I
installed ssmtp (similar to nullmailer, I think) to avoid a daemon and
setuid binary, but it would be cleaner just to have one MTA.

Post by hawson

Post by reidac
There actually is a mail relay on the cluster subnet, but it
only accepts mail for local delivery. The actual nodes run
"nullmailer", and are set up to default to a domain
which the mail relay recognizes as "local".