Sending, receiving, and organizing email in Outlook.com
It looks ok to me, check first step did you selected "Junk" folder from the folder list?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
For at least two weeks, I've been inundated with spam from the domain gostarmedia.com. I've created the following "solutions" all without success.
Rules
Sender Address Includes "gostarmedia" (without quotes)
Categorize as Spam
Move to Junk Email
Junk Mail
*@gostarmedia.com
gostarmedia.com
It would be really great if Hotmail could stop letting ****clowns like these from getting through if someone enters a valid domain. That or allow more wildcards (e.g. *@*.gostarmedia.com), instead of only allowing it in place of usernames preceding the @.
Today, I searched and deleted 16 out of 18 Junk Mail emails, that had the gostarmedia.com domain in their addresses.
Thanks!
-User since 1995
Sending, receiving, and organizing email in Outlook.com
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
It looks ok to me, check first step did you selected "Junk" folder from the folder list?
Copied from Mohammad, he has laid things out better than I have.
"The message Id should be this expression because they are using a single quote (') after "@" which is causing the flow failed and return error "Id is malformed." It should be
In the dynamic content popup, click on "Expression" tab.
Paste this:
triggerOutputs()?['body/Id']
Click OK (or Update).
Now mine is working 100%"
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more