I sent the email by using SendGrid authenticated domain. Here I sent a URL in tag for calling a specific URL. When I see this URL on mail it is encrypted. When I click the link it goes to the specific site well.
I think it is decoded again on the SendGrid site. But if I used Wi-Fi to connect to the internet, clicking the link can not go to the decoded URL, it is because of security.
Does anyone help me to avoid this security? I think if SendGrid sends the URL not encoded then there is no such a problem. So I hope someone helps me to solve this problem.
This is the problem of sendgrid setting.
After logging and click tracking settings.
And make the item-"allows every link to be overwritten..." disabled.
Related
I have a rails app running in production with sengrid.
At one point in my app I am sending an email with a confirmation link which redirects to a specific confirmation page :
%a.button.button-custom.button-blue{href: confirm_votes_path(#vote.confirmation_token, only_path: false)
However in production, Sengrid seems to modify the link inside my mails. I get something like :
href="https://u3881616.ct.sendgrid.net/wf/click?upn=pVistOUxWTXmIPFqqAw0AnJt-2BbCLbreZ3xbCIcCjU0qXsxlkph8Wd3VafON-2FVyJfT0PWClbesX-2F2oOjnxeXwwaDA80aCKixoULvRGUX7PgDg59Vde4HU6spxlzuqyUUF_e4qGN2gUHpERWs59wU8LHyeuQCdWWdC4Yjpw10HvUcUonj0ZfIp-2FiYACT83qOqsHMBnkJGcBsjpIoSUjVySxVhEtqCz7myXFB-2B7uTWKruQbH-2BG7-2FI2-2BFdmXC6nbf-2FFpgyNUivvir0Upib8e5r8YJY3caF-2BpKD-2FscuINwBQkM7n008mEGADo5w5w5fejlzhopGHvJegbSRePJ-2BBu3b3olUhP2q-2BX4lyJAYvegG4xnDPU-3D"
and the link redirects to the base url of my website and not the good confirmation url like it does locally.
What is going on with SendGrid here
You need to disable click tracking.
What should the final URL look like? SendGrid is click-tracking, like bwest said, but that will still work with tokens in the URL and such. SendGrid does the substitution-variable replacement first, then tracks the resulting URL.
So, I am throwing a hail Mary pass here, to see if anyone can catch it. I checked on Twitter and came up empty.
I added the following meta tag to the head of a website:
<meta property="twitter:account_id" content="3XXXXXXXX" />
I then confirmed that the tag is in the source HTML in between the head tags
Then from inside my account panel on Twitter there is a "Verify website" tool.
When I enter the URL and click "Verify website, I get the following:
Website ownership cannot be verified. Please add the metatag to your site.
Perhaps someone else has grappled with this and solved the issue? Thanks
I had the same issue. I assume your websites is "https" to fix this you need to temporarily set your website not to display "http" in the address. Once you hit verify it should work and you can change it back to "https" when verified.
Solved!
So I tried the following, to no avail:
Remove the middleware to redirect http:// URLs to https:// URLs (such that the site runs on HTTP without redirecting to HTTPS).
Unfortunately, this change did NOT seem to work by itself... so we clicked on the "Help?" button at the upper-right of the ads.twitter.com account dashboard.
After explaining the issue to the Twitter support staff, they were able to change something in their system (likely, invalidate some cached record somewhere) and the validation successfully went through. So don't be afraid to reach out to Twitter for support!
After verification, we were able to re-introduce the HTTP -> HTTPS middleware on our site, while remaining verified with Twitter.
I'm trying to send email from my app, emails seem to be going to mandrill correctly and there getting delivered, but I see nothing in my inbox.
I've even tried sending them through my domain and I'm still not getting them. I get them from my live website its using gmail but I want to switch
Using mxtoolbox.com I found
SMTP Reverse DNS Mismatch and
454 4.7.1 Relay access denied which could mean its been marked for spam?
It's sent through emails twice so I'm wondering if theres a time between emails sent or something.
When I was testing this I thought my emails where being dropped by gmail. I found that for some reason there was a very long lag going from Mandril to Gmail. I received all my tests about an hour after Mandril sent them. Hope this helps someone stuck like I was.
Found this question trying to diagnose my issue.
I am using Mandrill and found that sending emails from Mandrill to Gmail will take anywhere from 10 seconds to 15 minutes. Can't establish a reason why sometimes it takes longer.
Mandrill blocks certain domains from being the send address to prevent fraud, but as long as you're sending from an address you know exists to an address you know exists, you should be fine. Also, if that were the problem, the email would bounce rather than send. Also, some email services have policies that prevent you from doing things like sending an email to your address from your address from an external service. Based on that error message you provided, it could be something like that; I would check your provider's policies (and your spam folder).
Not an answer but if you look on your mandrill Outbound activity page and click on the green icon that says Delivered you should see that it says No smtp events.
I don't know why it doesn't send but this show that it hasn't sent.
Or should I say hasn't arrived where it was supposed to.
Update:
On further investigation I found out that the emails weren't sending because I was using my personal email address as the sender from_email: When I changed this to a more business sounding email address it worked. So make something up if you have to, like no-reply#nonsense.com
I'm using the grails plugin "mail=0.9". Emails are not sending on production server. It just works fine on development environment on localhost.
Error is given below;
Stacktrace follows:
javax.mail.AuthenticationFailedException
at javax.mail.Service.connect(Service.java:319)
at org.grails.mail.MailService.sendMail(MailService.groovy:63)
at org.grails.mail.MailService.sendMail(MailService.groovy:46)
at org.grails.mail.MailService$sendMail.call(Unknown Source)
at MailGrailsPlugin$_configureSendMail_closure4.doCall(MailGrailsPlugin.groovy:86)
at com.tkxel.chefvivant.api.SommelierController$_closure4.doCall(SommelierController.groovy:107)
at com.tkxel.chefvivant.api.SommelierController$_closure4.doCall(SommelierController.groovy)
at java.lang.Thread.run(Thread.java:636)
Can anyone help me? Why emails are not sending?
Thanks
Finally, after being spending the much time on this issue. I have fixed this error.
Actually the problem was just about to set the Gmail account settings. Google was sending the hidden captcha and that's obvious machine cannot recognize it. So that's why I was getting authentication error.
Solution:
I just unlocked the Gmail captcha and now it works fine.
Steps to reproduce this
1. Logout your gmail account first.
2. Visit this url https://accounts.google.com/DisplayUnlockCaptcha and then put username and password to login
3. Press "Continue" button to unlock the captcha
4. It will automatically save the settings.
Now, Check your application to hit the url like "Forgot Password" request. You will must receive email. :)
You can also read this article.
http://productforums.google.com/forum/#!topic/gmail/uBdBQAuGeTw
Thanks
javax.mail.AuthenticationFailedException means that you are useing incorrect credentials to access to account you use to send emails.
i have a problem with mail sending: magento doesn't send any mail, i'm trying to use the sendfriend functionality (i've extendend the ProductController of that Sendfriend module), but the problem is about any email (i've tried to do a registration or to change a password, but no email was sent). backend settings seems to be ok:
System->Configuration->system->Mail sending settings->disable Email Communications->No;
System->Configuration->system->Mail sending settings->Host ->locahost;
with the same settings on another local magento installation the system send emails correctly. what can i check?
you don't need to do any coding stuff. Its already available in Magento. You just need to enable the option of Email to a friend from the back-end. Hope this help you.