Send-as can only be disabled “globally”, the feature does/can not make a distinction from where a shared folder is opened. But you can decide if you want to use this functionality when opening a shared folder.
Afair the entered email address will be inherited by subfolders of the current folder, I do not remember if the same is true for disabling sendas. the limit can also be influenced from the plugindebugger (but it’s of course adviced to limit folders instead of raising the limit).
It’s Outlook 2016 Version 1808 (Build 10730.20101)
The problem is that once Kopano is installed - the problem actually affects ALL profiles. So even if I do as you suggest and use separate profiles for my Main email and my IMAP accounts, I can’t add the accounts from within Outlook itself. I have to instead add them by going to Control Panel ->Mail (Outlook 32bit) - which is still available in Windows 10 although I have to either enter Control Panel using the Search Bar or File Explorer.
@8gm-dk said in Using IMAP as the eMail interface in KOE - an alternative?:
Another question still remains:
Will I run into other problems that I do not readily see at the moment if I do the “dual stack” accounts in Outlook (IMAP and ActiveSync for all accounts, telling the customer to just use IMAP for eMail)?
Probably not even the Outlook developers would be able to answer this question. Maybe it will work “forever” without any issues. Maybe some Outlook update will change something regarding IMAP or ActiveSync handling and it will break. It’s just not possible to give you any guarantees.
will that work on our business productional environment where I run kopano-server 22.214.171.124-0 ? I guess it should because I would only update the OLE extension on my own Windows client workstation, right ?
in the ActiveSync realm it depends on the client if the server has to regenerate a new task or not. The client sends Regenerate tag with the value of either 0 (do not regenerate, the client will do it itself) or 1 (the server has to generate the new task). Outlook e.g. does it itself as you can see in the logs in step 1.
I deleted the item by selecting it in WebApp, then right-click on it and select “delete”.
When preparing log data, I stumbled upon an error message in the errorlog file: Mobile loop detected! After cleaning this up, the problem seems to be solved. It works now as expected. This seemed to be the problem. Lesson learnt: READ THE F… LOG FILES, STUPID CLIENT!
Mark this issue as solved, please, and accept my apologies for buggin you, stealing your time. I feel ashamed.