I'm not really an EWS user, just trying to help debug a mailing application that stopped working last year.
We get an error message when trying to send() that the connection was forcibly closed. Reading up on the issue it seems like a lot of folks are saying it's a TLS version problem.
Someone here think it's because we are using Basic Authentication (instead of Modern Authentication with OAuth 2.0). We don't see any issues directly related to authentication.
By still using Basic Authentication, can that cause the connection closed issue when we try to execute the send() method?
No a connection being forcibly closed is most likely either TLS, bad ip reputation (eg a lot of spam/fraud coming from a certain IP that has been blacklisted) or your sending a message with a very large attachment in a single request. If it was a Basic Authentication disabled issue you would get a 401 error, if its was that EWS had been disabled (eg via set-casMailbox) you could get a 403.
Related
I have an application token. According to documentation
If you are throttled for any reason, you will receive a status code
429 response.
I have received no errors that I am being throttled. Sending requests from other servers are accepted just not the one that has been working fine up until today. What needs to be done to unblock my server and/or prevent it from reoccurring?
I have already gone through multiple links before posting and it is not a repeat question.I am not pretty sure that i should post it here or on server fault.
I am trying to configure the SMTP email task but running into error mentioned below.
System.Net.WebException: Unable to connect to the remote server
System.Net.Sockets.SocketException:An attempt was made to access a socket in a way forbidden by its access permissions ipaddress:25
I also tried to verify using powershell, if the SMTP is fine and below are the results:
Using Send-mailmessage : It is working really fine
Using Net.Mail.SmtpClient : I could send email to organization email ids but not outside.
Can someone help me understand where exactly the problem could be.
The problem was Antivirus was blocking the requests from SSIS but was allowing the powershell requests.
In my wp8 app,
I enter a open wifi which is operated by communication operator
blocked by a portal page that needs using account and password to log in
after I post some data to a https url
I have the ability to use the wifi network to access to internet freely.
Now,I encounter a problem:
before the https connection established successfully,it will be running the Online Certificate Status Protocol (OCSP)
OCSP needs to access to CA like veriSign to verify the server certificate status
but I have no internet access at this moment.
So,my app return a Webexception whose description is "The remote server returned an error: NotFound".I think it is because of the failure of OCSP.
Based on above,I want to find a solution to sovle this:
My point is to disable the OCSP mechanism，Do you know how to do this?
And I also would like to know if there is another solution to sovle the problem.
Hope your advice,Thanks!
The way you'd do that on .NET is to set the ServicePointManager.ServerCertificateValidationCallback delegate and perform the logic you want to perform. But, unfortunately that is not yet available on Windows Phone.
There are various uservoice suggestions related to this, for example:
http://windowsphone.uservoice.com/forums/101801-feature-suggestions/suggestions/2146033-allow-self-signed-and-corporate-certificates-for-s
http://windowsphone.uservoice.com/forums/101801-feature-suggestions/suggestions/4299617-client-ssl-certificate-authentication
They don't apply to you directly, but if they end up gaining access to ServicePointManager then you'll be able to do what you want to do.
I'm located behind a SSL proxy and am trying to use Chrome with StackOverflow, but I'm unable to authenticate to Google's server (or any others) and get the following error:
"Error 107
(net::ERR_SSL_PROTOCOL_ERROR): SSL
protocol error."
Can anyone explain to me why this would be happening? I am able to access https://chase.com with no issue, so I'm not sure why the SSO function is having an issue.
Additionally, I'm able to use IE to authenticate with SO and Google with no issue (how I'm posting this )
My query string looks like this.
https://www.google.com/accounts/o8/ud?openid.claimed_id=http://specs.openid.net/auth/2.0/identifier_select&openid.identity=http://specs.openid.net/auth/2.0/identifier_select&openid.return_to=https://stackoverflow.com/users/authenticate/%3Fs%3D61ca4f73-a29d-4c67-b316-6b003cf50bb3%26dnoa.userSuppliedIdentifier%3Dhttps%253A%252F%252Fwww.google.com%252Faccounts%252Fo8%252Fid&openid.realm=https://stackoverflow.com/users/authenticate/&openid.mode=checkid_setup&openid.ns=http://specs.openid.net/auth/2.0&openid.ns.alias3=http://openid.net/srv/ax/1.0&openid.alias3.if_available=alias1,alias2,alias3&openid.alias3.required=alias4&openid.alias3.mode=fetch_request&openid.alias3.type.alias1=http://schema.openid.net/namePerson&openid.alias3.count.alias1=1&openid.alias3.type.alias2=http://schema.openid.net/contact/email&openid.alias3.count.alias2=1&openid.alias3.type.alias3=http://axschema.org/namePerson&openid.alias3.count.alias3=1&openid.alias3.type.alias4=http://axschema.org/contact/email&openid.alias3.count.alias4=1
I have C++ Win32 app that uses HttpSendRequest to request some URL (via https). It worked OK earlier; but then errors ERROR_INTERNET_INCORRECT_HANDLE_STATE began happen. Why these ones? Any ideas?
I stumbled across something very similar recently. It suggests that your HttpOpenRequest has either failed or not yet completed, or during the HttpSendRequest() call the connection died for some reason (SSL handshake problems, Certificate problems, or just simple TCP connection problems).
I specifically saw the problem when developing an app using the asynchronous WinINET process, and my calls to HttpQueryInfo and InternetReadFile were failing with that return code.
In my case, I wasn't correctly waiting for the async notifications from HttpSendRequest to be received before calling the other methods, and also in cases where I wasn't correctly dealing with failures during the connection.
I know its a year late, but hopefully that helps.
It seems trivial but,
did you have flag INTERNET_FLAG_SECURE in making HttpOpenRequest?
as described in:
http://support.microsoft.com/kb/168151
For I myself was stuck here for hours until I found above knowledge base entry.
I got the same error on Windows XP for HTTPS connection (all flags correct) for the HTTP2 server endpoint, I wonder if it can't properly handle HTTP2 connection or the certificate.