Bug 276053

Summary:	Can't set procmail lock file in akonadi Mbox modul
Product:	[Applications] kmail2	Reporter:	Frank Noack <fgroups>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	fgroups, montel
Priority:	NOR	Keywords:	investigated, triaged
Version:	2.1.0
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Frank Noack 2011-06-19 15:26:16 UTC

Version:           2.1.0 (using KDE 4.6.4) 
OS:                Linux

I'm updated to kdepim 4.6.0 and now I have any problems with kmail2. I like to get my system messages from /var/spool/user with KMail. For this I use the MBox modul of akonadi. But I can't set a lock file in this modul. The choice is fix at "none", but I like to use the procmail lock file. There is no way to change it. 

Reproducible: Always




OS: Linux (x86_64) release 2.6.38-gentoo-r6fz
Compiler: x86_64-pc-linux-gnu-gcc

Comment 1 Laurent Montel 2011-07-05 16:28:59 UTC

it's disable if you don't have lockfile program.
Use "which lockfile" to locate it on your computer.
If you have it and it's still disable there is an other pb.

Comment 2 Frank Noack 2011-07-05 20:42:37 UTC

I have installed postfix as MTA. Postfix installed /usr/sbin/postlock. I think it's a lockfile program. But "which lockfile" finds nothing. Any suggestions?

Comment 3 Laurent Montel 2011-07-06 08:02:35 UTC

Don't know but we search lockfile program not postlock
so install lockfile

Comment 4 Frank Noack 2011-07-06 10:40:40 UTC

I installed Procmail. Kmail works now correct. But why I must install Procmail additional to Postfix? The old Kmail worked also only with Postfix und without lockfile/Procmail. Postlock also generated a .lock file.

Comment 5 Laurent Montel 2011-07-06 18:57:23 UTC

I don't know I didn't create this resource and never used procmail.
So perhaps check is not perfect but don't know.

Comment 6 Laurent Montel 2011-07-27 07:55:26 UTC

Nobody has an idea about it ?
I don't use procmail and co

Comment 7 Laurent Montel 2011-12-21 09:04:43 UTC

needs info

Comment 8 Andrew Crouthamel 2018-09-19 14:25:44 UTC

This bug has had its resolution changed, but accidentally has been left in NEEDSINFO status. I am thus closing this bug and setting the status as RESOLVED to reflect the resolution change.