I am trying Axigen Mail Server if it is good enough for me to switch from a good old mail server that has a great file system that You can access natively with any file browser, like Total Commander, so I can check if a mail is on its place, or can delete or add mail, folders, edit rules in text files, so on… without any mail client, or web interface.
Axigen has something like this, but i can not check this, because if i try to mount a domain, or object (email account) the result error message is:
“The name you provided is invalid!”
Tried the command line too, but the same message.
On the GUI i filled the mounting panel like this, without the “” marks:
Mount point: “S:” (S colon backslash - do not know how to write backslash into this forum…)
Mount scope: “Domain”
In the [Enter domain here] filed: “afs”
“Afs” is a test domain I just created for the purpose of this file system test.
S: is an unused drive letter.
If I try without backslash, so just “S:” , the result error message is: “Bad drive letter.”
Tried object (email account) instead of domain, but the result is the same invalid name provided message.
I have to disappoint you but Axigen is not providing similar access to the internal objects (like messages, rules, etc) in clear text or allowing you to manipulate them (like remove or edit).
As you are on a Windows installation please note the requirement of using a 3rd party tool (Dokany). Is this is not acceptable than you may configure the Axigen FTP service, at least one listener and access the same data via the preferred FTP client.
I read both the Linux and Windows tutorial how to mount the Axigen storage, and I did everything as the articles said.
Dokany was missing at the beginning, but that was said as a missing dll by the error message. The article pointed to the github page so I installed Dokany and the error message gone that missed that dll.
Tried FTP too… can not connect to that service … default port 21, enabled. Tried 127.0.0.1:21, local IP address (192.168.1.102) too, but did not worked.
I understand that you managed to mount and access the special mount point where Axigen is exposing internal data.
Regarding the access via FTP my recommendation is to configure the listener on 0.0.0.0 (meaning all available IPv4 addresses) and port 21 and double check if the FTP Backup & Restore service is started (from WebAdmin > Services > Service Management)
The FTP Service was not running… Started and after that I could connect with the server admin account, and can see the domains and the account, files, etc. Plan B tested!
Plan A - the File System Access would be fine to get to work.
Is there an update that makes this File System Access function working?
On 10.3.3.11 it is still not functioning.
Should I update to 10.3.3.19? Will this update solve this bug?
Please confirm, that the 10.3.3.19 solves this error in Axigen Server.
Will install the update You specify to solve this issue. This function must work alone, without any windows dependency. It was not working back on Win7 x64, Win 10 1909 x64, Win 10 20H2 x64, on date 2020-NOV-02.
When I last reported this issue (about version 10.3.3.5), You admitted this error is by coding, and will correct the bug.
“Please note the problem you encountered was replicated locally and appears to be specific to Windows 10 OS (it does not occur, for example, on Windows Server 2016).
We are currently investigating this situation internally. We will update you as soon as we have any new information regarding this case.”
So I ask You to tell me, is there any change or is it still not a working function! (For me it is still not working on 10.3.3.19 ) Please tell me is there any plan to make it working.
Thank You!
Please know that we tested in the past when the problem occurred with an older version of Windows 10. We recently tested out again with a newer version of the OS (please see below the version used) and we were not able to replicate the problem. Please see below what we have used:
Windows 10 version 21H1, OS build: 19043.1165
Axigen verision: 10.3.3.19 on both server and webadmin/webmail (we’ve also tested with a 10.3.3.1 version and the result was the same, the problem does not replicate)
Dokan version 1.3.1 (available at the link below)
) Please tell me is there any plan to make it working.