Tags notifications not received - email-notifications

I have set several tags and also provided my mail id so that I can receive mails whenever there is some action related to those tags. It was a week back or so.
But it seems its not working as I haven't received any mails for far.
Is there some extra setting I need to do?

Related

How to improve email robustness? [mailgun, laravel]

I planned to improve email robustness using below way. I am using laravel and mailgun. If any bounces email is in the mailgun then i want to send that to someone related to the email(not to that previous receiver and it related with previous sender or someone) so that i plan to use Task scheduler and schedule every hour this process. After that email send successfully i want to remove that email from mailgun.
I actually want to know how to implement get bounces email from mailgun and if send successfully using Task scheduler i want to remove that email from mailgun. if any sample's to achieve this? or any different ideas?
Normally when a bounce happens, providers such as Mailgun will retry a few times depending on the bounce status/type. After failing to send to that email address, Mailgun will put that address into your Bounces list to avoid sending to that address in the future. There's really no point in trying to send emails to an address which doesn't exist, inbox is full, domain expired, etc. So perhaps you should review your bounce list before you consider doing this. Mailgun's dashboard provides the description and date it happened. If you wish to send to a particular address again, you can remove the address from the bounce list. More about bounces here.
You can use mailgun-php or simply use Guzzle to call their API to retrieve your bounces. I'm not sure what you meant my removing email, but hope this helps.
Edit:
You can use their API to get all your bounces, and also the message content (retention depends on your plan or settings) if you need the original content. You could also use their webhooks to get the failed emails, so you don't really need to schedule/cron.
Edit 2:
The bounce list only stores email addresses of previously bounced emails. Also, I just realized that, if you're checking hourly for bounced messages, looks like the suppression/bounce API won't be of much help since you can't know if a message has failed for an address already on the list. This is the only data from bounce list:
{
"address": "alice#example.com",
"code": "550",
"error": "No such mailbox",
"created_at": "Fri, 21 Oct 2011 11:02:55 GMT"
},
So looks like you've to use the events API or webhooks to get the failed messages.
I've used mailgun-php sometime ago, and I found that the it wasn't easy working with Events on that library due to protected properties of the class. So if you have trouble, maybe just use Guzzle or use webhook approach instead.

Mailchimp PUT always returns a false error so is impossible to check for real errors

I have coded some PHP scripts to create and send a newsletter using MailChimp API. Below the steps
1) First of all, I update a template with the products I want to include in the newsletter
2)I create a campaign
3)I attach the template content to the campaign
4)I send it
The issue happens when I attach the template content to the campaign.
If I check for errors before to send the campaign (to double check that the template was attached correctly)
I always get a timeout error, even if in reality by ignoring that error the campaign is sent without problems.
Obviously, I can't just ignore the error. I want a reliable system to avoid sending empty emails.

Plugins registered for email entity is not triggered

While i click the email send, i have triggered the plugin with post condition and message as send,setEntity and SetStateDynamicEntity to trigger plugin to update current email sending activity date in the custom field as last activity. While i send normal mail it triggers and update the field, if i send with an attachment in email this plugin not getting triggered. even though i changed the steps from post to Pre-condition it not working. Sometimes it working automatically and sometimes it was not working.
I just tried to recreate your scenario. I added a Plugin Step on "Send" Message of Email Entity. First Image will help you explain this.
Then I create an Email with attachment and send an Email. Second image will help explain this
Now when I profile a same plugin Step, I could see plugin been triggered for Send of Email with Attachment. Image below will show this.
Summary: Yes Plugin is triggered when you attach an attachment with Email and Send it.
Date Sent (schema name: senton) out of the box field already gives you the date and time when email was sent. Or, if you just need the date and time when email was last modified you have the Modified On (schema name: modifiedon) out of the box field.
Also, keep in mind that even if it worked, your logic would not give you the date and time in which the email was sent. It would give you the date and time in which the SendEmailRequest was processed by Dynamics.

Unable to get timestamp of the message posted by Slack App

Whenever my app posts ephemeral message to Slack channel (in response to a query by a user), I am unable to get the timestamp of my Slack app response. As I want to delete it once the user has made a selection using one of the buttons. Although I have subscribed to 'message.channels' event, I don't get a notification to my app whenever my app posts in the channel (in response to the user input), therefore, I am unable to get the timestamp of the message which I'll use to delete it. All I want is the timestamp of the message posted by my app so that I can delete it but I am unable to receive the timestamp. Please help!
For e.g. in Giphy app for Slack. Let's say the user invokes the app by calling '/giphy [dog]' where 'dog' is just an example of a search term. The app responds by sending a gif and user can either send it, shuffle to the next one or cancel it. I want a similar capability of cancelling the app response but I need the timestamp of the message in order to do so therefore I am asking for help.
Thanks.
Your approach can not work, because Slack is handling ephemeral messages differently from "normal" messages. They are only visible by one user and can not be modified by API methods (e.g. deletion).
But of course its possible to replace ephemeral messages. Here is how:
Your app can just reply to the interactive message request from Slack with a new message. That new message will by default override the original message including ephemeral messages.
You can reply in two ways:
Directly reply to the request from Slack with a message within 3 seconds
Send a message to the response_url from the Slack request within 30 minutes.
See here for the official documentation on how to respond to interactive messages.
This approach works both with interactive messages and slash commands.
See also this answer for a similar situation.

Magento 2 Order Confirmation Emails Not Sending

Currently having an issue with order confirmation emails not sending.
I have looked at various forums / solutions and these haven't worked.
My existing setup is using the MagePlaza SMTP to send email using Mandrill, this is working through their test function and also the Forgotten Password and Create account emails are being sent but not the Order Confirmation emails.
I am using IWD One Step checkout but have also disabled this to try with Magento default checkout and it doesn't work using either.
Asyncronous sending is set to disabled but I have also tried with it enabled. Both times no order emails are sent.
As I'm using Mandrill I have checked their API logs and the API request isn't being sent.
Any help/suggestions appreciated.
It's possible that the "From" address is wrong.
Goto Stores -> Configuration -> General -> Store Email Addresses and check if "Sales Representative" Email address is correct.
There is known bug in Magento 2.2.4/2.2.5/2.2.6 and you might be afected by it:
https://github.com/magento/magento2/issues/14952.
TLDR: There is no from data set on email transaction and messeges aren't sending at all.
Try thisfix:
https://github.com/magento/magento2/issues/14952

Resources