One thing that I have noticed, and this is the same for both SMTP integration (using our internal mail server) and ONLYOFFICE mail server ...

The initial email activation link for the admin account seemed to work just fine. But for any users that are "invited", it seems that ONLYOFFICE does not parse the %40 inside the user's email address properly. It does, however, parse okay for the initial admin activation.

As stated in another post I saw somewhere, manually changing the %40 -> @ seems to work okay, but that is of course not ideal for the average user. I am mainly wondering why the link works fine for the admin activation, but not for any invited users. Should be the same thing, no?

Thank you for your efforts. I have enjoyed playing with the product, it looks very promising and I am excited to help your development.

Unfortunately we cannot reproduce the issue. Please, click on the activation link in the activation letter. A windows with activation should appear. Could you, please, make a screenshot of this window (including address bar).

Ah -- so with your response, I went back to the configuration and tried a couple things to ensure I did not have a careless problem. What I found may be of interest to you. (This also applies to my other post at http://dev.onlyoffice.org/viewtopic.php?f=23&t=6158.)

With my setup, I am using Apache as a reverse proxy, since I do not have enough IP addresses to dedicate. I have manually set the DNS "custom domain name" inside ONLYOFFICE to the virtual host specified in Apache config. This does not seem to be the issue.

Now, if I remove the DNS custom domain name option and try all of the same operations again, everything works without error as you mention.

I am not familiar with the inner-workings of the software, so I do not know how this setting is used and by what parts. But a similar issue that I am seeing is that ONLYOFFICE seems to put together some of the HTML using its internal hostname, which is not the hostname I wish to use. When accessing the site from a remote network to its global hostname (office.example.com), much of the content is returned with links to its actual hostname (office0.example.local). This is true with or without DNS custom domain name.

What are your thoughts/suggestions? Do you think this is something I am mis-configuring on my end?