From owner-freebsd-questions@FreeBSD.ORG Sat Apr 10 14:11:17 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 011A116A4CE for ; Sat, 10 Apr 2004 14:11:17 -0700 (PDT) Received: from capable.rogards.com (63-255-228-251.ip.mcleodusa.net [63.255.228.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83EC843D4C for ; Sat, 10 Apr 2004 14:11:16 -0700 (PDT) (envelope-from rbeyer@capable.rogards.com) Received: from capable.rogards.com (localhost [127.0.0.1]) by capable.rogards.com (8.12.11/8.12.11) with ESMTP id i3ALLPOR066830 for ; Sat, 10 Apr 2004 16:21:25 -0500 (CDT) (envelope-from rbeyer@capable.rogards.com) Received: (from rbeyer@localhost) by capable.rogards.com (8.12.11/8.12.11/Submit) id i3ALLOOM066829 for freebsd-questions@freebsd.org; Sat, 10 Apr 2004 16:21:24 -0500 (CDT) (envelope-from rbeyer) Date: Sat, 10 Apr 2004 16:21:24 -0500 From: "Ross A. Beyer" To: freebsd-questions@freebsd.org Message-ID: <20040410212124.GA66774@capable.rogards.com> References: <20040408171625.GA55658@capable.rogards.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040408171625.GA55658@capable.rogards.com> User-Agent: Mutt/1.4.2.1i Subject: Re: problems with Mutt and esmtp X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Apr 2004 21:11:17 -0000 > > I'm having a problem getting the Mutt and esmtp programs to work > > together. What happens is that when I run Mutt and hit send, Mutt > > will just hang forever displaying its "Sending message..." message. > > I think that it might be something to do with the sending of the > > control character signalling the end of message, but I don't know > > for sure. > >You might use the ``tcpflow'' program to look at the traffic between >mutt and the mail server. Tcpflow uses a command syntax virtually >identical to tcpdump, but splits out each connection into separate >files making it much easier to look at the converstation. Bill, Thanks for your reply, but I guess I don't understand how that would help me. My problem is not inter-machine communication, it seems to be inter-process communication. Both Mutt and esmtp work independently of each other. I can have Mutt use the local sendmail and it works fine. I can run esmtp from the command line locally (presumably just like Mutt would) and it happily creates an SSH tunnel to the remote server, and talks to the sendmail daemon there, and delivers. However, when I have 'set sendmail="/usr/local/bin/esmtp"' in my ~/.mutt/muttrc Mutt just hangs trying to send the mail, no error message, nothing. Perhaps I'm not understanding how tcpflow would help me diagnose what things are being traded between these two programs running locally. I know that tons of people must be using Mutt & esmtp together just fine. Is there a particular config variable that I didn't set, a peculiarity that I'm not taking into account, or something about FreeBSD or my shell (tcsh) that is intercepting a control character or something? -- Ross