> this server not only supplies this config-v1.1.xml file but also an AutoDiscover file with a heap of Exchange stuff in it and that's triggered by whether the password is empty or not? Like I said, the config-v1.1.xml was a band-aid they put up for old Thunderbird versions, before the username field fix. They were not happy with that setup. They pleaded the case to me, and it's a widespread problem. Most other Exchange admins do not put up such a Thunderbird-specific config. We'll just be broken. See comment 5. I can't explain it any better than that.
Bug 1599029 Comment 9 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
> this server not only supplies this config-v1.1.xml file but also an AutoDiscover file with a heap of Exchange stuff in it and that's triggered by whether the password is empty or not? Like I said, the config-v1.1.xml was a band-aid they put up for old Thunderbird versions, before the username field fix. They were not happy with that setup. They pleaded the case to me, and it's a widespread problem. Most other Exchange admins do not put up such a Thunderbird-specific config. We'll just be broken. See comment 5 and comment 1. I can't explain it any better than that.
> this server not only supplies this config-v1.1.xml file but also an AutoDiscover file with a heap of Exchange stuff in it and that's triggered by whether the password is empty or not? Like I said, the config-v1.1.xml was a band-aid they put up for old Thunderbird versions, before the username field fix. They were not happy with that setup. They pleaded the case to me, and it's a widespread problem. Most other Exchange admins do not put up such a Thunderbird-specific config. We'll just be broken. See comment 1 and comment 5. I can't explain it any better than that.