Repetitive email open webhook from Mailgun server - email

I am getting repetitive email open callback for the users even though they only open email once.I am not sure this is a issue with mailgun open webhook call or something else is wrong
I would appreciate any kind of help on this
Thank you

Related

How to send email in reactjs

So I'm trying to create a forgot password feature and I want to send email to user for verification. The problem is how should I do that? I've tried frontend services like emailJS but that didn't work because you pre-define where the emails are sent. I need it to be sent to the user, not me.
I've also tried backend services like nodemailer but with nodemailer I have to generate a code on the backend, send it to the frontend and on the email. The problem with this is that if someone gets access to anothers email he can click forgot password and get access to the code by looking at request sent to the backend in the chrome's dev tools
So now I'm stuck trying to figure this out. Can anyone help me?

How to authenticate Inbound Mail? With SendGrid specifically?

I created an application which uses SendGrid's Inbound Parse Webhook. Whenever someone emails "whatever#mydomain.com", the email goes to SendGrid, and then SendGrid hits our server with a POST containing the email's contents. We can then feed that email data back into our main application.
I have it all working. But now I do not know how I am supposed to authenticate the messages SendGrid posts to our server. Does anyone know the best course of action for doing this? Verifying that our inbound emails actually come from authorized users of our main application?
Obviously we can check the "From" address in the headers, but I've read that these can be completely spoofed. Apparently "dkim" and "spf", two attributes of the incoming mail from SendGrid, have something to do with authorization. But i cannot find anything in the documentation, or really anywhere else for that matter, that tells me how I should be consuming these "dkim" and "spf" fields to verify message authenticity.
If anyone has any help, general, specific, or otherwise.. It would be greatly appreciated. Thanks in advance.
Well. Since this doesn't seem to be getting a lot of traction I thought I'd post my own janky-ass solution to the problem, on the off chance that anyone else runs across this issue in the future.
Disclaimer: this could be total garbage nonsense. But it appears to be working all right.
Basically I ended up taking some critical contextual information about the original message that initiated the inbound email. We encode that information in the local-part of the "Reply To" address that we set up with the SendGridMessage. Then I encrypt the encoded local-part.
When SendGrid POSTs to our server with the inbound email, we decrypt the "TO" local-part and validate the result. If it decrypts successfully, we check the "FROM", and verify that they are an actual authorized user of our main application. THEN, we verify that THAT user in question has the correct permissions to edit the information associated with the original encoded local-part of the "Reply To".

Make new gmail email not be grabbed by pop3

This seems like a fairly obvious thing but I can't figure out how to do it and am hoping one of your geniuses can help me out!
We have a Gmail email account and then a ticket system that checks that account and sends an auto-reply to the sender saying that the email was received. This is checked via POP3 but can also be done via IMAP if necessary.
What I want is this: For certain messages, I'd like to file them immediately in Gmail and have them go to a special folder and have them NOT be checked by the ticket system. That's all.
I tried creating a filter in Gmail to move them, skip the inbox, mark as read, all of that. They still get picked up by the ticket system.
I thought POP3 only checked the INBOX on any server, so I expected that if I skipped the inbox then it would not be accessible. This doesn't seem to be the case.
Please let me know if there are any tricks I can do.
Thank you so much!
Ben
The problem that you are running into is that when connecting to GMail via POP3, you are actually accessing the "All Mails" folder and not the Inbox, so filtering the messages does not remove them from the list presented to your client via POP3.
Switching to IMAP should solve this problem, however, since you'd be able to open whatever folder you wanted.

Cpanel: How to check if the email function is activated - contact forms from users don't get sent to my email

I have a website with a contact form.
For some reason the emails aren't getting sent to me, and the code should be fine.
My guess is that the mailing function from Cpanel is disabled.
How can I check if it is active/disabled?
The other option is that the server isn't giving the permition to do it. I really don't know what can be the problem. Can someone help me to solve this one out?
Thanks!
The host must have disabled nodody user mailing capabilities. In that case its better you change your code for sending emails via SMTP authentication method.

Launch Mail app to check for new email

I know how to launch the Mail app to write a new email (using mailto). But I have a facility for users who have forgotten their password to get it sent to their email, and when they submit the request I would like to launch the Mail app, preferably in their Inbox.
Is there a way to do this?
Not possible. Confirmed by Apple.
If it is possible, it might be outside the public APIs. That said, here's an idea that might work, but I don't have all the details for you. The way you get Mail to open up when you want to send e-mail is that the APIs handle a URL request for mailto: by passing it to Mail. Maybe you can find another URL type that you can request to have opened, Mail will try to open it, but then have nothing there for Mail to open. If all goes in your favor, Mail will open and not show anything to the user (even an error from the bogus request you sent it).
Hell if I know what type of URL you'd need a pass, and there's no guarantee that something like this wouldn't break in a future iPhone OS version.