Hi, On 03.03.2015 21:16, Janos SUTO wrote: > > Hello, > > On 2015-03-03 20:53, Frederik Wagner wrote: >> >> I'm using Debian wheezy. No SElinux or Apparmore enabled. > > ok > >> Somebody suggested that the access rights to the piler.key could wrong: >> It belongs 'root:piler' with mode 0640. For the access of the piler >> cmdline utilities it is ok, since I can retrieve mails with 'pilerget'. >> >> Does the WebUI also need access to the key? Should the webserver also be >> able to read the key? > > no, messages are read (using piler.key) by a setuid utility (pilerget), so > switch to user piler, then run 'pilerget 40000......' and see what happens, > check the maillog in case of a problem. For an exact piler id also check > the > maillog.
It's working, 'pilerget' on an archived message, as user 'piler'. Also I cannot find any errors in the mail.log. Is there a way of increasing Debug ouput, so I can see what happens, when the WebUI tries to retrieve message content? Thanks lot! Frederik > >> >> BTW: I configured with --sysconfdir=/etc/piler, so the key resides >> /etc/piler. Do I have to change any extra config in the WebUI? > > no > > Janos >
