Sender Quota Overview

Sender quotas allow Faspex admins to control the maximum volume of data that specific Faspex users can send to specific recipients over a rolling period, based on settings at the global and user account levels.

For example, admins can prevent all Faspex users from individually sending more than 25 GB over a twenty-four hour period, while allowing some of those users to send an unlimited amount of data.

Sender quotas can be applied based on who is sending, who is receiving, or both.

Senders and receipients can be exempted from sender quota enforcement based on their email address domain name.

Sender Quota Verification Logic

Faspex uses this logic to determine whether to verify sender quotas for a package being sent:

Data Allowed for a New Package When Enforcing Sender Quota

If the sender quota is being verified for a package, then the maximum number of bytes (in MB) allowed for the package is defined by the global sender quota configuration and possibly the sender's sender quota configuration:

Global and Current Account Sender Quota Configurations	Package Maximum Size
Global sender quota = Enabled	Global default sender quota minus bytes already sent by that user to non-whitelisted recipients within the current rolling period
Global sender quota = Default Sender's Sender Quota Override is selected and the Sender Quota value has a value greater than `0` MB	User account sender quota minus bytes already sent by that user to non-whitelisted recipients within the current rolling period
Global sender quota = Default Sender's Sender Quota Override is selected and the Sender Quota value has a value of `0` MB	`0` MB (no package can be sent)
Global sender quota = Default Sender's Sender Quota Override is selected and the Sender Quota value is empty	Unlimited (normally based on file storage)

Note: Faspex takes into account all user data sent within the current period (duration configured by Sender quota duration), even if sender quotas were not yet enabled. For example, a user sends 100 MB of data in the current period. An admin then enables sender quotas with a maximum of 4000 MB. The user has 3900 MB available in the current period.

Over-Quota Warnings and Enforcement

When users start the process of sending a new package, Faspex warns users as soon as possible that the package might go over quota:

If the user is over quota, Faspex notifies the user when they attempt to create a new package that they cannot send more data until the end of the current rolling period.
Note:
Faspex cannot determine the size of the package before its files are uploaded. Instead, Faspex relies on the HST Server node to pre-calculate the package size. Faspex uses that information to determine if senders will reach or exceed their sender quotas. The node must have the pre_calculate_job_size enabled (set to yes or any) for Faspex to use this information.

If the option is disabled (set to no), Faspex determines the size of the package as the transfer goes and stops the transfer when it determines the sender has reached or exceeded the sender quota. In the worst-case scenario, Faspex might not stop a transfer until most of the package is transferred.

Therefore, IBM Aspera recommends enabling the pre_calculate_job_size setting on the HST Server node (by default, set to any).
If the user is still under quota, Faspex allows the user to initiate a transfer. When the package size reaches or exceeds the sender quota, Faspex notifies the user that the user went over quota. Faspex then cancels the transfer and deletes the package.
Note:
During a transfer, Faspex checks a sender's available quota every 5 seconds. The polling frequency can allow some packages to go beyond the quota limit if Faspex does not check the in-transfer package at least once. For example, a user creates a new package while under quota and the transfer completes in under 5 seconds due to a small, package size and a high, transfer speed. Nevertheless, that package size is accounted for in the user's sender quota for any, future quota verification.

Sender Quota Exceptions

Admins can exempt individual accounts from sender quota enforcement by overriding the account sender quota and leaving the sender quota value empty. That requires the global sender quota setting to be set as Default.

Admins can also choose to whitelist email domains to exempt senders or recipients from sender quota enforcement based on their email addresses.

Note:

If users change their email address, that can impact their inclusion in sender or recipient whitelists, and therefore also impact sender quota enforcement.

This can be prevented by disabling the Allow users to change their email address setting (Server > Configuration > Security > Allow users to change their email address).