I just moved to cygwin from debian linux and am having some problems setting up my
email. I use mutt, fetchmail, and procmail. procmail writes most of my mail to ~/mbox,
my main mbox file. However, I noticed that mutt was not picking up the messages
written to ~/mbox by procmail.
I set up mutt to poll my pop3 server itself, and when it does this it writes to the
mbox file properly. Also, I looked at my old mbox file from my linux machine and I
figured out what's wrong: procmail on cygwin is not writing the leading From line for
each message. Thus mutt is just ignoring the messages it writes. Note that procmail
(the same version, 3.22) *was* writing this line on debian.
For example, the first few lines of each message in the mbox file should look like:
From [EMAIL PROTECTED] Tue Jul 01 09:15:07 2003
Return-path: <[EMAIL PROTECTED]>
Envelope-to: [EMAIL PROTECTED]
Delivery-date: Tue, 01 Jul 2003 09:15:07 -0500
But with procmail on cygwin, I'm just getting:
Received: from bar.com [168.143.80.100]
by localhost with POP3 (fetchmail-6.2.4)
for [EMAIL PROTECTED] (single-drop); Tue, 23 Sep 2003 13:49:53 -0500 (CST)
Received: from cujo.runbox.com (193.71.199.138)
by mail01d.rapidsite.net (RS ver 1.0.86vs) with SMTP id 3-0850523058
for <[EMAIL PROTECTED]>; Tue, 23 Sep 2003 14:50:59 -0400 (EDT)
Received: from [10.9.9.15] (helo=odie.runbox.com)
by lufsen.runbox.com with esmtp (Exim 4.20)
id 1A1sFY-0005RV-Lj
for [EMAIL PROTECTED]; Tue, 23 Sep 2003 20:51:00 +0200
Received: from mail by odie.runbox.com with local (Exim 4.20)
id 1A1sFF-00024v-LY
for [EMAIL PROTECTED]; Tue, 23 Sep 2003 20:50:41 +0200
Content-Type: text/plain; charset=iso-8859-1
etc. Namely, it starts right in with the Received: headers, without ever writing the
From line. If I just add in a dummy From line copied from another message in the mbox
file, mutt can then read the message written by procmail.
Anyone know what's going on?
--
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/
