We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We'd like to figure out what's causing this bug for you, but we haven't
heard back from you in a while. Could you please provide the requested
information? Thanks!
** Changed in: cyrus-sasl2 (Ubuntu)
Importance: Undecided = Low
** Changed in: cyrus-sasl2 (Ubuntu)
Status: Incomplete =
It should be incomplete, not triaged.
** Changed in: cyrus-sasl2 (Ubuntu)
Status: Triaged = Incomplete
--
saslauthd forces directory permissions that prevent postfix access
https://bugs.launchpad.net/bugs/68108
You received this bug notification because you are a member of Ubuntu
Server
We'd like to figure out what's causing this bug for you, but we haven't
heard back from you in a while. Could you please provide the requested
information? Thanks!
** Changed in: cyrus-sasl2 (Ubuntu)
Importance: Undecided = Low
** Changed in: cyrus-sasl2 (Ubuntu)
Status: Incomplete =
It should be incomplete, not triaged.
** Changed in: cyrus-sasl2 (Ubuntu)
Status: Triaged = Incomplete
--
saslauthd forces directory permissions that prevent postfix access
https://bugs.launchpad.net/bugs/68108
You received this bug notification because you are a member of Ubuntu
Bugs,
John,
I did some reading and found a lead that may solve the problem. If not,
we will need to provide steps to reproduce the problem in order to
complete the bug report so it can move forward to development.
Postfix runs in chroot, so 'var/run/saslauthd must be under
/var/spool/postfix. The
John,
I did some reading and found a lead that may solve the problem. If not,
we will need to provide steps to reproduce the problem in order to
complete the bug report so it can move forward to development.
Postfix runs in chroot, so 'var/run/saslauthd must be under
/var/spool/postfix. The
Of course, you're right John. Bobby is not a developer or a Canonical
employee, feel free to reopen your bug next time.
** Changed in: cyrus-sasl2 (Ubuntu)
Status: Invalid = New
--
saslauthd forces directory permissions that prevent postfix access
https://bugs.launchpad.net/bugs/68108
Five releases old
** Changed in: cyrus-sasl2 (Ubuntu)
Status: New = Invalid
--
saslauthd forces directory permissions that prevent postfix access
https://bugs.launchpad.net/bugs/68108
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I don't mean to offend anybody, but I'm not sure what the point of
filing bug reports is when it takes over 2 years to get the first
response and then it's dismissed because it's too old. I thought Dapper
was LTS.
--
saslauthd forces directory permissions that prevent postfix access
** Changed in: cyrus-sasl2 (Ubuntu)
Status: Incomplete = New
--
saslauthd forces directory permissions that prevent postfix access
https://bugs.launchpad.net/bugs/68108
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cyrus-sasl2 in
** Changed in: cyrus-sasl2 (Ubuntu)
Status: Incomplete = New
--
saslauthd forces directory permissions that prevent postfix access
https://bugs.launchpad.net/bugs/68108
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This was Dapper. I have since rebuilt the server with Intrepid roughly
following the Ubuntu Server Guide and did not have this problem.
However, the last I knew, my hack to the init.d script to munge the
permissions was still necessary.
--
saslauthd forces directory permissions that prevent
This was Dapper. I have since rebuilt the server with Intrepid roughly
following the Ubuntu Server Guide and did not have this problem.
However, the last I knew, my hack to the init.d script to munge the
permissions was still necessary.
--
saslauthd forces directory permissions that prevent
What version of Ubuntu are you using? Is this still an issue?
** Changed in: cyrus-sasl2 (Ubuntu)
Status: New = Incomplete
--
saslauthd forces directory permissions that prevent postfix access
https://bugs.launchpad.net/bugs/68108
You received this bug notification because you are a
What version of Ubuntu are you using? Is this still an issue?
** Changed in: cyrus-sasl2 (Ubuntu)
Status: New = Incomplete
--
saslauthd forces directory permissions that prevent postfix access
https://bugs.launchpad.net/bugs/68108
You received this bug notification because you are a
17 matches
Mail list logo
