Can i used actionable messages in Outlook for my internal LOB workflows?
I want it enabled only for my Office 365 organization
You can definitely use Actionable Messages (AM) for your internal LOB. The platform has capability of enabling actionable messages for a given organization.
Please fill up some details in the registration form on the developer dashboard link given in our documentation and we will follow up with you further.
https://learn.microsoft.com/en-us/outlook/actionable-messages/actionable-email-dev-dashboard
Regards,
Vasant
Yes, you can use actionable messages for your line of business workflows. Ensure that your action target URLs are internet reachable. As a developer you would have access to send actionable messages to yourself. To be able to send actionable messages to others you would have to register your email sender domain and action targets in the Actionable Messages Developer dashboard (in your case with the scope 'My Organization').
Actionable Messages Developer Dashboard
Documentation: Register your service
Related
I'm working on connecting Cloud Error Reporting to an on request Cloud Function (to eventually liaise with the JIRA API).
I have been able to successfully receive Monitoring Notification Channels' test notification to the webhook, however events triggering the email notification channel do not also trigger the webhook.
Is there a way to dispatch on error reporting event to a web URL or pubsub job with error_group attached?
Upon checking on a documentation regarding managing notification channels. Webhooks isn't supported by error reporting, as of now you can select 2 types of notification channels: email and mobile.
There's an ongoing feature request for Webhooks to be added in error reporting notification channel, but there's no ETA when this feature be rolled out . Please star and comment if you wanted the feature to be implemented in the future.
I'm planning to write a web service to automate some task for my Outlook.com email account. I want Outlook.com to send an HTTP request to my endpoint when an email arrives, so that I don't need to poll the server. Does Outlook.com provide such functionality?
That API has been deprecated.
You must use: microsoft graph
Outlook provides webhooks via what they call push notifications. You'll find details on this API in the Outlook Push Notifications REST API reference. The capability exists to receive events for a wide variety of resources, including email messages in Outlook.com.
You might also find some useful capabilities for notification of changes to messages with Use the Microsoft Graph API to get change notifications and Keeping messages and mail folders up to date in apps.
I hope someone will be able to help me with this since I am new with AWS stuff.
I have a Web App using .NET MVC which will be deployed/hosted in AWS. This is the description of what I would like to achieve:
1- Let's say that the Web App will insert products in a Products Table on SQL Server.
2- When this product is inserted, the system (AWS) will send an email to a Client from a Clients Table on SQL Server.
Is that possible with AWS?
Could I set a trigger in SQL Server and send an email by SES?
Is it better to use SQS?. So the Web App will publish messages in SQS, and then having another app listening and sending those emails, for instance a console app.
I will appreciate any direction or useful link.
Thanks all of you in advance.
The answer to your first question is 'yes'. Yes SQL server can use SES to send emails. Because SQL server can send emails, all you need to do is set it up to use the correct SMTP settings from SES once your account is verified and working with SES.
That said, I would never have my db server send emails, just doesn't seem like the right place to do it; even though you can.
I have developed and support several systems like this, and the usual pattern I use is to have the web application insert a message in an SQS queue that will be used as input to another process to send the email out. When possible I like to include all the details about the email into the SQS message, i.e. from, to, subject and the body - everything the downstream process will need to know to send them out.
In my case I use a windows service running on several EC2 instances in an autoscale group to poll the queue and send the emails out. In most cases, where I was able to store all the emails in the SQS body, the windows service is completely general purpose - it reads an SQS message, composes the email and sends it out. Because all of the details of the email are within the SQS message body, this single SQS queue and the windows service that is processing it, can process emails from a variety of applications because the service doesn't need to contain any business logic specific to the application and has no external dependencies.
As you talk about separation of responsibilities, I can't see anything less indicated to send email than a db server (even if it can do it).Sending emails is a task for your business layer, surely not for the data layer.
Use the web app to trigger the process of sending the emails, than implement it directly into the web app, or separate it with a messaging system (like SNS), with a queue system (like SQS) or whatever else.
I am working on django and sending emails to multiple users at once. in the given scenario it only tells me that if it has sent or not.
I want to display the report of same page that how many emails has sent to user successfully and how many not. more if i want to get details why email has failed to sent.
How would i do such things via SENDGRID APIs.
There are two options that I know of:
Connect to SendGrid Event Webhooks and start parsing events for every email to flag ones that were not sent. I believe you can configure SendGrid to only send certain events, so if you're interested in bounces you don't need to worry about handling all events.
The second option is to use a service like sendwithus which will connect to your SendGrid account on your behalf and track all bounces/opens/clicks for you and provide a simpler API/UI to view the data. I believe they do this via SendGrid's webhooks, so it's effectively the same solution but written for you.
Happy to elaborate on either, I've used both before.
Sitecore 6.6, Update 4 (rev 130214) with ECM 2.0 (rev 130123)
I've got a Sitecore installation where we're using a custom MTA. I've configured the Delivery Status Notifications section in the Email Campaign Manager root to include my Return Address POP3 information.
The custom MTA is sending the emails and my POP3 account is receiving the DNS bounce emails.
I can't get this information back into ECM. I've checked the Checked Bounced Messages task for ECM and while it's still configured to do the daily check, I've manually run it a number of times to no avail.
Any clues to why ECM wouldn't be able to pull in this information?
Thanks!
Check your architecture setup as ECM will not automatically receive
the DNS bouce emails count, as it is not using SAC because you are
using a Custom MTA. Have a look at the below image.
Since you are using Custom MTA, make sure you have the Delivery Status Notifications Settings configured properly. Especially the Notification Gathering, because guide says:
Whether or not to collect delivery status notifications from the e
mail box used by the module for sending messages. If this check box is
cleared, the rest of the section is ignored.
If this check box is selected, but other fields of this section are
empty, these fields will be inherited from the manager root.
Make sure the below two steps are followed. Read ECM Admin & Dev Guide
The MTA server sends the DSN messages to the corporate email address. The SMTP server sends the DSN messages to the address
specified in the Return Address field. Usually this address is hosted
on a corporate e-mail server.
The ECM module connects to the e-mail server and gets the DSN messages for further analysis. The POP3 protocol is used for this
connection. For more information about collecting the DSN messages,
see section Collecting Delivery Status Notifications.
Lastly check the subscriber's profile for UndeliveredCount property for
soft bounces and also the manager root item's Undelivered Max
setting, which should give you soft bounces (or maximum value of
UndeliveredCount property) per subscriber.
Let us know how you get along and if the above was useful.
With the help of Sitecore support and through some decompiling and adding additional logging of the ECM code, we have determined that the problem is that the custom MTA was stripping out the original headers that contained the references to the Sitecore campaignID.
When the campaignID headers are present, ECM works great and has no problem pulling the bounce messages back into Sitecore.