Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com From: Robert R Schneck Subject: Re: Command line email clients Date: Fri, 14 May 2004 20:49:04 +0000 (UTC) Lines: 14 Message-ID: References: X-Complaints-To: usenet AT sea DOT gmane DOT org X-Gmane-NNTP-Posting-Host: dhcp64-134-175-161.csch.sjc.wayport.net User-Agent: slrn/0.9.8.0 (CYGWIN_NT-5.1) Eduardo Chappa wrote: > I think your best option is to use Mutt, unless you really, really want > to use Pine. It is possible to use Pine, but only if you apply a patch to > make it work that way, Pine (without patching) does not send e-mail non > interactively. Pine does not require ssmtp, since Pine connects directly > to an SMTP server if you define "smtp-server" in your .pinerc file. You can also set "sendmail-path" in your .pinerc file to use "ssmtp -t". That's not particularly useful, but if you write a little script to queue outgoing mail and set "sendmail-path=/path/to/queuemail", and then have a separate script run regularly to try to send the queued mail using ssmtp -t, you have a nice way to use Pine offline. Robert -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/