Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 194044 - mail-filter/procmail sometimes "can't create user output file"
Summary: mail-filter/procmail sometimes "can't create user output file"
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Net-Mail Packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-28 00:52 UTC by John Huttley
Modified: 2007-11-26 19:18 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Huttley 2007-09-28 00:52:56 UTC
The issue has appeared on some of my machines, X86 and X86_64 going back about 6 months.
The system receives mail via postfix, which calls procmail as a transport, which calls /usr/lib/cyrus/deliver.
Sometimes procmail will fail with that message, but not always, nor always for the same user. Changing the procmail delivery service in postfix to perform one delivery at a time didn't help. Reemergeing stuff doesn't help.

Reproducible: Sometimes



Expected Results:  
Something changed a while back, the compiler, glibc, cyrus, db, something...

procmail performs a locking test during emerge, and that works ok.
I've got an instance of a user failing repeatably, so I'll try and instrument it.

In other cases, I've removed procmail and call deliver directly. However this customer needs an autoresponder...
Comment 1 John Huttley 2007-11-26 19:18:48 UTC
OK, I just haven't the means to diagnose this. However I found a workaround sufficent for my purpose.
In postfix Main.cf   put mailbox_transport=cyrus
Thats then the default, avooiding the buggy procmail.
put a line  mailbox_transport_maps=Hash:/  ....

When I have to use procmail for a user, normally to run an auto responder,
I put 
username      procmail  

in there for the duration and remove it as soon as possible.

nasty, but it works.

If someone with huge debugging mojo can look at it sometime, I'd be greatful.