I would like to automatically put incoming emails which are not from certain domains go to a specific folder in outlook. For example I want any emails that are not from xyz.com and personname#gmail.com to go into a folder outside emails .
I found this link but it is not useful as i dont know the exact domains from where I would get those emails
I have Microsoft office 16
While creating filtering rules, MS Office doesn't provide filtering for NOT conditions. However, this can be achieved by adding exception to the rule. You'll be able to find it after you set the conditions and the actions.
I would suggest to process all messages with an exception of Sender address includes as the domain you want to whitelist (xyz.com). Similarly, you can add more exceptions to this rule.
You can refer to this article.
Related
Found a very similar question here: Email aliases not returned as "To" address in logic app
TLDR: From within a logic app "When a new email arrives" trigger, How do I get the original alias that the email was sent to?
I have a logic app that creates a ticket based off an email sent to an outlook box. Now I want to be able to choose aspects of the ticket based off of whether or not the email was sent to the mailbox itself or an alias of the mailbox. The problem I'm having is that by the time logic apps gets a hold of the email, the alias address has already been replaced with the actual box's address ("alias1#place.com" -> "actualbox#place.com").
The actual mail in the inbox has the original email's alias information in the headers, but I can only get them by looking at the properties in outlook. I've tried to get the original "To" internetheader information both within logic apps (by exporting the email to blob storage and looking at headers there) and with the Microsoft Graph API. Sadly, the email exported by logic apps doesn't have the alias information and Graph API has pretty much every header but "To". At least one other person has lamented the lack of To
That said, the actual email still has the original alias information. Can someone help me get that information in logic apps without jumping through too many hoops? A many hoop solution is welcome if none other can be found though.
Use the Export email (V2) action from the Office 365 Outlook connector. This will give you the full message with original headers (including the actual To address)!
The flow here is, trigger on the incoming email, as you already are, then add the export email action providing the message id from that trigger to pull this specific email.
From there, you you'll have one big "body" property which you'll need to interrogate to find the To address.
Caveat on this though, it doesn't work when emails are sent between mailboxes in the same Office 365 tenant. Exchange Online will "helpfully" go, "I know that address... this is the address you wanted!"
What API are you using? In Outlook Object Model / MAPI / EWS, you need to retrieve the PR_TRANSPORT_MESSAGE_HEADERS MAPI property (DASL name http://schemas.microsoft.com/mapi/proptag/0x007D001F)
We arrived at a many hoop solution.
The "Primary" email box now has some rules that look at the internet headers mentioned above (Message -> Properties -> look for 'To:').
If it finds an alias there, it will put the email in a corresponding folder for each alias.
Then we have logic apps listening to each of the alias folders which will then send the email's information to the _Core logic app that does the actual processing.
I have created a distribution list in exchange that allow certain people from my company to receive emails from a particular email address. An example would be if you send an email to "blank#esi.com" then the people added to the distribution list would also receive it. Now I want to add some modification to this distribution list. If any Subject field of any incoming emails contains the phrase "RT" (without the quotes), send a copy of that email to "blank#tid.com". How can we achieve this?
I am currently using window server 2012 & Exchange 2013
You can use transport rules for this. In the GUI you go to Mail Flow, then Rules. When you add a rule you can select when it applies and what should happen when it does. In your case I would use "if subject or body includes (RT)" then "bcc message to.. (blank#tid.com)"
using the salesforce Email Services can we do means prevent duplicate cases and How please???
I understand your pain. My users often complain that our service email address is included in email conversations and this creates a case for each email received. They then have to spend hours merging the cases and pulling out the relavant material. Worse, they have to manually move email attachments from the duplicate child case to the parent case.
One solution is to purchase an AppExchange application that provides a custom email handler that works well. Look for the Email to Case premium on the AppExchange.
https://sites.secure.force.com/appexchange/listingDetail?listingId=a0N30000001R5cyEAC
Or you can do what I did and build a custom email handler. See my blog for the code which is currently working in our organization:
http://sforcehacks.blogspot.com/2012/01/email-to-case-can-create-too-many-cases.html
So, here's my situation. We have a department that needs the ability to use queues in CRM 4. They also need the ability to reply to e-mails that come to that queue from their department e-mail address. (So that any customer responses will go back to the queue to be handled by agents)
I originally was going to build a JavaScript customization that inserted a checkbox that said "Send From Business Unit". Toggling this would look up their department user based on the e-mail address on the Business Unit. I successfully got this working (as a concept), but found that actually sending triggers the dreaded "CrmCheckPrivilege failed."
Which is good, because that means CRM is actually enforcing security.
So my problem? I have no idea how to replicate this functionality and it's a must have for this customer group. Is there anyway to modify the e-mail after it's already gone through security checks via a plugin? Perhaps a pre-stage send plugin?
I want to be reasonably certain of success before I commit a lot of time to this solution. I'm also open to any other ideas too.
Thanks in advance,
Clif
Well, first, a "CrmPrivilegeCheck failed" can always be fixed by adjusting the user's roles and giving him the appropriate privilege (the privilegeId is always returned in the exception but may not be shown in the particular error dialog you are getting) and level, but this may not be wanted by the department.
A solution we have used is just slightly different from yours: Do not send the mails through another user, but through the queue. Queues can also be eMail senders in MSCRM. The queues should already have the correct eMail addresses set in order to work properly with the eMail router. Set up a way to determine the correct queue (like a field on the systemuser entity or a hardcoded queue name in your JavaScript) and set the from lookup accordingly in your JavaScript. That way the eMails will be sent using the name and address of the queue, so any direct replies will always have that queue as the recipient.
In outlook, the admin can force all users to endure a spell check for each email.
Can Outlook be set to enforce spell check only for emails that are outbound from the company domain, so that "in-house" emails would not be spell-checked, but all emails going out from the domain would be checked?
The setting comes you are seeing probably comes from the standard Outlook group policy which toggles the outlook setting (tools->options->spelling->always check before sending).
Group policies are applied per computer, or per users. Outlook doesn't appear to offer anything in its configuration pages, and there is nothing in the group policy to make that setting depend on the recipient.
I guess, that it may be possible to build some kind of add-on to accomplish this, but the functionality doesn't appear to exist right now.