From owner-freebsd-questions@FreeBSD.ORG Wed May 16 15:21:33 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6CDF91065670 for ; Wed, 16 May 2012 15:21:33 +0000 (UTC) (envelope-from ramirocaso08@gmail.com) Received: from mail-gg0-f182.google.com (mail-gg0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 22E448FC16 for ; Wed, 16 May 2012 15:21:33 +0000 (UTC) Received: by ggnm2 with SMTP id m2so1024051ggn.13 for ; Wed, 16 May 2012 08:21:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=+FRc8w7xy9wU9uj405zJPH+39tb5uee+5iN9zzHNIjY=; b=LbEzzWgGaR8m7rdLVwAQqDn36+XGNAk8qbrf1QfaqAuh0xavlBnUkefTm0oMjFgMdQ ioac147hjiQ8aOpnYrmFwxBsodu7ggHC2wcs9NPC/qh5Yrq+UnaFxIvwxEkaPOq15TcO 1dJ2YodCFR8VctAnnl7kPEF9bLf7+h0Xaijw33HtBNTq8umT/wOGQCCLLOKEoqdGG9Yv 3L3p6fSoTPxpkN9OJzXeNOz+0Q8Y1yJHfh2PSiU0MZWxW/0x9abFWzOXfr/iMF+tji4T PGvuSuDVwNdLlNMAaC+eqLAkdeBdBfpllm5wqG/t8lcqJUJvGhHVhP6RrzPKw2dXxc3o PvJA== Received: by 10.101.73.14 with SMTP id a14mr1215707anl.12.1337181692338; Wed, 16 May 2012 08:21:32 -0700 (PDT) Received: from [192.168.1.104] ([186.22.171.89]) by mx.google.com with ESMTPS id i2sm4847844anl.9.2012.05.16.08.21.28 (version=SSLv3 cipher=OTHER); Wed, 16 May 2012 08:21:31 -0700 (PDT) Message-ID: <4FB3C5F6.5040204@gmail.com> Date: Wed, 16 May 2012 12:21:26 -0300 From: Ramiro Caso User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:12.0) Gecko/20120503 Thunderbird/12.0.1 MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <4FB3ADA9.6060501@yahoo.com.ar> <9407d3f053a5b149c1cbd5d41d9777f1.squirrel@webmail.bsdftw.org> In-Reply-To: <9407d3f053a5b149c1cbd5d41d9777f1.squirrel@webmail.bsdftw.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: (mutt +) msmtp problem? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 May 2012 15:21:33 -0000 On 16/05/2012 11:04, James Edwards wrote: >> I use mutt (1.5.21) with msmtp (1.4.28) as MDA. Usually, everything goes >> smoothly, but every once in a while I lose network connectivity when >> sending email (I don't recall whether there is a correlation between >> this problem and my trying to send not-so-big but yet around 1mb files). >> >> Basically, what happens in trying to send an email is: >> >> May 16 10:01:17 **** wpa_supplicant[662]: CTRL-EVENT-DISCONNECTED >> bssid=**:**:**:**:**:** reason=0 >> ....... >> May 16 10:02:27 **** wpa_supplicant[662]: CTRL-EVENT-CONNECTED - >> Connection to **:**:**:**:**:** completed (reauth) [id=0 id_str=] >> ....... >> >> Then I try again, and the same thing happens. All msmtp's log shows is: >> >> errormsg='cannot write to TLS connection: Pipe Broken' exitcode=EX_IOERR >> >> Any ideas? >> >> Best, >> Ramiro > > Based on above, mutt and msmpt *appear* to be fine, but this seems to be a > problem with the wireless driver, card, or router - you are being > disconnected from the network, which in turn is causing the 'broken pipe'. Indeed, mutt + msmtp appear to be fine... My bad for not being clearer... However, there is a correlation that goes beyond credible coincidence: the disconnection happens when (and, as far as I can recall, only when) I use mutt + msmtp to send sizeable files. In particular, no disconnection occurs when I'm not using mutt + msmtp, or when I use mutt + msmtp but I send emails without sizeable attachments. Also, the disconnection happens within seconds of attempting to send the sizeable emails. I guess it is a problem with the wireless card, but it seems to be somehow closely linked to the event of trying to send sizeable emails using mutt + msmtp (when I use thunderbird to send the files, everything works as expected, no disconnection). > You could feasibly work around it by using a wired connection, or take a > look at what is going on with your wireless. My work around, for now, is to use thunderbird for sending large emails, so there's no hurry. But I'm a bit puzzled about what's happening.