DirectAdmin 1.702

Hi all,

Starting from version 1.702, sent email limits now also count local-to-local emails (changelog reference). Previously, emails sent between local accounts on the same server were not counted toward the daily sending limit.

This is causing problems for several of my clients. Many of them have forwarders set up to route incoming mail to other departments within the company (internal forwarding). With this change, all of that internal traffic now counts against the daily limit, which can quickly exhaust the quota even though no mail is actually leaving the server.

My questions:

  1. Is there a way to disable this behavior, so that local-to-local emails are excluded from the sent email count again?
  2. If not, would it be possible to make this an optional/configurable setting (e.g. a per-domain or server-wide toggle to not count local mail)?
I understand the reasoning behind counting all mail, but for setups that rely heavily on internal forwarding, the previous behavior made much more sense. A configurable option would be ideal so admins can choose based on their use case.

Thanks in advance for any guidance.
 
fln said:
Thanks @zEitEr. A new build is released with the following changes:

1. RoundCube installer will make sure /var/html/webapps directory have fixed permissions, it used to depend on user umask.
2. Fixed PHP patches order to resolve the conflict with lsapi for PHP 7.4, PHP 8.0 and PHP 8.1

The files.directadmin.com mirror automatically gets new files only a couple of days after release and MariaDB pushed out new versions only yesterday. Anyway we manually uploaded the RPMs for now.
Click to expand...


We are also seeing the Roundcube 1.7.0 404 issue on CloudLinux servers.

In our case, the problem seems related to CageFS symlink protection.

Current layout:

/var/www/html/roundcube -> ../webapps/roundcubemail-1.7.0-XXXX/public_html

When CageFS symlink protection is enabled, Roundcube returns 404. When it is disabled, Roundcube works.

We need a solution that keeps CageFS symlink protection enabled and allows Roundcube to work without issues. It should also survive future DirectAdmin / CustomBuild Roundcube updates, so the problem does not return after every update.

Could you please check if the new Roundcube symlink/path layout is fully compatible with CloudLinux CageFS, or suggest the correct permanent configuration?

Environment:
DirectAdmin 1.702
CloudLinux 8
CageFS enabled
LiteSpeed
 
You must log in or register to reply here.
Back
Top