[toaster] maildirsize updates (not)
Ok, I can't figure out what is going on. I have the latest toaster install up and working fine but maildirsize doesn't seem to keep up with incoming email. What exactly is supposed to cause maildirsize to be updated? Does it happen each time an email is delivered? maildirsize is being written to but it appears to only happen some of the time. For example here is the maildirsize on a new mailbox: 10485760S,1000C 222690 52 -94881 -1 -2954 -1 -8042 -1 -4420 -1 -5892 -1 -1820 -1 -1341 -1 -42350 -1 -1350 -1 -2515 -1 -4923 -1 -1788 -1 -39311 -1 -2197 -1 -1754 -1 Now this mailbox has over 150 messages in it and that is all that maildirsize has in it. Am I missing something or does this seem not right? FYI, this mailbox (postmaster) has only been opened via squirrelmail. It has never been popped. David Shirley http://www.webquarry.com
Re: [toaster] maildirsize updates (not)
David M. Shirley wrote: Ok, I can't figure out what is going on. I have the latest toaster install up and working fine but maildirsize doesn't seem to keep up with incoming email. What exactly is supposed to cause maildirsize to be updated? Does it happen each time an email is delivered? maildirsize is being written to but it appears to only happen some of the time. For example here is the maildirsize on a new mailbox: 10485760S,1000C 222690 52 -94881 -1 -2954 -1 -8042 -1 -4420 -1 -5892 -1 -1820 -1 -1341 -1 -42350 -1 -1350 -1 -2515 -1 -4923 -1 -1788 -1 -39311 -1 -2197 -1 -1754 -1 Now this mailbox has over 150 messages in it and that is all that maildirsize has in it. Am I missing something or does this seem not right? FYI, this mailbox (postmaster) has only been opened via squirrelmail. It has never been popped. ANY agent that delivers mail to this Maildir, be it qmail-local, vdelivermail, procmail, maildrop, or whatever, MUST be Maildir++ aware. Otherwise, maildirsize will be ignored. I'm not a procmail patch for Maildir++. However, maildrop by default does not compile with quota support. You need to compile that in. Perhaps you're using maildrop filters and maildrop is lacking quota support? Regards, Bill Shupp
Re: [toaster] maildirsize updates (not)
Bill Shupp wrote: I'm not a procmail patch for Maildir++. Not sure what I was thinking there.. this should read: "I'm not aware of a Maildir++ patch for Maildir++ support". Sorry. Bill
Re: [toaster] maildirsize updates (not)
No, no maildrop. It's a virgin toaster straight from your http://www.shupp.org/toaster/ page. Nothing optional was added except for one thing: I substituted qmail-toaster-0.6-1+greylisting.patch for the qmail-toaster-0.6-1.patch.bz2 patch. After making that sustitution I could apply the chkuser-0.6.patch (it failed in chunk 4 if memory serves correct) but I don't see where those substitutions would affect the behavior of updating maildirsize. Does maildirsize get updated each time an agent touches the Maildir in any way or only under certain conditions? On Friday, May 14, 2004, at 09:51 AM, Bill Shupp wrote: ANY agent that delivers mail to this Maildir, be it qmail-local, vdelivermail, procmail, maildrop, or whatever, MUST be Maildir++ aware. Otherwise, maildirsize will be ignored. I'm not a procmail patch for Maildir++. However, maildrop by default does not compile with quota support. You need to compile that in. Perhaps you're using maildrop filters and maildrop is lacking quota support? David Shirley http://www.webquarry.com
Re: [toaster] maildirsize updates (not)
> No, no maildrop. It's a virgin toaster straight from your > http://www.shupp.org/toaster/ page. Nothing optional was added except > for one thing: > > I substituted qmail-toaster-0.6-1+greylisting.patch for the > qmail-toaster-0.6-1.patch.bz2 patch. After making that sustitution I > could apply the chkuser-0.6.patch (it failed in chunk 4 if memory > serves correct) but I don't see where those substitutions would affect > the behavior of updating maildirsize. > > Does maildirsize get updated each time an agent touches the Maildir in > any way or only under certain conditions? If mail is delivered or removed, the file gets updated. Also, if you are checking the quota and the file size if too big, or the file is more than 15 minutes old, it will get recalculated. Regards, Bill
Re: [toaster] maildirsize updates (not)
Hmm. It does seem to get updated if squirrelmail deletes a message. The problem appears to happen when qmail delivers a message to an alias for that box. Perhaps my qmail-local is not patched for Maildir++ support. Is that patch included in the qmail-toaster-0.6-1+greylisting.patch? Your site's description of that patch implies that it is but I don't know how to check for sure if it is in there On Friday, May 14, 2004, at 10:57 AM, Bill Shupp wrote: If mail is delivered or removed, the file gets updated. Also, if you are checking the quota and the file size if too big, or the file is more than 15 minutes old, it will get recalculated. David Shirley http://www.webquarry.com
Re: [toaster] maildirsize updates (not)
> Hmm. It does seem to get updated if squirrelmail deletes a message. > The problem appears to happen when qmail delivers a message to an alias > for that box. > > Perhaps my qmail-local is not patched for Maildir++ support. Is that > patch included in the qmail-toaster-0.6-1+greylisting.patch? Your > site's description of that patch implies that it is but I don't know > how to check for sure if it is in there It should be. But if the maildirsize file is not updated when SquirrelMail deletes a message, then you may have other problems. Who owns maildirsize? You should probably run all agents that touch it as vpopmail. Regards, Bill
Re: [toaster] maildirsize updates (not)
Maildirsize is owned thus: -rw-r--r--1 vpopmail vchkpw196 May 14 12:52 maildirsize qmail-local runs as vpopmail, still no updates are made. I checked the qmail-toaster-0.6-1+greylisting.patch and it DOES contain the Maildir++ patch. The patch applied fine but how can I verify that it is in the compiled qmail-local? I'm not having any trouble with squirrelmail but I do see a bunch of these in /var/log/maillog: May 14 11:21:43 mailexp imapd: LOGIN, [EMAIL PROTECTED], ip=[:::127.0.0.1], protocol=IMAP May 14 11:21:43 mailexp imapd: Failed to create cache file: maildirwatch ([EMAIL PROTECTED]) May 14 11:21:43 mailexp imapd: Error: Input/output error May 14 11:21:43 mailexp imapd: Check for proper operation and configuration May 14 11:21:43 mailexp imapd: of the File Access Monitor daemon (famd). Does that give any clue? I wouldn't think that would affect the operation of qmail-local which I understand is responsible for updating the maildirsize file when delivering a message to an alias. When a message is delivered, I see this in the qmail log: @400040a5282720d5e81c new msg 3532276 @400040a5282720d6075c info msg 3532276: bytes 8871 from <[EMAIL PROTECTED]> qp 25086 uid 89 @400040a5282720fc0dbc starting delivery 453: msg 3532276 to local [EMAIL PROTECTED] @400040a5282720fc252c status: local 1/10 remote 0/20 @400040a5282721710af4 delivery 453: success: user_does_not_exist,_but_will_deliver_to_/home/vpopmail/domains/ DOMAINREMOVED/postmaster//did_0+0+1/ @400040a5282721712e1c status: local 0/10 remote 0/20 @400040a52827217135ec end msg 3532276 Obviously, I've munged the logs a bit to obscure the email address in question but it should still be clear what it says. I see no problem in that log entry. Do you concur? On Friday, May 14, 2004, at 11:23 AM, Bill Shupp wrote: Hmm. It does seem to get updated if squirrelmail deletes a message. The problem appears to happen when qmail delivers a message to an alias for that box. Perhaps my qmail-local is not patched for Maildir++ support. Is that patch included in the qmail-toaster-0.6-1+greylisting.patch? Your site's description of that patch implies that it is but I don't know how to check for sure if it is in there It should be. But if the maildirsize file is not updated when SquirrelMail deletes a message, then you may have other problems. Who owns maildirsize? You should probably run all agents that touch it as vpopmail. Regards, Bill David Shirley http://www.webquarry.com
Re: [toaster] maildirsize updates (not)
On May 14, 2004, at 1:41 PM, David M. Shirley wrote: @400040a5282721710af4 delivery 453: success: user_does_not_exist,_but_will_deliver_to_/home/vpopmail/domains/ DOMAINREMOVED/postmaster//did_0+0+1/ @400040a5282721712e1c status: local 0/10 remote 0/20 @400040a52827217135ec end msg 3532276 Obviously, I've munged the logs a bit to obscure the email address in question but it should still be clear what it says. I see no problem in that log entry. Do you concur? Perhaps there's a bug in vdelivermail where it doesn't count catch-all emails against the quota? -- Tom Collins - [EMAIL PROTECTED] QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/ Info on the Sniffter hand-held Network Tester: http://sniffter.com/
Re: [toaster] maildirsize updates (not)
I can confirm from experiments today that catch-all mail is definitely NOT counted in quotas. I thought that qmail-local did the delivery for catchalls but maybe I am mistaken. Does vdelivermail place mail in Mailbox dirs directly or does it call one of the qmail programs to handle the delivery? On Friday, May 14, 2004, at 04:43 PM, Tom Collins wrote: Perhaps there's a bug in vdelivermail where it doesn't count catch-all emails against the quota? David Shirley http://www.webquarry.com
Re: [toaster] maildirsize updates (not)
I just confirmed that all aliased mail IS being counted in the quota. The problem seems to lie purely in the quota counts on CATCHALL emails. Can anyone else confirm this behavior? On Friday, May 14, 2004, at 04:43 PM, Tom Collins wrote: Perhaps there's a bug in vdelivermail where it doesn't count catch-all emails against the quota? -- Tom Collins - [EMAIL PROTECTED] David Shirley http://www.webquarry.com
