M Dovey
My feedback
12 results found
-
9 votesM Dovey
shared this idea
·
-
202 votes
We started working on the new Axigen Drive — it’s an integration with Nextcloud and Onlyoffice.
An error occurred while saving the comment An error occurred while saving the comment M Dovey
commented
I suggest that you look into a partnership with seafile.com for file sharing\storage.
This is an alternative to owncloud\nextcloud for document sharing with some unique features such as integrated versioning (based on git).
An integrated solution including axigen and seafile would be welcome.
M Dovey
supported this idea
·
-
24 votes
What benefits would you see with an Axigen email client, compared to (1) third party compatible clients and (2) the existing WebMail?
An error occurred while saving the comment M Dovey
commented
Key limitations with the current offerings:
i) Thunderbird and related clients - works well for e-mail but no support for accessing\synchronising contacts, calendar or notes. Whilst there are some third-party plugins which partial address this, they take time to configure, not officially support axigen and as a result tend to be flakey. Some webmail features not available (e.g. temporary mail aliases)
ii) Axigen web mail - works well for a single account whilst online. Offers full axigen feature set (e.g. temporary mail aliases). Not possible to open multiple accounts simultaneously (without using multiple browsers). No offlline mode possible.
iii) ActiveSync clients - whilst ActiveSync clients work well on mobile devices (android\iOS), the desktop equivalents don't work well: Outlook activesync does not work with Axigen (gives connect error); emClient displays some oddities (e.g. all e-mails appear flagged); Windows 10 mail client works with occasional random temporary errors but the mail client does not always render html mail correctly. Some webmail features not available (e.g. temporary mail aliases)
iv) Outlook plugin - generally works well but Outlook can be unresponsive whilst background syncing a lot of e-mails. Works in offline mode well (providing you remember to change the default settings from download headers only). Includes calendar, note and contact support. Not possible however to open multiple accounts simultaneously. Some webmail features not available (e.g. temporary mail aliases)
-
1 voteM Dovey
shared this idea
·
-
48 votes
An error occurred while saving the comment M Dovey
commented
Sorry, I meant reject would be the sane default option for "Action if the SPF\DKIM tests fail and the DMARC policy for the domain or subdomain is Reject"
M Dovey
shared this idea
·
-
1 voteM Dovey
shared this idea
·
-
39 votes
An error occurred while saving the comment M Dovey
commented
This is how most greylist filters work (for example milter_greylist):
There is a permanent whitelist of ip address\ranges
There is a temporary whitelist of ip address, sender, recipient, date\time last e-mail received
There is a pending list of ip address, sender, recipient, date\time first e-mail attempt
When a host connects to send an e-mail, first it is checked if it is on the permanent whitelist, if it is, then the e-mail is accepted.
If not, it is checked if the sending host ip, sender and recipient is on the temporary whitelist, if it is the e-mail is accepted and the datetime stamp of last received e-mail is updated.
If not, the pending list is checked: if the host ip, sender and recipient is in the pending list, and the datetime state of the first attempt is at least x minutes ago (the value of x should be configurable but typically would be between 3 and 5), the e-mail is accepted, and the host, sender, recipient and date\time is added to the temporary whitelist, and removed from the pending list.
Otherwise, the e-mail is temporarily rejected, and if the host, sender, recipient is not in the pending list, it is added to the pending list.
Periodically, the pending list is purged of any entries older than a time which can be configured (typically 12-24 hours)
Periodically, the temporary whitelist is purged of any entries older than a time which can be configured (typically 28-56 days)
An error occurred while saving the comment M Dovey
commented
The greylisting implementation has never worked properly. I current use milter_greylist through the axigen milter support.
-
2 votesM Dovey
shared this idea
·
-
14 votesM Dovey
shared this idea
·
-
5 votesM Dovey
shared this idea
·
-
1 voteM Dovey
shared this idea
·
-
14 votes
An error occurred while saving the comment M Dovey
commented
I second this - file sharing is a major application in itself to do properly, and ideally requires dedicated sync clients for all platforms (including mobile) as the in built webdav clients are flakey (especially on Windows), lack functionality (such as version control and offline working), and tend to be slow (especially on Windows).
A file sharing solution whilst nice would distract resource from other more e-mail related features some of which are needed (e.g. multiple account support in the Outlook adapter etc.)
Is this integration locked into NextCloud or would this work with any webdav compliant cloud (including NextCloud, OwnCloud, SeaFile etc.).
We use Seafile rather than NextCloud due to Seafile's better version history management (its storage engine is based on a git-based version engine which also does deduplication rather than the NextCloud\OwnCloud approach of just storing historical copies in a hidden directory).