[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [vps-mail] white/blacklist user_prefs editors
- Subject: RE: [vps-mail] white/blacklist user_prefs editors
- From: Matt Cohen <lists@xxxxxxxxxx>
- Date: Tue, 15 Feb 2005 21:27:35 -0800
Here's what I did:
1)downloaded the tarball, set it up in /www/htdocs/webprefs/
2)edited config.php, removed comments from line 32:
require("auth/pop3.php"); , made no other changes to config file
3)After some testing, found out that the .spamassassin directory in
the user's folder has to be set to 777 (or probably could be set
lower with some user:group changes too, but I didn't play with that),
and the user_prefs file in that folder set to 666.
That's it - all worked fine from there. Basically, i'm just using
the person's pop username & password to login. Of course, I have
users that don't know their pop password..
...
Me: ok, just enter your email password:
User: but I don't have a password!? I just open outlook and click
'send/receive' and i've never been asked for a password ?
...
HTH,
Matt
At 12:27 PM -0500 2/15/05, Jim Smith said something about:
Hi Matt. I'm sure it is more "operator error" than anything. I'm not
familiar with the setup of a PHP "auth" directory. Do I put a .htaccess file
and password protect the directory above the auth directory (in my case the
webuserprefs directory)? I tried that but it doesn't respond and sends me
back to the $return_url address (I assume that I will set up the return_url
to go to an error message?). Should I use the pop3_noimap.php file? If so,
how do I set things up so someone going in using their pop3 ID will be able
to edit their own user_prefs file?
--
:-:+:-:+:-:+:-:+:-:+:-:+:-:+:-:+:-:+:-:+:-:+:-:+:-:+:-:+:-:+:-:+:-:+:-:+
Matthew I. Cohen http://www.iwbyte.com/
It Won't Byte Web Design & Hosting. Ob. Quote: "Reality is for those
email: lists@xxxxxxxxxx people who can't handle Fantasy"
======================================================================
This is <vps-mail@xxxxxxxxxxxx> <http://www.perlcode.org/lists/>
Before posting a question, please search the archives (see above URL).
Main Index |
Thread Index