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 From: "Gary R. Van Sickle" To: Subject: RE: Cygwin maildrop patches and issues (was Re: fetchmail 5.9.8 ...) Date: Thu, 25 Apr 2002 23:45:45 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal In-Reply-To: <20020426014050.GE1616@tishler.net> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 > > What you mention is true: maildrop is closely associated with maildirs > > (and it was due to one of my colleagues, who swears by maildir on any > > OS, that I came accross it). I intended to use mutt with maildirs, > > including a shared mail archive we keep, but did not get around to it. > > I tried Cygwin mutt 1.3.24 with maildirs and it did not seem to like the > ones generated by maildrop. If it did, this would "solve" (OK workaround) > any locking problems. > > Has anyone had success with mutt and maildirs? > FWICT maildirs have some filename issues (illegal chars in the names) that Windows chokes on. I can get inboxes to work OK, but e.g. mutt puts ":"'s and ","'s in the filenames it tries to create in your "received" folder. I do have a build of 1.3.28 that works OK with its *own* inbox maildir. Do you want the EXE to try out? -- Gary R. Van Sickle Brewer. Patriot. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/