Maximum File Size Changed but Not Applied

Maximum File Size Was Changed, but the New Limit Is Not Applied

Problem

You have changed the maximum file size in the system settings, but users are still unable to send or upload larger files.

This behavior usually occurs when active policy rules are still using the old upload limits.


Cause

In Cryptshare, policy rules override the general system settings.

This means:

  • Changes made in the default or global settings are not automatically applied to existing policies.
  • If a user or group is assigned to a policy, the limits defined in that policy take precedence.

As a result, the global upload limit is ignored.


Solution

The maximum file size must also be adjusted in the active policy rules.


How to Adjust the Policy Settings

1. Open the Policy Settings

Navigate to the following menu in the Admin Interface:

System Settings → Policy Settings

2. Edit the Relevant Policy

Click the edit icon for the policy you want to modify.




3. Navigate to the Upload Limit Settings

In the configuration wizard, click Next several times until you reach the page:

Retention Period and Maximum Transfer Size


4. Change the Maximum Upload Volume

Adjust the value for:

Maximum Volume per Transfer

to the desired size and click:

Apply

Important

If multiple policy rules are configured, the upload limit may need to be updated in all relevant policies.


Additional Information

  • Policies override the global system settings.
  • Especially check policies assigned to:
    • specific user groups
    • domains
    • sender or recipient rules

Related Articles

  • How to Adjust Policy Settings
  • How Policy Rules Work


Related Search Terms

  • Upload limit not working
  • Maximum file size not applied
  • Maximum upload size ignored
  • Policy overrides upload settings
  • Cryptshare upload limit issue
  • Dateigröße greift nicht
  • Uploadlimit funktioniert nicht
  • Maximale Dateigröße wird ignoriert
  • Policy überschreibt Einstellungen
    • Related Articles

    • Settings Changed, but the New Configuration Is Not Applied

      Problem You have changed a setting in the system configuration, but the new value is not applied for users or specific actions. This behavior usually occurs when active policy rules still contain different or outdated configuration values. Cause In ...
    • File pre-processing errors with ClamAV

      Inhaltsverzeichnis 1 Applies to: 2 Symptoms: 3 Cause: 4 Solutions: 4.1 Check if minimum system requirements are met 4.2 Check if your distribution is up-to-date 4.3 Restart ClamAV service 4.3.1 ClamAV failed to start with "Can't connect to clamd ...
    • Adjusting Policies

      Applies to All versions of Cryptshare Server Symptom The administrator is changing default settings (e.g. maximum size per transfer) in the Administration Interface and the changes are not taking effect. Cause Default settings are used for creating ...
    • Attachments are not stored in the Sent Items folder

      Applies To All versions of Cryptshare for Outlook Problem Attachments are not stored in the sent items folder regardless of the size of the files set for "Do not save outgoing files if.." in the admininterface. Cause The issue is caused by the ...
    • Migrating Cryptshare

      Applies to: All versions of Cryptshare Server Purpose: This article guides you through a Cryptshare Server migration. Solution: Be sure that your Cryptshare Server is running at least version 4.3.0 before proceeding. If not, please update as ...