New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Desktop clients all use MAPI/EWS, mobile clients use activesync.
Were able to give MAPI to everyone at no additional cost or restrictions. Activesync though either requires we use an opensource implementation, or pay Microsoft a per year license fee.
While some users felt the price was “fair”, we hoped we could offer someone similar at no cost.
Francisco
...
...
Thanks for ELI5-ing it to me
This is now fixed
Francisco
Great news. I've tried it, and it's working great.
There's a little flaw. When I checked the email settings in iOS after adding the email box as Exchange, I saw the auto-discovered Exchange server was set to us1.workspace.org rather than mail.mydomain.com. Was it by design? Can it be auto-discovered as mail.mydomain.com?
...
Can it be auto-discovered as mail.mydomain.com?
Would this be of any advantage? I only see it as an additional DNS lookup, and no real advantage otherwise.
I also used the workspace server in order to avoid an extra DNS lookup every time the email client initiates a connection (IMAP, SMTP, Exchange, etc)
Yeah, I can pull the ssl hostname for the domain and send that instead
will work on that today.
Francisco
Well, it did add an extra DNS lookup, but we have caches, so I don't think it adds noticeable overheads with proper TTL settings. It's just a nice-to-have feature, as the other auto-discovered protocols are translated to mail.mydomain.com as well.
You are awesome!
Has anyone poked around the webmail and able to find the disposable email feature? Care to share where it is, as I'm either blind or not looking in the right place...
TIA
Right click on the webmail pane.
Francisco
...
I must be a moron, but right-clicking anywhere in the webmail interface just shows the default browser right-click menu. Which pane are you referring to - the message list to the left, or the message preview to the right?
Or does it need to be enabled first?
I think on the left side where you pick your mail folders is where I saw it? Sorry just AFK at the moment.
There is a context menu though so maybe your browser is blocking it?
Francisco
...
OK found it. You actually have to right-click on an actual folder (or the top-left folder icon) in order for the proper menu to show... Why this was bundled with the folder functionality for right-clicking is beyond me...
@Francisco It looks like something has broken today. Outlook desktop and Apple Mail can no longer auto-discover POP/SMTP/IMAP/EWS settings, and EWS accounts (using the MAPI/EWS app password) can't be added (it used to be good). The iOS mail app can still auto-discover and add EAS accounts using the POP/SMTP app password.
Maybe you're doing something to the server and haven't finished yet?
You mean ONLY when trying to add a new account to Outlook / Apple Mail? Or does that also impact accounts already added? Because I'm in the latter category and my accounts work just fine
I meant when adding a new account to Outlook and Apple Mail. The already added accounts do not have a problem, but once an account is removed, it fails to be re-added.
I'll try it. You set it to use IMAP I guess? Not exchange?
Francisco
I set it to Exchange, it failed. I couldn’t see a manual option for Exchange so I couldn’t add it.
If I added it as IMAP, auto-discovery did not seem to work. With the manual input of server addresses and ports, it can be successfully added.
Can you PM me the domain? I can't replicate this. My test script dumps both autodiscovers w/o issue.
Francisco
Sure. I've PMed you a recording of my operation in Outlook. It's not only happened to one domain name, all of my domains have the same problem. The problem is similar in Apple Mail but with a different error message saying failed to check Username or Password (but I'm sure passwords are correct because I've successfully added 9 email accounts on different devices previously).
...
Wondering if this was fixed...
It works fine minus one bug.
Since this uses the IMAP password, if you have 2FA enabled, it'll break since the Calendar part of EAS is handled by WEBDAV on the backend, which uses a different password.
If you don't want to disable 2FA, it's probably best we disable CALDAV until we get our new backend completed.
Francisco
I think it was reported it didn't work using the MAPI / EWS password and autodiscovery on desktop (ie not IMAP on mobile). Manually configured using IMAP on mobile, it worked indeed
Exactly. And it’s working fine two days ago. I’m trying to figure out if the issue is from my end. I’ve also tried the eMClient and it was the same. I’ll use a proxy later to see if there’s something interferes and breaks when communicating with the auto discovery.
@Francisco did you mean you finished making the EAS autodiscover pull the mail.mydomain.com? If you did then it’s also weird I still see it pulling us1.workspace.org as of now.
I bet in that time you enabled 2FA.
We use Z-Push for our EAS implementation, which makes 3 connections (1 to IMAP for email, 1 to CALDAV for calendar, 1 to CARDAV for contacts). If you don't have 2FA enabled, then 1 single password covers all 3.
When 2FA is enabled, you get an app password for IMAP, EAS, WEBDAV, and EWS (I think?).
The EAS password doesn't work for our EAS because Smartermail isn't handling our EAS. This also means that when CALDAV tries to connect, it fails because the password is wrong, making all of EAS, and likely even autodiscover, bomb out.
The 'fix' for now is me disabling CALDAV in EAS. People can then hook WEBDAV in their phone for that until we get our own backend built out for Z-Push to unify things.
Not yet. Been a very busy week(end) with us working to hire new helpers, working on the Netherlands stuff, cranemail EU, etc.
Francisco
I did enable 2FA, but I've just disabled it and tried again. Unfortunately, the problem persisted. The problem is not with EAS, it's with EWS. I can connect to EAS on my phone without a problem (I don't need to sync with CALDAV, I selected to sync just emails).
I sent you two screen recordings last time. One was on a Mac, and the error message was "Unable to verify account name or password." (Maybe because it prompted for a username and password before trying to connect first). The other one was on Windows, and Outlook couldn't even get to the password verification step. It failed and stopped when discovering settings without asking for a username and password.
I've tried using a proxy and had the same problem. Through the proxy monitor window, I could see that the last domains it connected to before showing the error messages were autodiscover.mydomain.com (Mac) and api.diagnostics.office.com (Windows).
Edit:
I created a new email account and tried again (without 2FA). This time, Outlook prompted me to enter a username and password, but after I entered them, the same error showed. This means Outlook did send the username and password for verification in the autodiscovery step, but somehow, it failed to pass (probably NOT because the password was wrong; the password was correct, but it still failed). It's neither a 2FA problem nor a POP/SMTP/IMAP/EAS problem; it's an autodiscovery problem with Exchange (EWS) on the desktop.
Update:
I've tried Thunderbird with the paid Owl for Exchange add-on. It cannot be added with auto-discovery, either. However, Owl for Exchange supports manually entering the EWS server URL and settings, and the EWS account was manually added, and it worked.
But Outlook (both the classic and new Outlook), eM Client, and Apple Mail were all unable to get past auto-discovery and couldn't be added as Exchange accounts.
Can you test adding an Exchange account in Outlook and Apple Mail to see if it works? My already added accounts are working normally, just can't add new Exchange accounts in Outlook and Apple Mail anymore, and the current working accounts were only added two days ago. Something must have changed.
You know what… go into smartermail and make sure mapi is enabled still.
We updated smartermail recently and there was reports of mapi randomly getting disabled and required reenabling.
Francisco
It was enabled. And I did say that I disabled 2FA and also created a new email account without 2FA to test. It just don’t work with auto-discover, but works with manually entered settings. I have tried at least 50 times in four email clients. Did you tested it in one of the email clients I mentioned?
And I also mentioned that I manually connected to EWS in thunderbird with the Owl for Exchange addon and it was working. How can it be the password or protocol problem when the same password and protocol were accepted in manually entered settings.
I've just rechecked. MAPI is enabled.