Forum Widgets
Latest Discussions
How to Delete a Composing Email Attachment via Outlook Add-in?
Context: Server: Exchange Server 2019 on premise Client: OWA Category: Outlook Add-in Office JS API Set: Supported up to 1.5 only Problem Details: Delete an attachment added manually or through EWS API to an email item. Limitations: 1. Limitation of makeEWSRequestAsync() Office JS method: The makeEWSRequestAsync method in Office.js does not support the DeleteAttachment SOAP operation, which is required from outlook add in. -> Attempted Workaround - Using fetch with EWS SOAP Request: I tried invoking the DeleteAttachment operation via a fetch call to the EWS endpoint. However, EWS response states "requested web method is not allowed for this application". 2. OWA Limitation: As OWA in this environment only supports Office.js up to version 1.5, the modern attachment Office JS APIs and Graph APIs are not an option. Question: In an Exchange On-Premises scenario, how can I programmatically delete attachments via my add-in? Specifically, is there a recommended approach to obtain a valid token for EWS requests, or any supported alternative to perform DeleteAttachment? Any way to convert EWS attachment ID to Office JS attachment UUID? Additional Notes: I am aware that Exchange Online supports more modern APIs (Graph/REST), but my current deployment is strictly Exchange On-Premises. The add-in works well for reading attachments and other operations, except for deletion. Any guidance or recommendations would be highly appreciated! Thank you in advance.
Exchange Hybrid sending external email from on-premises
I have an Exchange 2019 server setup as our hybrid server. Mail flow works fine to any mailboxes moved to Exchange Online, inbound from the Internet is delivered successfully to on-premises mailboxes. Where we're having trouble is trying to send email to the Internet from an on-premises mailbox. My preference is to route all email through Exchange Online, so in addition to the Send connector the Hybrid wizard created, I created a second connector using the * SMTP space and sending to our smarthost, aka the record in the MX value from Exchange Online. I also gave this connector a cost of 2 so it still uses the default send for email going to our tenant. Any email that isn't going to our tenant, so domain.mail.onmicrosoft.com, is immediately rejected with the error "Remote Server returned '550 5.7.64 TenantAttribution; Relay Access Denied [ValidationStatus of 'CN=SERVER' is UntrustedRoot]" The Exchange Online connector from our Org to O365 is set to use subject name of certificate, .ourdomain.com. I even tried setting it to the external IP the emails would come from and that failed as well. One thing I noticed in the send log, the subject name of the cert is mail.ourdomain.com, not *.ourdomain.com as shown in the example from this URL. So, I even tried updating the EXO connector to look for the subject name mail.ourdomain.com and still no luck. 550 5.7.64 TenantAttribution when users send mails externally - Exchange | Microsoft Learn I also tried the steps here. NDR error 550 5.7.64 TenantAttribution when sending emails through EOP - Exchange | Microsoft Learn What could I be missing?
How to get token to fire ews soap request using fetch in exchange onprem setup?
I am currently developing an Outlook add-in for an Exchange On-Premises environment and have encountered a limitation with attachment management, specifically around deleting attachments. Context: Environment: Exchange On-Premises (On-Prem) Target: Outlook Web App (OWA) Office.js Version Supported: <= 1.5 (limited feature set) Problem Details: Limitation of makeEWSRequestAsync: The makeEWSRequestAsync method in Office.js does not support the DeleteAttachment SOAP operation, which is required for my scenario. Attempted Workaround - Using fetch with EWS SOAP Request: I tried invoking the DeleteAttachment operation manually via a fetch call to the EWS endpoint. However, this requires a valid authentication token. The challenge is: I am unable to retrieve a valid token from Office.js in the Exchange On-Premises setup. Methods like Office.context.mailbox.getCallbackTokenAsync do not seem to provide usable tokens for this purpose. OWA Limitation: As OWA in this environment only supports Office.js up to version 1.5, the modern attachment APIs and Graph APIs are not an option. Question: In an Exchange On-Premises scenario, how can I programmatically delete attachments via my add-in? Specifically, is there a recommended approach to obtain a valid token for EWS requests, or any supported alternative to perform DeleteAttachment? If direct deletion is not supported in this environment, are there known workarounds or roadmap plans for better attachment handling in on-premises setups? Additional Notes: I am aware that Exchange Online supports more modern APIs (Graph/REST), but my current deployment is strictly Exchange On-Premises. The add-in works well for reading attachments and other operations, except for deletion. Any guidance or recommendations would be highly appreciated! Thank you in advance.Cross forest Distribution Group list expansion
We have two forests in a 2-way trust. On each forest there's an Exchange 2016 Organization installed. On one forest a Distribution group has been created with users from both the forests, in ADUC we see the membership correctly for all the users. On the Exchange Console of that Forest opening the DG we can see only the "local" users and the SID for the remote one. Sending an email to the DG it only delivers to local forest's users. Why Exchange Server doesn't expand the DG membership as the ADUC does and deliver emails to all recipient ? Do we have to replicate remote Forest's Users as local contacts ? thanks
HCW fails to download
Erst einmal Entschuldige mich mich falls ich diese Frage im falschen Kanal stelle Hallo versuche gerade mit dem "Programm" Microsoft.Online.CSE.Hybrid.Client.application die HYbrid Stellung zu realisieren komme aber nicht weiter . Das Programm startet einwandfrei. Die Datei Microsoft.Online.CSE.Hybrid.Client.exe.manifest wird aber nicht heruntergeladen In der Firewall kann ich keinen Blockierten traffic sehen. Meldung die Anwendung konnte nicht dedownloaded werden. Erforderliche Dateien fehlen in der Anwendung. Wenden Sie sich an den Hersteller der Anwendung OS Server 2012R2 Software Firewall ist aus Kein Antivirenprogramm aktiv Falls jemand ähnliche Probleme hatte und die lösen konnte wäre ich sehr dankbar über Hinweise wie das geschafft wurde. Der Support von Microsoft war nicht sehr hilfreich Ticket ist aber noch offen. Die Aktivierung von C:\HCW\Microsoft.Online.CSE.Hybrid.Client.application führte zu einer Ausnahme. Folgende Fehlermeldungen wurden entdeckt: + 'file:///C:/HCW/Application Files/Microsoft.Online.CSE.Hybrid.Client_17_1_2714_0/Microsoft.Online.CSE.Hybrid.Client.exe.manifest' konnte nicht gedownloadet werden. + Ein Teil des Pfades "C:\HCW\Application Files\Microsoft.Online.CSE.Hybrid.Client_17_1_2714_0\Microsoft.Online.CSE.Hybrid.Client.exe.manifest" konnte nicht gefunden werden.
"Exchange Delegation Federation certificate is expired", is it needed?
On our Exchange OnPrem-server (2019) we have a Self Signed Exchange Delegation Federation with certificate but it expired recently. We run Exchange OnPrem in Hybrid with Exchange Online, there are currently no more mailboxes present on our OnPrem ExchangeServer. I have found an instruction on how to renew it. But it also states that if it is already expired, the current federation must be removed and a new one must be created. However, those instructions apply to Exchange 2013 and the commands are not available in 2019 https://learn.microsoft.com/en-us/exchange/renew-the-federation-certificate-exchange-2013-help Another forum-post somewhere states that for Exchange 2019 you need to run the Hybrid Configuration Wizard. We have run that multiple times already. For example, after upgrading our previouse Exchange 2016 to Exchange 2019 and after migrating the Exchange 2019 to a new server. If we look at the Exchange Delegation Federation via powershell, we only see our older domains present in that federation. Via the Hybrid Configuration Wizard, our current domains are present. This raises a question to us, do we need the Exchange Delegation Federation? Can we safely remove this from our exchange server ( Remove-FederatedDomain, (multiple) & Remove-FederationTrust) via the commands , run the Hybrid Configuration Wizard once more. Will this be sufficient?Reject multiple From addresses (P2 From headers) without a Sender header
We are proactively opting tenants out of the rollout that were detected as sending high volumes of emails exhibiting multiple From addresses without a Sender address header. These exempted senders will only be able to send emails exhibiting multiple From addresses without a Sender address header to recipients belonging to the same tenant as the sender. We will provide a subsequent update by the end of May 2025 (previously end of March) with an updated timeline for tenants that are opted out. The originator fields of a message consist of the from field, the sender field (when applicable), and optionally the reply-to field. The from field consists of the field name "From" and a comma-separated list of one or more mailbox specifications. If the from field contains more than one mailbox specification in the mailbox-list, then the sender field, containing the field name "Sender" and a single mailbox specification, MUST appear in the message. In either case, an optional reply-to field MAY also be included, which contains the field name "Reply-To" and a comma-separated list of one or more addresses. from = "From:" mailbox-list CRLF sender = "Sender:" mailbox CRLF reply-to = "Reply-To:" address-list CRLF The originator fields indicate the mailbox(es) of the source of the message. The "From:" field specifies the author(s) of the message, that is, the mailbox(es) of the person(s) or system(s) responsible for the writing of the message. The "Sender:" field specifies the mailbox of the agent responsible for the actual transmission of the message. RFC 5322 https://www.rfc-editor.org/rfc/rfc5322#section-3.6.2 General Availability (Worldwide, GCC): We will begin rolling out April 15, 2025, and expect to complete by May 15, 2025. GCC High, DOD: We will begin rolling out July 1, 2025, and expect to complete by August 1, 2025. If email clients including devices and applications that you use to send messages, do so using multiple From addresses but without a Sender address header after the change starts rolling out to your environment, you will get an NDR error code 550 5.1.20 “Multiple From addresses are not allowed without Sender address."Updating Email Addresses After Removing Domains from a Microsoft 365 Tenant
Microsoft 365 makes it easy to remove domains. However, if you remove a domain and don’t adjust email proxy addresses, some fix-up might be needed to make sure that mail-enabled objects don’t have primary SMTP addresses or proxy addresses that use the removed domains. This article explains how to fix up mail-enabled objects with PowerShell to remove traces of any removed domains. https://office365itpros.com/2025/03/19/remove-domain-adjust-addresses/
Exchange Server 2019 and Outlook Mobile App Andriod
Hello, We have exchange server 2019 on premises server with windows server 2019 AD. I have a strange problem, when configuring outlook on Andrion/ios app the account repeatedly ask for the password even though the password is correct. If I use another email client like Edison or Gmail client the accounts works very well. The problem is only with the outlook mobile application, any help will be appreciated. Thanks Syed
