sendmail: stickyhost; @host.domain.com

Hi. I have my DNS setup so that *.domain.name points to the same IP; am using sendmail 8.8.5 on a BSD/OS 3.0 system.

How do I setup sendmail.cf so that it does not "scrunch" user@host.domain.name to merely user@domain.name? I suppose it's FEATURE(stickyhost) in the .mc file but I can't simply generate a new sendmail.cf using m4 due to virtual server limitations.

Or perhaps, is there some rule that I should comment out or add so that user@host1.domain.name and user@host2.domain.name can point to different addresses (via virtmaps)?

Another way to state this would be, how do I get virtmaps to support @host.domain.name entries? I got it running fine for @domain.name entries.

Looking for rule(s), not m4 macros...

Thanks!
LVL 1
dirgeAsked:
Who is Participating?
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.

dirgeAuthor Commented:
Edited text of question
0
dhughes111797Commented:
Try this:
look for rules that have something like this in
them:
R$+ @ $+ . $m    or
R$+ < @ $+ . $m >   or
R$+ < @ $* . $m >   or
R$+ < @ $- . $m >
comment them out, then put sendmail in test mode with this new config file and try it out. If it doesn't work, it might help if you post the current sendmail.cf file that you are using.
0

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
dirgeAuthor Commented:
Actually, I found out that it is impossible with my particular setup: the mail relays do the "scrunching", i.e. canonicalization. You get the points for your time though... :)

The possible solutions would be: to assign separate IP addresses to each host so that host.domain.name does not get canonicalized down to domain.name; and to scan the headers for the first/lowermost "Received:... for <user@host.domain.name>" line. Unfortunately, the latter is not a sure thing. Some relays don't add the "for" clause.
0
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
Unix OS

From novice to tech pro — start learning today.