sendmail not using mailertable relay

I've done this before and recently, but it's not working this time. I have the following in /etc/mail/mailtertable:

I did make mailertable.db and did restart sendmail. I then sent a message to a user at, but it delivered with the following in /var/log/maillog:
Mar 24 13:03:18 mail sendmail[3244]: t2OH3IHk003244:, (0/0), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=30313, relay=[] [], dsn=2.0.0, stat=Sent (t2OH3IvM003245 Message accepted for delivery)
Mar 24 13:03:19 mail sm-mta[3252]: t2OH3IvM003245: to=<>, delay=00:00:01, xdelay=00:00:01, mailer=esmtp, pri=120470, [], dsn=2.0.0, stat=Sent (t2OH3IhV003613 Message accepted for delivery)

Open in new window

As you can see, it didn't even try to use the server and went right to

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

I think your syntax might be incorrect

first, I would check whether the feature to translate is enabled.
Then the entry might need to be
domain SMTP:mailserver

not clear what you are looking to do, are you looking to route email sent to through's mailserver?

I believe the use of mailertable will only try to send emails destined to the domain in the pattern through the mailertable route, if it is unreachable, I do not believe it will fall through and attempt to send to MX.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Try using this:

MarkAuthor Commented:
Putting SMTP: in front of the target server did the trick, although I successfully did this with a different target server a week ago without the SMTP: prefix. Not sure why it worked then. Maybe something to do with the target server. Dunno. Anyway, that solved my problem.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Email Servers

From novice to tech pro — start learning today.