At 20:49 02/08/2004, you wrote:
<snip />
This is extremely common, read the manpage for ezmlm-reject
Hello,
Yes I read it (-T option), but the mailing list had been created by qmailadmin. Do we consider it as a bug ?
How is it possible solve this problem with qmailadmin when we create a mailing list via the interface on a domain name which have domain aliases ?
Hi Nicolas,
aliased domains work identically to regular domains.
When a mail account or forward is created it is typically stored beneath .../vpopmail/domains/regular_domain.
When an alias domain is created a mapping is created in /var/qmail/users/assign that points the alias domain to the regular domain. That way mail to [EMAIL PROTECTED] will always be delivered by qmail to [EMAIL PROTECTED]
When a mailing list is created the login domain name is inserted into .../vpopmail/domains/regular_domain/list_name/inhost,outhost and several other files. N.B. that whichever domain was specified during login will become the list's new domain.
Mail to [EMAIL PROTECTED] and mail to [EMAIL PROTECTED] will both be delivered by qmail to the appropriate account; however, *only* mail to the domain specified in the list control files will be accepted by ezmlm. This is _not_ a qmailadmin issue; this is the way that ezmlm works.
So, here's the rule: If you want to modify a list you must login using the same domain you used when you created the list; if you login using a different domain and then modify the list in *any* way, the login domain becomes the list's new domain.
Hope that clears things up a bit.
Mike Wright
