I'd like to build the latest sqwebmail as it used to be: a CGI app without sqwebmaild. Is there a configuration option for that? If not, what's the best way to hack sqwebmaild to make it a stand-alone CGI app?
I assume that sqwebmaild was made to avoid the problems of running sqwebmail as a setuid binary. But my setup requires that feature. I let Apache take care of user authentication and access control. I use Apache::AuthKrb5AFS so my Apache acquires KRB5 tokens and AFS permissions before executing CGI scripts. That lets the old CGI sqwebmail inherit AFS permission from Apache and access user's mail directories in AFS without having to run setuid. The new daemon sqwebmail can't get KRB5 tokens from Apache (since its in anoter process space) and thus can't get into user home dirs. So, how do I make sqwebmaild act like the old sqwebmail CGI? Noel Burton-Krahn [EMAIL PROTECTED]
