Conversation
…) after a mailbox is created.
… it return a false. This is required to do additional checks in plugins that can stop the main application to finish the action.
…ugins give green light to continue with the deletion.
…etion of an aliases that is marked as required.
…le which can be used to stop the toggle function with a hook for class Alias.
…urn value to not break interrupt flow.
…to return error message to user why a alias could not be deactivated.
…akes sures that aliases are created if the complete domain is forwarded to another address.
|
Seems to me, that the plugin creates defined aliases right after we created first alias on a new domain. |
|
It does not make sense to create the aliases after the domain is created, because there is no destination defined where the mails should be sent or stored. The plugin is creating the aliases after a forward to an external address is defined or after a mailbox is defined. |
|
Hmmm... I really don't understand why someone would solve this problem in such a complex way. Do I miss something? You (silently) require the first alias/mailbox created to be the administrators one. But: If I don't know ("non-skilled users") that I need such "administrator addresses", why would I create a "administrator address" first, rather than a random "user address"? I think the best solution would be a static config parameter. When a domain is created, ViMbAdmin should create multiple aliases to this configurable destination. We're talking about "non-skilled users", "professional users" have their own solution for this. |
|
Probably it is better to display a notice, that this domain is missing some default addresses as log as they are not created. You should probably be able to dismiss that message if you do not intend to create those anyway. For a "non-skilled" user you certainly need to explain a little why he is needing those addresses and what each of it is for. Otherwise he would probably delete them afterwards anyway. |
This plugin enable a feature to automatically create aliases defined in application.ini.
There are some standard aliases that must always exist and a standard user is not aware of the fact that e.g. postmaster@domain must exist. The alias abuse@domain should exist, if not it is possible that your domain will get into a spam blacklist.
This plugin ensures that also a not skilled user as always the required aliases active.