Re: [Dovecot] pop3 gives a permission denied error on chdir
On Thursday 21 May 2009 12:40:00 you wrote:
exec "strace -f -o /tmp/access.log -etrace=file -p
" then try to access pop3 when fail occurs send us /tmp/access.log (gzipped)
attached
-- regards Kenneth Gonsalves Associate NRC-FOSS http://nrcfosshelpline.in/web/
On Thursday 21 May 2009 12:51:11 Kenneth Gonsalves wrote:
On Thursday 21 May 2009 12:40:00 you wrote:
exec "strace -f -o /tmp/access.log -etrace=file -p
" then try to access pop3 when fail occurs send us /tmp/access.log (gzipped) attached
were you able to detect anything? I am still stuck with the problem.
regards Kenneth Gonsalves Associate NRC-FOSS http://nrcfosshelpline.in/web/
On May 25, 2009, at 7:16 AM, Kenneth Gonsalves wrote:
On Thursday 21 May 2009 12:51:11 Kenneth Gonsalves wrote:
On Thursday 21 May 2009 12:40:00 you wrote:
exec "strace -f -o /tmp/access.log -etrace=file -p
" then try to access pop3 when fail occurs send us /tmp/access.log (gzipped) attached
were you able to detect anything? I am still stuck with the problem.
Well, strace says what Dovecot also says:
5598 chdir("/home/vmail/example.com/john") = -1 EACCES (Permission
denied)
On May 25, 2009, at 1:28 PM, Timo Sirainen wrote:
On May 25, 2009, at 7:16 AM, Kenneth Gonsalves wrote:
On Thursday 21 May 2009 12:51:11 Kenneth Gonsalves wrote:
On Thursday 21 May 2009 12:40:00 you wrote:
exec "strace -f -o /tmp/access.log -etrace=file -p
" then try to access pop3 when fail occurs send us /tmp/access.log (gzipped) attached
were you able to detect anything? I am still stuck with the problem.
Well, strace says what Dovecot also says:
5598 chdir("/home/vmail/example.com/john") = -1 EACCES (Permission
denied)
I can't really give any more suggestions. It should either be a
directory permission problem somewhere or SELinux or something. You
could maybe temporarily try installing v1.2 and see what it logs as
the error. It should tell what exactly is missing.
On Monday 25 May 2009 23:00:46 Timo Sirainen wrote:
were you able to detect anything? I am still stuck with the problem.
Well, strace says what Dovecot also says:
5598 chdir("/home/vmail/example.com/john") = -1 EACCES (Permission denied)
I can't really give any more suggestions. It should either be a directory permission problem somewhere or SELinux or something. You could maybe temporarily try installing v1.2 and see what it logs as the error. It should tell what exactly is missing.
SELinux is not installed, and since dovecot is able to write to the concerned directory when delivering mail, I do not think it is a permission problem. I think the error message is somehow wrong - I will install v1.2 and try again.
regards Kenneth Gonsalves Associate NRC-FOSS http://nrcfosshelpline.in/web/
On Tue, 2009-05-26 at 11:24 +0530, Kenneth Gonsalves wrote:
I can't really give any more suggestions. It should either be a
directory permission problem somewhere or SELinux or something. You
could maybe temporarily try installing v1.2 and see what it logs as
the error. It should tell what exactly is missing.SELinux is not installed, and since dovecot is able to write to the concerned directory when delivering mail,
Mail delivery path is completely different. There it's your MTA that sets up the permissions before calling deliver.
I do not think it is a permission problem. I think the error message is somehow wrong - I will install v1.2 and try again.
If strace says chdir() failed with EACCES, the only way it could be something else is if kernel is buggy or there is some kernel security module preventing the access.
If strace says chdir() failed with EACCES, the only way it could be something else is if kernel is buggy or there is some kernel security module preventing the access.
Or dovecot doesn't change uid to user one and still acts as dovecot user, but its unlikely to be true
If strace says chdir() failed with EACCES, the only way it could be something else is if kernel is buggy or there is some kernel security module preventing the access.
Or dovecot doesn't change uid to user one and still acts as dovecot user, but its unlikely to be true . solved - I had to reboot the server because postgresl was acting funny in another application - after the restart, it worked perfectly. Only I lost my 59 days uptime. Sorry to trouble you guys, but this is the first time in my
On Tuesday 26 May 2009 13:33:24 Max Ivanov wrote: life that I have solved a problem in a linux box by rebooting.
regards Kenneth Gonsalves Associate NRC-FOSS http://nrcfosshelpline.in/web/
participants (3)
-
Kenneth Gonsalves
-
Max Ivanov
-
Timo Sirainen