Exchange RFC 6710, RFC 6758 and RFC 4021 compliance
I need to verify whether Exchange Online supports the following SMTP extension RFCs: RFC 6710 - Simple Mail Transfer Protocol Extension for Message Transfer Priorities (MT-PRIORITY) RFC 6758 - Tunneling Plaintext Authentication Credentials Using TLS (CRAM) RFC 4021 - Registration of Mail and MIME Header Field Names Specifically, I need to know: Are these RFCs implemented and advertised in the Exchange Online SMTP EHLO response? Is there official Microsoft documentation that lists the complete set of supported SMTP extensions for Exchange Online? If these RFCs are not supported, is there a published list of unsupported RFCs or a roadmap for future implementation? Context: I'm integrating third-party mail systems that require RFC 6710 (MT-PRIORITY) support for priority message handling. Currently, Microsoft documentation only references RFCs 3030, 2920, 6698, and 8461 as supported extensions, but there is no comprehensive list of unsupported RFCs. Any clarification or documentation would be greatly appreciated.
Stop ASP.NET SMTP Emails from Appearing in Office 365 Sent Items Without Affecting Manual Sends
We are sending Emails to our clients through an ASP.NET application using the SMTP protocol and using an O365 Account (email address removed for privacy reasons). The problem is that every time a mail (reset password, otp, campaigns, etc) is sent from asp.net application, a copy of that mail is created in the "Sent Items" of the Support mailbox. This is not needed and it is quickly filling our Support mailbox. How to stop this? Is there any setting in the Exchange Server? Please note that the Support mailbox is also used by our company support representative to send resolutions to customers using O365 Outlook Web Access. The mails send by the representative are very much needed in the sent items. It's only the ASP.NET-sent mails that we want to prevent in the "Sent Items".
Sending emails using python SMTP from gmail to outlook being blocked
I am trying to send emails from my domains mailbox which is google based but it is being blocked with the following error: 450 4.7.26 Service does not accept messages sent over IPv6 [2607:f8b0:4864:20::f2e] unless they pass either SPF or DKIM validation (signature failure). Emails being sent to outlook if they are received are frequently ending up in the junk folder. I have a paid service so all users receiving emails from my platform are expecting these emails and I'm almost only having this issue with outlook, is there anything i can do from my end so that outlook stops flagging my emails to my customers?
Do final user accounts need office 365 licences to use SMTP server?
Hi, I have an app on Azure AD that requires this scope: https://outlook.office.com/SMTP.SendAsApp from office 365 exchange online API. to access SMTP server, as per documentation (https://learn.microsoft.com/es-es/exchange/client-developer/legacy-protocols/how-to-authenticate-an-imap-pop-smtp-application-by-using-oauth#authenticate-connection-requests). Will my final users account need to have this API licenced?
Exchange 2016 User Mailboxes Migrated to Exchange 2019 | IMAP | SMTP Permission
We have migrated from Exchange 2016 to Exchange 2019 Servers. Exchange 2016 servers have been shutdown now. When I initially setup a new servers, i created a new user and mailbox for each server. Problem: When we configure IMAP Profile in Thunderbird client (windows/Linux) the below happens: 1) new users on new servers - works fine 2) old users who were migrated from 2016 - the issue pops up when sending the email. receiving works fine. The error message is as shown
Receive Connector Parameters for Ubuntu Postfix
Hello, first of all, please excuse me if my wording is off - I usually have nothing to do with Exchange and Servers in general and never have. We are sending mail from a linux server to a recieve connector via postfix. While sending a larger amount of emails at once (lets say 50 different mails to 50 different adresses at once), we regulary get an error and after a few emails the sending process stops. I looked at the settings of our recieve conncetor and noted the following settings, that may be the source of this problem: MaxInboundConnectionPerSource: 20 MaxInboundConnectionPercentagePerSource: 2 So the questions are: 1. Does Postfix establish multiple Connections at once? If so, would our recieve connector stop recieving mails if Postfix establishes more than 20 connections? 2. If at a single time, only this one system sends mails, thus the Connection Percentage of this one source is at 100%, would our connector stop recieving? Thanks in advance and sorry for the unprofessional language.
Flow - Email To Address Display Name
Steps to reproduce the Issue: Create an email pbidistro@domain.com Set the name on the email as "PBI Distro" From Flow send email using SMTP or Gmail action. Receive email with Display Name as pbidistro In SMTP action, we have also tried the following in From field: "PBI Distro <PBIDistro@domain.com>" "PBI Distro (PBIDistro@domain.com)" So, is there a way to edit "Display Name" while sending an email through flow? We want to make sure the email's "Display Name" looks pretty when user receives the email.
