Re: client is blocking my mail server...
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 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 This is some sort of info/newsletter and it happens to be big (500KB message), it's why it's a problem for us. 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). Yesterday noon, i've searched through qmail source (it was hard to recall C programming :) but found a way to do this efficiently :) If everything goes OK, patch should be ready tomorrow :) -- Daniel Fenert--== [EMAIL PROTECTED] ==-- ==-P o w e r e d--b y--S l a c k w a r e-=-ICQ #37739641-== - czy linux bdzie dziaa gdy na innej partycji bd mia windows? - tak, cho z lekkim obrzydzeniem (robmar) ===- http://daniellek.linux.krakow.pl/ -=== +48604628083
Re: client is blocking my mail server...
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
Re: client is blocking my mail server...
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, but i takes all my bandwith... I'm searching for some solution which could make "private queue" for this client... He injects through SMTP... 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). 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 :) -- Daniel Fenert--== [EMAIL PROTECTED] ==-- ==-P o w e r e d--b y--S l a c k w a r e-=-ICQ #37739641-== No, I don't have a drinking problem. I drink, I get drunk, I fall down. No problem! ===- http://daniellek.linux.krakow.pl/ -=== +48604628083
client is blocking my mail server...
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 because queue is blocked for 30 minutes at most, but i takes all my bandwith... I'm searching for some solution which could make "private queue" for this client... I read something about serialmail, but as far as i read it takes all traffic from server. -- Daniel Fenert--== [EMAIL PROTECTED] ==-- ==-P o w e r e d--b y--S l a c k w a r e-=-ICQ #37739641-== Reincarnation: Life sucks, then you die. Then life sucks again. ===- http://daniellek.linux.krakow.pl/ -=== +48604628083
Re: client is blocking my mail server...
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... I'm searching for some solution which could make "private queue" for this client... You can install qmail again, e.g. under /var/qmail2, and use this second installation for your problem client. The trick will be diverting his messages to that qmail installation. If his ~2000 user list is handled by a list manager (such as ezmlm) on the qmail server, you can just reconfigure his list to use /var/qmail2/bin/qmail-inject. Same deal if injects the messages from a login account. 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. If all this just flew over your head, you can ask for clarification or consider hiring a qmail expert to do it for you. -Dave
