From: mouss on
Mauro Faccenda a écrit :
>>> This is harder than it looks. do you really need to worry about all this
>>> stuff or are you inventing problems?
>
> Well, I don't think I'm inventing problems, maybe I could do it in a
> easier way, and that's why I sent this mail to this list. ;)
>
> I had a lot of trouble with my mail servers getting into blacklists
> due to backscatter and in this setup I think I'll be more cautious
> about it.
>
> Thanks anyway. I think I'll take a look in that PHP code Robert posted
> in a previous message.
>

my meaning is: don't try to solve problems that you invent.

there is no 100% way to prevent bounces unless you abandon SMTP. SMTP is
a store-and-forward protocol, and this works very well and is efficient.
we don't like people bouncing junk when they can avoid it (backscatter:
because they don't validate recipient addresses at smtp time). but if
you bounce because of quota, it's a different thing. it doesn't matter
why you bounce. what matters is how often you bounce. if over quota only
happens once in a while, it's ok. but if you bounce too often, then you
have a local problem anyway. and you should fix the problem locally.

In all my life, I have never resorted to quota enforcement. Instead, in
every place I have been, I took it the "other" way:

- everybody has the right for $Q storage.
- people can use more than $Q, but they "lose the guarantee" (it's not a
"right")
- people should understand that they shouldn't get more than $Q for too long
- there's a hard limit. if they reach the hard limit, they lose their
connectivity and they need to ask to get "unlisted".
- we explain to users that they share a finite space, and that "we" have
no problem when users are over quota, but that if the disk is full, then
people won't get mail. => I've found this argument surprisingly
efficient. I've seen people almost cry after they were informed that
they exploded their quota...