I have just deleted a post in regards to a bug in Webalizer (webstats), where you would get a file not found error.
When I spotted this, I was working on my Test Bed system, and no one had ever accessed a website, via a domain name running on that system.
Webalizer only starts to work when someone accesses a domain as above via a browser, so it turns out there is nothing wrong with webalizer.
18/04/2025: Back by popular demand, the smtp auth fixing script.
I have had numerous emails asking for the links to the smtp auth fixing script.
I have gone one further than that.
I have created a new FAQ on smtp auth fixing, which includes the old script.
So, CLICK HERE to open the new FAQ.
13/04/2025: Slight adjustment to the Roundcube defaults script.
I have made a slight change to the Roundcube defaults script.
The script is now more likely to be able to restore Roundcube to “factory settings” successfully when its starts.
10/04/2025: New post to help you set the Roundcube defaults.
I have added a new post to the site to help you set up Roundcube Webmail.
The information and script from this post will save you some time when you create a new email account.
07/04/2025: The modified version of EHCP force has been added to the site.
I received several requests for this.
At the end of the day, I am only here to help you, so I have done what you wanted.
This means that the pre and post EHCP force install scripts are no longer needed, so the posts have been deleted.
I hope this does not upset the author of EHCP force, as that was never my intention, as I think he is an amazing developer.
06/04/2025: New version of the EHCP force update script created.
This EHCP force update script was changed on the 6th May 2025.
The 6th May 2025 script, contains a new “Fail Safe”, for sending emails via Roundcube, which means that in the event of an SMTP auth issue, you will still be able to send emails from Roundcube.
The script has better protection for the SMTP auth settings (saslauthd).
If you created your EHCP force update script before 6th May 2025, you should delete it using this command.
sudo rm /var/www/new/ehcp/scripts/updateehcp.sh
Then follow THIS POST again, when you need to update EHCP force.
03/04/2025: What a frustrating few hours.
This has taken forever, but I have created a version of EHCP force that works “off the shelf”.
Its an amalgamation of both the newer version and the older version installers.
There are so many changes to the new installer in regards to email, fixing it without knowing what has been changed is not going to happen.
I have based this version on the old installer, but with the latest version of the EHCP force application, then added some fixes for Ubuntu 24.04, and also copied in a few bits from the new installer.
I am a bit reluctant to publish it, as EHCP force is not my project and I don’t want to upset anybody.
Let me know your thoughts on the matter.
03/04/2025: What is going on with EHCP force email.
The entire courier setup has been changed, no sue why.
Compiling courier from source has always been a bit hit and miss, I have done it a few times.
It does appear on the face of it to have worked when you add the “DEB_BUILD_OPTIONS=nocheck” edit, however when you dig down into the system, you start to see the issues. Despite it all appearing to work emails are not getting sent for example.
Compiling courier from source in this way adds a good 15 or 20 minute onto the installer, which is my opinion is just not necessary.
Again, this is just my opinion, but I think it’s better to compile courier on a separate system, and then simply add the compiled (deb) files to the installer.
One final though is that maybe its time to think about moving over to Dovcot, it’s not that different to set up, and therefore only requires small changes to the installer.
02/04/2025: Ok, I see the problem with EHCP force email.
The “DEB_BUILD_OPTIONS=nocheck” edit, fixes courier-imap.
The problem is that “courier-authdaemon” is not getting installed as it needs courier-authlib, but courier-authlib has not properly been installed.
I am not going to lie, I am a little confused as to why EHCP force was published in this mess.
02/04/2025: EHCP force still not right with “DEB_BUILD_OPTIONS=nocheck”
I am doing some more testing, but even with the “DEB_BUILD_OPTIONS=nocheck” edit, there does still appears to be an issue with email in EHCP force.
27/03/2025: EHCP force needs “DEB_BUILD_OPTIONS=nocheck”.
The courier (email) compile section of the EHCP force installer can be fixed by changing a single line in the file called “build_and_install_courier_imap_deb_packages.sh”.
Line number 75 says the following.
./courier-debuild -us -uc
If you change this line to:-
DEB_BUILD_OPTIONS=nocheck ./courier-debuild -us -uc
Courier will actually get compiled and installed!
The file is located in the “scripts” folder within EHCP force.
27/03/2025: There has been a “phantom update” for EHCP force.
The reason I am calling it a phantom update is that it is not listed on the EHCP force website.
It would appear that EHCP force was updated on the 13/03/2025.
Having checked it out, the courier (email) compile part of the installer still does not work.
This update does not fix Fail2ban either as it still does not have the power to write to the IP tables.
13/03/2025: Absolutely bizarre update for EHCP force.
EHCP force released an update on the 28th February 2025, which DOES NOT fix courier (email) and Fail2ban on Ubuntu 24.04.
I do not understand.
08/01/2025: I have published the fix for the EHCP force new installation bug.
If you did inadvertently do a new installation of the latest version of EHCP force THIS POST, tells you how you can fix it.
08/01/2025: You CAN upgrade to the December 2024 version of EHCP force with breaking anything.
I have just done a test, and upgrading to the newer version of EHCP force does not break anything.
So it is just new installations that fail with email and Fail2ban problems.
This is very interesting indeed.
08/01/2025: Not only is email broken in the Ubuntu 24.04 version of EHCP force, so is Fail2ban (New installations).
The installation of Fail2ban on the new Ubuntu 24.04 version of EHCP force, does not have the power to write to the IP tables, thus it is not able to ban an IP address. This is due to a configuration error.
This issue is an easy fix at least. (My Post install Fail2ban fixing script can fix it).
08/01/2025: It is possible to fix the latest version of EHCP force (Email) from the command line.
I have managed to fix courier from the command line, but it is quite complicated.
In mid-2024, I compiled a courier-imap installer package file (deb), from the latest version of the courier source code.
This version also includes courier-pop.
Here is how I fixed it.
1. Clean out all the remains of the failed courier install.
2. Reinstall my new version of courier from deb files and also apt packages.
3. Reconfigure Courier for MySQL and EHCP force.
Let me know if you want me to publish this fix, like I said it is quite complicated to do.
07/01/25: I have changed the EHCP force install script on the site, the script now installs the previous version of EHCP Force.
This should be just a temporary until this issue is fixed.
The problem with the latest version is that the courier email system is not properly installed, which means that you cannot access your email. This is a problem on new installations only, as upgrades do not appear to be effected.
06/01/25: There are major issues with the latest update for EHCP force (New installations).
Please do not install it yet.
I am looking into it.
05/01/25: On the 19th December 2024 EHCP force was updated for Ubuntu 24.04, I have not had chance yet to test the new update, but it looks like that EHCP force Pre / Post-Install Scripts may no longer be needed.
When I have had chance to do some further testing, I will let you know my findings.
31/08/24: The 30/08/2024 update for EHCP force fixes the bug introduced in the 24/07/2024 release.
The 30/08/2024 update for EHCP force, also fixes the subdomain deletion bug and the Squirrelmail update bug.
28/07/24: If you updated EHCP force to the 24/07/2024 release, you may have a problem.
After the update is installed, you may see this, when you are navigating through the EHCP force control panel.
I am quite shocked the author of EHCP force has done this to be honest.
Anyway, I have created THIS FAQ, on how to fix it.
28/07/24: There is a major problem with the latest version of EHCP Force.
DO NOT UPDATE EHCP FORCE TO THE 24/07/2024 VERSION
27/06/24: Major update to the Spamassasin user interface post.
I have made a major change to the method of setting up a user interface for Spamassasin (please see the post for details).
I have also created a new FAQ, on how to modify your Spamassasin UI, to match the new setup.
19/06/24: New SMTP auth Issue.
Some users have reported to me that after running an EHCP force update, SMTP auth stopped working again (unable to send any emails).
It can be fixed by running the SMTP auth (post EHCP force install) fixing script again using this command in PuTTY.
sudo bash smtpauthfixv2.sh
The above assumes you did not delete the script from your system, if you did, please refer to THIS POST for instructions on how to download it again.
12/06/24: New Fail2ban repair script.
I have re written the EHCP force post install, Fail2ban fixing script to make it a bit more like the others, with some better error trapping etc.
I have also revamped the post a little, just to make it a bit easier to follow.
12/06/24: Bizarre update released for EHCP force.
The author of EHCP force released an update on 11/06/24, what’s bizarre about it is that it is not an update for Ubuntu 24.04 which is what people tell me they are waiting for.
Note: My EHCP force update script was updated today, It is important to use the new script or you risk breaking SMTP auth, and Squirrelmail.
30/05/24: Yes, you guessed it, I made a new SMTP auth repair script.
Decided to go with saslauthd instead of the courier-authdeamon.
Please note the file name has changed, see the post for details.
If you want to change to saslauthd, you can run this script even if you ran the old one, as will undo the settings for the courier-authdeamon, and change the SMTP auth method to saslauthd.
25/05/24: Just as a test, I was able to fix the existing SMTP auth method on my test bed.
Currently my SMTP auth fixing script, changes the authentication method from saslauthd to the courier-authdeamon.
I was wondering if it was possible to fix the existing method in EHCP force, and the answer is a big YES.
Not, sure yet if I am going to change the script, as my method is just as good.
23/05/24: Completely re-written the EHCP force pre install script.
Where, I have had no reports of the old script failing, it occurred to me that if the script did fail it would not tell the user, this could mean a lot of wasted time installing EHCP force, only to find out that the email did not work.
The script now checks each step as it goes, and reports any failures to the user.
16/05/24: I have now changed the (EHCP force post install) SMTP auth fixing script so that it also adjusts EHCP force, to stop it undoing the edits made by the script.
EHCP force should now not have the power to break SMTP auth (for sending emails), after the script has been run.
15/05/24: Found the problem with SMTP auth, it is NOT my script.
Whenever you change the main system options in the EHCP force control panel, the postfix configuration in “Fixed”, thus undoing our edit.
I am working on a fix for this.
14/05/24: I have made a slight change to smtp auth fixing script (EHCP force post install script).
Hopefully there will be no more issues, but only time will tell.
14/05/24: Added a note to the EHCP force post install scripts topic as a user reported, that she was still not able to send email, and entering these commands in PuTTY one by one fixed it. I have not been able to recreate this issue.
If effected though you MUST run both the EHCP force post install scripts(one time only, per server), before trying this fix.
Its not a good idea to try and run the scripts again, as it can mess things up, big time.
sudo su
service postfix stop
echo 'pwcheck_method: authdaemond' > /etc/postfix/sasl/smtpd.conf
echo 'mech_list: plain login' >> /etc/postfix/sasl/smtpd.conf
echo 'allow_plaintext: true' >> /etc/postfix/sasl/smtpd.conf
echo 'authdaemond_path: courier-authdaemon-socket' >> /etc/postfix/sasl/smtpd.conf
service postfix start
exit
11/05/24: Wow, the amazing people who write Fail2ban, have already created a new version that works on Ubuntu 24.04 without messing about with Python versions. I have completely changed my EHCP Force post install Fail2ban fixing script, it now just upgrades Fail2ban (and updates the Fail2ban config).
08/05/2024: The new site is still a work in progress.
As my regulars will already know, I am constantly finding and correcting spelling and grammar errors on the site. Also, where everything should be working, I am still in the process of testing it all, so if something is wrong or does not work, it may get fixed soon.
06/05/2024: Sorry that EHCP GN is not done yet.
I did not understand the enormity of the task when I took it on, and I am just short of time to dedicate to it.
As I am not an established developer, everything takes me longer as I have to spend time researching problems and how to fix them.
05/05/2024: I am worried about EHCP force.
I have a concern as to why EHCP force has not been updated for Ubuntu 24.04.
I really hope that EHCP force has not been abandoned.
The author of EHCP force does not get paid for his amazing work, so I hope that he has just been busy with more important things, or something on those lines.
Please do not contact him, as he works for free and I would hate to think that he is getting flak from something I have said or done.