Thanks for the "review" of things I thought I knew.
As it turns out, I already have several lists running on a vdomain.
The "vdomain" that was failing for me is not actually a vdomain - it is
a host_alias for the principal domain. (Had to do some digging to figure
So I guess my question is now much more complicated:
1) Can I create and manage a list for a host_alias? How?
2) If 1=no, is there any way to create a vdomain that behaves like a
host_alias. Then I can use the existing tools.
On 2011-01-13 12:47 PM, Eric Vey wrote:
> Hmm. I'm not sure I know what you mean, but I have had a list on a
> vdomain for years.
> Stop me if you know all this.
> There is a list admin GUI page. I get to it by http://mydom:7025
> Then Value added features in the left column.
> Then Mailing lists
> Then drop down the list under existing lists to select the vdomain and
> click refresh. This will show the list you created.
> That's where you populate the settings, members, etc.
> A file is created on the server with these settings (can't remember
> where now) and if I was afraid of things getting broken, I would copy
> that file to make a backup.
> Neil Herber (nospam) wrote:
>> I was trying to set up a new list on a virtual domain as described here:
>> It sort of works, but if I try to use the admin GUI to populate the
>> settings things get broken.
>> Could this be fixed so that the admin GUI properly handles the vdomain
>> list (my preference) or so that the admin GUI does not allow any
>> access to a vdomain list to prevent "accidents"?
Last Message | Next Message
Site Map |
Contact Netwin |
POP3 Mail Server |
Linux Webmail |
UnInstall instructions for all products
Copyright © 2017 Netwin Ltd. All rights reserved.