Daniellek <[EMAIL PROTECTED]> wrote:
>W dniu Mon, Feb 12, 2001 at 03:54:38PM -0500, Dave Sill wystuka-Bł(a):-A
>
>>If he injects them via SMTP, it's a bit trickier. You could run
>>/var/qmail2/bin/qmail-smtpd on a non-standard port, e.g., 2500, and
>>tell him to configure his mail client to use port 2500.
>>
>>You could also configure your main tcpserver to listen to port 25 on
>>the existing IP address (and 127.0.0.1) and set up another tcpserver
>>on an aliased IP address dedicated to that client. Then you'd have to
>>tell him to configure his mailer to that IP alias.
>
>Ok, this solution would work but isn't best... I't would block all my client
>traffic (even short - one recipient letters).
I don't know the nature of your client(s) or their mail usage
patterns, but if the offending messages are sent by a particular user,
you could give that single person the alternative SMTP host or
port. That would subject only that one person to waiting for the big
delivery. If even that's not acceptable, that person can simply set up
an alternative mail user configuration for the bulk sends--or simply
reconfigure their SMTP server settings before and after sending a bulk
message.
>Following this thread - is there possibility to check before sending mail to
>queue if it has more than (for example) 50 recipient it wolud be forwarded to
>this second qmail-queue. This would be ideal solution...
>
>There's tarpit patch which checks if there are no more recipients that number
>from control/tarpitcount file. Maybe it is possible to alter this patch to
>suit my needs... I mean without rewriting whole qmail :)
Sure, it's a SMOP (Simple Matter Of Programming).
-Dave
