1

Topic: Iredapd - sending limits for two periods

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version 1.7.4 MARIADB edition
- Deployed with the downloadable installer
- Almalinux 9
- Store mail accounts in MariaDB
- Web server Nginx
- Manage mail accounts with CLI and MariaDB
====

G'day All,

We've just installed a test installation of iredmail to check whether it will provide us with basic functions we require on our email servers.

We immediately hit a gotcha related to setting email sending limits which we've always had in place on all our servers.

We require an outbound sending limit of 120 items per hour per user, and also an outbound sending limit of 500 items per day per user.

Initially we assumed this would be easily solved by using the iredapd MySQL database with...

INSERT INTO throttle (account, kind, priority, period, max_msgs) VALUES ('@example.com', 'outbound', 50, 3600, 120), ('@example.com', 'outbound', 50, 86400, 500);

However, due to the designed key structure, that of course failed with...

ERROR 1062 (23000): Duplicate entry '@example.com-outbound' for key 'account_kind'

We tried a kludgy workaround of...

INSERT INTO throttle (account, kind, priority, period, max_msgs) VALUES ('@example.com', 'outbound', 50, 3600, 120), ('@.', 'outbound', 50, 86400, 500);

However, then only the first rule was applied. Users were correctly limited to sending 120 emails per hour, but they could send at that rate for every hour of the day and exceed the 500 per day limit.

Is there a trick to this, or is this a genuine limitation?

Thanks for any advice you can provide.

Best regards,

LBJ

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: Iredapd - sending limits for two periods

Hi,

iRedAPD uses the first matched throttle (SQL query with 'ORDER BY'). It doesn't support throttling as you described.