shinerweb
Forum Replies Created
-
Forum: Plugins
In reply to: [WP-Filebase Download Manager] WP-Filebase and WordPress 5.7Avoid like the plague. Whilst it will work to some degree, it requires a lot of modification to have it run free of errors and not consume server resources.
There is zero support or updates available so I would highly suggest you look elsewhere.
There are other plugins available that offer the same (if not more) functionality that are still/better supported.Whilst it was a fantastic plugin in it’s day, it is no longer worth the hassle IMHO
@tneville – thankfully, I persuaded the clients to bypass using GoDaddy mail relaying and hosted the mail servers elsewhere.
I know you know, but most users don’t realise that even though they’ve paid up front for their GoDaddy hosting doesn’t prevent them from splitting email away from web services for next to no cost for most GoDaddy users.
GoDaddy also have a pretty low limit of 500 mails per day when using their relay on their basic plans. Including system mails (not just mails to visitors/sales etc) can often exceed the daily limits on even a relatively low traffic site.
Nice one Tim.
This would make a good FAQ or pinned post somewhere!
Had the same issue with a client the other day. Don’t you love that shudder you get when you hear “GoDaddy”!!
That’s a function of the server your running on and its connection to Office365. It’ll either be your server (most likely), your route to office365 or office365 itself.
Absolutely nothing you can do with post SMTP to improve the timings sorry.
- This reply was modified 5 years, 4 months ago by shinerweb.
Tim,
Do you think it’s anything to do with the fact he’s doing the From: to a Gmail address (orders.csisaddlepads@gmail.com) but sending via an SMTP server at a different domain (csisaddlepads.com).Could that mail server be rejecting the mail (no relay???).
Could try setting the From: to an account/address at that domain and setting the Reply to: as orders.csisaddlepads@gmail.com
Am fairly sure the plugin was taken down whilst they investigate a few errors that were being reported.
It’ll be back soon no doubt.
Keep an eye out on the blog for any latest news. I know they are very busy at the moment so the plugin was probably removed quickly to avoid too many others downloading the plugin. (Reports of it causing a WSOD / Fatal error – so the priority would have been to stop that happening on other sites).That is more likely down to the settings within your Gmail account being set to “prevent less secure apps from connecting” which is hardly a fault of the plugin itself.
Forum: Plugins
In reply to: [3CX Free Live Chat, Calls & Messaging] Failed to load SourceMap@designtimestudio The message you are seeing is a warning only and has nothing to do with why your problems with seeing a blank page. It is simply a warning displayed by your browsers debugger that it can’t see a debug file it can use to show more information in your browsers debugger.
If you are still having issues, you might want to raise a ticket with Divi Support directly. Have you disabled caching and minification during debugging?
It might be that your web host or firewall on your server is blocking out-going access.
Ask your webhost if they are blocking any outbound ports and have them add an exception for the port you need.Ask your host if they are blocking access to ports 587 or any other outgoing ports.
Can you clarify if you are trying to import WP SMTP plugin settings into Post SMTP plugin?
If so, not sure you can do that. Post SMTP has been upgraded and improved on since the days of WP SMTP.
The current Post SMTP import/export works between itself (i.e. export from Post SMTP, import into Post SMTP).If you are trying to import WP SMTP settings into another installation of WP SMTP, you’ll be better off posting that question in the WP SMTP forum (https://wordpress.org/support/plugin/wp-smtp/)
Might be quicker manually transferring the settings from your old WP SMTP set-up into your new Post SMTP set-up if indeed, that is what you are trying to do.
This is a problem seen on one.com
Make sure that the To: or From: are registered email addresses on your account.
i.e. if you are going to send via test-address@your-domain.tld make sure there is an email account set up called test-address@your-domain.tld
@stokim Some web hosts block PHP Mailer or change it’s behaviour.
A compromised web server could use PHP Mail without the need for a username/password to be supplied to send an infinite amount of spam whereas an SMTP account needs authorisation to log in with (usually !!).
Depending on your web host, they may have blocked the ports required by PHPMailer by default and you need to ask them to whitelist those ports, or they may have switched off the PHP Mailer function completely.
It’s why email sent with PHP Mailer has a lower reputation than (most) emails sent via SMTP.
@marcusjwilson to be fair, the main reason people install POST SMTP is to use an SMTP server. In this configuration, the problem isn’t seen.
It’s only if you are using the PHPMailer that the problem arises. Using PHPMailer is usually a bad idea on most web hosts which unless you have a dedicated server or a server with a unique IP address (for both web server (easily done) AND mail server (not usually done). As @yehudah suggests, you’d be better off using an SMTP account (or one of the other mail methods rather than PHPMailer). You get a much better email delivery rate this way.
If you don’t have access to an SMTP account or other mailer account and have to use PHPMailer, then there isn’t really much use in having POST_SMTP installed (other than for logging).Only those using PHPMailer will see this issue.
What is the output from the diagnostics, and what do you see in the transcript logs?
What is your current mail setup? (Diagnostic output will give us more information)