Fixing Vesta CP Exim Email Incoming error with T=local_delivery defer (-1): Malformed value “0MM”

Applicable for vesta cp 1.0.0-5 version)

If you lately encounter an issue with mail incoming with vesta cp after an auto update took place, your /var/log/exim/main.log shows something similar below-

2021-12-19 03:39:42 1mxheU-000374-0o == R=localuser T=local_delivery defer (-1): Malformed value “0MM” (expansion of “${extract{6}{:}{${lookup{$l$….

Step-1 Finding vesta version

Well the following steps I had to do to solve. Before further proceedings we need to find out vesta version. My particular version 1.0.0-5 is generating this error of receiving email- specially where disk quota of email users had “Unlimited” quota.

Finding vesta version is a bit tricky. You need the paste following bash lines-


create a new bash file anywhere you want , for example /root/ with the name and add the following code to it.

#vestapc version checker
#beta script

# Checking installed vesta version
if [ -d "/etc/sysconfig" ]; then
rpm_format="$rpm_format RELEASE='%{RELEASE}'"
rpm_format="$rpm_format ARCH='%{ARCH}'"
rpm_format="$rpm_format UTIME='%{INSTALLTIME}'\n"
eval $(rpm --queryformat="$rpm_format" -q vesta)
DATE=$(date -d @$UTIME +%F)
TIME=$(date -d @$UTIME +%T)
dpkg_data=$(dpkg-query -s vesta)
pkg_date=$(stat -c "%Y" /var/lib/dpkg/info/vesta.list)
ARCH=$(echo "$dpkg_data"|grep Architecture |cut -f 2 -d ' ')
VERSION=$(echo "$dpkg_data"|grep ^Version |cut -f 2 -d ' '|cut -f 1 -d \-)
RELEASE=$(echo "$dpkg_data"|grep ^Version |cut -f 2 -d ' '|cut -f 2 -d \-)
DATE=$(date -d @$pkg_date +"%F")
TIME=$(date -d @$pkg_date +"%T")
echo $VERSION-$RELEASEand then run the file using

and you will get your current running vesta cp version , for example: 1.0.0-5


Get rid of the “unlimited” quota for your email account. Change it to some value eg 80GB or more and check.

Now check sending email to you cp user account. Hope it’ll work.


One thought on “Fixing Vesta CP Exim Email Incoming error with T=local_delivery defer (-1): Malformed value “0MM”

  1. Thanks so much for this!
    There is definitely a Vesta bug with the ‘unlimited’ setting. I had a mailbox w/5.89GB and it was jammed for a month until I set it with ‘100GB’

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.