Posts by kess
-
-
I'm pretty sure that SpamAssassin is not blocked from some blacklists…
By the way, if your server is blocking someone because It's present in some blacklists, that's not your problem.
Else, if you're blocked because you're present in some blacklists… well that's your problem.
You need to see why (could be a lot of reasons)…
A good starting point could be that one: https://mxtoolbox.com/blacklists.aspx
-
-
Sorry but I can't help you further… I don't use compiled versions…
Seems like the compiled version is not going to read Environment Variables when launched from cli.
One last step could be to create your personal custom php.ini file for your cli cron:
1. copy your actual php.ini to phpxyz.ini
2. edit phpxyz.ini and change
to
then try to launch your cron with:
-
And what happens you you run the following in your crontab ?
Or, just for test:
Create a php file with the following contents:
and name it test.php
What's the output of:
What's the output of:
-
Strange, because my crontab is working perfectly using this method.
I use the sury provided packages, I don't compile them.
-
Or you could just set the correct env variable in your cron job.
Have a look at the first line:
Display MoreCode- TMPDIR=/var/www/virtual/your-whmcs-domain.xxx/phptmp
- # DO NOT EDIT THIS FILE - edit the master and reinstall.
- # (/tmp/crontab.Pdunk9/crontab installed on Fri Sep 6 18:07:37 2019)
- # (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $)
- # Edit this file to introduce tasks to be run by cron.
- #
- # Each task to run has to be defined through a single line
- # indicating with different fields when the task will be run
- # and what command to run for the task
- #
- # To define the time you can provide concrete values for
- # minute (m), hour (h), day of month (dom), month (mon),
- # and day of week (dow) or use '*' in these fields (for 'any').#
- # Notice that tasks will be started based on the cron's system
- # daemon's notion of time and timezones.
- #
- # Output of the crontab jobs (including errors) is sent through
- # email to the user the crontab file belongs to (unless redirected).
- #
- # For example, you can run a backup of all your user accounts
- # at 5 a.m every week with:
- # 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/
- #
- # For more information see the manual pages of crontab(5) and cron(8)
- #
- # m h dom mon dow command
- */5 * * * * /usr/bin/php7.2 -q /var/www/virtual/your-whmcs-domain.xxx/00_private/crons/cron.php
-
-
I gave you the right solution in my first answer to your question.
As far as I can see, you like having problems or to invent some new ways to find new methods to generate problems.
The standard SPF record permits e-mail sending through the server itself, if you want to add a relay you have to tell the SPF record that this relay exists. There are some ways in order to achieve that, through IP, through name, through include, etc.
I don't know what you are doing, I don't know which is the actual situation, I don't know your actual structure. You are the person in charge, you are the person who should know what's happening… At least, you should be the person (as a system administrator) who should know how SMTP (and all dependencies like SPF, DKIM, DNS, etc.) protocol works.
-
If from outside your server HTTP port is unreachable, you won't never get a LetsEncrypt Certificate.
Let's say, you want a LE certificate for your FQDN my.fqdn.local… What happens if I browse http://my.fqdn.local from outside of your network ?
