I am getting weird messages from some of the subscribers on vchkpw list when I 
post to the list ([EMAIL PROTECTED])

Below are two examples.

----- Forwarded message from Gail Davis <[EMAIL PROTECTED]> -----
    Date: Tue, 09 Sep 2003 19:47:51 -0700
    From: Gail Davis <[EMAIL PROTECTED]>
 Subject: Re: [vchkpw] Quota problem: negative values in
        Maildir/maildirsize (Relocating)


My office space has been relocated. I will be in temporary office space until 
November 1, 2003. The temporary office space will not have phone lines or e-
mail access. I will be receiving phone calls on my cell phone (559) 908-5685. 
I will be checking my e-mail but my access to it will be intermittent. I'm 
sorry for any inconvenience this may cause. Thanks for your patience. 


----- End forwarded message -----

Second message claiming I was reported for spamming:

----- Forwarded message from Prodigy Abuse Department <[EMAIL PROTECTED]> --
    Date: Tue, 9 Sep 2003 21:45:32 -0500 (CDT)
    From: Prodigy Abuse Department <[EMAIL PROTECTED]>
Reply-To: Prodigy Abuse Department <[EMAIL PROTECTED]>
 Subject: [ ABU1063161914072 ] [vchkpw] Quota problem: negative values in 
      To: Tim Hasson <[EMAIL PROTECTED]>

     Thank you for writing to SBC Internet Services Policy Group. 
We apologize for the inconvenience you have experienced. This is an auto-
generated response designed to let you know that we have received your report, 
which will be investigated personally by one of our Support Representatives 
within 48 hours. Your report is important to us and we will treat it 
accordingly. Please note that we can only take action with SBC Internet user's 
accounts (which have SBC Internet IP addresses), and not those with any other 
IP address.

You will not receive another message from us unless we need to request more 
information from you to further our investigation. Please do not respond to 
this e-mail, as any messages sent to this particular address by using 
the "Reply" button will not be read. We appreciate your understanding that due 
to our privacy policy, we will not report back to you about any action taken 
against SBC Internet users. However, we want to assure you that we will take 
appropriate action against SBC Internet users who have violated the SBC/Yahoo 
Terms of Service or the Acceptable Use Policy

In order for us to process your complaint, please check that you have 
submitted all of the following information for each type of incident:

