Jay Lee wrote:
... The other
possiblity would be getting your hands on the 1.4 beta of serversidefilter
plugin. I believe it was posted to the squirrelmail-devel list a few
weeks back. The 1.4 version will include a secure SUID binary that will
perform the filter installation with the proper rights.
Unfortunately, the included binary is for Linux. The makefile, to rebuild it, is set up for Linux, and I don't have the expertise to port it to FreeBSD. Even worse, it requires libraries that are created, but not installed, during a build of the mail client "pine", and I definitely don't have the expertise to extract that section from the pine build and make it into a port that would build and install the proper libraries on their own, as the documents suggest is true on on some Linux distros (that they are installed separate from pine).
It looked like the perfect solution to my problem, but sadly, I don't think I can use it. :-(
I decided to not give up so easily. :)
When I installed my FreeBSD (5.2.1-RELEASE-p3) system, I declined to set up Linux emulation. So, I installed the "linux_base" port, and added 'linux_enable="YES"' to my /etc/rc.conf file. So now I had Linux emulation going.
After following all the installation instructions, I tried to run the test.sh script that comes with the plugin, to see if it would work. It attempts to get and put a user's filter file. This didn't work so well. First, I had to port the script, as the test commands were incompatible with FreeBSD's /bin/sh command, and they weren't properly saving the exit codes in some places. Having fixed the script, I tried again. This time, I got errors related to, and from, the binary itself. Turns out I had to 'brand' the binary, so that FreeBSD would know how to run it. That was accomplished by running:
brandelf -t Linux filtercmd
I tried once more, but again, it failed, saying the credentials I gave it were bad. On a hunch, I turned off STARTTLS on port 143, and tried again - success! Now, I *need* the connection to be secure (local policy). The Makefile for filtercmd clearly allows for tls support (or not), depending on a setting. Perhaps I need to specify something to filtercmd to tell it to use tls to port 993, instead of clear text to port 143, or perhaps I need a binary that has the tls support compiled in, as maybe this one doesn't have it. So, that's the next step - to figure that out.
Just thought I'd document getting this to work, for any other FreeBSD'ers out there who are thinking of using this module. :)
-ste
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
