On Wed, Feb 02, 2005 at 02:58:43PM -0500, Roger Merchberger wrote: > %ENV=(); # which basically wipes out any remaining environment. > > All I had to do was comment out that line, and everything works > like a champ! Thanks all!
Great! > >This is the exact same error that showed up a while ago for Jos, who > >also used a custom checkpassword program, even if his implementation > >was in C. > > Ah, then it didn't pop up during my searches of the archives. I'll > have to try to do better next time. 'Course, I'd centered my > searches around ' error 111 ', so if I gratuitously embed it here > subliminally, someone else searching for it may find it... ;-) 111 is basically a catch-all error code for anything that fails after the connection has been accepted but before bincimapd has started and is ready to accept commands, which makes it a less than ideal search string/keyword. > Every couple of years I try to allocate enough time to learn it > well enough, but then I get sidetracked/busy... so I still don't > know it very well. I never seem to have enough 'round tuits' in my > toolbox, you know... I guess you just have to decide on a project and go through with it. But it probably shouldn't be anything with a deadline when you're doing it to learn a new language. :) As for toolbox, well, it'll grow over time. > >Does vcheckpw (?) from vmailmgr support PGSQL? > > When I wrote my program, PGSQL support was minimal, and it didn't > support using a hashed directory structure. If it does now, why not use it, that way you'll future proof for any changes made in vmailmgr as well. > and compared to SpamAssassin, the overhead of a perl checkpassword > program is nothing. ;-) Well, overhead is one concern, but I think the security viewpoint is more important. > Well, thanks to your help, I now have it working! Thanks a lot, and > y'all have a good day, eh? I'm glad it works! :) //Peter
