Try setting only soft limits. The soft limits should mail to the user and to the admin. Then you have to go with a (set of) procedures that answer the questions: "what if the user doesn't clean up his mail box?" "what if he keeps going over limit?" Some things you can do is at Level One, send out a report of who's over quota and how long they've been over. Maybe how many times in the last 3 months too. Level Two, burn half his inbox to CD, truncate and send him the CD. You're sure that the mail is not still at the sendor's machine? You did log a temporary delivery failure DSN 4.0.0 which should mean the sender keeps the message and tries again later. Hattie Rouge > -----Original Message----- > From: psyche-list-admin@xxxxxxxxxx > [mailto:psyche-list-admin@xxxxxxxxxx] On Behalf Of > glarm@xxxxxxxxxxxxxxx > Sent: Wednesday, May 07, 2003 10:56 AM > To: psyche-list@xxxxxxxxxx > Subject: Re: Quota Problems > > > Hello, > I have found for the first time evidence that my mail gets > chucked. Where to I do not know. No bounce messages to the > sender, in this case I use two accounts, user glarm and user > krusty. I have not seen any messages from postmaster about > over quota or failed to deliver. As you can see from below > the email dies in cyber space sad thing is that it was > checked for viri and checked for spam. > > How could I set something up to notify the sender that the > user is over quota. I set up warnquota but that only send to > the person who is overquota and root. Any one know of a way > to solve this? > > Dylon > > > May 7 10:40:57 sucia imapd[6044]: Login user=krusty > host=sucia.interisland.org [127.0.0.1] May 7 10:40:57 sucia > imapd[6044]: Logout user=krusty host=sucia.interisland.org > [127.0.0.1] ^[[BMay 7 10:43:21 sucia sendmail[6045]: > h47HhL9u006045: from=<krusty@xxxxxxxxxxxxxxx>, size=535, > class=0, nrcpts=1, > msgid=<32798.12.17.134.116.1052329401.squirrel@xxxxxxxxxxxxxxxxxxx>, > proto=SMTP, daemon=MTA, relay=sucia.interisland.org > [127.0.0.1] May 7 10:43:21 sucia sendmail[6045]: > h47HhL9u006045: Milter add: header: > X-AntiVirus: checked by Vexira Milter 1.0.1; VAE 6.19.0.3; > VDF 6.19.0.11 May 7 10:43:21 sucia imapd[6052]: imap service > init from 127.0.0.1 May 7 10:43:22 sucia imapd[6052]: Login > user=krusty host=sucia.interisland.org [127.0.0.1] May 7 > 10:43:22 sucia spamd[2628]: connection from > sucia.interisland.org [127.0.0.1] at port 33099 May 7 > 10:43:22 sucia imapd[6052]: Logout user=krusty > host=sucia.interisland.org [127.0.0.1] May 7 10:43:22 sucia > spamd[6057]: info: setuid to glarm succeeded May 7 10:43:22 > sucia spamd[6057]: processing message > <32798.12.17.134.116.1052329401.squirrel@xxxxxxxxxxxxxxxxxxx> > for glarm:500, expecting 903 bytes. May 7 10:43:22 sucia > imapd[6058]: imap service init from 127.0.0.1 May 7 10:43:22 > sucia imapd[6058]: Login user=krusty > host=sucia.interisland.org [127.0.0.1] May 7 10:43:22 sucia > spamd[6057]: clean message (2.6/5.0) for glarm:500 in 0.5 > seconds, 903 bytes. May 7 10:43:22 sucia imapd[6058]: Logout > user=krusty host=sucia.interisland.org [127.0.0.1] May 7 > 10:43:22 sucia sendmail[6053]: h47HhL9u006045: > to=<glarm@xxxxxxxxxxxxxxx>, ctladdr=<krusty@xxxxxxxxxxxxxxx> > (1774/1810), delay=00:00:01, xdelay=00:00:00, mailer=local, > pri=30838, dsn=4.0.0, > stat=Deferred: local mailer (/usr/bin/procmail) exited with > EX_TEMPFAIL > > > > > > for my case, a bounce mail will be mailed back to the > sender to tell > > him the user's account is over-quota...but most probaly > only sys admin > > are likely to > > understand the message..... > > ----- Original Message ----- > > From: <glarm@xxxxxxxxxxxxxxx> > > To: <psyche-list@xxxxxxxxxx> > > Sent: Wednesday, May 07, 2003 6:18 AM > > Subject: RE: Quota Problems > > > > > > Hattie, > > Thanks for your response in this matter. I still can not determine > > where the mail goes, I turned up the logging to 15 and I am > going to > > try 99 next. I just cant find a single line that says what it does > > with it. It is all in hopes of getting warnquota to work so I/they > > would know before a I/they goes over quota. I will continue > to search. > > Thanks again.. :) > > > > Dylon > > > > > >> This is a guess because I haven't actually set up a quota on mail > >> boxes. In every company I've been in, no one wanted to risk their > >> career over possible lost mail - they'd rather a policy of > unlimited > >> disk (but within budget, of course). :-) > >> > >> My guess is that since a bounce is handled by sendmail and > delivery > >> is handled by the local mailer, and since it is the local > mailer that > >> would get the error from the quota daemon, the mail will > be lost. If > >> not lost, possibly it would be put into the queue but as > you say, you > >> don't see it there. > >> > >> You might get around this by setting your sendmail server to queue > >> everything before delivery. > >> > >> Did you turn up your log level? You should be set to at > least 15 and > >> I would set it all the way up to 99 while testing. Log to another > >> server if you have to. This is a critical question. > >> > >> > >> Hattie Rouge > >> > >> > >>> -----Original Message----- > >>> From: psyche-list-admin@xxxxxxxxxx > >>> [mailto:psyche-list-admin@xxxxxxxxxx] On Behalf Of > >>> glarm@xxxxxxxxxxxxxxx > >>> Sent: Tuesday, May 06, 2003 1:02 PM > >>> To: psyche-list@xxxxxxxxxx > >>> Subject: Quota Problems > >>> > >>> > >>> Hello, > >>> > >>> I have set up quota on a test server and populated it with 1500 > >>> accounts. I have set up squirrelmail and sendmail. I am wondering > >>> how I would get the warnquota function to work on this server. I > >>> cannot find good documentation on this. I am wondering > when my quota > >>> fills up what happens to the inbound mail that does not > fit? I have > >>> seen that I cannot find it in queue or in queue in the > other sending > >>> server. Does it go to the bit bucket? I would think that the mail > >>> would bounce somewhere. But I cannot find any evidence of > this after > >>> looking at the logs. > >>> > >>> Thanks > >>> > >>> > >>> > >>> > >>> > >>> -- > >>> Psyche-list mailing list > >>> Psyche-list@xxxxxxxxxx > >>> https://listman.redhat.com/mailman/listinfo/ps> yche-list > >>> > >> > >> > >> > >> -- > >> Psyche-list mailing list > >> Psyche-list@xxxxxxxxxx > >> https://listman.redhat.com/mailman/listinfo/psyche-list > >> > > > > > > > > -- > > Psyche-list mailing list > > Psyche-list@xxxxxxxxxx > > https://listman.redhat.com/mailman/listinfo/psyche-list > > > > > > > > > > -- > > Psyche-list mailing list > > Psyche-list@xxxxxxxxxx > > https://listman.redhat.com/mailman/listinfo/psyche-list > > > > > > -- > Psyche-list mailing list > Psyche-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/ps> yche-list > -- Psyche-list mailing list Psyche-list@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/psyche-list
