|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: mouss (mlist.only
free.fr)
Date: Wed Dec 05 2007 - 07:51:40 CST
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
utahnix wrote:
> mouss wrote:
>> utahnix wrote:
>>
>>> Is there a simple way I can simply instruct Postfix to drop/delete
>>> messages returned from Cyrus as a result of over quota? I know Cyrus has
>>> a lmtp_over_quota_perm_failure option which turns the over quota
>>> responses into permanent failures instead of temporary failures, but I
>>> don't want backscatter (which I've just realized is a problem for me),
>>> and I really don't know if I care to keep mail as a result of an over
>>> quota issue (users should know better than to get over quota).
>>>
>>> Or is there a better way of handling mail rejected by the MUA because of
>>> quota issues that won't cause backscatter?
>>>
>>>
>>>
>>
>> over quota bounces are still acceptable (because they are infrequent).
>> what you can do is to add users to a block list when they are over
>> quota. This way, mail will be rejected at smtp time.
>>
>>
> Actually this user's bounces are very frequent... they have a very low
> quota and most of the messages entering the server are intended for
> them. My predecessor made this employee change their email address
> several times, thinking it would fix the problem, but after a few
> months, it would be back to normal. I have found it is simply an
> education issue (when to give your email address out, etc), but
> unfortunately, the person does not want to be educated.
>
> A block list? And this is done via a MTA (i.e. postfix) level? Can you
> tell me how to do this, or at the very least, point me in the right
> direction?
>
>
you can use a cron script to find users who are over quota, and update a
map as needed. you can require that the user clicks on some button
somewhere to reactivate his account (provided he is no more over quota).
alternatively, you can deliver with a wrapper script that calls your
real MDA, and lists the user if the MDA returns an over quota error.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]