Carlos Williams wrote:
Thanks for that info. Can someone also comment on this? I asked a
friend via email and this was his response to the same issue:
******************************
"I used nslookup to verify the address your queue is showing, and it
does correspond to je.jfcom.mil. But a request for the mail-exchangers
for jfcom.mil does not indicate that this host should be receiving
mail. The mail-exchangers for that domain are:
smtp01.jfcom.mil
smtp02.jfcom.mil
This is irrelevant. Your users addressed the mail to
....@je.jfcom.mil, not ....@jfcom.mil.
So this problem resolves into a new one: how did your Postfix come up
with the name je.jfcom.mil to send messages to? Did the user
explicitly specify that host as a target?
The user addressed it to @je.jfcom.mil, which is where postfix
is trying to deliver it. This could be a mistake on your
user's part, but it's not postfix's job to second-guess the
sender. It would be a horrible mistake for postfix to deliver
mail to a parent domain MX when the specified host is unreachable.
...
******************************
My question is how did he find smtp01.jfcom.mil? And more important,
why then is my Postfix server trying to send to a different smtp
address?
Your clueless friend looked up the mx for jfcom.mil. That's
not the recipient domain your user specified.
There is no problem with your server; it's doing exactly what
it's supposed to do.
The possible problems include
- recipient's mail server is down
- sender mis-addressed the mail
You could ask your user to verify the address, but other than
that, nothing for you to do.
-- Noel Jones