hi All,
Thank you for you replies.
It indeed seem that the linsrv is thinking that he is the MTA for the domain.
Ivan
====
>What do you have in /etc/mail/local-host-names?
Nothing. Just: "# local-host-names - include all aliases for your machine here."
> Also, you may try changing your DS (smart host) from FQDN to IP, like this:
[root@linsrv mail]# grep -i "DS\[" sendmail.cf
DS[198.168.199.16]
[root@linsrv mail]#
In spite of these changes, it again the local hosts that is replying to the sendmail request:
[root@linsrv mail]# sendmail -v -d9.99 -d38.99 abcx@mydom.mu < /dev/null
getauthinfo: root@localhost
openmap() dequote:dequote NULL: valid
openmap() host:host NULL: valid
host_map_lookup(mydom.mu) => getcanonname(mydom.mu), trying dns
getcanonname(mydom.mu), found
FOUND mydom.mu
host_map_lookup(mydom.mu) => CACHE mydom.mu
abcx@mydom.mu... Connecting to [127.0.0.1] via relay...
220 sdblx2.cmt.mu ESMTP Sendmail 8.13.1/8.13.1; Fri, 30 Nov 2007 12:35:31 +0400
>>> EHLO linsrv.mydom.mu
250-linsrv.mydom.mu Hello linsrv.mydom.mu [127.0.0.1], pleased to meet you
250-ENHANCEDSTATUSCODES
...
I also found that our new MS Exchange Server has the "content filter" feature enabled. But still, the problem does not seem to be so far away!
further ideas will be most welcomed.
kind regards
yogeeraj
No person was ever honoured for what he received. Honour has been the reward for what he gave (clavin coolidge)