I've checked both sites through my browser:
So, if the problem persist for you, it could come from your browser.
Thread closed.
We don't provide any support for the unstable i-MSCP versions (git versions). I'll test the behavior and fix the issue if any, according your report but no solution will be given for your current installation.
That would be awesome if you could report that unexpected behavior on our bug tracker. When an account is removed, the CronJobs plugin should also remove the cron jobs that belong to that account. This is at least the expected behavior when the plugin is enabled and us working correctly.
A problem can arises if the cronjob plugin was disabled or wasalready in error state. If so the cron jobs won't be removed automatically.
Anyway, we should add a fix here to avoid such errors. If the owner (unix user) of some cron jobs doesn't longer exists on the system (orphaned cronjobs), those should be removed from the database without further treatment. In a perfect world, this should be achieved with a fk constraint (cascade deletion) but the current i-MSCP database schema make this difficult.
Thank you.
Dont take this the bad way, but that theme looks way smoother than the current default one.
Good job.
This doesn't hurt me in any way. First because I'm not the author of the current layout, and secondly, because I admit that I'm not a designer at all 
There are people that are good for designing new layout, other for code architecture... That why sometime we need more than one people working on a project.
Publication on my facebook regarding this works https://www.facebook.com/nuxwin/posts/10215325832759269
Good morning,
Check your orders on the WHMCS side. There is surely one without the required domain name which you need to delete first. We encoutered the same issue konzeptplus office.
When you setup a product that make use of the ImscpHosting module on the WHMCS side, you need make sure that a domain name will be required.
On the module side, we should add a check for that specific case instead of assuming that a domain is always passed-in (input data). This will be fixed in next WHMCS plugin version.
Thanks Laurent.
I think the the SpamAssassin Feature should be implemented in the next SpamAssassin version (Dropping the Spam).
Adding RBL with the gui is better than to use a listerner..
Just my 2 cent
This is not so easy to implement something at the UI side because there nothing on the backend side that allows to update the postfix configuration file. If we want do that, we need add another layer on to backend side which would allows to override default configuration, even after i-MSCP installation. This is what we are doing with plugins in fact (backend side).
I don't really understand why it would be so tedious to make use of a listener in that specific case. The i-MSCP Postfix server implementation provide a routine that make edition of the main.cf file very easy. As a sysadmin, editing a single file to remove or adding RBL servers is not so hard, isn't it?
BTW: You can keep your 2 cents in your pocket. I do not do the sleeve. Best would be to propose hundred of dollars... 
Good morning,
When a customer setup email forward (such as forwarding to gmail, hotmail)... best would be to not forward the mails when they are flagged as SPAM. I think we could make something like described here: https://aikar.co/2014/09/05/fi…mail-postfixspamassassin/
What I would want is: If the mail is flagged as SPAM, we deliver it locally but we don't forward it. I need have a look at the Postfix documentation for that. Of course, if the SPAM get forwarded to services such as gmail, hotmail, you'll get blacklisted very faster because their system will report you as a spammer... That's a real and big problem.
Regarding your idea to add a feature for RBL servers, you can do that through listener file... Don't forget that for most of RBL, you're rate limited.
mikerhyner konzeptplus That's the problem we talked about and which we need to fix.
