@dbeato said in Substantial OnPremise Exchange Vulnerabilities announced yesterday Patch Immediately:

@DustinB3403 Yeah, Exchange 2013 and over. You have to also be on the last 2 Cumulative Updates from Exchange 2013, 2016 or 2019. For 2019 You only can get the updates through Microsoft Volume Licensing.

Yeah, a customer attempted an update from 2016 CU15.1 to CU19, it errored out on the last step, they restored (bad move) and had some mail flow issues for a bit.

But they are back online now

@black3dynamite that will work. I'll report back on Monday when I get the user on the phone.

@Dashrender said in Managing Distribution Groups in an Exchange Hybrid Environment:

@EddieJennings said in Managing Distribution Groups in an Exchange Hybrid Environment:

I ought to have clarified. DUO MFA comes into play with Outlook for our mailboxes that are in Exchange Online. On-prem mailboxes (the few we have left aren't subject to DUO).

Are those that are left on prem - are they actual users? If so, I'm curious why they can't be migrated?

Eventually all users will be migrated, so, yes, we still have real users on-prem.

This is outside the scope of the original question / scenario, but I've learned a good bit during this process with much of that learning validating a few things I already knew, such as the value of taking the necessary time to plan, and prep the environment for migration (removing unnecessary objects, etc.).

Looks like @Osvaldo was able to get it.

@dbeato said in 550 5.0.350 Remote server returned an error:

@WLS-ITGuy said in 550 5.0.350 Remote server returned an error:

@dbeato said in 550 5.0.350 Remote server returned an error:

@WLS-ITGuy said in 550 5.0.350 Remote server returned an error:

571 Delivery not authorized, message refused

That messages means a lot of things but yeah Whitelist on their Spam Filter end, Adding your IP to your SPF record, check if there is anything on the body of the message triggering the block on their end (i.e. URL or site link).

It is Office 365 with Exchange - I have created all the records that Microsoft wanted me to.

So, just to be clear, this is 100% not on my end, correct?

It shouldn't be on your end, the message is coming from the recipient's end server.

Right, which means that they received it.

can we get some tags added to this?

o365
scan2email
receiveconnector

@JaredBusch said in Email server options:

@Dashrender said in Email server options:

This comparison misses taking it beyond year 5.

Why take it beyond 5 years? Because if it is on premises, it will need to be upgraded again.

@Dashrender said in Email server options:

If you add SA to the original licenses - because you know the plan is the keep using Exchange going forward - it will raise the costs noticeably in the beginning, but come renewal time it will make it significantly less. Less enough to be under O365? not likely, hell, even the 5 year plan would be more expensive for onprem vs O365... but it might lower itself over time because of the SA difference.

SA is a scam to get more money. Always has been for the SMB. With negotiated pricing for Enterprise, it is the right thing.

If you're a company that only upgrades once every 10 years - then yeah... SA is a waste of money, but you're already talking about upgrading again in 5 years, so SA could very much make financial sense - show me the numbers before you poo poo it.

@jt1001001 said in Exchange auto mapped account removal.:

Umm..Where was this like 2 weeks ago when I needed it? Thanks!!!

Hiding in the 3rd page of Google results, that's where!

@dbeato said in Office 365 Moving Emails to Deleted Items:

@dafyre said in Office 365 Moving Emails to Deleted Items:

@dbeato said in Office 365 Moving Emails to Deleted Items:

@dafyre said in Office 365 Moving Emails to Deleted Items:

e got a strange one... I have a user here whose Emails go from whatever folder they are in to the Deleted Items folder after being read... Sometimes. Sometimes it doesn't happen for several minutes, and other times it happens right away.
The user hasn't been phished that we can tell. No bogus rules in Outlook forwarding things to the deleted items. Check both Web and Outlook 2016.
What am I not looking at that could be causing this?

They got hacked though
https://blogs.technet.microsoft.com/office365security/how-to-fix-a-compromised-hacked-microsoft-office-365-account/
https://docs.microsoft.com/en-us/office365/securitycompliance/responding-to-a-compromised-email-account

Sometimes the rule is a dot on the name....

I am assuming it's a hacked account, but we changed the password to a new one. I disconnected all of her sessions from Office 365.

Still happening. I see no rules with a dot in the name... or spaces or foreign characters. I see exactly the number of rules on my CLI as I do in Outlook and OWA.

Can you clear them all ? Take a screenshot of the settings and then remove them and see what changes. The rules run autonomously and is not someone running them.

That's what we've done now. All of the rules are disabled. End-user is turning them back on one at a time now.

@scottalanmiller said in Microsoft BCL or Bulk Complaint Level Values for Email:

Some sources call this an SCL or Spam Complaint Level.

Emails into O365 have both BCL and SCL.

I have a script that I wrote to do this.

https://gitlab.com/dafyre/powershell-utils/raw/master/export-O365Group.ps1

It gets you the person's DisplayName and their email address.

If you're exporting a Distribution List, just add the -distributionlist switch.

If you're exporting an Office 365 Group (Unified Group), then leave that switch out. Other parameters should be self explanatory.

Does the message trace in Exchange tell you anything? I know that when I had on-prem exchange and barracuda, I had weird issues where the attachment size restrictions being smaller/more restrictive on the Exchange server exhibited this behavior. The barracuda delivered, but Exchange rejected due to policy.

@JasGot said in Exchange connectors:

I need some help sorting out the exchange connectors on a server.

We were called in to figure out a spam problem. It's not severe and during our exam, we are trying to check the configuration of Exchange and get mail test tools to be happy.

Right now we are getting: Reverse DNS does not match SMTP Banner from mxtoolbox.

This is a simple MS Exchange setup; One Exchange server on a domain, people connecting with MS outlook from inside the building on the domain and from outside the building using Ms Outlook, and two copiers that can send e-mail.

The issue is all the receive connectors. It's not clear to me which one mxtoolbox is seeing.

They are:
Client Frontend EXCHANGE
Client Proxy EXCHANGE
Default EXCHANGE
Default Frontend EXCHANGE
Outbound Proxy Frontend EXCHANGE
Scan2EMail

I'd like to know what each one represents. ie; I presume Frontend mean Internet facing, but I'm not sure. Also, do internal MS Outlook users connect to a receive or send connector? (or both?)

Thanks.

You should change the ELHO name on all of them so it matches your external URL (Which in turn needs to match your Reverse DNS name).

The Outlook clients connect to the Exchange server and Exchange sends the emails they do not connect to the connectors.

Added tags.

@dbeato said in Exchange / Office 365 Auto Response from Public Folder:

@scottalanmiller said in Exchange / Office 365 Auto Response from Public Folder:

@travisdh1 said in Exchange / Office 365 Auto Response from Public Folder:

@scottalanmiller said in Exchange / Office 365 Auto Response from Public Folder:

We have a public folder on Office 365 that is email enabled, the customer would like an auto-response from the public folder. I'm not sure if that is even possible.

Wouldn't that be an auto-response setup from one of the accounts that receives those emails?

Does that work with a public folder?

Yes, with Folder Assistant through Outlook. Otherwise you can create a rule for incoming emails through Office 365 to accomplish that too.

Yeah, seems... poor. Found this for doing it through Outlook, which would be unreliable and clearly not useful.

https://www.codetwo.com/admins-blog/setting-public-folder-auto-reply/

@mrwright4hire said in Mail stuck in Office 365, Enterprise Exchange queue!:

@dbeato said in Mail stuck in Office 365, Enterprise Exchange queue!:

@mrwright4hire said in Mail stuck in Office 365, Enterprise Exchange queue!:

A few users are having issues sending out emails. Not everytime, but intermittent. Has anyone experienced this type of issue before? I can use all the help I can get. I would like to know how to release the emails and avoid emails getting stuck again.

In advanced, thank you for your efforts.

Have any of your users been not able to send at all? I am not seeing that right now.

Great question dbeato! Here's the thing, I myself tried to email the same address while monitoring it from Barracuda. Nothing showed up as going out. It's strange cause we received email from the address.

So it is on the received end of Barracuda?

@dustinb3403 said in How Do You Stop Office 365 Low Severity Alert Emails:

As a general thought on this, automatic mail forwarding could be a compliance issue, so make sure to keep this in mind before you go turning off alerts that might be a compliance issue later on. . .

Automatic mail forwarding is a "every few hours" task. So these alerts are a ridiculous amount of crying wolf. It's created a "zero belief" system in MS alerts. At this point, there are no alerts, just spam, is how it is seen.