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...
On linux you have the vmd module in the kernel. ESXi also have drivers.
Damnit - it's been awesome for several years with Windows 10 where no external drivers were needed during install because they were all baked into the default ISO... since the VMD stuff has been around since 2018 (though only in laptops since Gen 11 Intel Core processors) I really wish MS would include it in new ISOs.
Maybe Windows 11 has it....there is always hope at the horizon.
User education is next thing - and we do provide user education at hiring and then once a year. I really wonder - for the average worker - how effective is it? I think the answer to this comes down to your employees themselves. Again, someone also already mentioned that as well.
In my company, KnowBe4 has been really good. Users get yearly and quarterly videos and are encouraged to ask questions. Plus I setup a random monthly phishing scam test in addition to my very targeted bi-annual spear phishing tests I setup.
I really like it when users ask for help to decipher whether an email is phishing or not. We go over the potential red flags and if it is a Phishing test, I will let the user decide whether to click the link or not. 99% of the time they pass. If they click it, we have a small chat right then and there about what just happened.
Management only gets serious about it when they hear something in the news or through the client grapevine. Then its all hands on deck until.....
IMHO, it has been pretty effective when they see demonstrations of what is possible as compared to letting them read a PowerPoint, answer a couple questions and move on. Kind of like the great Medical - Fraud, Waste and Abuse presentation. All I hear is, "Ugh, anyone have the answers?" or similar statements.
Yeah, I've been asking for a solution like this for years. I even did one of their free tests, and the amount of people (and the specific people) who failed it was staggering (OK not really - come on, we know users). But the board just said - come on, can't you just train them? which I replied - no, I can't. it's not my skillset and the other features included in these packages would take ages for someone like me to develop, etc - they still said no.
Now fast forward to now - new CEO, new board members - those two groups have decided to buy into training solution because of other reasons.. and this solution does include some computer smarts type training.
We have KB4 Gold package that is good enough for us. No need to go above that for the medical field IMHO.
The problem is the process... why would someone be reporting spam and why is someone blocking it? That doesn't make sense. Get a good spam filter, configure, train people how to delete, done
"But this is the way we (they) have always done it... "
You mean they are "reporting" as in actually reporting it to someone? And not by marking it as spam in the email client?
Yeah, that doesn't make any sense. Far too time consuming.
Outlook Toolbar.. Reporting
d4517c20-ac54-44fd-a195-1b6ef87caf87-image.png
OK, but that just ends up sending an alert email to the designated phishing mail contact, which is IT right?
It would have made more sense if those emails had been forwarded to Trend Micro automatically and their adaptive algorithm would have learned how to detect them.
Right now Trend Micro doesn't have a clue what emails their user are classifying as spam or phishing attempts. Because that happens way after the email has passed through their gateway.
That's interesting.
With Appriver - we forward emails to [email protected] and appriver deals with it. Other than constantly reminding people that's where the report needs to go - I don't really deal with it.
Thought as Scott mentioned - so much spam is a once and done situation - so reporting it is often pointless.
That's not a bad process. But still a bit more than just "mark as spam" which is really simple.
oh, that most definitely is. and it's an option we have in O365.... but we now have two layers of spam filtering - appriver and MS...
So people have to report to O365 AND AppRIver? Do they really catch enough different to justify filtering twice?
no, they don't - and likely they aren't. I've shown nearly no one how to report to MS - so that's the one that's skipped. Everyone has been told about forwarding email to spam@appriver - and yes, it's more work than just right click - mark as spam, but not so much so that people don't do it.
Why report to that one when O365 is the important one and the one that's like 10x more likely to be permanent instead of being clearly in the "should be removed" category? Less work, better results, less long term risk.
Time, the old process is already in place. It's just a matter of informing people at this point - it just hasn't happened yet.
You're too young to remember the horror of Clippy?
Get off my lawn!
Consider yourself lucky!
I am lucky! Not because I'm too young but because I'm too old - too old to remember every irritating thing Microsoft managed to come up with...
Clippy - how could you possibly forget about Clippy? Now - if you said you forgot about MS Bob - that I could understand.
You just had to bring up MS Bob, didn't you! I spent an evening while working as an intern for my high-school installing that **** ******* piece of **** software in an entire classroom. Nobody could figure out how to use it, even with the teacher's manual to refence.
What's even funnier - I have no clue what MS Bob is - other than quite possibly the worse piece of software MS ever put out. and I only know that by reputation.
