General
| Influence Axigen’s future product evolution — get early access to new features mockups, prototypes, and early previews and tell us your opinion. Join our product community newsletter |
276 results found
-
Cluster like Exchange DAG
You could implement Cluster like Exchange DAG does. In this way no more shared LUN is necessary and it even easy to cluster Axigen Server across multiple ESXi or Hyper-V.
This can bring a very nice feature to Axigen that no other Email product has (apart Exchange).
Think about!26 votes -
More informative error notifications
If one user tries to send a message to another with the full mailbox (overquota) within axigen webmail domain, operation fails and he gets "the message could not be send" error though the address exists.
14 votes -
Kaspersky AntiSpam filter
It is possible that Kaspersky Antispam didn't check local postal addresses never or it is possible to make an option of shutdown of check on spam for users of one domain?
2 votes -
check MX record and reverse DNS
There is one more problem:
Axigen -> DNS Check
use Reject message if originator's domain has no MX entry
use Reject message if the originalting IP has no reverse DNS entryIf i use this two rules, they work as ALL conditions(not ANY conditions), that is wrong.
it is possible to make so that checked the MX record first and then checked reverse DNS,
and if MX record pass then don't checked reverse DNS.
Because not always MX record = A record in DNSThat is Reverse DNS has to be included only for entering connections or has to exclude…
1 vote -
BlackList and WiteList
For example, I incidentally added to a black list and in white the same sender and when receiving mail it automatically gets to Recycled folder.
What to avoid such situation in the future, can make:
1. The first verification of the white list and then the black
And if the addressee is in the white list, in black to ignore
2. Or
If you add to the white list, and the addressee is in black, reported about it
(and if you add to a black list, and the addressee is in white)4 votes -
Please focus on improving your core functionality
Please don't waste time on this when there are proven free tools out there like https://owncloud.org/.
5 votes -
Bulk update/modification feature on webadmin
our customers asked from us to implement a bulk update/modify/delete/insert feature, to be able to change an attribute for more accounts ot domains in same time.
7 votes
AdminGabriel
(PM, Axigen)
responded
Could you give me some examples of attributes that your customers would like to bulk change? Can’t this be done using account classes?
-
Hide Received header from authenticated messages
Please consider to implement an option that will allow Axigen to hide (like not include) 'Received' header from the sent messages which are received through authenticated connections (for example through SMTP-IN or WEBMAIL services).
5 votes -
Integrate PGP-Encryption
Maybe you can partner with https://www.mailvelope.com/.
44 votesAdminGabriel
(PM, Axigen)
responded
Not a priority for now. Will keep the latest evolutions under observation, but for now we’ll not going to plan this.
-
Drag & Drop support for calendar
So I can move appointments easily
3 votes -
Update downloadable binaries when there is a patch available
Currently it seems that binaries from download section are not updated when there is a patch available.
What now happens is that customers download the initial version, install it. We have to apply the patches afterwards. This is causing double effort. It would be better to included them in downloadable packages instantly.1 vote -
Improve support for lager mailboxes
Large mailboxes (>20GB) cannot be handled properly within AXIGEN. Webmail is having real issues handling such big mailboxes, especially when there is no folder structure. Searching is nearly not possible.
7 votes -
Allow moving mailboxes between clustered nodes
When using a clustered environment it would be helpful if I could move mailboxes between servers in order to re-organize the logical location of a mailbox.
5 votes -
Clustering support with auto-failover
Currently in a clustered environment we have to following situation:
If a backend-node goes down, all mailboxes mounted there are not reachable anymore.
If I use a shared storage where mailboxes are located physically it would be technically possible
the remaining nodes do not mount that existing mailboxes mount mailboxes which were located on the failing node.4 votes -
Execute rules on catch-all accounts
Currently filers and rules are not executed when using catch-all accounts. This feature is really important because especially when using catch-all additional filters would be really helpful to organize these mails.
27 votesAdminGabriel
(PM, Axigen)
responded
I understand the request, but before we schedule this, I would like to better understand the actual use case.
@All: Could you please detail your catch all usage, with a practical example, and as well as give some examples as to what kind of rules you would create (e.g. 1. conditions, 2. actions)?
Thank you,
Gabriel -
Provide Meaningful storage charts
Currently the storage charts only show how much space is used out of the allocated storage. In most cases the charts show an usage of 99% - which is good. But admins think that their storage is running out of space. So the current charts are rather useless. They just indicate if I should issue the compact storage or not. Really helpful would be a graph indicating that I really have to add an additional storage container, soon.
20 votes -
SPF Whitelisting
Most mailing lists now implement the Sender Rewriting Scheme to ensure compatibility with SPF and DMARC etc.
However, not all do. If a mailing list forwards e-mail from a domain with an SPF record without rewriting the sender, then the e-mail whilst legitimate will fail the SPF checks.
I've already submitted a proposal to implement moving the e-mail to the Axigen quarantine if it fails SPF rather than reject it outright. In this way e-mails from legitimate maillists which aren't compatible with SPF can be detected. However, in order to allow receipt of e-mails it would also be necessary to…
2 votes -
Add move to quarantine to advance routing rules
Add an action of move to quarantine to the advance routing rules.
14 votes -
Allow quarantine as well as reject for Additional Antispam Methods
Currently for the additional anti-spam methods (SPF checking, GeoIP checking, DNS blacklists, reverse DNS and MX record checking) the options are to deliver the e-mail or reject.
Add to these methods the ability to quarantine any e-mail failing the relevant checks (SPF checking, GeoIP checking, DNS blacklists, reverse DNS and MX record checking).
5 votes -
Moving in the right direction
Moving in the right direction
Needs to keep the files safe and away from intruders so a strong authentication is needed. Stay away from mapping or sharing drives from the users it will become a cumbersome application and harder to manage.1 vote
- Don't see your idea?