Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <014f01c32701$795378f0$c69a3f42@moose>
From: "Pat Lightbody" <plightbo AT cisco DOT com>
To: <cygwin AT cygwin DOT com>
References: <045a01c326cc$71b5f580$6a01a8c0 AT moose> <20030530180234 DOT GC1860 AT tishler DOT net>
Subject: Re: Fetchmail, Procmail, and Mutt
Date: Fri, 30 May 2003 16:16:17 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

> Note that a MTA (e.g, sendmail, postfix, etc.) in not needed on the
> receive side, but...

I tried it about a year ago and I ended up at a deadend when fetchmail was
trying to deliver via an MTA. So it sounds like there is a way around this?

> > I want to use Mutt to handle my POP mail after it's been download from
> > the server.
>
> You will need one (e.g., ssmtp and/or exim) on the transmit side.

OK, i'll work on getting email first, then sending :)

-Pat



--
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/