I have several new clusters that Maborak installed for me but he forgot to do the extra step that would cause the reputation for the new IP's to show.
I opened SSH and ran the commands...
/var/www/clients/client1/web1/web/media/admin/addons/mta/api/cli.php --populate-ipguard
and
/usr/local/bin/php /var/www/clients/client1/web1/web/media/admin/addons/mta/api/cli.php --populate-ipguard
(per my best understanding of the instructions at the bottom)
This is the error message I receive for the first command.
/$ /var/www/clients/client1/web1/web/media/admin/addons/mta/api/cli.php --populate-ipguard
/var/www/clients/client1/web1/web/media/admin/addons/mta/api/cli.php: line 1: ?php: No such file or directory
/var/www/clients/client1/web1/web/media/admin/addons/mta/api/cli.php: line 2: //: is a directory
/var/www/clients/client1/web1/web/media/admin/addons/mta/api/cli.php: line 3: syntax error near unexpected token `|'
/var/www/clients/client1/web1/web/media/admin/addons/mta/api/cli.php: line 3: `// | AUTHOR: Maborak Technologies <[email protected]>
Since I already have IP monitoring working on other clusters, is there any need to create new crons as mentioned below?
Instructions from Maborak.com
Reputation/Blacklist IP Monitoring
The IP Monitor feature requires extra configuration:
Fetch RBL and Reputation query list
/usr/local/bin/php /path/to/Interspire Email Marketer/admin/addons/mta/api/cli.php --populate-ipguard
You need to run this command only one time.
Cron Job entry
0 0 * * * /usr/loca/bin/php /path/to/Interspire Email Marketer/admin/addons/mta/api/cli.php --check-ipguard
0 0 * * * /usr/loca/bin/php /path/to/Interspire Email Marketer/admin/addons/mta/api/cli.php --check-ipguard --type=blacklist
0 0 * * * /usr/loca/bin/php /path/to/Interspire Email Marketer/admin/addons/mta/api/cli.php --check-ipguard --type=whitelist
This Cron Job entry will check the IP Reputation and Blacklist each day at the morning.