Hi,
I was just wondering if anyone has any experience getting this to work properly?
We're migrating from on-premise Exchange to 365 and when we have test migrated a mailbox polled by vFire we're having a few issues.
We have always used POP in vFire to get the emails, so we're continuing with this and this is how are settings look in vFire for the migrated mailbox now:
Image may be NSFW.
Clik here to view.
We have ticked "Use SSL" - as advised by Alemba - but leaving this unticked and it also seems to work. Apart from this we haven't made any other changes and the mailbox seems to be getting polled and calls are being logged. However...
In the server event log we are getting loads of error events like this:
Image may be NSFW.
Clik here to view.
All of these entries contain this:
Infra.Mail.Pop3.Pop3ReceiveMailHandler - Technology - JB Test - ERROR: (Infra.Mail) Error in Infra.Mail
Infra.Mail.Pop3.Pop3ReceiveMailHandler - Technology - JB Test - Type: (System.RuntimeType) MailBee.Pop3Mail.MailBeePop3LoginBadCredentialsException
Infra.Mail.Pop3.Pop3ReceiveMailHandler - Technology - JB Test - Source: (System.String) "MailBee.NET"
Infra.Mail.Pop3.Pop3ReceiveMailHandler - Technology - JB Test - Message: (System.String) "Wrong account name and/or password. The server responded: -ERR Logon failure: unknown user name or bad password."
Infra.Mail.Pop3.Pop3ReceiveMailHandler - Technology - JB Test - Stack Trace: (System.String) " at a.k.i.a(String A_0, String A_1, String A_2)
at a.o.a(AuthenticationMethods A_0, AuthenticationMethods A_1, SaslMethod A_2, AuthenticationOptions A_3, String A_4, String A_5, String A_6, String A_7)
at a.l.a(AuthenticationMethods A_0, AuthenticationMethods A_1, SaslMethod A_2, AuthenticationOptions A_3, String A_4, String A_5, String A_6, String A_7)
at a.l.e()
at a.k.j.e(Boolean A_0)
at a.k.j.e()
at a.al.b6()
at a.x.a(Boolean A_0, String A_1, String A_2, String A_3, String A_4, AuthenticationMethods A_5, AuthenticationOptions A_6, SaslMethod A_7)
at a.x.a(Boolean A_0, String A_1, String A_2, AuthenticationMethods A_3)
at Infra.Mail.Pop3.Pop3ReceiveMailHandler.DoConnectIfNecessary()
at Infra.Mail.ReceiveMailHandler.ConnectIfNecessary()"
Infra.Rules.EmailInService.PollAllInboxes ERROR: (Infra.Services.Messaging) The username or password supplied is invalid.
Infra.Rules.EmailInService.PollAllInboxes Type: (System.RuntimeType) Infra.Mail.InfraMailException
Infra.Rules.EmailInService.PollAllInboxes Source: (System.String) "Infra.Mail"
Infra.Rules.EmailInService.PollAllInboxes Message: (System.String) "The username or password supplied is invalid."
Infra.Rules.EmailInService.PollAllInboxes Stack Trace: (System.String) " at Infra.Mail.ReceiveMailHandler.ConnectIfNecessary()
at Infra.Mail.ReceiveMailHandler.get_MessageCount()
at Infra.Rules.EmailInService.ProcessSingleInbox(InfraSession Session, ServiceToken Token, ReceiveMailHandler EmailIn, IonixIncomingEmailController Controller)
at Infra.Rules.EmailInService.PollAllInboxes(InfraSession Session, ServiceToken Token)"
Infra.Rules.EmailInService.PollAllInboxes
The username and password are not invalid - as the emails are being POP'ed and calls logged, but it is still filling up the event log with these events.
Anyone else tried this and got it working with errors being generated? I have raised this with Alemba, but they advised me that 365 is currently not supported, but they are aware that some other clients have got it working.
Thanks for any advise, Ian