Hi.
Here is the setup of our Departmental Linux network:
(1) Our subnet of the University network is called dsm.fordham.edu, with IP
addresses 150.108.64.x.
(2) Our mail spool is on a machine that is MX'ed to dsm.fordham.edu. This
mail spool is NFS-visible on all machines.
(3) Our lab machines are on a subnet (10.11.3.x) that is separate from the
rest of the network. The router connecting the lab machines to the
rest of the network is at 150.108.64.100, a/k/a linux-user.dsm.fordham.edu
in /etc/hosts and the NIS hosts map. The router uses NAT.
(4) The mail alias for root on all machines is root [at] dsm.fordham.edu.
The hostnames of all the lab machines had been linux-user.dsm.fordham.edu.
This led to a problem, namely, that it was impossible to disambiguate the
mail msgs that were coming from the lab machines; they all appeared to be
addressed to root [at] linux-user.dsm.fordham.edu.
For this reason, we changed the hostnames of the lab machines to be
linux-user-101.dsm.fordham.edu (etc.).
Having done same, mail that is sent to root of the lab machines is now
winding up at dsm.fordham.edu (good!), but prepended with an error msg:
---%<------%<------%<------%<--Cut-Here-%<------%<------%<------%<---
----- The following addresses had permanent fatal errors -----
root [at] dsm.fordham.edu
(reason: 553 5.1.8 <root [at] linux-user-101.dsm.fordham.edu>... Domain of
sender address root [at] linux-user-101.dsm.fordham.edu does not exist)
(expanded from: <root [at] linux-user-101.dsm.fordham.edu>)
----- Transcript of session follows -----
.... while talking to dsm.dsm.fordham.edu.:
>>> MAIL From:<root [at] linux-user-101.dsm.fordham.edu> SIZE=1664
<<< 553 5.1.8 <root [at] linux-user-101.dsm.fordham.edu>... Domain of sender
address root [at] linux-user-101.dsm.fordham.edu does not exist
501 5.6.0 Data format error
---%<------%<------%<------%<--Cut-Here-%<------%<------%<------%<---
After reading Q4.5 in the sendmail FAQ, I added "linux-user.dsm.fordham.edu"
to /etc/mail/local-host-names on the lab machines. This gets rid of the
error msg, but the mail now appears to come from linux-user.dsm.fordham.edu,
rather than linux-user-101.dsm.fordham.edu.
The FAQ also said:
> There are a couple of additional cases where you don't actually want local
> delivery, and thus adding domain.net to class w is not the right fix:
>
> (*) When relay.domain.net should just be acting as a forwarder, e.g. a
> firewall/gateway box. The proper fix could be to set up a mailertable
> entry for domain.net.
But I'm not quite sure how to do this. Moreover, some of the documentation
on mailertables talks about changing MX recordsd. We don't have control
over the DNS entries for our subdomain, and getting The Powers That Be to
change them takes a long time, so interactive experimentation is out of the
question.
I would appreciate any suggestions on how to get rid of the error msgs, but
still have it look as if the msgs are coming from the address
root [at] linux-users-101.dsm.fordham.edu.
Thanks.
--
Art Werschulz (8-{)} "Metaphors be with you." -- bumper sticker
GCS/M (GAT): d? -p+ c++ l u+(-) e--- m* s n+ h f g+ w+ t++ r- y?
Internet: agw STRUDEL cs.columbia.edu
ATTnet: Columbia U. (212) 939-7060, Fordham U. (212) 636-6325
