| To: | qmail@list.cr.yp.to |
|---|---|
| Subject: | Re: Dozens of qmail-smtpd processes eating 100% of CPU |
| From: | Kyle Wheeler <kyle-qmail@memoryhole.net> |
| Date: | Fri, 18 May 2007 12:46:04 -0600 |
| Comment: | DomainKeys? See http://antispam.yahoo.com/domainkeys |
| 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 |
| Dkim-signature: | v=0.5; a=rsa-sha1; c=relaxed; d=memoryhole.net; h=received:comment:domainkey-signature:received:received:date:from:to:subject:message-id:mail-followup-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; q=dns/txt; s=default; bh=1sH2IcnpGltibiURBV2NkihDkb0=; b=KB8o6h3BwMLqQ93ok3naJByyfhxvPwnb48ube8Q2/YyB7SSvJT9utzizmPNQI+ER8dZeBvV/G/Tf5l9FD+TbJRJM1zqxwej9YoIzPuVfm5k3WY0eD6E13x1//23H7DPj11lVI+zJmnvhtAkXtNfCnjPQZafg3fbEIUaIYgTx7dg= |
| Domainkey-signature: | a=rsa-sha1; q=dns; c=nofws; s=default; d=memoryhole.net; b=TZHOB7j3GK/k2bNK3NPTJ6Ov8nsN2Mwt4VHO6uPUcydpQvryP2Q7yiepmEY5SXPzmez1ERBi2fxbBKwWF0M0ogLAJlvU39Kj+j5LMaS6e/FBNuRwp9VICU4GA1UxazhFrngboZDD/EUPqwEY60EI1hByoL/P7izjjP+yuqXE4es= ; |
| Domainkey-status: | good |
| In-reply-to: | <924f29280705181128l286d84fdia4de414a7df6f2a1@mail.gmail.com> |
| Mail-followup-to: | qmail@list.cr.yp.to |
| Mailing-list: | contact qmail-help@list.cr.yp.to; run by ezmlm |
| References: | <464DBC1B.30204@sourcefire.com> <20070518163703.GH29250@marvin.we-be-smart.org> <464DE3E0.8070200@sourcefire.com> <20070518175145.GA18422@caesar.cse.nd.edu> <924f29280705181128l286d84fdia4de414a7df6f2a1@mail.gmail.com> |
| User-agent: | Mutt/1.5.15cvs (2007-05-02) |
On Friday, May 18 at 02:28 PM, quoth Jason Frisvold: On 5/18/07, Kyle Wheeler <kyle-qmail@memoryhole.net> wrote:Well, if I'm right and it is the TLS/SSL patch, then it will only become a problem when people who support STARTTLS attempt to contact you. Since many servers do not, it won't be a problem most of the time.This one's pretty easy to check too.. Set your mail client up to use TLS and start sending mail.. Watch the processor and if you see it spike when you start trying to send, this could very well be the problem.
Even easier:
openssl s_client -starttls smtp -connect localhost:25
If that takes longer than a second to connect, we've found our
culprit.
~Kyle
--
Compassion is the basis of morality.
-- Arnold Schopenhauer
|
| Previous by Date: | Re: Dozens of qmail-smtpd processes eating 100% of CPU, Jason Frisvold |
|---|---|
| Next by Date: | Re: Dozens of qmail-smtpd processes eating 100% of CPU, Alex Kirk |
| Previous by Thread: | Re: Dozens of qmail-smtpd processes eating 100% of CPU, Jason Frisvold |
| Next by Thread: | Re: Dozens of qmail-smtpd processes eating 100% of CPU, Alex Kirk |
| Indexes: | [Date] [Thread] [Top] [All Lists] |