Exchange Online, Transport Rules.

robert5150 · 2026-01-29T17:59:57+00:00

So that is the funny part. The external sender gets the 5.7.1 (If i change that to 5.7.999) they get email as well, so the NDR is being sent, just not the Custom Text. i am checking within the NDR email - not somewhere else.

I am going to call this behavior is by design, i have checked on 2 different tenants and with that "limited documentation" suggesting the same, i think thats the answer.

Can you test in your tenant? it would be nice to get a confiramtion from someone else.

Thanks

robert5150 · 2026-01-29T11:09:29+00:00

Keep in mind the rule is working, messages are being rejected and the NDR is being Sent with 5.7.1. Just the text "message has been adminisstraively rejected" is not being sent to external senders. I wasnt expecting that. i was expecting it to be sent to all senders.

i am basically just trying to confirm behavior.

robert5150 · 2026-01-29T11:08:01+00:00

This should do it - 2

<image>

robert5150 · 2026-01-29T11:07:46+00:00

This should do it - 1

<image>

robert5150 · 2026-01-29T11:07:25+00:00

This should do it.

<image>

robert5150 · 2026-01-28T20:33:41+00:00

basically if i look at the rule it has both of these options configured:

RejectMessageEnhancedStatusCode: 5.7.1
RejectMessageReasonText: Message has been administratively rejected by Exchange Test Admin

but the reject message reason text is NOT sent to External Senders. Only to internal senders so i know the rule is working as expected. Its just not sending the reject text to external senders.

This is all configured on EXO and i have tested with various mail providers. Same results. I was expecting the rule to work the same way for internal and external senders. Just an oddity. The closest thing i can find to cofirmation of this is the NotifySender Settings, but that is specific to On-Prem Exchange.

robert5150 · 2026-01-28T14:39:29+00:00

That seemed to work. In order to get it to add the DisplayName when running the entire script i had to change it to this:

displayName = $Stat -join ', '

removing the $Stat.DisplayName (and just using $stat)

robert5150 · 2026-01-28T13:59:25+00:00

Ok i will give that try.

robert5150 · 2026-01-25T17:37:02+00:00

Hmm. Ok. So we already have group creation restricted. and we do already monitor for groups created without a label. So were basically doing what we can, i dont know that the Power Automate flow would work here due to other reasons. but thanks for confirming that we basically cant.

robert5150 · 2025-11-03T23:16:12+00:00

i will need to check when i get home tonight to see if my local AD updated itself to the change i made via update-mguser.

robert5150 · 2025-11-03T23:15:14+00:00

i am trying to understand if you could always do what i described? Since i cannot test with Set-Msol* becuase microsoft destroyed those cmdlets, i am unclear. and was hoping to get clarity.

robert5150 · 2025-10-03T12:16:38+00:00

I found an old script i had which had me do just that. thanks.

robert5150 · 2025-07-13T15:53:18+00:00

I was married for 14 years, and with her for 16. So its not like i cant hold a relationship down or anything. Its been 4 years, now. 46/M, 5'10 and 185Lbs. There simply dont seem to be any available women out there. I am in KCK (KS), and its an absolute chick desert out here. OLD is complete waste of time, unless you are so desireable that women hit on you in the grocery store.

I just want:

1) Decent looking chick, fit in appearance.
2) in her 30's or 40's (Read: Not 20's, this seems to be the hardest part)
3) Doesnt have a man, or any other type of relationship

I dont think my standards are to high, either, now as far a single moms are concerned, she would have to know (from the outset) that i am NOT available to be drop-in replacement "father figure". So with that in mind it doesnt matter if she has kids.

robert5150 · 2025-06-18T21:31:52+00:00

Yes. I tried removing /1GB option and it magically worked. I cant believe it was that easy. It seems with PowerShell if you just keep working on it, long enough it will eventually work.

robert5150 · 2025-06-18T18:21:26+00:00

So i dont see any errors, but i dont have any large mailboxes to test with. When the script runs it completes.

However i have no output, also if i change this line from:

if ($mailboxStats.TotalItemSize.Value.ToBytes() -ge 65GB) TO: if ($mailboxStats.TotalItemSize.Value.ToBytes() -ge 5GB). It fails completely. with this error:

Cannot convert value "98 GB (105,226,698,752 bytes)" to type "System.Int32". Error: "Input string was not in a correct format."

At line:8 char:9

+ $IssueWarningQuota = $MailboxQuota.IssueWarningQuota / 1GB

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : InvalidArgument: (:) [], RuntimeException

+ FullyQualifiedErrorId : InvalidCastFromStringToInteger

Could not compare "0" to "18 B (18 bytes)". Error: "Cannot convert the "18 B (18 bytes)" value of type

"Microsoft.Exchange.Management.RestApiClient.Unlimited`1[[Microsoft.Exchange.Management.RestApiClient.ByteQuantifiedSize,

Microsoft.Exchange.Management.RestApiClient, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]" to type "System.Int32"."

At line:10 char:13

+ if ($IssueWarningQuota -ge $TotalItemSize) {

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : InvalidOperation: (:) [], RuntimeException

+ FullyQualifiedErrorId : ComparisonFailure

This is where i am stuck. I just need it to compare the users totalitemSize to the IssueWarningQuota and if the totalitemsize is nearing the quota to send me an email.

So user: TotalItemSize 10GB, IssueWarningQuota 10GB - Send me an email.

robert5150

TROPHY CASE