--Rafa� Krzewski wrote on 05.02.03 14:37 +0100: > 1) using ordinary aliases > > Courier FAQ, under Q: using wirtual domains states that it is possible > to use sendmain-style virtual domains with the following alias entry: > > [EMAIL PROTECTED]: maciek > etc.
And where is the problem with that ? > On the other hand, manual page for makehosteddomains contains the > folowing "NOTE that [EMAIL PROTECTED] must be a real account, not a mail > alias.". This 'alias@' is confusing and not what you want. Its simply a domain-wildcard and the same convention is used in authuserdb, authmysql etc. It really should be named 'default@' to be consistend with dot-courier (.courier-default), but thats probably too late. > This makes me wonder how would the aforementioned sendmail-style alias > work. My understanding is the following > -if I put pah.grupy.engo.pl into hosteddomains courier will look for > a local mailbox named '[EMAIL PROTECTED]' ignoring aliases > alltogether, and will fail to deliver the message. [...] > If the sendmail-style aliases really work I'm obviously missing > something, I'd mostly appreciate explainations. Just give it a try. Using aliases will cause rewriting of the receipient-address (recorded in the Delivered-To) with @me, this would be the only valid reason to avoid them at a isp. > 2) creating artificial LDAP entries > > Since courier would be looking for local account named > '[EMAIL PROTECTED]' I could add the following entry to LDAP: Also userdb would work, without using aliases at all. Create multiple entries for all receiving addresses. Roland ------------------------------------------------------- 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
