X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=2.4 required=5.0 tests=AWL,BAYES_00,BOTNET X-Spam-Check-By: sourceware.org Message-id: <4B844C55.1080709@cygwin.com> Date: Tue, 23 Feb 2010 16:44:53 -0500 From: "Larry Hall (Cygwin)" Reply-to: cygwin AT cygwin DOT com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.21) Gecko/20090320 Remi/2.0.0.21-1.fc8.remi Lightning/0.9 Thunderbird/2.0.0.21 Mnenhy/0.7.5.0 MIME-version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Fetchmail call to procmail no longer works under Cygwin 1.7.1-1 References: <3a8528891002220612q63d1ee8fxc69140f9b41685c5 AT mail DOT gmail DOT com> <20100223021729 DOT GA6116 AT tishler DOT net> <3a8528891002221948k38c0cc7ei24a4822a86803df6 AT mail DOT gmail DOT com> <20100223131352 DOT GA4172 AT tishler DOT net> <3a8528891002230733x644a3bc1na91ddccacafb2e41 AT mail DOT gmail DOT com> <20100223164927 DOT GA212 AT mimosa DOT garydjones DOT name> <20100223182852 DOT GD4172 AT tishler DOT net> <3a8528891002231114p3b23ef4cjced067a0b16fa9fd AT mail DOT gmail DOT com> <20100223193543 DOT GE4172 AT tishler DOT net> <3a8528891002231220w428ec33x74a19275e8a537bf AT mail DOT gmail DOT com> <3a8528891002231237u633942cfyb19ce8ead56d9d1f AT mail DOT gmail DOT com> In-reply-to: <3a8528891002231237u633942cfyb19ce8ead56d9d1f@mail.gmail.com> Content-type: text/plain; charset=UTF-8; format=flowed Content-transfer-encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 On 02/23/2010 03:37 PM, Thomas Baker wrote: >> Evidently if it does not find /home/TBaker/.procmailrc, it does >> not go looking for /home/tbaker/.procmailrc. Since my entire >> file system is based on tbaker, I'd love to find a way to eradicate >> the "TBaker" from my system entirely. The guy who set up my XP >> installation many years ago set my login as "TBaker" but it has >> never caused any practical problems until now. He should still be shot. ;-) > This worked: > $ cd /home > $ cp tbaker/.procmailrc TBaker > $ procmail VERBOSE=on procmail: [3528] Tue Feb 23 15:22:39 2010 > procmail: Rcfile: "/home/TBaker/.procmailrc" > procmail: Assigning "MAILDIR=/home/TBaker" > procmail: Assigning "INCLUDERC=/home/tbaker/u/config/procmailrc/procmailrc" > procmail: Assigning "LOG= > " > > procmail: Assigning "VERBOSE=on" > procmail: Assigning "LOGABSTRACT=all" > procmail: Assigning "MAILDIR=/home/tbaker/u/folders" > procmail: Assigning "DEFAULT=/home/tbaker/u/folders/mbox" > procmail: Assigning "PMDIR=/home/tbaker/u/config/procmailrc" > procmail: Assigning "LOGFILE=/home/tbaker/u/config/procmailrc/procmail.log" > procmail: Opening "/home/tbaker/u/config/procmailrc/procmail.log" > $ > > In a pinch, it looks like this would solve the problem, but it is an ugly > workaround. Yeah, I wouldn't go that far when a symbolic link to /home/tbaker would suffice. > It would be nicer to expunge any references to "TBaker" entirely. > I guess they are in the Win32 registry? I do not find any in my > cygwin configuration > files. > > Hang on... There it is in /etc/passwd...: > TBaker:unused_by_nt/2000/xp:1003:513:U-OCTAVIUS\TBaker,S-[...omitted...]:/home/TBaker:/bin/bash > > and /etc/passwd was last accessed on 2007-11-16, so it would seem > procmail _was_ able > to work with this before the latest update -- if indeed /etc/passwd > has anything to do with > procmail's operation... Changing the user name in '/etc/passwd' to use the proper case should resolve the problem though. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- 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