message bodies not saved

[kgourlay]

Hi, I've been exploring piler and it looks like a great choice for our small organization. I am most familar with Rocky or CentOS in production, so I have been working on installing piler on my Rocky 10 development system. I installed from source and after correcting some permissions errors and a missing Python package it appears to be mostly working.

Mail is being imported and metadata shows up in the web ui, but message bodies and attachments do not. Files are being created in /var/piler/store but I'm guessing they don't contain what they're supposed to because they're all the same size. I haven't located any errors in the logs when a message comes in, but I did see some like this when trying to use the web ui:

Jul 24 09:16:40 dev pilerget[962358]: /var/piler/store/00/6a6/9b/23/500000006a636393262242ac008687a19b23.m: cannot open()

I'm stuck on this one. It seems like it might be another file permissions issue, but I can't figure it out. Any suggestions?

[kgourlay]

Digging a little deeper and this looks like I was mistaken about files being created but not containing what they are supposed to. The files actually are fine, since I can ready them with pilerget from a shell. So this may be a similar issue to #456 . But setuid and setgid are correct on the binary.

So it appears that what is happening is my php-fpm configuration is ignoring the setuid / setgid flags on pilerget and running it as the php-fpm user (apache in my case). If I give apache permission to /var/piler/store then things start working the way I'd expect from the webui.

I'm not sure if this makes sense as a solution. In my development environment the permissions are not critical, but in production it may be more important to keep the mail archive protected from other PHP scripts. If/when we are ready to put this in production, I'm inclined to spin up a dedicated VPS anyway, so that might make the question moot.