|
Bugzilla – Full Text Bug Listing |
| Summary: | Subdomain stops postfix/cyrus working | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Michael Schwartzkopff <misch> |
| Component: | AppArmor | Assignee: | Dominic W Reynolds <dreynolds> |
| Status: | RESOLVED WONTFIX | QA Contact: | Dominic W Reynolds <dreynolds> |
| Severity: | Critical | ||
| Priority: | P5 - None | ||
| Version: | RC 1 | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Michael Schwartzkopff
2005-12-16 11:07:10 UTC
Thanks for the info: we will look into this issue. For working around repeated cycles for single rejects. You can use the command line utils "complain" and "enforce" to toggle the mode of a profile. So for the above: 1. Run "complain /usr/lib/postfix/local" - would toggle the profile into learning mode 2. In learning mode you can then completely execute your use case (mail delivery and retrieval) 3. Run YaST-> AppArmor -> Update Profile Wizard to capture the new behavior 4. Run "enforce /usr/lib/postfix/local" to reset this profile to enforce mode Will exercise this use case and update profile set for a maintenance release in feb. Will close this bug when the release has been pushed to the maintenance system Michael, could you attach the logfile that included the additional accesses you required to allow cyrus and postfix to work together? Thanks Sorry, but I did set up this machine nearly two months ago. Where are the logfiles saved? Michael, the logs are in /var/log/messages; if the errors were a while ago, syslog may have rotated the logs to a messages.1, or similar. Thanks No reaction for 8 months, closing as CANTFIX. |