X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 	tests=BAYES_00,SARE_MSGID_LONG40
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <20100223021729.GA6116@tishler.net>
References: <3a8528891002220612q63d1ee8fxc69140f9b41685c5 AT mail DOT gmail DOT com> 	 <20100222220208 DOT GA1308 AT tishler DOT net> 	 <3a8528891002221452h48008b49t2a17aa42a97ee5e AT mail DOT gmail DOT com> 	 <20100223021729 DOT GA6116 AT tishler DOT net>
Date: Mon, 22 Feb 2010 22:48:14 -0500
Message-ID: <3a8528891002221948k38c0cc7ei24a4822a86803df6@mail.gmail.com>
Subject: Re: Fetchmail call to procmail no longer works under Cygwin 1.7.1-1
From: Thomas Baker <thomasbaker49 AT googlemail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

Jason,

On Mon, Feb 22, 2010 at 9:17 PM, Jason Tishler <jason AT tishler DOT net> wrote:
> Please note the following:
>
> =C2=A0 =C2=A0http://cygwin.com/acronyms#PPIOSPE

My apologies if I overlooked that - I'm temporarily working in googlemail
because of this procmail situation and feel out of my usual element (mutt).

>> Ah, how interesting! =C2=A0It is indeed a directory. =C2=A0I deleted the
>> directory, sent some test messages to myself, and now at least they
>> are indeed accumulating in one single mbox file called TBaker. =C2=A0That
>> is certainly progress!
>
> Hmm... =C2=A0Who or what created that directory?

The directory has been there for several years.  Maybe I created it
at some point in the belief that it was needed.  It is a credit
to the fetchmail authors that fetchmail at least gave each incoming message
a unique name and no data was ever lost through this mistake.  Mail was
always passed on to procmail -- or _almost_ always.  Two or three times per=
 year
I'd notice that mail had stopped coming and find the msg.* files accumulati=
ng
in /var/spool/mail/tbaker directory.  Rebooting would usually solve the
problem.  So this is not an entirely new problem.  What is new is that
no amount of rebooting or re-running setup.exe is fixing the problem now.
Even though the (apparently) same configuration is running smoothly on
my netbook...

>> Procmail, on the other hand, is already set to VERBOSE and writes to a
>> logfile procmail.log. =C2=A0On the netbook, where procmail works, it does
>> write to the logfile. =C2=A0On the desktop, where procmail does not work,
>> it does not write to the logfile, making me think it is somehow not
>> even being called.
>
> What happens if you call procmail from the command line directly? =C2=A0D=
oes
> it find your ~/.procmailrc file on the desktop machine?

procmail -v does find $HOME/.procmailrc and /var/spool/mail/TBaker
on the desktop machine.

> Could case sensitivity be causing your problem (i.e., tbaker vs.
> TBaker)? =C2=A0What does the "logname" command and "$HOME" variable indic=
ate
> on each machine?

On the netbook:
	logname: tbaker
	$HOME is /home/tbaker

On the desktop
	logname: TBaker
	$HOME is /home/tbaker

If this problem came up only after an update to Cygwin 1.7, after
working perfectly for years, is it possible that Cygwin is getting the
logname from a different location now?  Though I believe the logname on
the desktop has been TBaker for years.

This is drawing me deeper into the mechanics of mail than I ever
thought I'd need to go.  I'm still using Windows XP and wondering
whether this might be the moment to take the plunge to Windows 7.
Is it likely that starting with a clean install of Windows 7 and
Cygwin might just make this problem go away?  I thought that would
be more work than de-bugging fetchmail/procmail, but now I'm not so
sure.

Tom

--=20
Tom Baker <tbaker AT tbaker DOT de>

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple