Viktor Dukhovni <postfix-us...@dukhovni.org> wrote ..
> When not material (i.e. not resolving a problem with a particular
> domain), you can choose to consitently lightly obfuscate domain names
> and email addresses, in a consistent manner, a=>a, b=>b, ...
Would require a lot of search & replace. Whattheheck, it isn't like the bad
guys aren't all over the new machine already *anyway.* (Although I still might
change user account names. Don't want to make it *too* easy for 'em. ;)
> For a deper exposition of concepts, you could either of the two books
> (O'Reilly or No Starch).
Right now the goal is to just get it running. "Deeper exposition" will need
to wait. I am keeping a log, though, so maybe I can write something up for the
next schlub who needs to do this.
> - Run not walk away from using the legacy /etc/aliases file.
> Use it ONLY for:
I'm good there, I think. The /etc/aliases file is tiny, basically the
default sending system accounts to root; even the mailman list aliases were
removed many years ago and moved to virtusertable along with the SmartList
lists (yeah, I know, but it's hellish fast). That file, however, is 60k+ (1600+
lines, although a sizable amount is remmed crap I need to rip out anyway). But
before you point to that as the root of all problems, right now in postfix I
have a ONE-LINE virtusertable hashed, and THAT ONE LINE has me dead-stopped in
my tracks and coming here asking if it's ok to post because @$mydomain gets
grafted onto the unix account name it's pointing to causing a fail.
So there's that... (Sorry, I'll type up the issue properly including
postconf output and logs someone tomorrow after I get all the reading done.)
Charlie
