The following calls seem to be returning empty results when opening a mail hosted in a mailbox on Exchange WebServer 2013 15.0.1473.4003
office.context.mailbox.userProfile
office.context.mailbox.item.to
Exchange WebServer 2013 15.0.1473
Sample of Clients tested
Mac | Outlook 16.29 (190908.02) | Fail
Mac | Outlook 16.16.14 (190909) | Success
Mac | Outlook 16.16.13 (190811) | Success
Mac | Outlook 16.29 (190908.02) | Success
PC | Outlook 16.0.12026.20264 | Success
UPDATED: The issue is appearing for only one single client (Outlook 16.29 - 190908.02) but is working fine for another user with the same version.
Related
I'm looking at implementing the necessary handling for CORS on a Device which exposes a basic HTTP server for control. In order to define how the Device should respond I've found myself attempting to understand just how the browser would be configured to perform the requests. In particular, I'm trying to better understand the behaviour of a browser around Fetch's Request credentials mode (and to a lesser extent XMLHttpRequest.withCredentials).
I'm aware that it would be problematic for the Device to respond with Access-Control-Allow-Origin: * if the Initial Server has set the request's credentials mode to be include. This is per the table here.
I don't quite understand when / why the Initial Server would actually set this mode.
Is this...
a flag to the browser so its aware the Initial Server has explicitly added credentials in its request to Device
a request to the browser's internal mechanisms to find any credentials for Device it has stored, and to include them in the CORS Request
a request to the browser's internal mechanisms to forward on any credentials it has used when talking to Initial Server onto the Device
other (?)
I'm assuming its intended for enabling option 2 due to the reference to the Confused Deputy problem in the above link but my knowledge of browser behaviour is non-existent.
If there were certain URIs on Device which required an Authorization header, would that have a definitive effect on the value of the credentials mode specified with the request (even if I assume the Initial Server was likely to be the one specifying the value for that header)? This is of interest, as I believe if include mode is required for these paths, then this would necessitate the addition of a Access-Control-Allow-Credentials header on the CORS Response.
The following diagram is just an overview of the expected interactions. Its assumed the CORS Preflight request is necessary for the resources being retrieved.
Browser Initial Server Device
| | |
| GET | |
| ----------------> | |
| | |
| Also GET Device | |
| <---------------- | |
| | |
| CORS Preflight Request (OPTIONS) |
| ----------------------------------------> |
| | |
| CORS Preflight Response |
| <---------------------------------------- |
| | |
| CORS Request (GET) |
| ----------------------------------------> |
| | |
| CORS Response |
| <---------------------------------------- |
Under the Batch Service option, we are running a custom dot net activity, and that .net tool downloads data from some APIs. It was working fine without any issues until yesterday. Now we are facing the below error while downloading data from the APIs. I don't know why we are facing such an issue suddenly.
Error: The request was aborted: Could not create SSL/TLS secure
channel. StackTrace: at System.Net.WebClient.OpenRead(Uri address)
at Import.DownloadSite(String url, String type)
The same .Net tool works fine in our local desktop machines(Windows 10 OS). Getting the error only in the batch account machine. So I think the problem is in the batch account machine.
Using the below C# code for downloading data from the APIs:
WebClient wc = new WebClient();
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12 | SecurityProtocolType.Tls11 | SecurityProtocolType.Tls | SecurityProtocolType.Ssl3;
return wc.DownloadString(string.Format(ApiUrl, type));
I tried most of the solutions suggested in the below link, and nothing works for me.
The request was aborted: Could not create SSL/TLS secure channel
More information:
.NET Framework: v4.5
Batch machine: Windows Server 2012 R2 (x64)
You need to Add HTTP Header "Expect" with value "100-continue". In your case, please add these lines of code before creating the request :
ServicePointManager.Expect100Continue = true;
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls
| SecurityProtocolType.Tls11
| SecurityProtocolType.Tls12
| SecurityProtocolType.Ssl3;
I have an application for which I am writing tests using pytest to validate the behavior. The application is as follows
+-------------------+
| App under test |
+-------------------+ +------------------+
| external library | | remote endpoint |
| (socket client)-+--->| (socket server) |
+-------------------+ +------------------+
I am writing tests for the "App Under Test". The App imports external library and the socket client is an integral part of external library. I want to mock the remote endpoint and must be able to respond mock data when ever there was a request made and validate the "App Under Test"'s behavior. How to achieve this?
P.S. I am interested in the behavior of "app Under Test". The behavior of the app depends on the data it receives from the socket server. I am NOT interested in the underlying "external library".
How can i set an alert in OMS when a server is powered off or is not available? I have searched on google but the alerts either dont work or too many get sent . I need the alert to be generated as soon as the server goes offline
i found out myself
Heartbeat | summarize LastHeartbeat = max(TimeGenerated) by Computer | where Computer == "server1" | where LastHeartbeat < ago(5m)
Framework: Laravel 4.2
Server: Amazon ec2 Linux
Yesterday \Mailing::send was still working and then suddenly today it stop sending emails. I don't know what has happened.
here is my mail.php config:
<?php
return array(
/* x
|--------------------------------------------------------------------------
| Mail Driver
|--------------------------------------------------------------------------
|
| Laravel supports both SMTP and PHP's "mail" function as drivers for the
| sending of e-mail. You may specify which one you're using throughout
| your application here. By default, Laravel is setup for SMTP mail.
|
| Supported: "smtp", "mail", "sendmail", "mailgun", "mandrill", "log"
|
*/
'driver' => 'mail',
/*
|--------------------------------------------------------------------------
| SMTP Host Address
|--------------------------------------------------------------------------
|
| Here you may provide the host address of the SMTP server used by your
| applications. A default option is provided that is compatible with
| the Mailgun mail service which will provide reliable deliveries.
|
*/
'host' => 'mail.1fx.cash',
/*
|--------------------------------------------------------------------------
| SMTP Host Port
|--------------------------------------------------------------------------
|
| This is the SMTP port used by your application to deliver e-mails to
| users of the application. Like the host we have set this value to
| stay compatible with the Mailgun e-mail application by default.
|
*/
'port' => 587,
/*
|--------------------------------------------------------------------------
| Global "From" Address
|--------------------------------------------------------------------------
|
| You may wish for all e-mails sent by your application to be sent from
| the same address. Here, you may specify a name and address that is
| used globally for all e-mails that are sent by your application.
|
*/
'from' => array('address' => 'info#philwebservicescloud.net', 'name' => '1Fx Cash'),
/*
|--------------------------------------------------------------------------
| E-Mail Encryption Protocol
|--------------------------------------------------------------------------
|
| Here you may specify the encryption protocol that should be used when
| the application send e-mail messages. A sensible default using the
| transport layer security protocol should provide great security.
|
*/
'encryption' => 'tls',
/*
|--------------------------------------------------------------------------
| SMTP Server Username
|--------------------------------------------------------------------------
|
| If your SMTP server requires a username for authentication, you should
| set it here. This will get used to authenticate with your server on
| connection. You may also set the "password" value below this one.
|
*/
'username' => 'info#philwebservicescloud.net',
/*
|--------------------------------------------------------------------------
| SMTP Server Password
|--------------------------------------------------------------------------
|
| Here you may set the password required by your SMTP server to send out
| messages from your application. This will be given to the server on
| connection so that the application will be able to send messages.
|
*/
'password' => '******',
/*
|--------------------------------------------------------------------------
| Sendmail System Path
|--------------------------------------------------------------------------
|
| When using the "sendmail" driver to send e-mails, we will need to know
| the path to where Sendmail lives on this server. A default path has
| been provided here, which will work well on most of your systems.
|
*/
'sendmail' => '/usr/sbin/sendmail -bs',
/*
|--------------------------------------------------------------------------
| Mail "Pretend"
|--------------------------------------------------------------------------
|
| When this option is enabled, e-mail will not actually be sent over the
| web and will instead be written to your application's logs files so
| you may inspect the message. This is great for local development.
|
*/
'pretend' => false,
);
I have tried restarting the instance. Its still not sending.
First find out if there is any mails stuck in email spool. If it is empty then it is lavarels problem. Otherwise mail is stuck and could be affected by antispam filter. To resolve it fill this form