| SYSTEM INFORMATION | |
|---|---|
| OS type and version | Ubuntu 24.04.5 LTS (GNU/Linux 6.8.0-139-generic x86_64) |
| Usermin version | 2.570 |
| Webmin version | 2.670 |
| Virtualmin version | 8.2.0 GPL |
| Webserver version | nginx/1.24.0 (Ubuntu) |
| Related packages | postconf mail_version = 3.8.6 |
| SpamAssassin version 4.0.0 | |
| running on Perl version 5.38.2 |
Hello there,
I hit an issue with quota, arising with an e-mail account that has Unlimited quota, which is puzzling:
/var/log/procmail.log reports:
Time:1790338283 From:xxxxxxx@xxxxxxx.org To:yyyyyyyy@yyyyy.com User:yyyyyyyy@yyyyy.com Size:832279 Dest:/dev/null Mode:None
Disk quota for yyyyyyyy@yyyyy.com has been reached.
procmail: Program failure (73) of "/etc/webmin/virtual-server/lookup-domain.pl"
From xxxxxxx@xxxxxxx.org Fri Sep 25 22:11:46 2026
Subject: zzzzzzzzzzz
Folder: /dev/null 4479700
The server is in production so I’m wary to fiddle to reproduce, but here’s as much detail I can think of for now, for background:
xxxxxxx@xxxxxxx.org is a CCTV NVR sending alert messages which can be quite large. Sometimes up to 10MB.
Previously, xxxxxxx@xxxxxxx.org was whitelisted in /etc/spamassassin/local.cf under welcomelist_from but I removed that line, and placed the address instead under the yyyyyyyy Virtualmin user for the yyyyy.com domain.
I’m not at all sure, but maybe this change caused a temporary backlog of some kind (?), because I could see a list of files in /home/chroot/nnnnnnnnnnnnnn/./home/yyyyy.com/users/yyyyyyyy/Maildir/new/, but asking to fetch them over POP3 would return “No new messages.” The files just seemed to sit there.
The total size of the files in that path was about 60MB – not larger than the parent domain’s quota of 12GB, and also weird because the e-mail account is set to Unlimted quota. So not sure how that’s tripping the error in procmail log.
The settings I have in Virtualmin → Email Settings → Spam and Virus Scanning are like so:
which blackhole the messages (/dev/null) – but I’m puzzled on the error mesage in /var/log/procmail.log
Testing the configured port that was listening and responded fine:
$ nc -v -w 3 127.0.0.1 11000
Connection to 127.0.0.1 11000 port [tcp/*] succeeded!
Double checked mailbox quotas, like so:
I was concerned to miss pending alerts, so to get around the problem, I manually cleared out /home/chroot/nnnnnnnnnnnnnn/./home/yyyyy.com/users/yyyyyyyy/Maildir/new/ which seemed to restore normal workings… Just reporting in case this is a weird edge case bug with quota, or some such!
