

() I do not maintain this add-on anymore. I will keep my pages online for the archive. You can get new versions from their github page. But the guys from Ericsson have taken over maintanance. This is obvious because Thunderbird can detect the ports but is unable to verify the account.() As you can read I no longer maintain this add-on.

I've looked into the matter with one of our network administrators but our network settings are correct.

Still, when a user tries to connect a mailbox using IMAP, or when I try to connect to the testmailboxĮxchange.otrstest using POP, the e-mailclient Thunderbird finds the correct port numbers but is unable verify the account: Set-ServerComponentState -Identity SRVXX -State Active -Requester HealthAPI -Component PopProxy Set-ServerComponentState -Identity SRVXX -State Active -Requester HealthAPI -Component ImapProxy Yesterday we concluded that we didn't enable the ImapProxy and PopProxy components, so we did this as well (SRVXX is our Exchange server but I've removed the identity): I've used the following PowerShell command: The POP and IMAP services are running normal on the Exchange server.įor Problem 2 I've enabled POP on a specific test account: exchange.otrstest. I've done a lot of searching on Google but I can't find a similar problem.īy default, POP has been disabled on all mailboxes. Same problem as with the IMAP connectivity: we can connect using Thunderbird (as means of testing) but we get the same prompt:īecause these two problems are similar I've decided to put them in both in one question. This way, the custom CRM can extract the e-mail using POP protocol from the Exchange mailboxes and we are able to e-mail directly

To e-mail directly from Exchange mailboxes to these CRM mailboxes we have decided to configure POP boxes on our Exchange server. Right now we are using a postfix solution on a Linux host which hosts those POP boxes, but because we want to be able Problem 2: Another application we use for our customer e-mail (a custom build CRM) uses POP boxes to extract the e-mail from it. To connect to their mailbox with the prompt stating: ' username or password invalid'. For some reason they want to use Thunderbird with the IMAP protocol to view their mail. Problem 1: some colleagues use Linux on their workstation, and they normally use Outlook on the web to access their Exchange 2016 mailboxes. Users are using Outlook on the web (OWA) or Outlook (Exchange protocol) to access their mailboxes. We are using an Exchange Server 2016 setup which is working fine.
