When processing your phpList queue with a crontab, you may get the following error:
bash: /home/yourname/phplist: Permission denied
This happens if your phplist script is not executable. It is an easy fix. Simply make the phplist script executable and it will run as expected:
chmod u+x /home/yourname/phplist
If you are trying to process your phpList queue using a crontab, you will have to set up the phplist script provided in the bin directory to work with your system. It looks like this:
#!/bin/bash# script to run PHPlist from commandline. You may need to edit this to make it work
# with your shell environment. The following should work for Bash# in commandline mode, access is restricted to users who are listed in the config file
# check README.commandline for more info# identify the config file for your installation
export CONFIG# alternatively you can use -c on the commandline# run the PHPlist index file with all parameters passed to this script
/usr/bin/php /home/website/public_html/lists/admin/index.php $*
Of course you will want to modify all the paths to fit your phpList install. Most importantly, however, is to not forget to modify the FIRST line if need be. Otherwise, if your bash interpreter exists elsewhere, when your try to execute your script you will get the following error:
/path/to/phplist: Command not found.
For the majority of the installations out there, /bin/bash should be fine, however on some systems you may need to edit this to point to where your bash interpreter is installed. In my case, I had to change it to /usr/local/bin/bash.
To future-proof my changes, I also symlinked to where my bash existed:
ln -s /usr/local/bin/bash /bin/bash
That way I will not have to re-edit new versions of the phplist script in future phpList upgrades.
As a follow-up to my post on getting rid of the X-Authentication-Warning error when using phpList on FreeBSD, here's how to do the same in Linux.
Open up /etc/mail/trusted-users in your favorite editor, and add both the user that your Apache is running under, as well as any usernames which are processing phpList queues and bounces via crontab. For example, your trusted-users file should look like this:
Save & Exit. Restart sendmail with the following command:
Now when you send mail with phpList, the headers won't contain X-Authentication-Warnings.
One security drawback that you should be aware of: Any user on your system can now use PHP to send email with "forged" headers. You basically just gave everyone on your system "Trusted User" status to Sendmail, so be sure that you trust your users before actually doing this!
See how to do this on FreeBSD
When trying to automate processing of the mail queue and/or bounces in phpList, I came across the following error when calling the phplist command line script from a crontab:
Error: USER environment variable is not defined, cannot do access check. Please make sure USER is defined.
This happens because when a crontab executes, the $USER variable is not set. We must set it in our script. So open up the phplist file and add the following:
The entire file should now look like this:
export USER/path/to/php /home/yourusername/path/to/phplist/admin/index.php $*
Note that you also must set the $commandline_users variable in your config/config.php:
$commandline_users = array("yourusername");
With all of that in place, you can automate your queue and bounce processing with a crontab like this (adjust your paths accordingly):
# Suppress crontab emails
# Process phplist queue daily, every half hour
0,30 * * * * /home/yourusername/phplist -pprocessqueue
# Process phplist bounces once a day, 5am
0 5 * * * /home/yourusername/phplist -pprocessbounces
If you enable the $message_envelope variable in the config.php file of phplist for processing bounces, sendmail will probably complain with the following header in your email:
X-Authentication-Warning: your.domain.com: httpd set sender to firstname.lastname@example.org using -f
This is because only "trusted users" are allowed to change the message envelope. By default, sendmail only considers root, daemon, and uucp as trusted users, so if you try changing the message envelope as the user Apache is running under (in my case httpd) sendmail will attach that nasty warning header to all your outgoing mails. Spam blockers don't like this!
There are a couple of ways to fix this:
- Add httpd (or whatever user Apache is running under) to the daemon group:
pw groupmod daemon -M httpd
- Add httpd (or whatever user Apache is running under) to Sendmail's trusted-users file. Open up /etc/mail/your.domain.com.submit.mc in vi and insert the following line:
FEATURE(`use_ct_file') dnl # Trusted users
Save & Exit.
Now you must create the trusted-users file in /etc/mail:
Open /etc/mail/trusted-users with vi and on one line simply add the name of the user under which Apache is running:
Save & Exit. Run the following commands in /etc/mail to commit the changes to Sendmail and restart the server:
That's it, you should be good to go. Mail sent via PHP/Apache will no longer contain the X-Authentication-Warning header.
Note that there is a downside to this. Any user on your system can now use PHP to send email with "forged" headers. You basically just gave everyone on your system "Trusted User" status to Sendmail, so be sure that you trust your users before actually doing this!
UPDATE: How to do the same in Linux
When using the script "phplist" to process queues or bounces on your phplist installation, you may receive the following error:
./phplist: Command not found.
This is caused by the file being in the wrong fileformat. You probably edited it on your Windows/Mac machine, uploaded it, and attempted to execute it. In order for this to work, the file must be in UNIX file format. To fix, open the file with vi ("vi phplist") and type the following command:
: set ff=unix
Save, and exit, and your phplist should work as expected.
If you get the following error:
/bin/bash: bad interpreter: No such file or directory
That is because you either don't have bash installed, or if you do, it's in a different location. The first line of the phplist script ("#!/bin/bash") must point to where your bash is installed. Find it with "whereis bash" or "find / -name bash", edit the first line of the phplist script to match, and you should be good to go.