Hi there, after some discussion on the vchkpw list it seemed that the following issue fits better into the qmailadmin list.
The current behaviour of qmailadmin is to use the real domain of a user for every action, even if the user logged in with an alias domain. This isn't a problem with POP3, IMAP4, SMTP and so on, where [EMAIL PROTECTED] and [EMAIL PROTECTED] are equivalent. However, ezmlm lists are bound to exactly one domain (ezmlm will bounce mails if sent to an alias domain name, telling the sender that it didn't find its own list address in To: or Cc:), and it isn't always the best way to force this domain to be the real domain. For example, in my setup I have an "internal" real domain in the style of <userid>.user.jonaspasche.com where one or more alias domains can be added to. Works fine in every manner, but not with ezmlm, which is fixed to the internal hostname. Even for setups that use a "real domain" as the real domain it could be nice to let the user simple choose in which of his "n" alias domains he wants to create the mailing list. The simplest thing (IMHO) would be to just re-use the domain name he entered through the login process. As a quick hack, I disabled the line in vpopmail.c's vget_assign function that overwrites the given domain name with the real domain name. This seems to work fine for my setup, but according to Michael Bowe it will break all alias domain functionality when using the MySQL backend, because vpopmail wouldn't find any configuration information when looking for the wrong domain name. After some discussion, Tom Collins suggested to change qmailadmin to reuse the domain name entered for actions like creating ezmlm lists. Are there any comments on this? Possible problems? Suggestions? Thanks, Jonas
