From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4214d7b188dcd9812956cf8e6863004b@mail.nanosouffle.net> To: lucio@proxima.alt.za, 9fans@9fans.net From: Akshat Kumar Date: Mon, 9 Feb 2009 22:44:49 -0500 In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-blwslndsyzrigkfwcvpxyyaokm" Subject: Re: [9fans] UPAS, IMAP, and SMTP Topicbox-Message-UUID: 9b50346c-ead4-11e9-9d60-3106f5b1d025 This is a multi-part message in MIME format. --upas-blwslndsyzrigkfwcvpxyyaokm Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Nah, I just didn't have a factotum entry for SMTP username and pass. Everything is fine otherwise. ak --upas-blwslndsyzrigkfwcvpxyyaokm Content-Type: message/rfc822 Content-Disposition: inline Delivered-To: akumar@mail.nanosouffle.net Received: by 10.142.79.4 with SMTP id c4cs317363wfb; Mon, 9 Feb 2009 07:06:39 -0800 (PST) Received: by 10.214.78.5 with SMTP id a5mr6832172qab.245.1234191998522; Mon, 09 Feb 2009 07:06:38 -0800 (PST) Return-Path: <9fans-bounces+akumar=mail.nanosouffle.net@9fans.net> Received: from gouda.swtch.com (gouda.swtch.com [67.207.142.3]) by mx.google.com with ESMTP id k42si11198141rnd.15.2009.02.09.07.06.36; Mon, 09 Feb 2009 07:06:38 -0800 (PST) Received-SPF: pass (google.com: domain of 9fans-bounces+akumar=mail.nanosouffle.net@9fans.net designates 67.207.142.3 as permitted sender) client-ip=67.207.142.3; Authentication-Results: mx.google.com; spf=pass (google.com: domain of 9fans-bounces+akumar=mail.nanosouffle.net@9fans.net designates 67.207.142.3 as permitted sender) smtp.mail=9fans-bounces+akumar=mail.nanosouffle.net@9fans.net Received: from localhost ([127.0.0.1] helo=gouda.swtch.com) by gouda.swtch.com with esmtp (Exim 4.67) (envelope-from <9fans-bounces@9fans.net>) id 1LWXhM-0007PN-5T; Mon, 09 Feb 2009 15:05:24 +0000 Received: from tracker.proxima.alt.za ([192.96.32.140] helo=mutter.proxima.alt.za) by gouda.swtch.com with esmtp (Exim 4.67) (envelope-from ) id 1LWXhK-0007PH-RB for 9fans@9fans.net; Mon, 09 Feb 2009 15:05:23 +0000 Received: from plan9.phyrql.alt.za (gprs01.rb.mtnns.net [41.208.50.160] (may be forged)) (authenticated bits=0) by mutter.proxima.alt.za (8.14.3/8.14.3) with ESMTP id n19F4jQ1018887 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for <9fans@9fans.net>; Mon, 9 Feb 2009 17:05:02 +0200 (SAST) Message-ID: To: 9fans@9fans.net Organization: Proxima Research & Development Date: Mon, 9 Feb 2009 17:04:36 +0200 From: lucio@proxima.alt.za In-Reply-To: <4e6ca2050902090412w60795d1ap64d32b056a3b73eb@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] UPAS, IMAP, and SMTP X-BeenThere: 9fans@9fans.net X-Mailman-Version: 2.1.9 Precedence: list Reply-To: lucio@proxima.alt.za, Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.9fans.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: 9fans-bounces@9fans.net Errors-To: 9fans-bounces+akumar=mail.nanosouffle.net@9fans.net > EHLO plan9 > the connection is lost and upas tries again -- something is amiss. I seem to recall that MTAs are set to demand a full FQDN for the EHLO message? I guess GMAIL could send you some explanatory message. ++L --upas-blwslndsyzrigkfwcvpxyyaokm--