Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date: Sat, 15 Feb 2003 21:11:21 -0500
From: Ajay Simha <asimha AT cisco DOT com>
To: Max Bowsher <maxb AT ukf DOT net>, Ajay Simha <asimha AT cisco DOT com>,
   cygwin AT cygwin DOT com
Subject: Re: procmail and NTSEC
Message-ID: <20030216021121.GA3884@cisco.com>
References: <20030215152030 DOT GA1916 AT cisco DOT com> <001a01c2d505$ea7ae2f0$78d96f83 AT pomello> <20030215160221 DOT GA1232 AT cisco DOT com> <002801c2d50c$996b11d0$78d96f83 AT pomello> <20030215213459 DOT GA1032 AT cisco DOT com> <20030216085449 DOT A9196 AT ms>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030216085449.A9196@ms>
User-Agent: Mutt/1.4i

On Sun Feb 16 08:54:49 2003, Greg Matheson wrote:
> On Sat, 15 Feb 2003, Ajay Simha wrote:
> 
> > > >>> When I had NTSEC on I'd get:
> 
> > > >>> $ procmail VERBOSE=yes .procmailrc < testmail
> > > >>> procmail: [3936] Wed Feb 12 00:39:58 2003
> > > >>> procmail: Suspicious rcfile "/home/asimha/.procmailrc"
> > > >>> procmail: Couldn't read "/home/asimha/.procmailrc"
> 
> I don't know about NTSEC, but man procmail says:
>        Suspicious rcfile "x"  The owner of the rcfile was not the recipient or
>                               root, the file was world writable, or the direc-
>                               tory that contained it was  world  writable,  or
>                               this  was the default rcfile ($HOME/.procmailrc)
>                               and either it was group writable or the directo-
>                               ry that contained it was group writable (the rc-
>                               file was not used).

Yes. It was a combination of not having the right content in /etc/passwd /etc/group
and file permissions and directory permissions of my home directory.

Now for the record here is what things look like:

asimha AT ASIMHA-W2K /home]$ ls -l
total 0
drwx------+   8 asimha   Administ        0 Feb 15 21:03 asimha

[asimha AT ASIMHA-W2K ~]$ ls -l .procmailrc
-rw-------+   1 asimha   Administ     2246 Feb 15 00:38 .procmailrc

[asimha AT ASIMHA-W2K ~]$ !procmail
procmail VERBOSE=yes .procmailrc < testmail
procmail: [3836] Sat Feb 15 21:06:48 2003
procmail: Rcfile: "/home/asimha/.procmailrc"
procmail: Assigning "MAILDIR=/home/asimha"
procmail: Assigning "MAILDIR=/home/asimha/mail/"
procmail: Assigning "FORMAIL=/usr/bin/formail"
procmail: Assigning "LOGFILE=/home/asimha/procmail.log"
procmail: Opening "/home/asimha/procmail.log"

Now ssh is happy with the permissions and ownership as well.

Thanks to all who helped.  And anyone who runs into this problem please feel free to email me
(while copying cygwin AT cygwin DOT com of course :-).

I now have mutt, procmail, fetchmail, ssh, aspell combination working. I want to get something
decent working for printing from within mutt next.

Currently for printing from mutt I use a simple shell script:


#!/bin/sh
cat $1 > /tmp/tmp.txt
cygstart --print /tmp/tmp.txt

this allows the tmp.txt to be handled by winword (default handler for txt files in my setup).

I'm sure that there are better ways but this works for directly connected and network printers.

-ajay
> 
> So perhpas your home directory is world writeable, or group writeable.
> 
> -- 
> Greg Matheson            No trees were killed in the sending of this message. 
> Dr Bean's Penpal Pool    However, a great many instructions were executed. 
> Address: palpool         --from Richard Rognlie's signature
> Domain:  @cn91.chinmin.edu.tw

--
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/