Any outlook guru's here?
-
My favorite thing to do in most of these situations is install the PWA version of Outlook, and uninstall the locally installed version.
This also points out another major shortcoming of Micorsoft's Outlook. Nobody knows which Outlook thing it is by just the name. The free email service? The locally installed software? The PWA? There are probably more that I'm not thinking of off the top of my head.
-
@travisdh1 said in Any outlook guru's here?:
My favorite thing to do in most of these situations is install the PWA version of Outlook, and uninstall the locally installed version.
This also points out another major shortcoming of Micorsoft's Outlook. Nobody knows which Outlook thing it is by just the name. The free email service? The locally installed software? The PWA? There are probably more that I'm not thinking of off the top of my head.
iOS version
Android Version
Windows full client
Mac Full client
Outlook.com
Outlook Web Access (old Exchange)
Outlook on the Web (current Exchange and O365) (can be pinned as PWA)Plus they are working on a unified version of Outlook
-
So this is still an issue - Outlook and Google workspaces aren't syncing the calendar, everything else sync'd.
all research I've done is pointing to 3rd party apps that have no guarantee to actually work
-
@WrCombs said in Any outlook guru's here?:
So this is still an issue - Outlook and Google workspaces aren't syncing the calendar, everything else sync'd.
all research I've done is pointing to 3rd party apps that have no guarantee to actually work
Correct. But don't let the customer define this as a "problem." The two are not related and should not sync. That he's wanting them to sync is the problem. That's like saying that his Google Calendar doesn't sync to MangoLassi. What? Why would it, the two are not related.
So nothing wrong with wanting something that doesn't exist, but he needs to understand that he's asking for something that isn't a thing and acting like it is broken when the issue is that he bought the wrong software for the task that he wants done.
In theory, some third party software MIGHT be able to get the two to talk to each other, but it'll never be official, or supported and could certainly break. He designed this not to work, that's by his own design. If he wants you to try to make it work anyway, don't pretend that you are fixing something that isn't working, you are attempting to overcome a "by design" limitation that he, the customer, put in place personally.
-
@WrCombs said in Any outlook guru's here?:
everything else sync'd.
What is "everything else?" IMAP carries mailboxes, nothing else. It should sync one thing, the email mailboxes. Nothing else is supposed to sync between the two because there is no protocol for anything else. And it isn't really a sync like it sounds, it's that both things sync to the mailbox storage. They don't sync to each other.
-
@scottalanmiller said in Any outlook guru's here?:
@WrCombs said in Any outlook guru's here?:
everything else sync'd.
What is "everything else?" IMAP carries mailboxes, nothing else. It should sync one thing, the email mailboxes. Nothing else is supposed to sync between the two because there is no protocol for anything else. And it isn't really a sync like it sounds, it's that both things sync to the mailbox storage. They don't sync to each other.
everything else is Mailboxes and his phone sync'd the contacts --Which I understand are separate things entirely.
-
@WrCombs For this kind of thing, i highly recommend building a home lab Postfix / Dovecot server and running your own "pure" email system with no extra layers. Understanding exactly what each piece does in a system with nothing layering on extra features, protocols, ports, management, etc. makes it a lot easier to learn the underlying mechanisms which, in turn, helps to make identifying behaviour much easier.
When you manage a pure SMTP / IMAP system, that there IS no calendar, no calendar protocol, etc. becomes really obvious. When someone demands unrelated components be connected, it's obvious when "there's no tool for that here."
In this case, Outlook lacks a Google Calendar connector or viewer, that's not something Outlook offers. Why does the customer expect it to do so when Outlook was never supposed to do that? Knowing what the customer has set up (an IMAP reader) helps to instantly identify when they are asking for something that makes no sense.
-
@WrCombs said in Any outlook guru's here?:
@scottalanmiller said in Any outlook guru's here?:
@WrCombs said in Any outlook guru's here?:
everything else sync'd.
What is "everything else?" IMAP carries mailboxes, nothing else. It should sync one thing, the email mailboxes. Nothing else is supposed to sync between the two because there is no protocol for anything else. And it isn't really a sync like it sounds, it's that both things sync to the mailbox storage. They don't sync to each other.
everything else is Mailboxes and his phone sync'd the contacts --Which I understand are separate things entirely.
Right, so only email synced. That's kinda different than "everything else." One implies a straightforward email mechanism that is working exactly as designed. The other suggests a complex web of things in which one component is failing.
-
@scottalanmiller said in Any outlook guru's here?:
@WrCombs said in Any outlook guru's here?:
@scottalanmiller said in Any outlook guru's here?:
@WrCombs said in Any outlook guru's here?:
everything else sync'd.
What is "everything else?" IMAP carries mailboxes, nothing else. It should sync one thing, the email mailboxes. Nothing else is supposed to sync between the two because there is no protocol for anything else. And it isn't really a sync like it sounds, it's that both things sync to the mailbox storage. They don't sync to each other.
everything else is Mailboxes and his phone sync'd the contacts --Which I understand are separate things entirely.
Right, so only email synced. That's kinda different than "everything else." One implies a straightforward email mechanism that is working exactly as designed. The other suggests a complex web of things in which one component is failing.
I see that now
-
In this case I think everything is going to come down to setting and managing customer expectations. Why did the customer install a tool that was almost entirely wrong for his (or any) use case? What made him thing that Outlook was acceptable or would work when it would normally be really obvious that it is wrong in every way (this is a pattern that would never be expected to work, let alone the specific situation.)
So that's something you need to figure out internally. Was this a pure customer mistake (he ignored advice and made a decision despite being told this was nuts) or did someone accidentally tell him that Outlook would be okay to use? Then figure out how to frame the options.
The options are basically these...
- Live with the limitations he's chosen and move on.
- Stop using Outlook.
- Switch from Google email to Office 365.
- Use a third party connector that is unsupported.
That's it.
-
sent over recommendation and leaving it at that .
thanks !
