

![]() | Start a set with this search |
![]() | Include this search in one of my sets |
![]() | Exclude this search from one of my sets |
![]() | Permalink to these results Paste this link in email or IM: |
| Atom feed for tracking future search results Paste this URL into your reader: |
2 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Over Quota Problem!!| From | Sent On | Attachments |
|---|---|---|
| Anthony | Feb 25, 2004 1:37 am | |
| Mariano Absatz | Feb 27, 2004 10:10 am |

![]() | Permalink for this message Paste this link in email or IM: |
![]() | Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | Re: [maildropl] Over Quota Problem!! | Actions... |
|---|---|---|
| From: | Mariano Absatz (ba...@baby.com.ar) | |
| Date: | Feb 27, 2004 10:10:45 am | |
| List: | net.sourceforge.lists.courier-maildrop | |
Hi,
besides a 'mee too' to this message, I'm having a strange problem related to quotawarnmsg that is quite the opposite from this...
I'm using ZMailer with maildrop+LDAP for local delivery, and courier- imap+LDAP POP3 only server.
It seems that the rate limit for the quotawarnmsg is not working... users are receiving this message multiple times in a row... afaik, even with no actual deliveries in between (or maybe bounces because of quota exceeded).
e.g: this is the tail of a 'ls -lart new': -rw------- 1 mailuser mail 117437 Feb 26 21:51 1077843033.M456876P814V0000000000000009I0014B97B_0.fe2,S=117437 -rw------- 1 mailuser mail 456944 Feb 26 22:15 1077844472.M742555P17493V0000000000000009I0014898E_0.fe2,S=456944 -rw------- 1 mailuser mail 2718 Feb 26 22:34 1077845643.M940503P31619V0000000000000009I0014BB33_0.fe2,S=2718 -rw------- 1 mailuser mail 3215 Feb 26 22:50 1077846600.M303815P10358V0000000000000009I0014BB8A_0.fe2,S=3215 -rw------- 1 mailuser mail 540818 Feb 27 01:13 1077855148.M563605P10258V0000000000000009I000EB621_0.fe1,S=540818 -rw-r----- 1 mailuser mail 913 Feb 27 01:14 1077855194.M450746P11118V0000000000000009I0012A31E_warn.fe1,S=913 -rw------- 1 mailuser mail 280353 Feb 27 01:14 1077855194.M387956P11118V0000000000000009I0011D5EB_0.fe1,S=280353 -rw-r----- 1 mailuser mail 913 Feb 27 01:44 1077856983.M351447P9934V0000000000000009I001428DC_warn.fe1,S=913 -rw-r----- 1 mailuser mail 913 Feb 27 01:48 1077857291.M665111P22120V0000000000000009I0014BC87_warn.fe2,S=913 -rw------- 1 mailuser mail 7586 Feb 27 01:48 1077857291.M556870P22120V0000000000000009I0014BC77_0.fe2,S=7586 -rw-r----- 1 mailuser mail 913 Feb 27 04:44 1077867826.M385097P17678V0000000000000009I001478B6_warn.fe2,S=913 -rw------- 1 mailuser mail 76401 Feb 27 04:44 1077867826.M316452P17678V0000000000000009I00147694_0.fe2,S=76401 -rw-r----- 1 mailuser mail 913 Feb 27 05:58 1077872266.M175088P8839V0000000000000009I0014C98B_warn.fe1,S=913 -rw------- 1 mailuser mail 221795 Feb 27 05:58 1077872265.M849652P8839V0000000000000009I0014C98A_0.fe1,S=221795 -rw-r----- 1 mailuser mail 913 Feb 27 06:38 1077874674.M469263P13358V0000000000000009I00145202_warn.fe2,S=913 -rw-r----- 1 mailuser mail 913 Feb 27 07:26 1077877559.M706832P26509V0000000000000009I0014BF61_warn.fe2,S=913 -rw-r----- 1 mailuser mail 913 Feb 27 07:26 1077877559.M653028P26507V0000000000000009I000A675E_warn.fe2,S=913 -rw-r----- 1 mailuser mail 913 Feb 27 07:28 1077877661.M938829P3158V0000000000000009I00147DDE_warn.fe1,S=913 -rw-r----- 1 mailuser mail 913 Feb 27 07:28 1077877661.M442767P3147V0000000000000009I00146FBD_warn.fe1,S=913 -rw-r----- 1 mailuser mail 913 Feb 27 12:03 1077894161.M702461P24508V0000000000000009I001492E8_warn.fe1,S=913 -rw-r----- 1 mailuser mail 913 Feb 27 12:04 1077894268.M36884P25472V0000000000000009I000A1571_warn.fe2,S=913 -rw-r----- 1 mailuser mail 913 Feb 27 12:33 1077895927.M78708P9941V0000000000000009I0014C9DC_warn.fe1,S=913 -rw------- 1 mailuser mail 21785 Feb 27 12:33 1077895927.M59825P9941V0000000000000009I0014C817_0.fe1,S=21785 -rw-r----- 1 mailuser mail 913 Feb 27 12:33 1077895966.M852620P13004V0000000000000009I0014C778_warn.fe2,S=913 -rw-r----- 1 mailuser mail 913 Feb 27 12:33 1077895966.M779767P12989V0000000000000009I0011C8B9_warn.fe2,S=913 -rw-r----- 1 mailuser mail 913 Feb 27 12:53 1077897210.M252107P31667V0000000000000009I0014C9E7_warn.fe2,S=913 -rw-r----- 1 mailuser mail 913 Feb 27 13:03 1077897773.M599010P6195V0000000000000009I0014B433_warn.fe2,S=913 -rw-r----- 1 mailuser mail 913 Feb 27 13:15 1077898477.M103536P14207V0000000000000009I00140AC3_warn.fe2,S=913 -rw-r----- 1 mailuser mail 913 Feb 27 13:26 1077899159.M884306P21178V0000000000000009I0014131B_warn.fe2,S=913 -rw-r----- 1 mailuser mail 913 Feb 27 13:26 1077899161.M755377P21183V0000000000000009I0014CB6E_warn.fe2,S=913 -rw-r----- 1 mailuser mail 913 Feb 27 13:26 1077899148.M805896P11910V0000000000000009I0014C638_warn.fe1,S=913 -rw-r----- 1 mailuser mail 913 Feb 27 13:41 1077900053.M734422P20584V0000000000000009I0014B885_warn.fe1,S=913 -rw-r----- 1 mailuser mail 913 Feb 27 14:08 1077901667.M703954P7883V0000000000000009I000AFC39_warn.fe2,S=913 -rw-r----- 1 mailuser mail 913 Feb 27 14:10 1077901791.M590871P5177V0000000000000009I000EB0AC_warn.fe1,S=913 -rw-r----- 1 mailuser mail 913 Feb 27 14:10 1077901831.M240685P9204V0000000000000009I000EB46C_warn.fe2,S=913 -rw-r----- 1 mailuser mail 913 Feb 27 14:44 1077903860.M154657P28415V0000000000000009I000AFC3B_warn.fe2,S=913 -rw-r----- 1 mailuser mail 913 Feb 27 14:44 1077903860.M426659P28422V0000000000000009I0014CD5F_warn.fe2,S=913
And this is a 'ls -lart' of the maildir itself:
drwxr-x--- 3 mailuser mail 104 Feb 17 18:56 ../ -rw-r----- 1 mailuser mail 0 Feb 18 00:02 quotawarn -rw-r--r-- 1 mailuser mail 200 Feb 26 09:26 courierpop3dsizelist drwx------ 2 mailuser mail 48 Feb 26 09:27 cur/ -rw-r----- 1 mailuser mail 23 Feb 27 14:44 maildirsize drwx------ 5 mailuser mail 224 Feb 27 14:44 ./ drwx------ 2 mailuser mail 48 Feb 27 14:48 tmp/ drwx------ 2 mailuser mail 6176 Feb 27 14:48 new/
all those *_warn.fe2,S=913 files are identical warning messages... see the creation times of the files and see that there are many that don't even have actual messages in between them.
The maildirs themselves are in an NFS mounted partition. Maildrop is invoked from the mailserver like: maildrop -d $u -w 90 where $u is substituted by the complete e-mail address. The LDAP configuration says (among others): search_method mail quota_attr pertMaildirQuota and all entries have the 'pertMaildirQuota' attribute with a maildir quota specification (only size is used)... the standard entry looks like: pertMaildirQuota: 5242880S
I'm using maildrop 1.6.3 and courier-imap 2.2.1.
I'd be grateful for any hint to avoid this... I don't want to get rid of the '-w 90'.
TIA
El 25 Feb 2004 a las 17:28, Anthony escribió:
Dear All,
I am using Qmail + LDAP PATCH + MAILDROP now.
I have one over quota question.
For example, If I set "maildrop -w 80", the quotawarnmsg will delivery to the user's mailbox when it reach 80% Full.
However If the mailbox was over quota (over 100%), no warning message delivery. I know this is normal for the design of maildirquota.
But I want to let the user know his mailbox exceed its quota even over 100%.
Anyone know how to do it?
Thanks
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id 56&alloc_id438&oplick
_______________________________________________ Courier-maildrop mailing list Cour...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/courier-maildrop
-- Mariano Absatz - El Baby mailto:ba...@baby.com.ar http://www.baby.com.ar/ PGP KEYS: http://www.baby.com.ar/datos/personales.html#claves_pgp |\ _ _\\/'> Powered by Pegasus Mail /|__) http://www.pmail.com ) )\
----------------------------------------------------------- Don't worry about the world coming to an end today. It's already tomorrow in Australia. -- Charles Schulz







