OMG 2022 and same issue

4 years later same problem. Sad times

That would match only if the disclaimer was already at the very end of the message.

The exception condition is not working that results in adding multiple disclaimer at the end. I have opened the case with Microsoft for this issue and the Microsoft engineer was able to reproduce the same issue and it was assigned to product engineering team now.

The hoops you have to jump through to change a primary SMTP domain in a onprem / Office 365 Hybrid mode for a new domain after the mailboxes have already migrated and all changes must be made on prem but the MX record for that and the prior domain hits a SPAM Cloud, disable archiving on the old domain, send it to 365 and your only option is a Transport Rule to block this domain and reply with a shortest message possible and the customer hoping you are getting the job done and few ways to prove it beyond sending from gmail to an account in the old domain to validate the transport rule is working and getting back a really unprofessional looking email that says this was the domain and now it is this? And that is one example.

Of all the things that must be accomplished to add a domain to an Exchange Organization, with AD and Exchange On-Prem but running in Hybrid-Mode, mailboxes already migrated to the cloud, new UPN, new SMTP alias, domain registration, managed DNS, adding the domain to Office 365, TXT records, SRV records (Skype for Business), then swapping out the existing primary to secondary, taking the secondary of first.last@newdomain.com, and on set date except mail from original primary SMTP domain, don’t deliver it, drop it, respond with a message. I have most of that scripted. That is the easy part. Notice how all of that is just a dependency to get on Exchange Online and use the Transport rule in the first place.

If you want to contribute and fix this… Take a look at this link below. And no, I’m not trying to intentional redirect you here and the site does require you sign up if not mistaken in full disclosure but this is where I’m published and help others. Microsoft is wasting my and the customers time with products like Yammer and Delve and other things that cause mass confusion if you enable them on the E3 license without a full fledged business plan and Transport Rules haven’t changed in years and the most optimal way to deal with certain scenarios and where on-prem you can buy thirdparty products you have lost all control once that migration batch says “Completed successfully”. This is a technology issue, industry wide. I know what I’m doing about it – what are you doing about it?

Me
https://www.linkedin.com/in/vcissgroup

https://www.experts-exchange.com/questions/29019440/New-SMTP-and-old-SMTP-Drop-old-SMTP-but-respond-with-custom-message-to-external-recipient-a-lot-more-Revised.html

Like the article says, that’s the expected behavior.

If you have multiple transport rules that are applying signatures, then yes I would suspect that more than one rule is applying for that sender. You’ll just need to go into your transport rules (aka Mail flow rules) and inspect their conditions, and then look at the sender and try to determine why multiple rules are applying.

HI Paul

I might be not answering your question properly, as I said I am new I am new in th field,

I am told that it is suspected that multiple rules are wrongly applied to this user account, which I need to figure it out,

I think getting a way out to that would be helpful, in short I think I need to be able to view what rules are applied to this specific mailbox as emai are going out.

Please can you guide me how, we are on exchange 2013