@gjacobse It is not compatible. There was another project out there that was ARM compatible. I think it fizzled or was bought by Google several years ago now. Sigh
"Free Hosted" doesn't mean it's the right thing. But in many cases - you can beat it to work for you. Just depends on the work and stress you want to deal with, what you want to give up and what you will never have..
I'd go as far to say that the "free" version is seldom the right thing. Often the reason to look for a solution in the first place is to become more effective and spend less time on something. Just stepping up to the first paying tier usually gets you a lot of features that will save you time for a very modest monthly cost.
Makes no sense. I have a feeling that something is buggy in the firmware.
What makes no sense is that you think it is firmware.
Just throwing out ideas because it doesn't make logical sense to me. Any thoughts as to what else it could be? Why would the device reply to pings for an hour after reboot, then suddenly stop?
It's expensive. If you print a lot, it's crazy. If you hardly print anything, maybe the convenience is worth it. But if you print a lot, maybe it's rethinking printing itself that would make sense.
Seems that I managed to be in an Admin CMD window rather than my normal CMD window. Obviously that will cause issues since that would be cross accounts.
yeah - in retrospect that was dumb. Someone has to be the champion of a project otherwise it will get no legs.
And with no champion, well, clearly it's just withered...
Right, it feels like even the creator didn't believe in it.
Amazon is providing the service, not the software. So they don't need to adhere to GPL and similar licenses.
oh they have to adhere, it's just that the license clearly states that there are no limits on use. So they were adhering perfect.
ELK was upset that they didn't like how the code was being used when run in production and wanted control of the use of their code, not the reading or modification of the code.
My guess is that Zimbra is getting by on mostly legacy installations though. Self-hosted email is hard to justify nowadays.
I think moreso they are killed off by their crap licensing, BS installation practices, lack of updates, and MailCow coming along and taking their candy away.
IF you feel the crazy need to host your own email, MailCow does it better than Zimbra, and is truly OS (and deploys natively to Docker.)
I have two physical servers that would take a great deal of time to rebuild to virtual so a conversion from P2V would be ideal. What are you guys using to do P2V conversions?
I was looking for VMWare's converter but I don't think it exists anymore.
It's better to just reinstall on a new Windows (I'm guessing) and do whatever upgrades that are needed at the same time.
P2V is not a good generic solution. Consider it for quick and dirty band-aid solutions only.
Totally agree. Use migration time as a good time to run side by side and migrate the app and update / cleanup with a fresh install. If you have good procedures, this will be trivial. If you don't, even better, this is a chance to catch gaps in the knowledge base.
FreePBX is Sangoma 7, a fork of CentOS 7.
They had a private alpha of FreePBX 15 or 16 built on CentOS 8 that was never public. That was killed when RedHat killed CentOS 8.
FreePBX 16 is still Sangoma 7, but with PHP 7.4 ported in and a few other updates.
There has been no announcement yet, but a few threads on, choosing a new fork to go forward with.
@pete-s In the US they tend to say "as short as possible." Email is always a legal quagmire and the best thing to do is to delete is as quickly as possible. Which, of course, can't be that fast. So we are generally talking 1-2 years. But you rarely want to keep it longer not because it likely contains details of people breaking the law, but because a legal discovery request is extremely expensive and a great way to attack even otherwise honorable businesses. It's a huge cost you can leverage against someone that they can only reasonably mitigate by not having much email to go through.
Man - that would be so awesome. But even if management did agree that - you'd have people that would be looking for ways to maintain the data for a much longer period - like printing and saving in a cabinet.. shudder.
I like many of the replies I get about cleaning out email. "Why, its free!" "Why, my 50 GB of email is nothing when we have 16TB drives for $200" "Why do I have to remove email older than 13 years, it isn't hurting anyone" "Why would I do that, I may need it later (Medicare Newsletters prior to 2010)" and the list goes on and on.
Exactly!
Then my next question is - if something is so important that you need to keep it - why is it in email in the first place? Why can't you get that data someplace else more related to whatever it is you're saving it for? (That said, I realize that other documentation for something simply don't exist).
Don't you dare get me started down this path. I had HUGE arguments about this with an ex-employee over the period of 10 years. The user could not/would not understand her email box is not a document database / DMS. The last I counted, she had over 300 different nested folders in her email.
Now that the user is gone, their mail copied to a shared mailbox for management to hunt/search and waste their time with if they choose.
It probably easier to have retention policy in place from the start.
If you know email retention is time-limited, you'd have to come up with some other way to store things.
But some people are just hopeless no matter what...
