In article <slrnimifal.fte.saper(a)saper.info>fo>,
Marcin Cieslak <saper(a)saper.info> wrote:
I am currently having
"MYPRIMARYEMAILADDRESSOUTSIDE,\saper" in my $HOME/.forward
which gives me a nice capability to use mail(1) or mailx(1) to quickly read
whatever my jobs running on the localhost do. I do not mind
*not* having this replicated accross the cluster, so a process running
on willow sends mail to willow etc.
I do not have any LDAP entry related to mail (and
it's fine, too).
Will local delivery on the Solaris boxes still
Yes, this will still work. However, since you have a .forward file,
your LDAP email address will be entirely ignored. This means that email
to saper(a)toolserver.org will be delivered to your local account on
hawthorn or clematis as well as being forwarded to your forwarding
If you have no email address set in LDAP, then nothing will change from
how it works at the moment, except that incoming mail from outside the
Toolserver will arrive on clematis/hawthorn instead of on nightshade.
I understand that all hosts will start processing LDAP
and forwarding the rest to the two hosts you named.
Not exactly. clematis and hawthorn will only handle incoming SMTP, i.e.
mail to user(a)toolserver.org...
From the point of redundancy, I'd rather have
local mail delivered where
it originated, since that host is most possibly up. I personally don't
care much about mail originated externally (preferably I'd like
to have one local mailbox to clean up).
... which mean that if you send mail from a Toolserver system, it will
be delivered by that system, whether it's delivered locally or forwarded
elsewhere. This includes mail from SGE and from cron, and it applies
even if you send mail to an @toolserver.org address. hawthorn/clematis
are only special because they will be listed as the mail exchangers for
Will local, per-host mail (from mail(1) or SGE) be
Yes, as above.