Hi, I'd like to setup virtual domains using authpgsql. I've done that
successfully. I want to make sure I understand my options for setting up
aliases. I think I have to choose between the following mutually exclusive
choices:
1) The catchall alias, which requires a local system account:
# in aliases file
@domain.com: localuser
PRO:
- can catch all unknown mail
CON:
- requires a local system account
- cannot mix with non-local (virtual) accounts?
2) Specifying distinct aliases in the PostgreSQL database; e.g.,
# in the passwd table
# id, home
[EMAIL PROTECTED], [EMAIL PROTECTED]
[EMAIL PROTECTED], [EMAIL PROTECTED]
Note that user2's "home" is the same as user1, so in that sense user2 is an
"alias" for user1.
PRO:
- can define all users in the db
CON:
- each "alias" (pseudo-alias?) creates a separate login
- cannot catch all unknown mail
It would be nice to have the ability to define aliases that are not logins
and to define a catch all for hosteddomains when using a database
authentication module (e.g., authpgsql). But it doesn't seem like that's
possible with Courier (without a patch).
Have I made a mistake in my analysis of my options?
Thanks,
// mark
-
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
