Mail Archives: cygwin/2002/07/14/17:09:55
The readme files that were included with the package made me think that
the author mostly uses the POP features to write to his own local mail
file, but I could be wrong. thats why I suggested that the recently
released 1.4 may not have tested the combo I was using. I could of
course be wrong.
> 3. Extremely occasionally, Cygwin procmail will leave a stray .lock
> file around which can cause a misfiling of mail messages. I am
> attempting to track down the root cause of this problem. Any help
> would be greatly appreciated.
>
> I have the above problem but only on the order of once every month or
> two. So, if you are experiencing this at much higher rate, then you may
> have uncovered a different problem.
I haven't been able to detect any stray .lock files laying around, and
it happens everytime I try to write to my spool file. Once on opening,
and once on syncing, when it tries to write.
> BTW, I am still using my own private build of mutt 1.4, configured as
> follows:
I hadn't tried building mutt 1.4 plain for a while, and after reading
gary's readme files, and his mentioning of some security fixes and a
bunch of bug fixes, I was hesitant to build from the pure source. His
release notes suggests applying his patches to the original sources.
If thats not needed, I could always build from scratch too, but I would
at least like to see what gary did to the code to confirm if I need to
worry about getting his code roled in to the original source I build
from.
Thanks for the information. Its appreciated.
Guy
--
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/
- Raw text -