| To: | qmail@list.cr.yp.to |
|---|---|
| Subject: | Re: Service Not Available |
| From: | Kyle Wheeler <kyle-qmail@memoryhole.net> |
| Date: | Wed, 8 Aug 2007 10:59:34 -0600 |
| Comment: | DomainKeys? See http://domainkeys.sourceforge.net/ |
| 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: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=z24rHBC0mkiN3X2Kelc8QU7mPmk=; b=YHLXJ93tVhi4KVxvxxO8iunF/jw0xB1w3goBRD78Vs0b6IR1Q5/b/r71ZOk831lMO45+d3CovJ3YlTOVPLdT9ckO9DC7ck4EpeGIeI6g5iWB8CUp0UL7JbAQ0cCdc5DzZp0mWx1KCkFBwBEdBC2v87mv1pCNbNqp1MLLyWa3JLI= |
| Domainkey-signature: | a=rsa-sha1; q=dns; c=nofws; s=default; d=memoryhole.net; b=hegsjA7+tegmySuo512YfheOo/LYlQTv0CBsVAgm2yIodwvHX8+pq6GTvopOqQnYipEfqRa4UKS9rVLXZxWB6LANwvS4B80udxAyxbMU0VRL940j+nMECSADvwvmsGvHQzWsnWvW8Mi90jT3hOjftyk+U+apSb+hGEQiZTWHM8E=; h=Received:Received:Date:From:To:Subject:Message-ID:Mail-Followup-To:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:User-Agent; |
| Domainkey-status: | good |
| In-reply-to: | <c7a6d16d0708080938m5a104b8ar2385d4245d8a4d26@mail.gmail.com> |
| Mail-followup-to: | qmail@list.cr.yp.to |
| Mailing-list: | contact qmail-help@list.cr.yp.to; run by ezmlm |
| References: | <c7a6d16d0708080938m5a104b8ar2385d4245d8a4d26@mail.gmail.com> |
| User-agent: | Mutt/1.5.16 (2007-07-16) |
On Wednesday, August 8 at 12:38 PM, quoth Jon Daily: I've had my qmail server up and running for awhile now, and it is working. However, I know when I am sending messages to it through my application that I often get "Service not available. Reply: " That's an odd message. What application is giving you that message? I have been able to dramatically decrease the "Service not available" messages by adding four MX records all pointing to different IP addresses that actually point to the same qmail smtp server, but I still think this response is happening too frequently. I am currently handling a small amount of messages ( < 1/min) and am worried what will happen when the traffic grows. My gut feeling, given that you haven't given us *any* information about your setup, is that you probably have your concurrency limits too low. How are you running qmail-smtpd? What does your run file look like? What do your logs look like? Does anyone have any idea why I may be receiving this, or a possible fix. Is this normal? Do I need a fifth MX record?
You shouldn't need more than one MX record per qmail server.
~Kyle
--
The real problem is not whether machines think, but whether men do.
-- B. F. Skinner
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: cannot start: unable to read controls, Daniel Mahoney |
|---|---|
| Next by Date: | Re: Qmail TLS - No Received encrypted header [SOLVED], Unga |
| Previous by Thread: | Re: Service Not Available, Jon Daily |
| Next by Thread: | Bind outgoing SMTP traffic to specific IP address, Phil Breskey |
| Indexes: | [Date] [Thread] [Top] [All Lists] |