| To: | qmail@list.cr.yp.to |
|---|---|
| Subject: | Re: Advanced tricks I use to get rid of spam using MX 4xx |
| From: | Harald Hanche-Olsen <hanche@math.ntnu.no> |
| Date: | Mon, 27 Nov 2006 20:53:58 +0100 (CET) |
| Delivered-to: | sp-com-lists@consult.net |
| Delivered-to: | gmail-qmail@securepoint.com |
| Delivered-to: | sp.com.list@gmail.com |
| Delivered-to: | mailing list qmail@list.cr.yp.to |
| In-reply-to: | <456B03BA.1060303@perkel.com> |
| Mailing-list: | contact qmail-help@list.cr.yp.to; run by ezmlm |
| References: | <45686D69.5040003@perkel.com> <20061127143127.GA29898@discworld.dyndns.org> <456B03BA.1060303@perkel.com> |
+ Marc Perkel <marc@perkel.com>: | No - on my system a 4xx error only means that that particular server | isn't ready. It means try the other servers or come back later. In that case, it would probably be better to just stop listening on the smtp port while the load is too high. But you want to tailor your response to what host is connecting: Too bad then that unix doesn't let you move such decisions into userland. If you're listening on a port, you accept all incoming connections no matter what, and then the best you can do is either just drop the connection, or try to tell the client to go away, and this is where you clash with established protocol. Are there Unix variants that will let you decide in userland what to do about an incoming SYN? The Hurd perhaps? AFAIK, one of the design goals of the Hurd is precisely to move stuff from the kernel into userland. - Harald |
| Previous by Date: | RE: Advanced tricks I use to get rid of spam using MX 4xx [X200611276963], Maintenance Fees Inquiries |
|---|---|
| Next by Date: | Re: Advanced tricks I use to get rid of spam using MX 4xx, Uncle George |
| Previous by Thread: | Re: Advanced tricks I use to get rid of spam using MX 4xx, Markus Stumpf |
| Next by Thread: | Re: Advanced tricks I use to get rid of spam using MX 4xx, Donald Nash |
| Indexes: | [Date] [Thread] [Top] [All Lists] |