Unsolicited Commercial/Bulk Email ("Spam"):
- FULL message headers
- Subject line exactly as it appears in the original message (i.e. 'Re: Make 
- Trimmed body.  Send only as much of the text as needed to show the e-mail's 
- Limited commentary.  We understand your frustration with Spam, but the less 
time we spend reading your email, the more time we have to fight Spam.

If we determine that the Spam originated from another ISP, we may refer the 
matter to the respective ISP.

Intrusion/Disruption Attempts (Trojans, "Hacks", Port Scans, etc.)/ Denials of 
Service (ICMP "floods", brute-force connections, etc.):
- Full log files containing all of the information below:
      - IP Address of intruder (or the DNS name pointing to said address)
      - Date/Time Stamp with ZONE (either numerical [-0600] or alpha [CST])
      - Protocol/Port used (either numerical [25] or alpha [SMTP])
      - Number of instances of each packet type received

Newsgroup violations:
- FULL message headers (including NNTP and Xtrace information)
- Subject line exactly as it appears in the original message (i.e. 'Re: Make 
- Trimmed body.  Send only as much of the text as needed to show the e-mail's 
- Limited commentary.  As with Spam, the less time we spend reading your 
email, the more time we will have to take care of the problem.

Please keep in mind complaints could take up to 48 hrs to process.

Many software packages will log and report what they construe to be suspicious 
behavior.  These reports are only as good as the software configurations and 
tend to err on the paranoid side. Submissions generated by such software in 
which relatively minor errors are reported (i.e. a single ICMP packet, UDP 
frames from ICQ, DNS packets) will be discarded without response from SBCIS 
due to the volume of such requests received.

SBCIS does not tolerate abusive Internet behavior, and will take all steps 
reasonably necessary to enforce the Terms of Service (ToS) and Acceptable Use 
Policy (AUP).  We will not supply you with any details relative to our other 
customers or users unless compelled by law to do so.  If you wish to obtain 
such information, you must first obtain a valid subpoena, court order, or 
other valid and enforceable legal instrument allowing you to do so. 

You are responsible for securing and protecting your own computer system and 
network.  SBCIS does not provide anti-virus or virus recovery services.  You 
should contact the manufacturer of your computer, or a qualified provider of 
virus recovery services, in order to obtain assistance with this matter.

For copyright issues, please send all correspondence to [EMAIL PROTECTED]

For our DMCA Agent contact information, please see our designated DMCA Agent 
in our Terms of Service located at http://sbc.yahoo.com/terms/

Customer Care/Billing:
If you have questions or need assistance regarding an account or billing issue 
please contact our Customer Care Department by calling 1-866-SBC-DIAL for SBC 
Yahoo! Dial subscribers or 1-877-SBC-DSL5 for SBC Yahoo! DSL subscribers.

Terms of Service: http://sbc.yahoo.com/terms/

Acceptable Use Policy: http://support.sbcglobal.net/legal/aup.shtml

Thank you,
SBCIS Policy Department 

--------------------Original Email Message--------------------

>From [EMAIL PROTECTED] Tue Sep  9 21:45:14 
Received: from pimout2-ext.prodigy.net (pimout2-int.prodigy.net 
        by abuse-int.prodigy.net (8.12.9/8.12.9) with ESMTP id h8A2j5uv029074
        for <[EMAIL PROTECTED]>; Tue, 9 Sep 2003 21:45:06 -0500 
Received: from vmf.prodigy.net (vmf-ext.prodigy.net [])
        by pimout2-ext.prodigy.net (8.12.9/8.12.3) with ESMTP id h8A2lD9T163692
        for <[EMAIL PROTECTED]>; Tue, 9 Sep 2003 22:47:14 -0400
X-Header-NoReverseIP: IP.name.lookup.failed[]
X-Originating-IP: []
Received: from ns1.inter7.com ([])
        by vmf.prodigy.net (8.12.9/8.12.3) with SMTP id h8A2l2nm396188
        for <[EMAIL PROTECTED]>; Tue, 9 Sep 2003 22:47:06 -0400
Received: (qmail 25965 invoked by uid 511); 10 Sep 2003 04:01:31 -0000
Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
Precedence: bulk
List-Post: <mailto:[EMAIL PROTECTED]>
List-Help: <mailto:[EMAIL PROTECTED]>
List-Unsubscribe: <mailto:[EMAIL PROTECTED]>
List-Subscribe: <mailto:[EMAIL PROTECTED]>
Delivered-To: mailing list [EMAIL PROTECTED]
Received: from unknown (HELO mx1.aidasystems.com) (
  by evanston.inter7.com with SMTP; 10 Sep 2003 04:01:30 -0000
Date: Tue,  9 Sep 2003 19:46:51 -0700
From: Tim Hasson <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: AiDA WebMail 3.2.1
Subject: [vchkpw] Quota problem: negative values in Maildir/maildirsize

I am using vpopmail-5.2.1, courier-imap-2.0, qmail-1.03. I use both courier-
imapd and courier-pop3d instead of qmail-pop3d.

A few days after I migrated my users from an old mail server to my new nfs 
server, users started getting weird quota reulsts on the webmail quota.
vuserinfo reported 0% for the usage although du -sh on the user's maildir 
reported about 3-4 megs. Looking at maildirsize, there was many lines with 
negative values.
telnetting to the imapserver 143, logging in as the user, and issuing "a001 
getquota ROOT" I get also negative USAGE value.

While googling for something related to this problem, I found only one post:

Mr Sam said:
This can happen if mail gets delivered to a mailbox by a delivery agent that 
does not update the quota tracker. 
Solution: use deliverquota or maildrop to deliver mail, and make sure that 
the quota is correctly specified.

This is not the problem for me however. The only programs that deliver to 
maildirs are vdelivermail, maildrop (both compiled with maildirquota support), 
and qmail-local. I know qmail-local doesn't support maildirquota++ but this 
never was a problem, and I confimed it's not the one causing the problem (read 

So looking at the maildirsize file in the maildirs of users having the 
problem, they all had negative values. So I wrote a little shell script (see 
at the end of this message) that finds those mailboxes with bad maildirsize 
files, deletes them, runs /home/vpopmail/bin/vuserinfo -Q [EMAIL PROTECTED] on 
the accounts for which the maildirsize was deleted to recreate it, and then 
sets the proper permission (uid/gid vpopmail/vchkpw).

This solved the problem. Sending mail from local domain to another local 
domain, or from a remote domain to a local domain both seem to reflect the 
_correct_ size now, and instantaneously.
Therefore it's not qmail-local?

I am suspecting it could be that the file sizes changed slightly when moved 
over to the nfs server on a ext3 partition with a 4096 blocksize. The 
filesystem on the old mailserver was ext2 and default blocksize (redhat 6.2).

Could this possibly confuse courier-imap and cause it to put negatives in 
maildirsize? or is it vdelivermail that was confused?

Any thoughts, ideas?

Best Regards,
Tim Hasson

Here is the script I used to fix the maildirsize files:


echo "[*] Finding maildirsize files..."
sizes="`find domains -name maildirsize`"

echo "[*] Finding bad maildirsize files and saving them in badmaildirsize.tmp"

rm badmaildirsize.tmp

for i in $sizes; do
   if [ ! -z "`grep "-" $i | head -1`" ]; then
      echo $i >> badmaildirsize.tmp

echo "[*] Creating [EMAIL PROTECTED] list for whom we recreate maildirsize"

rm mailboxdir.tmp

# get "domain.com/user" from domain/domain.com/user/Maildir/maildirsize
   sed s/domains.//g badmaildirsize.tmp | \
     sed s/.Maildir.maildirsize//g > mailboxdir.tmp

rm fixemail.tmp

#  change domain.com/user to [EMAIL PROTECTED]
mailboxlist="`cat mailboxdir.tmp`"
for mailbox in $mailboxlist; do
   username="`echo $mailbox | sed s#.*/##`"
   domainname="`echo $mailbox | sed s#/.*##`"
   echo "[EMAIL PROTECTED]" >> fixemail.tmp

rm mailboxdir.tmp # we dont need it anymore

echo "[*] Deleting bad maildirsize files"
deletelist="`cat badmaildirsize.tmp`"
for maildirsize in $deletelist; do
   rm $maildirsize

echo "[*] Recreating deleted maildirsize files"
addresses="`cat fixemail.tmp`"
for emailaddress in $addresses; do
   /home/vpopmail/bin/vuserinfo -Q $emailaddress

echo "[*] Setting owner/group vpopmail/vchkpw on maildirsize files"
newmaildirsizefiles="`cat badmaildirsize.tmp`"
for newmaildirsize in $newmaildirsizefiles; do
   chown vpopmail:vchkpw $newmaildirsize

----- End forwarded message -----

Tim Hasson
Consultant, AiDA Systems
(209) 639-2989 Voice

Reply via email to