I am using version 3.4 and when I create a process to forward an email I get the following message when it tries to connect to our Exchange server.
Error. None of the specified authentication methods is supported by the server..
We do not require a username and password to connect but have tried both with and without.
I have another rule that is "send an email" and this one using the same exact settings works fine.
For testing I modified the process to send an email and it goes through fine except I need it to forward the email.
I enabled logging on the receive connector for Exchange and get the following log which shows that anonymous connections are being accepted but the parser appears to get confused and go braindead because it has no credentials to give.
,+,,
,*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
,*,SMTPSubmit SMTPAcceptAnyRecipient SMTPAcceptAuthenticationFlag SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender BypassAntiSpam BypassMessageSizeLimit SMTPAcceptEXCH50 AcceptRoutingHeaders,Set Session Permissions
,>,"220 mail.myoffice.com Microsoft ESMTP MAIL Service ready at Mon, 28 Oct 2013 16:11:17 -0700",
,<,EHLO [10.90.0.50],
,>,250-mail.myoffice.com Hello [10.90.0.50],
,>,250-SIZE 10485760,
,>,250-PIPELINING,
,>,250-DSN,
,>,250-ENHANCEDSTATUSCODES,
,>,250-AUTH,
,>,250-8BITMIME,
,>,250-BINARYMIME,
,>,250-CHUNKING,
,>,250-XEXCH50,
,>,250 XSHADOW,
,-,,Remote
If I enable authentication it will let me login and forward the email but only as the logged in user not as the original offsite sender (which anonymous will let me do if I could get connected anonymously)
Error. None of the specified authentication methods is supported by the server..
We do not require a username and password to connect but have tried both with and without.
I have another rule that is "send an email" and this one using the same exact settings works fine.
For testing I modified the process to send an email and it goes through fine except I need it to forward the email.
I enabled logging on the receive connector for Exchange and get the following log which shows that anonymous connections are being accepted but the parser appears to get confused and go braindead because it has no credentials to give.
,+,,
,*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
,*,SMTPSubmit SMTPAcceptAnyRecipient SMTPAcceptAuthenticationFlag SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender BypassAntiSpam BypassMessageSizeLimit SMTPAcceptEXCH50 AcceptRoutingHeaders,Set Session Permissions
,>,"220 mail.myoffice.com Microsoft ESMTP MAIL Service ready at Mon, 28 Oct 2013 16:11:17 -0700",
,<,EHLO [10.90.0.50],
,>,250-mail.myoffice.com Hello [10.90.0.50],
,>,250-SIZE 10485760,
,>,250-PIPELINING,
,>,250-DSN,
,>,250-ENHANCEDSTATUSCODES,
,>,250-AUTH,
,>,250-8BITMIME,
,>,250-BINARYMIME,
,>,250-CHUNKING,
,>,250-XEXCH50,
,>,250 XSHADOW,
,-,,Remote
If I enable authentication it will let me login and forward the email but only as the logged in user not as the original offsite sender (which anonymous will let me do if I could get connected anonymously)
Thanks, this was a bug. We have just fixed it and it will be working in the upcoming version of the program