That's not to say that ITSPs that aren't VARs never recommend it. We do recommend O365 from time to time, but it's just one of many solutions. Are up to 400% the cost of Zoho, which is arguable a nicer platform anyway, it can be hard to justify. We have customers who want enterprise, hosted email, but are moving off of the O365/GSuite family because it just doesn't make sense for them. As the cost of hosting has come down, the email providers aren't lowering cost (not the big two, anyway) making them priced more and more out of the market.

@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.

@matteo-nunziati said in Outlook 2016 Export to PST Missing a Lot of Data: @scottalanmiller said in Outlook 2016 Export to PST Missing a Lot of Data: @obsolesce said in Outlook 2016 Export to PST Missing a Lot of Data: You can right-click on the mailbox, or a folder, and in properties, you can see how much data is there versus on the Exchange server. Most is there, for sure. But definitely not "all". Confirm. I got always this end result. This is just best effort. Not complete at all. That's just crappy, especially as Microsoft themselves recommend it.

@coliver said in Receipt Logs for Office 365 Emails: @momurda said in Receipt Logs for Office 365 Emails: @coliver This is done whenever MS feels like it, yes? I mean, you may not get the results for a while. Nope it's done whenever you submit the search. It's stupid powerful. I do one at least once a week and never have had to wait more then a few minutes. Yep, that’s my experience as well.

You can use Powershell as well Set-MailboxAutoReplyConfiguration -Identity username -AutoReplyState disabled

@jaredbusch said in Does Office 365 Support Plus Notation in Email (+): @scottalanmiller said in Does Office 365 Support Plus Notation in Email (+): @kelly said in Does Office 365 Support Plus Notation in Email (+): The period notation is really annoying for me. I signed up [email protected] when it was in beta and this "feature" wasn't publicized. Years later someone else was able to register [email protected] and now I get DoTerra order details and the like. I have no idea what I don't get at this point. Don't know about a period notation feature. What does that do? And how do that not break email globally? The same way that + doesn't break it. It is outside of the RFC altogether. So as long as wtf ever service you sign up for lets you type it, then you can do it. As for what it does. Well [email protected] is a common thing. But someone that signs up to gmail with [email protected] can also receive email from email sent to [email protected] or even [email protected] Google simply ignore all periods on the left of the @ for gmail based email addresses. Gmail only, not GSuite. Wow, that's.... weird. I guess it works until they do something like the story above and screw it up.

@obsolesce said in Standard Email Signatures in Office 365 with Embedded Images: @pete-s you need to fix that... Done.

This would work on prem exchange. Probably works with a tweak for o365. Get-mailbox | get-inboxrule | remove-inboxrule

@aaronstuder : After several minute delays between their replies, they'll eventually give you a phone number to call instead...

@scottalanmiller Perhaps they did at one time, but selected the option to not show it again.

I have seen this before and it is usually with IE or Edge and can login on Chrome or Mozilla Firefox. I also try to clear all the user sessions via powershell.

A bit outside your specific question; however on my Exchange servers I just disabled the MSExchange ActiveDirectory Topology Service; doing that prevented the rest of the Exchange services from loading and KB40720650 loaded without issue

I wouldn't like to see the end of 365, but I would always like to see good competition to Microsoft, a leopard never changes its spots in my eyes and Microsoft have history with all the previous court cases in some of their dodgy practices and monopolisation..they slagged off Linux to high heaven in the older days and now their embracing it? Might be something to do with Microsoft using it as part of their azure backend. You can't doubt they make some excellent products but they have always ripped people off and most of their licencing models are complete shit...I think in a few years people will be moaning to high hell once all their subscription models have been increased through the roof and Microsoft know you won't go over to Google now as their Google apps/g suite has been left in the dust. Microsoft are far from a perfect company and it does iritate me when people di*k ride and never see any fault with them and a lot and most are Linux haters I find as well...

These are the kind of things you think someone would catch. Not like it's some random 3rd party app on some 3rd party OS on some 3rd party host.

Outlook for the win.. Thanks

@scottalanmiller said in List All Public Folders in Exchange or Office 365 with PowerShell: Want to get a list of all of the public folders on your Exchange system, whether on premises or hosted, try this: Get-PublicFolder -Identity "\" -Recurse | Get-PublicFolderClientPermission | where{$_.Accessrights -eq "owner"} More on Get-PublicFolder from TechNet That's pretty cool. I was wondering why you were piping into every owner since you could create public folders in Exchange without delegating owners, but then I had remembered you can create them on the client side as well after a root or folders are created in Exchange and added to the client, which is explained in your first pipe. Thanks for the note.

@momurda FYI I would have selected your post as the answer, but the NodeBB plugin doesn't let you do that.

As the others have asked.... Outlook can use anything. It is often associated with Exchange, but there is no specific connection. Zimbra, GoDaddy, anything could be the email that Outlook is showing you. And your question is about the email server, not Outlook. So knowing that someone has connected with Outlook doesn't give us any starting point.

Just setup Veeam Backup for Office 365 and going to give it a test to try and avoid this scenario.

At least you found a (somewhat) viable workaround.

Everything detailed it here: https://products.office.com/en-us/exchange/microsoft-exchange-server-licensing-licensing-overview