As far as I have seen, you are currently supporting outlook 365 but not Outlook Web App (Exchange).
Maybe I just do not understand all the outlook/microsoft apps but I usualy use owa and not outlook.
I have created a Custom Service with http://owa.mein-exchange.de , but then I do not get notifications in rambox about it.
I think this needs multiple services for the different versions of Microsoft Exchange.
The company I work for uses Exchange 2013 and I use the following Custom Code (Advanced Settings in Service) to show the correct unread badge:
function checkUnread() {
var elements = document.querySelectorAll('._n_17.ms-font-color-themePrimary'),
sum = 0;
for (i = 0; i < elements.length; i++) {
var unreadCount = parseInt(elements[i].textContent.trim());
if(unreadCount % 1 === 0) {
count = parseInt(elements[i].textContent.trim());
sum += parseInt(elements[i].textContent.trim());
}
}
updateBadge(sum)
}
function updateBadge(a) {
a >= 1 ? document.title = "(" + a + ") " + originalTitle : document.title = originalTitle
}
var originalTitle = document.title;
setInterval(checkUnread, 3000);
You may also take a look at this repo with some custom js code for that feature.
https://github.com/bundyo/owa-rambox
But I am wondering if you have the same experience than me:
When I double click a message to open, it switches into my default browser to ask for sign in, but in addition Rambox opens a second window with the opened message.
Boring to always have to close my default browser.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Please don't close this, it is a feature I think many would like to see.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed since there has not been any recent activity. Please open a new issue for related bugs.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Most helpful comment
Please don't close this, it is a feature I think many would like to see.