Postak @ Etnetera
My feedback
9 results found
-
2 votesPostak @ Etnetera shared this idea ·
-
20 votesPostak @ Etnetera supported this idea ·
An error occurred while saving the comment An error occurred while saving the comment Postak @ Etnetera commentedThese two other ideas should be merged to this one and all their votes counted together:
https://axigen.uservoice.com/forums/294255-general/suggestions/37699177-storage-capacity-monitoring-management
https://axigen.uservoice.com/forums/294255-general/suggestions/16633336-email-notifications-for-a-domain-reaching-a-percen -
9 votesPostak @ Etnetera supported this idea ·
-
2 votesPostak @ Etnetera supported this idea ·
An error occurred while saving the comment Postak @ Etnetera commentedyes, this would be great
-
25 votesPostak @ Etnetera supported this idea ·
An error occurred while saving the comment Postak @ Etnetera commentedPlease add at least Fulltext search in WebAdmin -> Domain & Accounts -> Manage Accounts -> Search Account:
- in the case of the form of the account name givenname.surname, it would be useful to be able to search by surname -
1 vote
An error occurred while saving the comment Postak @ Etnetera commentedHi @Bradley Silverman,
As I wrote, I know, that I can do this in the CLI... the request is about the same feature in the WebAdmin interface.
Postak @ Etnetera shared this idea · -
1 votePostak @ Etnetera shared this idea ·
-
51 votesPostak @ Etnetera supported this idea ·
-
143 votesPostak @ Etnetera supported this idea ·
a) It would be great if Axigen can somehow notify the administrator that some storages are full, for example by email to the postmaster or in the WebAdmin interface in Storage Charts by using the exclamation marks and other background color.
b) It is also stupid that Storage Charts do not contain information on how much space is allocated by all of the message storage containers/files from the maximum possible allocation - currently the administrator must count manually: <Max number of message storage files> * <Max message storage file size> is greater than <Currently allocated disk space> ... :-(