shinerweb
Forum Replies Created
-
Do you have any of the full headers from the emails ending up in spam.
The reason(s) for it being filtered into spam should be within those headers (in theory!)Is it happening for all recipients, or just certain email providers (like Yahoo, Gmail etc).
Given you had the same problem with the new SMTP provider that you did with SendGrid suggests that there could be something wrong with your local configuration.
But the fact you mention your reputation and secure Lightspeed server sounds like you really know what you’re doing! (Can bet you are climbing the walls !!)One suggestion, does the sending account/email address actually exist?
I’ve had several sites where we used a do_not_reply@this-domain.com email address (for an unmonitored reply address). This would cause some mails to be rejected during both the send (on some SMTP servers) and at reception (by the end users). Whatever anti-spam measures were in place was obviously checking to see if the sending address was a valid mail account. We ended up just creating an email fwd and that stopped the issues. (Clutching at straws here)Has your host updated your PHP version or added in any MOD_SECURITY rules?
Are you seeing any errors in your browser console?
Given I use HTML formatted emails from multiple external sources of emails, I’d suggest that it is YITH Abandoned Cart Plugin appending the erroneous “,Content-Type: text/html”
Especially if regular WooCommerce emails are working fine until you enable the YITH Abandoned Cart PluginThat plugin is extracting the email address from a partially completed cart process and then using it to email the user to get them to complete the process.
It appears that the email address being passed from YITH contains the “,Content-Type: text/html” which is generating the “invalid email address format”.
As to why it goes away when you switch off Post SMTP, I’d guess that Post SMTP is doing it’s proper error checking on the addresses it is supplied.
Without Post SMTP you are using the native PHP Mailer php mail function which maywell generate an error but is being recorded at system level. You would only see it if you enabled PHP error logging. It likely sends the first of what it thinks is two comma delimited emails, and creates a php error for the “,Content-Type: text/html” address in the 2nd email.
Because the first email has sent, you assume it is all working fine.I’d get in contact with the YITH plugin author to check with them and switch on PHP error logging to see if you are missing some errors being raised.
Ah, so you’re saying “what if all SMTP is blocked” by a firewall update for example. Fair point, however, I’d still argue that PHP Mailer is so badly supported and performs, that I wouldn’t rely on that for a back-up either. For that instance, there are two other notification methods other than “Website Admin” (under the Notification tab). Namely SLACK and PUSHOVER. Both of those whilst not allowing emails to still be sent from the site, will alert you to an issue.
Given the number of issues with PHP Mailer and the general lack of technical knowledge by users, having PHP Mailer as a fallback could cause more frustration. PHP Mailer tends not to work in many more cases than it does work. Unfortunately, the abuse of PHP Mailer was such that it simply isn’t trusted by most email providers/spam filters.
There are two notification methods other than WP Admin Email that are much more reliable and do not use the mail ports/mechanism and are therefore not likely to be blocked in addition to any SMTP blocking. If firewall/system update has caused that much grief, there probably isn’t much that will work.
But I get what you are saying, if during Post SMTP there is an issue, then at least try PHP Mailer automatically as a fallback (and perhaps send a system notification to alert the admin of an error) rather than have no fallback set as standard. I’d still argue against that in favour of SLACK/PUSHOVER notifications given how unreliable I’ve found PHP Mailer to be.
You appear to be using Gmail to send your emails but have prevent override email set to yes. Are you sending emails as your Gmail account or using your domain in the address?
Are SPF and DKIM set up correctly.
Try reconnecting your Gmail account using an App password rather than the main Google username/password.
Do you see any other error messages within the server transactions within the log?
Those are the things I can initially think of.
Contact imunify360 security or Greengeeks and ask them why?
Do you have SPF and DKIM set up correctly for your domain?
**Not linked or affiliated to Post SMTP at all – Just another user**
The PHP Mailer is inherently the worst method to use due to the number of hosts that block it and the low spam scores it can give meaning it is by far the least reliable method of sending. It was the exact reason that POST SMTP and other SMTP plugins were born, i.e to get away from using the PHP Mailer option.
If mail is that important to the operation of your website, it would be a much better option to have a 2nd SMTP service set up and available with the SPF and DKIM records set up correctly. Ideally on a separate domain on a separate server. Even Gmail or Office365 correctly authenticated would be more useful as a fallback than the PHP Mailer function.
If PHP Mailer does function, in most ‘shared hosting’ type scenarios any emails sent internally (i.e. from your site to say ad-address@your-domain.com, i.e. on the same server are likely to get through. Whilst this may be ok for website admin type emails such as security emails, WordPress system emails etc, PHP Mailer will still be very unreliable for any external emails (such as those sent to your customers in the event of sales emails for example). The use of PHP Mailer as a fallback in that instance would not be of much use.
Having said that it does vary from server to server. If you are running your own dedicated server and your IP and server reputation are fully under your control, and all your server configs are fully accessible by the developer, then there is no reason a PHP Mailer set-up cannot function well. (It is however most unlikely that a dedicated server would be running a mail server in addition to a web server in which case, you’d be using external SMTP servers anyway so adding a standby SMTP server wouldn’t be such a big leap).
**Not linked or affiliated to Post SMTP at all – Just another user**
What are the results of sending a test email when you are using the smtp.office365.com settings.
That suggests you do not have them set up correctly.
Have you set up your SPF/DKIM records correctly?(ps. I don’t work for POST SMTP, I’m another plugin user offering ‘advice’).
Make sure WooCommerce is sending emails using the same domain that you are using to send the emails (or the same address in some instances).
and/or
Make sure you have SPF and DKIM records set up for the WooCommerce sending domain on the domain you are using to send.This last one might sound weird but trust me, if you are sending from something like sales@yourdomain.com and you are using mail.yourdomain.com to send, make sure you have a forward or a mail account set-up for sales@yourdomain.com
Some abuse checks will verify that the sales@yourdomain.com is a valid account and if it doesn’t exist, it will fail the test and bounce the emails.
(We hit this one a few times when we started using do-not-reply@our-domain.com
We had to actually create a forward for do-not-reply@our-domain.com to stop emails from being rejected during send).It could be that you have not enabled the email from within LearnPress.
On the left-hand side menu, under LearnPress, click settings.
Open the Email tab and ensure all the email types you want to be sent are enabled- This reply was modified 4 years, 8 months ago by shinerweb.
That is normal and mentioned in the documentation and something that needs to be done at your end.
If you are using a separate email service (in your case SendGrid), then you need to add an SPF entry to your DNS to authorise SendGrid to send them on behalf of your domain.
When a website some-domain.com sends an email, “some-address@your-domain.com” various antispam tools run checks. One of which is to check the IP address of the sending mail server matches the domain, or that the IP address of the sending mail server is authorised to send emails on behalf of that domain.
SPF records are part of your DNS records. If you log into SendGrid, they should give you the settings that you need to enter in your SPF record in your DNS records.
I suspect that the fact you are using naamchin.com to send emails on behalf of hakcollections.com might be the cause of your failure.
When you send a test message, do you see any errors in the transcript (along the lines of cannot be used as mail relay or similar).
Or have you correctly set up the naamchin.com to send emails on behalf of a different domain?
Forum: Plugins
In reply to: [WP-Members Membership Plugin] Logged into wrong accountDo you have any caching plugins enabled?
Forum: Plugins
In reply to: [List category posts] Display certain bag of post IDshttps://github.com/picandocodigo/List-Category-Posts/wiki/How-to-select-which-posts-to-show
includeposts – IDs of posts to include in the list. Ex: `[catlist includeposts=”2,97″]