Quoting Sandy Drobic <[EMAIL PROTECTED]>:
[EMAIL PROTECTED] wrote:
I'm on opensuse 10.1.
I read the mailing list and noticed many people with the same problem.
Cyrus and Postfix are on the same machine.
Postfix cannot connect to the ltmp socket and deliver mail to Cyrus, so
it can then deliver to users:
---
host postfix/lmtp[7070]: A8721F25E: to=<[EMAIL PROTECTED]>, relay=none,
delay=17,
status=deferred (connect to
/var/lib/imap/socket/lmtp[/var/lib/imap/socket/lmtp]: Permission denied)
---
srwxrwxrwx 1 root root 0 Jun 25 10:33 /var/lib/imap/socket/lmtp
drwxr-x--- 13 cyrus mail 4096 Jun 26 08:03 imap (/var/lib/imap)
---
user cyrus is cyrus.mail
user postfix is postfix.postfix
---
the user Postfix does not have permission to access the socket.
I tried to stop apparmor, but even so it didn't work, with the same
message. I went thru the apparmor profiles and there was nothing about
the postfix user/group neither the executable or that particular
diretory. The apparmor profiles are the same from default install, and
all mentioned software are from the 10.1 repositories.
When I add the postfix user to the mail group, it works ok. But I don't
want to do that, it might cause some misbehavior(?), I would like a
What misbehaviour did you encounter?
Sorry, I wasn't clear, I meant, changing the default users/groups
permission setup might cause eventual misbehaviors/problems.
different more "correct" approach, say to change apparmor config to let
the postfix user or the executable from postfix which tries to use that
socket to do so. What do you think would be more appropriated?
It's a rather miserable affair. The Default configuration does not cover
the delivery via lmtp. I think they fixed the permissions in 10.2, though
I haven't checked it lately. Adding postfix to the mail group was a
sufficient solution for me.
Since you (and others, I read some more messages) reported changing
permissions with apparently no collateral effects solved the problem,
I'll try this. The emails I read were from previous opensuse versions,
and since I still have the problem on 10.1, I don't plan to go to 10.2
or 10.3 now, I decided to check the mailing list first.
You could simply tell Cyrus to put the socket in a directory where the
user postfix already has access to. Though I am not sure if this will
break when you update. It shouldn't break. Another question is if you have
other applications that need to access the socket?
Right now just postfix and cyrus. This might change in a near
future, I may consider moving the socket elsewhere.
thanks,
Lauro
--
Sandy
List replies only please!
Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
