> config-v1.1.xml. People would then fix the username MANUELL_BEARBEITEN: IHRE_MEDMA_ID@medma.ad.uni-heidelberg.de That's precisely what the admin does *not* want. That's the old hack. It's a band-aid, because older TB could not do better. The admin who created this file contacted me specifically asking how to avoid that. The discussion with him lead to the solution in bug 1518155. Many on-premise Exchange servers have that same problem, because it seems the standard configuration for Exchange to use the Windows login, not the email address. > why do we detect that it's an Exchange server first? As described in comment 14, we detect everything at the same time, then pick the best result. Here, we detect that there is an Exchange server that needs a login and we have the wrong credentials, so we ask the user to enter the correct Windows login username. That also helps IMAP, because it would need the same username.
Bug 1599029 Comment 19 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
> config-v1.1.xml. People would then fix the username MANUELL_BEARBEITEN: IHRE_MEDMA_ID@medma.ad.uni-heidelberg.de That's precisely what the admin does *not* want. That's the old hack. It's a band-aid, because older TB could not do better. The admin who created this file contacted me specifically asking how to avoid that. The discussion with him lead to the solution in bug 1518155. Many on-premise Exchange servers have that same problem, because it seems the standard configuration for Exchange to use the Windows login, not the email address. > why do we detect that it's an Exchange server first? As described in comment 14, we detect everything at the same time, then pick the best result. Here, we detect that there is an Exchange server that needs a login and we have the wrong credentials, so we ask the user to enter the correct Windows login username. That also helps IMAP, because it would need the same username. What needs to happen is for the config.xml file to be removed, given that TB is now fixed.
> config-v1.1.xml. People would then fix the username MANUELL_BEARBEITEN: IHRE_MEDMA_ID@medma.ad.uni-heidelberg.de That's precisely what the admin does *not* want. That's the old hack. It's a band-aid, because older TB could not do better. The admin who created this file contacted me specifically asking how to avoid that. The discussion with him lead to the solution in bug 1518155. Many on-premise Exchange servers have that same problem, because it seems the standard configuration for Exchange to use the Windows login, not the email address. > why do we detect that it's an Exchange server first? As described in comment 14, we detect everything at the same time, then pick the best result. Here, we detect that there is an Exchange server that needs a login and we have the wrong credentials, so we ask the user to enter the correct Windows login username. That also helps IMAP, because it would need the same username.