On Tue, Jan 30, 2018 at 05:03:54PM -0700, Gregory Nowak wrote: > The bad news is that now sqwebmail isn't working, and it still did > after my upgrade to jessie.
I have this solved thanks to a tip from the courier-sqwebmail listwhich pointed me in the right direction. The sqwebmaoil cgi binary communicates with the sqwebmail service backend through a unix domain socket sqwebmail.sock. In debian stretch, that socket lives in /var/lib/courier. The problem was that appearently in debian stretch, the permissions on that directory are 750. Changing the permissions of /var/lib/courier to 755 fixed this for me. This is a major show stopper, and should be filed as a bug if it isn't already. Can I file this in devuan's bug tracker, or do I need to install debian stretch, and file the bug from there against debian's bug tracker (if it isn't filed already)? This is a bug which effects sqwebmail for me, and doesn't seem to effect any of the other courier components I have. However, since I do have multiple courier components installed, I'm not sure if simply installing the sqwebmail package would create /var/lib/courier, or not. I suspect that it would, since sqwebmail.sock does get placed there. Can I file this against the sqwebmail package? Thanks. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
