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)"
Related
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.
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.
we've got a Exchange 2013 postbox with several E-Mail addresses assigned.
For better organization, Exchange should move incoming mail into various folders.
The target-folder depends on the SMTP-Address to which the mail was sent to.
Problem is: Exchange 2013 recognizes only the postbox itself as receipient and does not distinct between the different TO-addresses. How can a serverside-rule be made which respects TO?
Thanks for help!
Moving messages to a folder is a mailbox server side rule. You could log into the mailbox via OWA or Outlook and set up this rule.
Exchange will deliver mail to the recipient, its upto the recipient via rules what they want to do with it from there.
Is there a way to setup Outlook 2010 to run a script or some other form of sanity-check when you attempt to SEND messages from the client? My specific situation is that I use the same outlook client for multiple accounts (work, gmail, VPS server, etc) and I've found myself a couple of times sending emails "from" the wrong account.
In a perfect world I'd want to be able to write a script with logic something like the following:
when (I hit send)
if (the "source" account is "myuserid#gmail.com") then
if (there are addresses in TO or CC that match "work.com") then
pop up a dialog box that says:
"You appear to be sending email to work.com from gmail.com - do you really want to do this?"
if yes, then send it and return
if no, go back to the message compose window
that way, I'd have to actually very intentionally use a non-work email address to send email to the work people (which is rare in my particular case)
Try SendUsingAccount to read the "source" account in ItemSend.
I want to send an email automatically when I assigned a task to a person in team foundation server.
how can i do?
Either setup an alert for every single person in your team. It is not possible to use a field in the work item to define the recipient of the e-mail. It is not possible to use a smtp server that needs authorization.
Another option is to create your own action to send the email