W dniu Wed, Feb 14, 2001 at 01:35:17PM -0500, Dave Sill wystuka(a):
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
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
W dniu Mon, Feb 12, 2001 at 03:54:38PM -0500, Dave Sill wystuka(a):
I had concurrencyremote set to 40, but with this setting it blocked my queue
for several hours! (some of receipments are very far from me), so i switched
to 120 and it's better because queue is blocked for 30 minutes at most,
On of my clients two times a week sends his "info" letter which is about 300KB
and adressed to ~2000 accounts...
I had concurrencyremote set to 40, but with this setting it blocked my queue
for several hours! (some of receipments are very far from me), so i switched
to 120 and it's better
Daniellek [EMAIL PROTECTED] wrote:
I had concurrencyremote set to 40, but with this setting it blocked my queue
for several hours! (some of receipments are very far from me), so i switched
to 120 and it's better because queue is blocked for 30 minutes at most, but
i takes all my bandwith...
