exchange server

2639 Topics

Exchange Server error in '/owa' application
ASSERT: HMACProvider.GetCertificates:protectionCertificates.Length<1 Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: Microsoft.Exchange.Diagnostics.ExAssertException: ASSERT: HMACProvider.GetCertificates:protectionCertificates.Length<1 Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [ExAssertException: ASSERT: HMACProvider.GetCertificates:protectionCertificates.Length<1] Microsoft.Exchange.Diagnostics.ExAssert.AssertInternal(String formatString, Object[] parameters) +241 Microsoft.Exchange.Clients.Common.HmacProvider.GetCertificates() +478 Microsoft.Exchange.Clients.Common.HmacProvider.GetHmacProvider() +143 Microsoft.Exchange.Clients.Common.HmacProvider.ComputeHmac(Byte[][] messageArrays) +16 Microsoft.Exchange.HttpProxy.FbaModule.SetCadataCookies(HttpApplication httpApplication) +826 Microsoft.Exchange.HttpProxy.FbaFormPostProxyRequestHandler.HandleFbaFormPost(BackEndServer backEndServer) +2776 Microsoft.Exchange.HttpProxy.FbaFormPostProxyRequestHandler.ShouldContinueProxy() +20 Microsoft.Exchange.HttpProxy.ProxyRequestHandler.BeginProxyRequestOrRecalculate() +229 Microsoft.Exchange.HttpProxy.ProxyRequestHandler.InternalOnCalculateTargetBackEndCompleted(TargetCalculationCallbackBeacon beacon) +1379 Microsoft.Exchange.HttpProxy.<>c__DisplayClass3f.<OnCalculateTargetBackEndCompleted>b__3e() +311 Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate) +35 Microsoft.Exchange.HttpProxy.Diagnostics.SendWatsonReportOnUnhandledException(MethodDelegate methodDelegate, LastChanceExceptionHandler exceptionHandler) +121 Microsoft.Exchange.HttpProxy.ProxyRequestHandler.CallThreadEntranceMethod(MethodDelegate method) +69 [AggregateException: One or more errors occurred.] Microsoft.Exchange.HttpProxy.ProxyRequestHandler.EndProcessRequest(IAsyncResult result) +416 System.Web.CallHandlerExecutionStep.InvokeEndHandler(IAsyncResult ar) +231 System.Web.CallHandlerExecutionStep.OnAsyncHandlerCompletion(IAsyncResult ar) +172
Solved
Nikolas_Athanasakis
Jul 14, 2021 Place Exchange
Views
3likes
Comments
Shared mailbox: Use send-as, not send on behalf from Outlook 2016
Hello, We have a lot of shared mailboxes. For every shared mailbox, we create a specific security group that contains the members who should have access to that particular shared mailbox. We give full mailbox permissions and send-as permissions for that particular security group onto the shared mailbox. For example, security group A has full mailbox access and send-as permissions onto shared mailbox A. By adding users to security group A, they have full access to the shared mailbox. We create every new shared mailbox/security group combo using Powershell. That has been working flawlessly for the last years. However, for a recent new shared mailbox/security group combination, when a user that's member of the related security group wants to send an e-mail from the shared mailbox (by changing the from field in Outlook and selecting the shared mailbox from the global address list), Outlook tries to send every time 'send-on behalf'. This only happens for that newly created mailbox. I compared the output of Get-Mailbox and Get-RecipientPermission for the new problem shared mailbox and an older shared mailbox (which enable users to send mail send-as from outlook just fine) but I couldn't find any differences. For your information, that's the error we get back immediately after trying to do a send-as for the new shared mailbox: Your message did not reach some or all of the intended recipients. Subject: Test from Outlook Sent: 23/11/2017 9:27 The following recipient(s) cannot be reached: name of sending user on 23/11/2017 9:27 This message could not be sent. Try sending the message again later, or contact your network administrator. You do not have the permission to send the message on behalf of the specified user. Error is [0x80070005-0x0004dc-0x000524]. Why does Outlook always tries to do a send on behalf (what we don't want) where else for other shared mailboxes, send-as works fine? Using send-as from OWA however works just fine for the newest shared mailbox. It only seems a problem related to Outlook (tested on multiple clients that have access to the shared mailbox) and that particular new shared mailbox. Thanks in advance.
Solved
Tom Glorieux
Nov 23, 2017 Place Exchange
Views
3likes
Comments
"NeedsApproval"
Hi All, So I have been migrating mailboxes from onprem to O365 in the hybrid config with no issues. Today I have two migration batch jobs that state "NeedsApproval", but everything migrated. Kind of confused as i don't see a way to "approve" the jobs and I don't see any issues. Any ideas?
LED04
Oct 13, 2021 Place Exchange
Views
1like
Comments
DELETE DUPLICATE EMAILS
I would like to know the easiest way in order for me to delete multiple emails under my Microsoft Exchange Accounts
padamssm
Aug 25, 2020 Place Exchange
Views
0likes
Comments
does not designate permitted sender hosts
Hi Everyone I am hoping someone can assist me with the following issue. I have SPF and DKIM configured on my domain, which appear to be setup correctly but when I examine the message header of an email I sent I see the following entry "None (protection.outlook.com: za.cfao.com does not designate permitted sender hosts)" Just to add I am using Exclaimer for signature management. Please can someone examine the header below and advised if I configured something incorrectly. "Delivered-To: nsadheo@gmail.com Received: by 2002:a4f:c15:0:0:0:0:0 with SMTP id 21csp930979ivm; Wed, 21 Aug 2019 06:30:56 -0700 (PDT) X-Google-Smtp-Source: APXvYqyk6Zvuz4Zzp1WUwoJQlz3EsF/mENO5B7uNOXkWXKiQUJ9CmIl25//eS3gDvDa/NqaFIZJg X-Received: by 2002:a17:906:158c:: with SMTP id k12mr31626198ejd.83.1566394255976; Wed, 21 Aug 2019 06:30:55 -0700 (PDT) ARC-Seal: i=2; a=rsa-sha256; t=1566394255; cv=pass; d=google.com; s=arc-20160816; b=lbJV6glrTA9esPnHzJRI/x2ugMmh1yM0zYOO4Hmhvpeuwblxjcnlf4yErbNS9ShdTC zz7tB3Tlp63d+mH95cXl0tVS6pXE852lUmxX47jdY5tuQ86Mn788xO/HP8y1VlFlamK2 zTuOJ3ow4d264I2lPWXgueWLQOOwVvjyLOsz0hxpo4TIfLY+YLvTr2XlDUW7F4ZIC50o fjfU5YP15UvEHg4+YPHRqmiMQyp6DT6No71nhWhbZyCdzTWFs6A8a2QJEYYuY5hccLd7 4sHcycJKruMu0BIGoa7e5O/BS5zXRxqoPzN9IvrMQu0IiI0hQS4Fc+iqTs+RRuRnl8Ex z3bA== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=mime-version:content-language:accept-language:message-id:date :thread-index:thread-topic:subject:to:from:dkim-signature; bh=mEa8xeBYgC5oDAMvVia716t3ct7BI+dA6l0bklr8UAM=; b=AC+iiIgfhye53K/jD2GTMuQhsu1Us5iZQcxKe/x1ww59llPOzWCipIVOSJ6kO2/kM5 5QesFTIYMNlMRaJwaHWOkR+Muy2SRaaxpPhLc4lpbjmdZpgtxKZlyLmuXkx3UZvIVjzL hMOz4U7K6G0iDr8LgxsRRCjMWjUMBQAE6ohKsxlTT4aA1aiCp/Fqe48DjpBK8/Wwkj+5 Ui8Lvtv2xiwFIuRtITLmBNz0+Z2dbInt1pTAsMQhE5dJyH7TjIuFaPB484UNz3m21xX6 S1WKMEPP19uGuXCFJUtkSmZyJub93td7GsYXCE3v765FkYeTV7SukV6EQavzyE7esCLR OOtA== ARC-Authentication-Results: i=2; mx.google.com; dkim=pass header.i=@za.cfao.com header.s=selector2 header.b=FP6CtFnn; arc=pass (i=1 spf=pass spfdomain=za.cfao.com dkim=pass dkdomain=za.cfao.com dmarc=pass fromdomain=za.cfao.com); spf=pass (google.com: domain of nsadheo@za.cfao.com designates 40.107.5.95 as permitted sender) smtp.mailfrom=nsadheo@za.cfao.com Return-Path: <nsadheo@za.cfao.com> Received: from EUR03-VE1-obe.outbound.protection.outlook.com (mail-eopbgr50095.outbound.protection.outlook.com. [40.107.5.95]) by mx.google.com with ESMTPS id p9si10358093ejf.115.2019.08.21.06.30.55 for <nsadheo@gmail.com> (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 21 Aug 2019 06:30:55 -0700 (PDT) Received-SPF: pass (google.com: domain of nsadheo@za.cfao.com designates 40.107.5.95 as permitted sender) client-ip=40.107.5.95; Authentication-Results: mx.google.com; dkim=pass header.i=@za.cfao.com header.s=selector2 header.b=FP6CtFnn; arc=pass (i=1 spf=pass spfdomain=za.cfao.com dkim=pass dkdomain=za.cfao.com dmarc=pass fromdomain=za.cfao.com); spf=pass (google.com: domain of nsadheo@za.cfao.com designates 40.107.5.95 as permitted sender) smtp.mailfrom=nsadheo@za.cfao.com ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=F+DwKETlHrzExLzhUmKe8DYH+g1ahFs/Ec9iuYU3WMOuPoD9LotwlIEWnRWr2ECk4a/jkV7N1x3bMakycJaZK/PYADiDo5GLXeaatvirya0YnMIYTNAV3rsmCKOxge1fkYTEi53IYOKBEy6kwAFnMEFlL9szBZ7JnUNyFu1tm17huZXUl4DT8nzAPcJs21gu5o2hGkKhPW7goMWDyZ/VVfQS7/q+X6uOwXStbGHhitkh2tw0Z6N7D4GPdU1WMxjrrmXYta4V2mGRvwM8K6s+QIEZx0h+2nmwvYQm9j5VeWQLsJ6HxWmVW4TDYBVbK7hjVk5l20iGZzpUnmndHc6Jjw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=mEa8xeBYgC5oDAMvVia716t3ct7BI+dA6l0bklr8UAM=; b=OlIwiuD9XISvwzVd1HdhPWx6ADnQiHYi+SUnkn6XGlIYa0RLu27hdFJbPDupi6xFv/LFyXqjv+g2gGpsAWY5nVvIPqICsw6iF7kYot/oEmYlsyoabmZbY2kIQAqXrxOn0eLMv/V0/2saTO3KM0SuhWENDBfZ4HeJ3F8L6O7QqI5a+g0KMR5SxDeapiLVD/qTZ5RxFcyPHeysnw1o0j4fmtIPI8ZPAM8JYufhdO/AkWgsDC6N3JraMUvwVeE23tmYZBzruS6Ip51aiUuoeGMY3YBAhYnFlQgbPNXgy4WwRfxeCeLhoR7jzA1QXHrUNjY/qjMrYGtS4LsSw8eUWM2ewg== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=za.cfao.com; dmarc=pass action=none header.from=za.cfao.com; dkim=pass header.d=za.cfao.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=za.cfao.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=mEa8xeBYgC5oDAMvVia716t3ct7BI+dA6l0bklr8UAM=; b=FP6CtFnnw6NVQziPrjiZsfdDEBYGCCmQAq3O5/goannAvxIwiT8pJagAe9vqYgQOcn/OXY4lB0SqUmS5UfrZi/iumosCAUW8fd/dOm/ltG+4OyZ41zecTdTflhNvdiSgxEUldjLvURAnYgyFjxxCjzCMQEq7gVp/N8lAwZ2E7Rk= Received: from DB8P190MB0730.EURP190.PROD.OUTLOOK.COM (52.135.63.144) by DB8P190MB0730.EURP190.PROD.OUTLOOK.COM (52.135.63.144) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2178.16; Wed, 21 Aug 2019 13:30:54 +0000 Received: from DB8P190MB0730.EURP190.PROD.OUTLOOK.COM ([fe80::71bf:4419:8bc4:a699]) by DB8P190MB0730.EURP190.PROD.OUTLOOK.COM ([fe80::71bf:4419:8bc4:a699%2]) with mapi id 15.20.2178.020; Wed, 21 Aug 2019 13:30:54 +0000 From: Navishkar SADHEO <nsadheo@za.cfao.com> To: NC Sadheo <nsadheo@gmail.com> Subject: test1 Thread-Topic: test1 Thread-Index: AdVYJKY9mClFl38XRWend63MaL4MVg== Date: Wed, 21 Aug 2019 13:30:54 +0000 Message-ID: <DB8P190MB0730A5E666636DC0871F162FF1AA0@DB8P190MB0730.EURP190.PROD.OUTLOOK.COM> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=nsadheo@za.cfao.com; x-originating-ip: [105.23.225.190] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: cf0e2d89-8b6b-48db-e189-08d7263bcad7 x-microsoft-antispam: BCL:0;PCL:0;RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020);SRVR:DB8P190MB0730; x-ms-traffictypediagnostic: DB8P190MB0730: x-microsoft-antispam-prvs: <DB8P190MB0730D72F146971F54A573808F1AA0@DB8P190MB0730.EURP190.PROD.OUTLOOK.COM> x-ms-oob-tlc-oobclassifiers: OLM:1728; x-forefront-prvs: 0136C1DDA4 x-forefront-antispam-report: SFV:NSPM;SFS:(10019020)(4636009)(346002)(396003)(376002)(366004)(136003)(39850400004)(199004)(189003)(81156014)(26005)(55016002)(6116002)(186003)(9686003)(3846002)(54896002)(6306002)(73894003)(74316002)(316002)(2906002)(102836004)(99286004)(6506007)(256004)(71190400001)(71200400001)(8936002)(33656002)(790700001)(7736002)(4270600006)(6436002)(25786009)(7116003)(6916009)(476003)(14454004)(486006)(76116006)(7696005)(66066001)(1411001)(66446008)(64756008)(66946007)(66476007)(66556008)(217283003)(52536014)(5660300002)(86362001)(8676002)(53936002)(81166006)(478600001);DIR:OUT;SFP:1102;SCL:1;SRVR:DB8P190MB0730;H:DB8P190MB0730.EURP190.PROD.OUTLOOK.COM;FPR:;SPF:None;LANG:en;PTR:InfoNoRecords;A:0;MX:1; received-spf: None (protection.outlook.com: za.cfao.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: s8HgQRDDo8xAYqnGArehkBX6oT8ql8aX1kVqtuMf+kHwheBv6i0An7xYGP7tvMkVskJljufiIPvSoWm7q166ekbNowo0HY2g0VptApLjHACVN+WRyRd1kXwfpT74x2BodJ2dS7BCsTzX6Ax1FZ1cq8FhDmRj8InG2vLlXes69Lgpwf8cHwbc578zHeALzuTHakLe7XlVZYLvL6/MQjLq+ARP1A7ybfgxvtMiJnk8keKAxOTB8+hblcaXjov0WsFtHvtKLr7fMLPlJUWOMYzMzoo383lWUX//97BLdB/tZbE= x-ms-exchange-transport-forked: True Content-Type: multipart/alternative; boundary="_000_DB8P190MB0730A5E666636DC0871F162FF1AA0DB8P190MB0730EURP_" MIME-Version: 1.0 X-OriginatorOrg: za.cfao.com X-MS-Exchange-CrossTenant-Network-Message-Id: cf0e2d89-8b6b-48db-e189-08d7263bcad7 X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Aug 2019 13:30:54.3575 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 15d1f070-0301-4099-9892-b8198001c1a6 X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: ydoY64BQKqKLBzQBXy9uHHQqH1OTIdPN8oEyGwTG1DnCr2DEBjsc6ZYrkvgO8e/0qKNxTENPNdgObCvlqFC/YQ== X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB8P190MB0730 --_000_DB8P190MB0730A5E666636DC0871F162FF1AA0DB8P190MB0730EURP_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable --_000_DB8P190MB0730A5E666636DC0871F162FF1AA0DB8P190MB0730EURP_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang=3D"EN-ZA" link=3D"#0563C1" vlink=3D"#954F72"> <div class=3D"WordSection1"> <p class=3D"MsoNormal"><span style=3D"font-family:"Segoe UI",sans= -serif"><o:p> </o:p></span></p> </div> </body> </html> --_000_DB8P190MB0730A5E666636DC0871F162FF1AA0DB8P190MB0730EURP_--"
Solved
Navishkar Sadheo
Oct 15, 2019 Place Exchange
Views
0likes
Comments
Configuring Delegate access via PowerShell.
Is the following window configurable at all via PowerShell? lots of Googling brings up various options and none seem to work. (this is in relation to the box below specifically) Things I've noted: Delegates set here are "ResourceDelegates" for the Get-CalendarProcessing output, but you can't use Set-CalendarProcessing as it only works on resource mailboxes (Error : "ResourceDelegates can only be enabled on resource mailboxes.") Under Get-MailboxFolderPermission user:\calendar you can also see the delegates setup, and with a SharingPermissionFlags of "Delegate, CanViewPrivateItems" (if set when adding them via the GUI above) but using Set-MailboxFolderPermission or Add-MailboxFolderPermission you can't seem to set those flags. Anyone had any ideas? hooking into EWS perhaps?
Solved
Ben Harris
Feb 14, 2018 Place Exchange
Views
0likes
Comments
AutoMapping Shared Mailbox based on security group
Hi, We were under the impression that once on exch 2016 we would be able to use mail enabled security groups for shared mailboxes -- and (this is the important part) still be able to have the automapping feature work (ie. all members of the security group would see the share mailbox in their outlook profile) Testing has shown this not to be the case, and now I am seeing this: https://technet.microsoft.com/en-us/library/jj919240(v=exchg.160).aspx which is also suggesting that shared mailboxes cannot automap on a security group. Can anyone say for sure one way or the other - is this on the radar to start working eventually? I know people have been talking about this since exch 2010.
Solved
Cody Henschel
Sep 11, 2017 Place Exchange
Views
0likes
Comments
I created an Exchange Online mailbox but it doesn't appear in on-prem EAC. How do I fix?
I discovered this issue because the CRM for Outlook add-in (the modern one, not the full client) complained that a new user was not logging in with the same email address and is Dynamics 365. I couldn't confirm this no matter where I looked so I checked his Office 365 user and, sure enough, his default SMTP address is username@tenant.onmicrosoft.com rather than username@ourdomain.com. I also notice that he doesn't have any of the other standard aliases that other users have. The key difference with him is that he's the first new user I created where I didn't first make an on-prem mailbox and migrate it up. Not knowing any better, I thought, "Why go through that step? I'll just create the mailbox in the cloud." At this point I'm a bit unsure what step to take next. When I look at EAC on-prem I don't see his user there at all. All other users either have a mailbox type of "User" or "Office 365". Should I migrate him to on-prem then back?
Solved
Chris Parker
Apr 24, 2017 Place Exchange
Views
0likes
Comments
Hybrid EXO - The execution of cmdlet Set-SyncMailUser failed
Hello So we have following situation: Hybrid environment Staff member with migrated (remote) mailbox leaves the company license is removed user is moved into a non-sync OU and O365 mailbox is moved into deleted users after the grace period, mailbox is deleted same users comes back in the company few months later (after the grace period of the mailbox) and the same AD account is re-enabled and re-synced with O365 In the on-prem exchange console the same mailbox is showing as : Remote O365 mailbox but in EXO is nothing, no mailbox assigning license returns error: Exchange: The execution of cmdlet Set-SyncMailUser failed..; Exchange: An unknown error has occurred. Refer to correlation ID and if try to perform new-moverequest also returns error: The operation couldn't be performed because object 'returning-staff@abc.xyz' couldn't be found on '........PROD.OUTLOOK.COM'. I checked the Error field via MSOL, but showing nothing, literally empty space Also checked the "msExchHomeServerName" its all clear Not sure what else to look for/change
Solved
Anton5032
Oct 20, 2020 Place Exchange
Views
0likes
Comments
BIMI Logos – Another Way to Stop Email Spoofing
Brand Indicators for Message Identification (BIMI) is a new industry effort to help identify email from reputable companies by displaying their logo alongside email (and potentially other items) in applications. https://office365itpros.com/2018/12/06/bimi-office365/
TonyRedmond
Dec 06, 2018 Place Exchange
Views
8likes
Comments