Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email firstname.lastname@example.org
From: mouss (moussnetoyen.net)
Date: Tue May 06 2008 - 13:20:56 CDT
Jozsef Kadlecsik wrote:
> On Mon, 5 May 2008, mouss wrote:
>> a simple approach is to update an access db at delivery time, and use
>> this in check_recipient_access.
> Sorry, I don't understand it. What kind of access db could be updated at
> where? At the final delivery, updated by the 'local' process? Something I
> must overlook then.
>> another approach is to set two quotas for users
>> - if the "low" quota threshold is reached, a warning is sent to the user
>> - if the "next" quota level is reached, the user is blocked, and needs to
>> contact the postmaster to get unlisted (once he purged his mailbox).
> I don't have any control over the destination machines, just at the relay
if you have no control over the remote server, how would you know there
is an over quota event? Even if the remote system is a postfix,
overquota will only be noticed after mail was accepted and queued and is
about to be delivered.
if you can have the final delivery agent to update some quota table,
then you can use this table as an access map in the relay MTA.
otherwise, you can have a cron that periodically checks quotas (only for
recipients that you delivered mail to recently, to avoid scanning a
whole mail store) and updates an access map.