> On a Debian system, php is only available as a binary if you install
> the php4-cgi package. The PHP4 Apache module package does not contain
> any binary that is executable from the shell.
> Anyway, the binary in the php4-cgi package is /usr/bin/php4.
>
> I did not mean to say that apache has to be configured to use the PHP4
> CGI binary instead of the module.
I am not really sure what you are getting at here. The plugin works with
the apache module or php cgi. Same as squirrelmail.
The script to update the config file is the only thing that would need a
php binary, but this step is not required anyway.
> Yep, regexps are supported for the user. I did not deny that (or at
> least did not want to). Maybe my grasp of the english language is not
> that good (I'm a german native)...
>
> But if I understood it correctly, $SPAMVALUE and $UNSUREVALUE allow
> the admin to set the criteria whether a message is spam or ham or
> unsure. Conclusion: The user does not have to bother about which
> X-Header provides which information, but _can_ set a rule that sorts
> mail according to the spam/ham/unsure criteria the admin has provided
> in the config.php.
> My point is: SpamAssassin does only provide a yes/no flag in it's
> X-Spam-Status header. Additionally, I can read out the hit points as
> numerical value. But to completely figure them out, I need regexp
> support in the config.php.
>
> Anyway, while writing this, I remembered that SpamAssassin can be
> configured to always set the X-Spam-Level header, which just displays
> one asterisk for every hit point. If I assume correctly, $SPAMVALUE
> and $UNSUREVALUE are just tested against the corresponding header via
> strpos() or similar. Then I can write a rule in the config.php not
> using regexps, so my request is rather obsolete for my original
> intention.
>
We can work on adding some sort of regexp to the SPAM values.
>>> Virtual domain user setup: I think there is a way to automagically
>>> ask
>>> courier to reveal it's virtual domains, but I need some time to
>>> investigate this. Maybe there's some code I can provide.
>>
>> Why do we need this? To aviod the virtualdomains file?
>
> Nope. To avoid redundancy. The courier-mta admin needs to add the
> hosted domains to two files in completely different places using this
> approach.
>
> Some time ago, I wrote some code for another plugin that asks the
> courier-authdaemon for the corresponding system user.
> I will send it to you when I have extracted it from the plugin and you
> don't refuse in the meantime.
What is the compatiblity of this with other imap servers?
>>> The text input field for the filter criteria is a bit small for
>>> people
>>> who want to use regular expressions.
>>
>> At least you admit that there is Regular expression support.
>> We can work on this. The entries are getting too wide as it is, and
>> will not display well on low resolution screens.
>
> Sure. At least anyone who can write regexps is presumably able to
> write the regexp in $FAVORITEEDITOR for clarity and then use
> copy&paste :-)
The gui was something I wanted to work on, but is taking a low priority
right now.
>>> I would appreciate the ability to set the "default" filter; i.e. the
>>> filter that is run after all other filtering rules did not match.
>> This is supported in the config file, and not in the gui currently.
>
> What does "currently" mean? You plan to support it?
It could be easily added to the user interface, but has not. However, you
can setup a default delivery method in the config.php file.
> What I really would appreciate is that the admin could write some
> complex codeblocks that no user-friendly interface can put together.
> The user then sees the description provided by the admin and can
> insert it between his own filtering rules.
> But maybe that is too much of a feature, seen from the point of
> usability. Maybe I'm the only one who will ever use such a feature...
> so I could even write this feature myself (provided I find more of
> that damn thing named time...)
This type of feature would be nice, but is beyond what the plugin can do.
There are alot of complex filtering options that would be really nice to
have, and I intend to have them at some point. Unfortunately my time is a
bit limited. I promised the current release about 6 months ago.
|
