To be honest Nick I can not remember either. It has been years since I have done my SOGo setup, but you are right the proper configuration would be: MailFieldNames = (clearMailAliases,mail).
I recall I had an issue with ClearOS aliases, my mail account name is never used to transmit emails, I only use aliases. Something clashed with the way ClearOS had configure the LDAP structure and how an LDAP structure was interpreted by SOGo. I think I wanted to do this: MailFieldNames = (clearMailAliases), but was not possible with the ClearOS structure and I ended up adding a field to the ClearOS LDAP structure for it to work.
Can not really check this right now, I am on vacation and If my wife caught me working... you know what I mean. But I will come back with more on this issue.
Thanks Tony for the update on some of SOGo features i.e. SOGoMailAuxiliaryUserAccountsEnabled Installing SOGo 2.0.5 on ClearOS 6.4.0. I can see that you have moved on to SOGo 3. Seeing that you seem to like it over 2, I will give it a try ... but last time I looked at it, I did not warm up to it.
I have had to learn first how to put a new ClearOS 7.3 together, I just recently did in an ESXI env. That include getting use to the CentOS world again, last time I played with those babies was in the good old ClarkConnect days. The good part is that my mail data is on a different server and I can focus on the front end first. I just finished getting Squirrelmail going, still my favorite for searching and speed but now the speed is lees of an issue, I always though I lived in the country but now not so sure anymore since we recently had fiber installed in our neighborhood.
Anyways thanks again for the instructions above, hopefully I can give it a try. I do have a question about the ClearOS LDAP structure for: Mail Aliases, the structure that ClearOS 6.x adopted at the time was a master detail relationship and that did not fit very well with SOGo. I remember modifying the ClearOS LDAP structure to fit SOGo world any experience with this topic?
I am aware of that feature, but I am not grasping why you are showing me this?
Nick maybe you had another approach in mind? I use SSH as a tunnel to run RDC sessions. The SSH service is configured with two access approaches:
The WAN connections disallows root access and only one user is allowed to connect via an ssa rsa key.
The LAN connections allows root and users access via password and/or ssa rsa key.
I think Webconfig is not very happy with me having two 'PermitRootLogin' in the configuration file.
I broke the SSh Server Webconfig browser page after modifying the ssh configuration file i.e.Ooooops: Configuration file parse error occurred.
I understand that it can be difficult to parse a configuration file that has been modified externally and the risk of doing so can be unforeseen.I will let the powers at be decide if this is a bug or not. Here is the modified culprit code:
The use of 'PermitRootLogin' in a block probably conflicts with the one that is currently set.
Another issue with the Webconfig page: I added an additional port to the configuration, the web page shows only the last port that was configured from the configuration file. That also would probably not do well during a browser page update? I did not try...
I think I found the problem.
During the manual partitioning, I deleted the current partitions and created new ones. All seem correct as you can see in the following picture ClearOS Incorrect Partitioning.jpg, it created a new installation called: ClearOS Linux 7.3.0 for x86_64 but that does not work, it seems to create a server missing some if not all of ClearOS modifications.
What I did on my xxx attempt, same as above deleted all the current partitions. But instead I created the New ClearOS 18.104.22.168 80516 Installation by: 'Click here to create them automatically', deleted and modified the new default partitions and that created the correct partition scheme see the included: ClearOS Partitioning.jpg
My installations are done on a ESXI platform, I have attempted to install ClearOS 7.3 with my standard partition scheme. On reboot I get a console (white screen) and can not get webconfig started from the browser. The installation works when I do not define my own partitions.
I notice that the /etc/default/grub configuration is slightly different, though not a critical change:
Custom Partition grub conf:
Default Partition grub conf:
Custom File System:
Instead of the Default File System:
I can not find anything in the logs that indicates a problem, again I might not have noticed it. The concern is that if the /etc/default/grub configuration did get build properly, there might be something else? and I am at a lost on what that might be.
I originally installed ClearOS 7.1 for a test run and had to leave the testing project for a period of time. I came back recently and updated to 7.3, ran into the same issue as Matthew (B.T.W. thank you for the solution).
Here is my configuration file: /usr/clearos/apps/base/deploy/servicewatch showing the deamon to be monitored:
and additional info:
[root@cognoquest ~]# chkconfig --list
Note: This output shows SysV services only and does not include native
systemd services. SysV configuration data might be overridden by native
If you want to list systemd services use 'systemctl list-unit-files'.
To see services enabled on particular target use
'systemctl list-dependencies [target]'.
netconsole 0ff 1ff 2ff 3ff 4ff 5ff 6ff
network 0ff 1ff 2n 3n 4n 5n 6ff
storage 0ff 1n 2n 3n 4n 5n 6ff
syswatch 0ff 1ff 2n 3n 4n 5n 6ff
zbootevent 0ff 1ff 2n 3n 4n 5n 6ff
[root@cognoquest ~]# service --status-all
netconsole module not loaded
lo ens192 ens224 ens256 ppp0
Currently active devices:
lo ens192 ens224 ens256 ppp0
/etc/init.d/syswatch: line 18: [: =: unary operator expected
● syswatch.service - SYSV: This daemon keeps an eye on your Internet connection and other critical systems.
Loaded: loaded (/etc/rc.d/init.d/syswatch; bad; vendor preset: disabled)
Active: active (running) since Sun 2017-03-26 15:08:10 EDT; 1 day 1h ago
Process: 1812 ExecStart=/etc/rc.d/init.d/syswatch start (code=exited, status=0/SUCCESS)
Main PID: 1897 (syswatch)
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
Status bootevent: [ OK ]
Please note Incorrect 7.3.0 ISO md5 sum on download web page: https://www.clearos.com/products/purchase/clearos-download Shows: SHA256sum: b4da8ffa10945e4d95478edb32f7a3dd9691f9a6c6d7820b1ffa346f6eb6a878 and does not match mirrors: 0ba358dddf233f1631db8bf48911c1a7838887a1c854980c5a1d17c1a59d5812 *ClearOS-DVD-x86_64-22.214.171.124516.iso