> 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.
This worked:
$ cd /home
$ cp tbaker/.procmailrc TBaker
$ procmail VERBOSE=on <test.mbox
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. 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...
Tom
--
Tom Baker <tba...@tbaker.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
