I support this - in case of harvest or other attacks, kerio should blacklist the IP and drop any connections they get from it, without allowing SMTP.
This might remove our Mailserver from some botnets maybe.... we get flooded very much meanwhile, dunno why. Same with our backup mail server. And everythings secured...
I was just asking the same - that would be awesome :D
AFAIK KOFF needs the cache to actually work... there is no "without" option.
For the TS enviroment I use a local, single SSD in the server as cache hdd (reroute with registry) and it works like a charm for all users. Never had one complain about the speed. :)
This is an awesome idea! Using the default signature of outlook or another program, you could tell kerio with a custum footer string, where to actually put the footer.
It would be nice to have somehow the same options like cobian backup offers. Most important would be an FTP Backup option (locky trojan <3) and to do a seperate, full backup to another location. So do the regular backup to the nas, but once a month a full backup to another server and keep like 6 copies there max.
So you can restore, if something goes really wrong or the usual backup won't go so much back into the past.
298 votesHeather P responded
We like this idea! Whilst not assigned to a release yet, we are looking at comments and votes for this request.
323 votesHeather P responded
Thanks for the idea. This is on our product backlog, but not assigned to a release. This feature is still open for voting.
We have been looking at this item, but do not have a date yet. Please see comments.
Please see our Kerio Connect 9.1 beta for Remote Archiving per domain.
November 2017 update – we are looking at ways of making KOFF faster
I can support this. KOFF is REALLY slow with bigger mailboxes, especially for roadworkers with laptops and 5.4k drives. Not everyone runs SSD's.
This request is being reviewed.
Mhh, I use kerio with Active Directory and if I change the user name in the AD, it also get's changed in Kerio.
The undeletable log and no-reconvert option is meant to be in line with the current data protection laws. You might look into it, but you stand responsible for it. (Yeah, Admin could still delete them somehow, but not the boss ;))
I would also welcome something like that, but in my case it's in case of user calling in sick. Same problem today...
User called in sick - so I set the forward to his colleague BUT the mails he got till I activated are in his mailfolder. And our company forces the users to never give out their pw, so I would have to reset his pw, open his account, set a delegation of the mail folder, tell him the new pw and set his account to "force pw change by first login". If that happens with a roadworker, he would need to change the pw in every device too, because the last 24 pw are saved and forbidden to use.
In Exchange I just did a "give full access to user XYZ" and done.
For data protection reasons it might be an idea for the admin to enable a "config mode" to set the folders and delegations for the users all at once - sending the users a "undeletable" message with a overview what the admin did after he turns the config mode off.
Also if the admin gives delegation out of the config mode in case of someone being sick etc. he should be forced to give a reason why and that also should create a not deletable message for the user to see who/why/what folders were delegated.