On Monday 16 July 2007 13:04:24 Sam Varshavchik wrote: > No. There's nothing wrong with aliases. But you need to describe your > problem clearly, and concisely.
True enough. I was switching backends in order to figure out if that was the
issue, and did not express myself clear enough.
Here is the current setup:
Using auth-pgsql, and its working.
This database holds email-_address_ => (clear, home, maildir, ..) mappings;
and this works. maildrop works as well.
For example, in the auth db, a user '[EMAIL PROTECTED]' may send mail via
smtp auth, and may receive mail to his maildir as defined in the database.
I can alias "[EMAIL PROTECTED]: [EMAIL PROTECTED]", and this works as
expected.
However, if I try to alias a complete virtual domain to an account, this
fails.
aliases: "@vdomain: [EMAIL PROTECTED]"
result: 550 User unknown.
Yes, I did makealiases, and -dump shows the expected result ("@vdomain:
[EMAIL PROTECTED]").
On a related note, I cannot get mailman to work with virtual domains. Here as
well all mails to any list address return 550.
(setup:
[EMAIL PROTECTED]: |/var/lib/mailman/mail/mailman owner
mailman)
I got the impression I am to use authentication accounts WITHOUT the domain
part in it, and then I am to map actual mail addresses to those local
accounts via aliases. However, that did not work as well (because makealiases
postfixed @`cat /etc/courier/me` to it automatically?).
Regards.
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/
_______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
