I think that most admins do not really care about physical disk usage as long as it's not exceeded, and most service providers prefer calculating quota against apparent usage instead of real usage, so they can charge you for that.
Aki
On 8.2.2020 18.16, Martynas Bendorius wrote:
Doesn't it currently confuse them? Because they'd reach their quota, while actually there would be a lot of disk space left :) + their whole mailbox could take a lot more space due to indexes and other files in the filesystem, and quota would not be reached.
Also, I've dovecot is using fstat's st_size parameter. This is not "correct", in that the actual space used on disk is always higher.
If we count the number of 512B blocks used (st_blocks), and multiply by 512 to get the true disk usage.
I'll be looking forward for your feedback/ideas.
Thank you!
-- Best regards, Martynas Bendorius
On 2020-02-08, at 17:57, Max Kostikov max@kostikov.co wrote:
I think these changes will confuse users because calculated quota wouldn't be equals with total messages sizes.
Marsistynas Bendorius писал 2020-02-07 11:07:
Is there any reason why dovecot relies on S= instead of real disk size email takes? there, including indexes and mails without S=... if we'd read
- compressed mails take less than than the S= specified
- we could avoid using "S=" for the lookups and count every file
filesizes
-- With best regards, Max Kostikov
W: https://kostikov.co | DeltaChat: mk@eprove.net