I'm using Aschroder SMTP Pro on my Magento site. The test for email sending(that the plugin does) is successful but order confirmation emails are not being sent.
I enabled email and exception log but i don't manage to see any error in it.
Send mail method in System > Configuration is set to "Separate Email" for each section.
Email templates are correctly configured.
What am i doing wrong?
Thank you.
I also struggled with the problem of order e-mails not being sent in CE 1.9.1 but found the problem after a while:
As of Magento CE 1.9.1 Magento doesn't send order emails directly during the order process.
Instead the mails are queued and are sent by the cron.
So make sure to configure the Magento cronjob properly.
Also refer to:
http://www.magentocommerce.com/knowledge-base/entry/ee1141-ce191-responsive-email#cron
http://www.magentocommerce.com/knowledge-base/entry/ce18-and-ee113-installing#install-cron
There are many things that can cause what you're describing, and most of them are completely unrelated to Magento.
From the limited amount of information you've provided, my guess would be that your email is undeliverable because your domain lacks Sender Policy Framework records (or one of the other major authentication standards like DKIM, SenderID, and Domain Keys), or because the IP/domain you're testing delivery from was formerly occupied by a spammer and has been blacklisted (which happens).
When it comes to testing emails, I usually test delivery to gmail accounts, because they seem to be the most receptive of the public web-based emails. Any kind of company email is usually a bad choice, because they're more likely to have stricter deliverability standards.
The problem was caused by a bad plugin...i had another problem and resolving it Magento restarted sending confirmation emails.
Here is the link to my question(with answer) : Source model "" not found for attribute “privacy” Magento 1.9
Strange things...
Related
SendGrid is able to track if an email "... was accepted by the receiving server".
How would one go about doing this in an application that uses Gmail SMTP servers rather than SendGrid? (For example, a NodeJS application that uses nodemailer, or a Ruby-on-Rails app that uses Action Mailer, to send email through Gmail SMTP)
Google's different levels of paid G Suite offerings have logging you can use: Track message delivery with Email Log Search (google.com).
If you're not paying for G Suite and you're trying to build a way to collect statistics yourself, that becomes more tricky. Email service providers will generally count an "open" using something like a click-through on a link in the email (linked back to a property you control), or the loading of an image in the email (again, loaded from a property you control). You can read more about how ESP email open rates work here: The Science Behind Email Open Rates (and How to Get More People to Read Your Emails) (superoffice.com)
Gmail's SMTP servers don't report email delivery, only if there's a bounce. Google is somewhat closed with that, only paid users in G Suite can actually see the detailed delivery status using the Email Log Search tool.
Hope this helps.
I'm making a user management system for my app, and I need to send users a "forgot my password" email with a token that lets them reset their account password. I signed up for SendGrid through Azure (to get the 25,000 emails per month free, which sounded like a great deal) and wrote some code to use it, but after testing my program a bit I was dismayed to find that only a couple of my emails actually went through.
After going onto the SG control panel, I found that 4 out of the 6 test emails I sent went through, and all of the others were rejected as being spam. I sent an email to mail-tester.com to see what it though my spam score was and it gave me a 4.3/10.
The email in question was a single sentence with a link to the password reset, without any images or other elements. I only sent those 6 emails out, so the volume of my emails definitely wasn't the issue. Still, I'm very puzzled as to why my messages are getting flagged as spam.
Without going to the trouble of making an elaborate authentication setup, are there any basic changes I can make to my system to make it get through to users?
In this case it's most likely because you are sending such a short message, with a link to 'reset your password' from a non-whitelabelled email address (the email address you're sending from cannot be verified against the actual domain), and the link may also be a different URL. It's probably getting pulled up as a potential phishing email.
You can rectify this by white labeling your domain and email links via the SendGrid dashboard, it's easy to do and should improve your deliverability.
Also check out this article from the SendGrid support team about White Labeling.
A question from 2015 which is sadly still relevant today as usage of SendGrid increases.
My organization has blocked all SendGrid mails except for those on the paid tier using fixed IP addresses with resolvable public DNS names (such as sendgrid1.sampledomain.tld) which we then whitelist.
There are now far too many domain impersonation, phishing and other spam mails coming in from SendGrid for us to allow everything from them - roughly 10 000 mails over a seven day period, which is far too many to manually report to SendGrids abuse department.
So my answer would be that switching to the paid tier of SendGrid is the better option if you like a better chance of your mails arriving intact at their destination.
I receive only Spam Mails from Sendgrid.
Goes direct to Spam folder and try to report Sendgrid everywhere I can. Maybe they get blocked by most mail servers and make them think about their policy in "hosting" all these Spammers.
In my case my emails are marked as spam because of the anchor label different to the href being actually called.
And that's because of the 'click tracking' setting of sendgrid.
So, if you have something like
yourdomain.com
sendgrid may replace the href and you end up with something like:
yourdomain.com
The sendgrid page being called tracks the click and then redirects the user to the url you originally set. But this sometimes results in your email being marked as spam.
Try to set 'click tracking' in sendgrid dashboard to off: settings | tracking | click tracking.
details here: https://sendgrid.com/docs/ui/account-and-settings/tracking/
Always start by setting up Domain Authentication, formerly known as domain whitelabel as #MartynDavies says. Found under Settings -> Sender Authentication in the UI. Should look like this:
https://sendgrid.com/docs/ui/account-and-settings/how-to-set-up-domain-authentication/
To identify problems have a look at Activity and choose to see deferred, drops, bounces, blocks and spam reports.
https://app.sendgrid.com/email_activity
Under Suppressions you can see details for Blocks and Bounces among others:
https://app.sendgrid.com/suppressions/blocks
https://app.sendgrid.com/suppressions/bounces
There you can see errors like:
550 5.7.1 SPF check failed. em1234.mydomain.com does not declare 11.222.33.44 as a valid sender
If it says Verified but you see errors like this then contact SendGrid support.
One thing that has worked is to upgrade from the Free plan to Essentials or Bronze via the Azure Portal. This made a lot of the emails marked as spam pass through.
I had a similar issue when trying to send a user verification email using SendGrid.
In my case, using a custom domain as the sender identity solved the issue.
Make sure to also verify the domain before using it.
I have a website based on WordPress.
Every page has his own Contact form.
I am using Configure SMTP
+ Contact7
(SMTP is setup to user Gmail as a SMTP server).
After a while I'm curious why I am actually doing it this way.
Is Gmail that secure or it is only about SSL?
Is WP build in mail function secure (and good) enough to use it?
In total: what is the best way to make contact form in WordPress and avoiding my mails getting to the spam folder?
I was told that the solution descriped above (Gmail SMTP) is the best way, is it?
Well, the build-in mail function works fine for most uses, like sending "Password lost" or "New user registered" mails or even contact forms.
If you send more than just a few (can´t name a number) mails via contact forms, newsletters etc. you will probably want to use a mailserver for that, either an external one (GMail) or a properly configured internal one. They go much easier past spam protection because they are known for sending mails and are probably whitelisted at the big mail providers. Your webhost most probably is not and might be considered as spam very fast when he is sending mails regularly.
If you want to send a lot of mails in a short span of time you should probably go one step further and choose a service like Mailchimp or something similar for that. Their business is sending newsletters and so nobody (means the mail providers) wonders, when they have lots of mails incoming from one of those servers.
For your use case I would stick to SMTP via GMail, when it works fine for you. As you are not sending lots of mails in a short span of time you´ll have only little problems with getting rated as spam and you also have a trusted server sending those mails. Seems fine for me.
in a recent project I integrated a custom Contact Form which uses the silverstripe Email Class. Unfortunately the sent E-Mails do not arrive at the client. It seems to depend on the host/domain of the target E-Mail Address. E.g. gmx does work (but spam), but receiving the mails on the E-Mail Address of the client does not work at all (hosted at united domains). Thanks,
Florian
The Email class in SilverStripe is admittedly not the greatest ;) But apart from potential lowlevel encoding errors, email delivery mainly depends on factors outside of SilverStripe.
You can start debugging mailservers, DNS records, spam headers, bounce emails, etc - but in the end its probably far easier to leave email delivery to a SaaS-provider like SendGrid or MailChimp. Both have offerings where you can just point your PHP configuration to their SMTP servers. SendGrid has a nice best practice collection on what to watch out for when sending emails in general.
I've been using Contact Form 7 in Wordpress without too many problems. In a current installation, I can send mail to webmaster#domain.com but get an error when trying to send mail to user1#domain.com. I've checked this Stack Overflow ticket:
Wordpress - Contact Form 7 Not Sending to Certain Email
But enabling the SMTP mail plugin doesn't modify the behavior of the bug, and the mail server is not external (like the ticket in question). Any idea what the issue might be? Thanks!
EDIT: user#domain.com is a valid email address and also succeeds when running it against open source online email checkers.
Kind of a hack, but I had this happen to me when I tried to have the emails sent outside of the domain to a gmail account. I ended up adding CC: youremail#gmail.com to the Additional Headers and it worked well afterwards.