Peter,
Just got it installed, nice that it works out of the box, just a couple of things:
Zarafa-App
In clearos 5.2 you were allowed to disable/enable pop/imap in the web interface along with also changing the ports, is this going to be possible again or is this just not available due to this being a beta test if that's the case then fair enough that's fine.
User creation
When adding a new user now on clearos There is an e-mail section that is blacked out while alias is available to write. Is it possible on 6.2 for you to enable to not make the username the e-mail address? That would be great some times we would like to have a username mail.info and of course there can be an alias that is info but when sending it will send as mail.info and not info@domainname.com
If this is a feature you can impliment that would be pretty amazing.
webmail/certs
It's really great that https works out of the box without doing quite alot of configuring like before on 5.2 for that thanks alot you've saved alot of monitinous work for me
I just wanted to know a few things:
* Z-push when it gets implimented/in your testing repos will that also be https by default like the webmail or will we need to use proxy pass for that too?
mysql/attachments
I just set up zarafa to use the normal mysql which seems to only work if you set the user to be unlimited if you choose a normal quote like 10GB it's full up.
system-mysql quotas seem fine, so I'm guessing clearos isn't set to use the normal mysql at all. Are there any plans in the near future to support normal mysql for zarafa?
Glad to hear that zarafa test are already underway I will set up a 6.2 box to test, however a suggestion just to add regarding what tim said:
* Please allow option of mysql database for backup purposes for community users, it's fine for people who professional they will have zarafa-backup but for community it makes it hard.
* Public folders should probably be increased alot, we had a company who had a public folder of 18GB of e-mails definately 100MB won't be enough, I think thel imitation should increase.
Thanks peter glad to know that the samba issues have been known by the team and will be working on them soon. Unfortunately we couldn't wait for this as one server install is tomorrow so will have to use 5.2 for now. Hopefully the othwr two clients can use 6.2 as they will be deployed late may when zarafa comes out.
Can I just add a suggestion as well regarding openvpn?
Your app market has the client certification manager description saying it is only needed for pptp, this is misleading considering it is also needed for openvpn, I think the description should be changed so it makes this less confusing.
Also having this issue with 64-bit version I am now trying to install 32-bit in hopes that will work a bit better. Hopefully it's not an issue with 64-bit.
I am also having an issue with openvpn here is what I get as an output.
Code:
ay 11 16:47:03 themis openvpn[1278]: MULTI: multi_create_instance called
May 11 16:47:03 themis openvpn[1278]: 192.168.1.68:50040 Re-using SSL/TLS context
May 11 16:47:03 themis openvpn[1278]: 192.168.1.68:50040 LZO compression initialized
May 11 16:47:03 themis openvpn[1278]: 192.168.1.68:50040 Control Channel MTU parms [ L:1542 D:138 EF:38 EB:0 ET:0 EL:0 ]
May 11 16:47:03 themis openvpn[1278]: 192.168.1.68:50040 Data Channel MTU parms [ L:1542 D:1450 EF:42 EB:135 ET:0 EL:0 AF:3/1 ]
May 11 16:47:03 themis openvpn[1278]: 192.168.1.68:50040 Local Options hash (VER=V4): '530fdded'
May 11 16:47:03 themis openvpn[1278]: 192.168.1.68:50040 Expected Remote Options hash (VER=V4): '41690919'
May 11 16:47:03 themis openvpn[1278]: 192.168.1.68:50040 TLS: Initial packet from 192.168.1.68:50040, sid=aafe4631 d4be7318
May 11 16:47:05 themis openvpn[1278]: read UDPv4 [ECONNREFUSED|ECONNREFUSED]: Connection refused (code=111)
Code:
May 11 16:47:29 themis openvpn[1278]: read UDPv4 [ECONNREFUSED]: Connection refused (code=111)
May 11 16:47:29 themis openvpn[1278]: 192.168.1.68:50175 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
May 11 16:47:29 themis openvpn[1278]: 192.168.1.68:50175 TLS Error: TLS handshake failed
May 11 16:47:29 themis openvpn[1278]: 192.168.1.68:50175 SIGUSR1[soft,tls-error] received, client-instance restarting
May 11 16:47:30 themis openvpn[1278]: read UDPv4 [ECONNREFUSED]: Connection refused (code=111)
May 11 16:47:31 themis openvpn[1278]: read UDPv4 [ECONNREFUSED]: Connection refused (code=111)
1194 is enabled on the firewall on clearos I have even tried eanbling all firewall ports just to test this and still no joy. I may need to use pptp it seems in the mean time if openvpn doesn't work.