had to chmod u-s procmail after feisty dist-upgrade

Bug #111816 reported by Eric van der Vlist
6
Affects Status Importance Assigned to Milestone
procmail (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: procmail

I have a configuration with postfix, procmail and dovecot that worked fine in Edgy.

After migration to feisty, mails were occasionally stored in mail user's directories with owner.group set to root.mail and that caused permission errors in dovecot which couldn't access these mails.

Tracking down differences between the configuration before and after the upgrade, I noticed that the suid user's bit had changed in procmail and chmod u-s procmail appears to solve this issue.

See also bug 8608 which complains of the reverse issue after migrating to Edgy!

Thanks,

Eric

Revision history for this message
Andreas Moog (ampelbein) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. Was this also a problem when upgrading to gutsy or hardy? Thanks in advance.

Changed in procmail:
assignee: nobody → andreas-moog
status: New → Incomplete
Revision history for this message
era (era) wrote :

Actually the "see also" bug should be bug 68608.

The back-and-forth decisions to revert and unrevert suid permissions are documented and somewhat explained in the changelog. These are downstream Ubuntu changes. There are other changes in the privileged operations which vaguely to me look like the original author's intentions with these mechanisms are not well understood, but then, neither do I pretend to really understand them.

Andreas Moog (ampelbein)
Changed in procmail:
assignee: andreas-moog → nobody
status: Incomplete → Confirmed
dino99 (9d9)
Changed in procmail (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
era (era) wrote :

I don't understand why the bug was changed from Confirmed to Invalid. Could you please document your reasoning, or revert the change. Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.