Hello *, I have following server:
<storrage00.tdnet.eu> (store all the UNIX users and
there content)
<mail.tamay-dogan.net> (has <storrageNN> over NFS mounted)
<pgsql> (non public)
<tdhome.net> (access all the ~/public_html/
on the <storrageNN> servers)
<tdcloud.net> (access private date on
)
<vserver00.tdnet.eu> (store websites and can access ~/web/
over NFS on <storrageNN> servers)
All the users where created on <storage00> as "normal" UNIX users and
there login name is also there email address. So, now you can imagine,
that this give problems if <mail> is responsable for different domains,
where maybe two users have the same names...
So my idea is, to use a script an rename all UNIX users by a construct
like
user00001
user00002
user00003
etc
and then use the /etc/courier/aliases/ directory to point the EMail
adresses to the new user construct.
Do you think, this is OK?
I mean, I do absolutely not want to use LDAP. But I can use the
PostgreSQL to use the mapping or whatever is required. I mean, I can
use pam_pgsql and courier authpgsql.
Since my users can creathe ANY mail names of there choice, every user
has a ~/.courier_aliasses file which is maped to /etc/courier/aliases/
and whatched by a cron process for changes which run "makealiases".
Question: Is there a limitation in the number if files or symlinks in
the /etc/courier/aliases/ directory? I think also on using
my PostgreSQL for all this aliasses and generate only one
file automated which then run "makealiases"
Any suggestions?
Thanks in avance
--
Michelle Konzack ITSystems
GNU/Linux Developer 0033-6-61925193
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
