Michelle Konzack writes:
So my idea is, to use a script an rename all UNIX users by a construct like user00001 user00002 user00003 etcand 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?
This is mostly a system limitation. Last time I read this topic, Linux starts to grind down with around 20000 files in the same directory. But that's old info, things might have changed. And that applies to native Linux filesystems. With NFS-mounted filesystems, this becomes an issue for the NFS server (won't matter if the server is also Linux, of course).
You don't have to have just one alias defined in each file of its own. You can put everything into a single alias file.
Linux userids are 32 bits; but it is not advised to use 32 bit userids for compatibility with filesystems and APIs that expect 16 bit UIDs. Pretty sure one of them is NFS, so that's going to be your limiting factor.
pgpCPuW8GEU5l.pgp
Description: PGP 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
