This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Mailcap and Cygwin/Mutt 1.2.5i


Tom,

On Tue, Jun 11, 2002 at 09:30:05AM +0200, Thomas Baker wrote:
> On Mon, Jun 10, 2002 at 04:16:45PM -0400, Jason Tishler wrote:
> > I just added the following in my ~/.mutt/muttrc file:
> > 
> >     set mailcap_path=~/.mutt/mailcap
> 
> Yes, I tried that and every variation I could think of thereof,
> and it never worked for me with the Unixmail build of Mutt 1.2.5i,

Please don't ask for Unixmail support on this list -- which is for
Cygwin (as in the official Cygwin distribution) related posts only.

> but it does now for the current cygwin.com build of the same that
> I just downloaded.

Good.

> > Attached is my mailcap file that can be used as a sample.  I have some
> > "glue" scripts (e.g., winword) that facilitate calling the real viewer.
> 
> Someone (Olaf?) recently posted a few of these on the mutt-users
> list.

Yes, I saw Olaf's post.  Actually, those scripts seem to be mine:

    http://cygwin.com/ml/cygwin/2002-06/msg00566.html

> > > 1) The Unixmail package has mutt_dotlock, the mutt binary was
> > >    compiled with +USE_DOTLOCK, and my muttrc has "set
> > >    dotlock_program=bin/mutt_dotlock", but the cygwin.com
> > >    binary does not have it.

The Cygwin mutt maintainer *should* rebuild mutt with "+USE_DOTLOCK".
He should build a mutt 1.4 too. :,)

> > > Is the cygwin.com Mutt somehow
> > >    more "dangerous" with regard to mail coming into an mbox
> > >    that is being read (WIN2000 file system)?
> > 
> > Probably not because the mbox files *should* be locked via fcntl()
> > too but I would recommend verifying this WAG.
> 
> When I'm reading the incoming mbox and more mail comes in, the new
> messages appear in the listing.  I take it that means it is being
> locked, perhaps by fcntl()?

IMO, the above does not imply locking via fcntl(), but the following
does:

    $ mutt -v
    Mutt 1.2.5i (2000-07-28)
    [snip]
    -HOMESPOOL  -USE_SETGID  -USE_DOTLOCK  +USE_FCNTL  -USE_FLOCK
                                           ^^^^^^^^^^
    [snip]

> > My WAG is that you are using the procmail "-m" option, because there
> > have been other recent posts reporting this problem.  If I'm correct,
> > don't do that.  Instead invoke procmail (via fetchmail) as follows:
> > 
> >     # from ~/.fetchmailrc
> >     mda "/usr/bin/procmail -d %T"
> 
> Got the message.  I'll try that, thanks!

Good.

> > Maybe?  See the following READMEs:
> > 
> >     http://www.tishler.net/jason/software/fetchmail/fetchmail-5.9.12.README
> >     http://www.tishler.net/jason/software/procmail/procmail-3.22.README
> 
> Thank you for the pointer!

You are welcome.  Please post the above URLs to the mutt-users list.
I've been lurking there (to see what is being posted about Cygwin), but
I'm not ready for yet another mailing list right now.

Jason

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]