From: Hank on
I have been configuring a Ultra 20 M2 with Solaris 10 u8 10/08 loaded
from scratch on a new hard disk. Since the installation will include
a Mailman mail server, I wanted to give sendmail a thorough checkout
before proceeding. I had already set up three user accounts on the
machine a couple of weeks ago.

After changing DOMAIN to solaris-antispam (Sun STILL ships with
relaying enabled) in main.mc, I did a quick check of the aliases file
and added a couple for local use, then ran newaliases.

Sending mail to any of the user accounts from another ISP, I got a
"loops back to me" failure. I could sent to root. The three accounts
are the same names as on another IP machine at my site, so I figured
"interaction" of some sort. Tried adding a new account with a
username not used elsewhere, and could send to that.

After nearly a day of jiggery-pokery, auditing my router setups,
named zone files, and disconnecting the router between two LAN's, I
saw in the logs a complaint that the aliases data bases were out of
date.

I took a good hard look at the aliases file, as I had not touched it,
to see what might have changed. At the bottom, every one of the users
I had added had an alias of the form:
username:username(a)127.0.0.1.

That turned out to be my looping problem. I took those out, ran
newaliases, and can now receive mail sent over the internet backbone
at all accounts.

My question: what put those aliases in that file? I have a hunch that
it was using the SMC to add users rather than command line.

This was Solaris 10 x86 10/08, but I'll guess that the Sparc version
behaves the same. Why does something add those aliases?

Hank

From: nelson on
> username:username(a)127.0.0.1.

it's been a while since i've done much with sendmail but that's
certainly odd - but i've never actually used SMC to provision users.

as a quick test, if you add another user with SMC does it an entry
appear in the aliases file for that user?