So that is where we are now. A missing package, unclear documentation and yum unable to resolve dependencies for some of the remaining packages. As the support community showed no interest in Kopano being used in production and actually got angry that we wanted to, we decided to halt here. But there is the documentation in case anyone runs into this and wants to pursue it further.
I want to configure email on osTicket. Please remember, I am not technical.
I hope the following does not seem needlessly verbose to you. I have worked with engineers over the years. They typically generally very strongly preferred terse communication to verbose communication.
According to Configuring email on osTicket, "In order to use Gmail, your host must support SSL, so osTicket can negotiate the secure connection, and you must enable IMAP or POP in your GMail or GApps account."
I have a Google Apps account, although I think it might be called a Google Suite account now. (I wearied years ago of trying to keep up with Google's executives' seemingly absurdly comical efforts to confuse their customers by capriciously rebranding/renaming/canceling products. Be that as it may, Google makes many excellent products several of which I use nearly every day).
I have not really used that Google Apps account much in about eight years, but it is grandfathered in as a free account. I logged in the other day and verified that it is still active. Therefore, I would like to use it.
Also, the domain name which is associated with the GoogleApps account is not currently registered with a registrar. The domain name appears to be actually unregistered. After GoDaddy's pernicious practice (years ago) of snagging domains people had looked up but did not register, I prefer not actually look up the domain name for fear some other registrar might snatch it up. I simply went to the URL and saw it was down. Also, the name is not quite obscure but it is close therefore, I would be surprised if anyone had registered it.
Would I need to re-register my domain in order to test out the osTicket email functionality with with the GoogleApps? I suppose I probably would. See, I do not want to test the osTicket email functionality through some other method than GoogleApps because my experience from around 2005 to 2010 with GoogleApps email service was excellent (nearly flawless if I remember correctly) and because I have a read many horror stories of people who seemed technically competent trying to manager their own email servers.
I suppose I might test could configure email on osTicket to run through Gmail instead of GoogleApps, but then I would run the risk that email would work properly through Gmail but not through GoogleApps. What is your opinion? Does my concern seem "over the top" the top to you?
My domain is a .com domain. It looks like for less than $10/year I could register the domain with Namesilo.com (I read many glowign reviews about Namesilo.com on various sub Reddits). But I estimate I won't go live for another 3 to 6 months, and therefore don't want to bother signing up with Namesilo.com and trying to figure out how their site works.
Sure, it supposed to be easy. But I remember spending many hours wrestling with GoDaddy to get all sorts of things set up (including my email) set up about 8 years ago. Eventually, I set everything up properly. But tasks like this always seem to take me a couple/few hours to figure out. Of course, once I actually get them set up and know how they work, the same stuff that took with a couple/few hours only takes a maybe five to ten minutes the next time I do it.
I probably spent at least 3 to 4 hours Googling and trying various methods to install osTicket 1.10 on CentOS 7. Now I can install it in about 10 minutes.
If I were to need re-register my domain to test osTicket's email feature though my Google Apps account then I suppose I would reluctantly sign up for an account with Namesilo.com. Maybe it really will be easy for me to figure out how to use Namesilo.com. Maybe it will only take me, say, five to ten minutes. But I doubt it. By the way, I want to be clear: I am not in any way attempting to besmirch Namesilo.com. I have never actually used their service at all.
But see. I am not technical. Therefore nuances and nomenclature that technical folks are familiar with are often so foreign and confusing to me that it usually takes me a while to "get up to speed on them." Once I understand the technospeak, I translate it into plain English and put it into some step-by-step notes for myself that I can refer to as needed.
I am sorry for this verbose message. Thanks for taking the time to read it.
Did anyone ever figure out if there was a way to setup files for firewalld? Or was the XML service files the way to go?
XML I think.
That's what I was afraid of. We're using IPTables on all of our OEL7 servers right now but I think moving to the default firewalld may be a good idea. I'll have to look into the XML config and see how much more difficult, if at all, it is over the IPTables file. It's a shame we can't just copy a single file around anymore but the XML files probably won't be too much more difficult.
Ya it's not bad at all. Here's the config from my Identity Management server. It's pretty similar to /etc/sysconfig/system-config-firewall on RHEL 6, just in zone specific XML files.
<description>For use in public areas. You do not trust the other computers on networks to not harm your computer. Only selected incoming connections are accepted.</description>
Those services are predefined right? You can also build your own services via the same process.
Ya and you can define specific ports. I prob could have grabbed a better example.
No, I think I've got it just need to investigate actually setting these up.
Legacy is a fallback driver that you never want to use, it's low performance and high overhead. If you needed that for CentOS, it would make Hyper-V a silly, non-production ready platform. But Hyper-V is a good, solid performer.
Not only that, but I install all of my CentOS 7 VM's as Generation 2 when on Hyper-V they work perfectly with default settings for everything except secure boot. Uncheck secure boot. Everything else is 100% default settings.