On Thu, Aug 10, 2000 at 12:40:06AM +0200, Einar Bordewich wrote:
> My tormentor is a customer and is allowed to relay through our mailserver.
>
> The problem is that I want him over on a mailinglist solution. He most likly
> will switch to mailinglist eventually, but I think it's a little bit drastic
> to block him out just to speed up the action ;-) I feel it would be more
> correct to implement some limitations on the mail server, affecting all the
> users.
>
> This because we from time to time have users/customers that pops off a mail
> with 100+ recipients. In my opinion beneath 100 is acceptable, over this
> number it's improper use. I might be out on a limb here, so please correct
> if I'm wrong.
It's your service, you define it. For some, 1000 is fine, for others 10
may be unacceptable.
> And yes, if he's smart he can abuse the solution, but then again he's
> deliberately have to do it, breaking our agreement and policy. I don't
> belive in policy when there is no hardware or software limitations to back
> that up.
And what hardware/software do you propose to use to back up the
policy that says he can't make multiple submissions?
One solution that generally covers it is to charge them for the
number of recipients or the total bytes sent or whatever. Naturally
self regulating then. You can generate billing information for the
mail logs.
Regards.
