Message Board Integration (YaBBSE, its easy - how to share)

Hello Dev.

I've encorperated the YaBBSE message board into my SM
install as a form for all SM users to converse with
eachother.

http://jadz.com/screenshot.jpg

It was very easy to do, I removed the cookie based
authentication used in YaBBSE and used the session
$username to authenticate. If the user does not exist in
the YaBBSE database he/she is automatically added.

I think that other people would be interested in this but
I'm not sure how to get it to them. Can you make a plugin
that requires the installation of other software (YaBBSE
in this case).

Perhaps this has been done and documented somewhere else...
(not I didn't use the spelling plugin on this one)

-----------------------------------------------
Joseph D. Adams - Youth Opportunities Unlimited
4 1/2 Camp Road - Kingston 4, Jamaica W.I.
W: 876-759-2080  H: 876-946-2850 C: 879-387-9766
Electrical and Computer Engineering Alumni '02
Dalhousie University

-------------------------------------------------------
This SF.net email is sponsored by: Get the new Palm Tungsten T 

Re: Using hidden imap-folders for storing information

>> I don't think this is possible with the UW server, the user can see
>> every file under their home directory (and the directories below it)
>> as a potential folder. This even includes files beginning with a dot.
>>
> Thnx for the reply.
>
> I just did some further research and probably all servers with the acl
> extension supports hidden mailboxes. (just remove the list property from
> the acl)
> With UW it's like you said more complex. In the mailinglist I read
> something about a hidedotfiles option in the recent UW releases.

Talking about UW.

I know lot of people uses it because it comes pre-installed on most
distros. It hasn't got many features, but it's stable and strong. I say
this because UW is an IMAP server we've got to take into account.

Maybe we can think in a way to complement UW. Mainly we're talking about
two features we need: Folders containers that can contain messages (UW
can't) and hidden folders.

Both things can be achieved from inside SM emulating these features. For
example we can create "hidden folders" called -root or something like that
into each container, and show its content when the container is clicked.
SM will be the responsible in not showing such folders. Hidden folders for
sensible data and address book could work exactly the same. SM will hide
them.

Re: Using hidden imap-folders for storing information

>>> I don't think this is possible with the UW server, the user can see
>>> every file under their home directory (and the directories below it)
>>> as a potential folder. This even includes files beginning with a dot.
>>>
>> Thnx for the reply.
>>
>> I just did some further research and probably all servers with the acl
>> extension supports hidden mailboxes. (just remove the list property
>> from the acl)
>> With UW it's like you said more complex. In the mailinglist I read
>> something about a hidedotfiles option in the recent UW releases.
>
> Talking about UW.
>
> I know lot of people uses it because it comes pre-installed on most
> distros. It hasn't got many features, but it's stable and strong. I say
> this because UW is an IMAP server we've got to take into account.

The reasons I use UW are:

- it's installed with RedHat, so it's "just there"
- it works (I haven't had any problems with it)
- it keeps everything in the standard mailbox format, which means I can
easily knock up simple scripts to manage regular tasks

N.B. on the last point, no doubt I could rewrite these scripts and get the
same functionality if I moved to Cyrus or something, but that would be
something else new to learn. For a server with 5 users it's not worth it.

At one point I thought I was going to have to move to Cyrus because

Re: Using hidden imap-folders for storing information

I like the idea of simlpifying prefs, but an unhidden folder is not a 
good idea.

My users primarily use pc-based imap clients, and only use SM when they 
are not at their normal PC.

Also, admins will like the freedom to install different imap servers, 
so any system has to be movable.

Michael

On Sunday, December 1, 2002, at 03:12  PM, 
squirrelmail-devel-request <at> lists.sourceforge.net wrote:

>> The only problem left will be with external IMAP clients. For the case
>> of the -root folder I would leave it the way it is, making sure the 
>> user
>> knows that these folders called -root are the -root messages container
>> of the folder. For the rest we could unsubscribe on logout and
>> re-subscribe on login.
>
> I tend to leave SM logged on at least one locked machine most of the 
> time
> and then access the IMAP server from another external client in the
> meantime, I know some of my users do too.

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

Spell checker executing my message...

Greetings,

I was spell checking a post that had this code example (PalmOS):

// Set the label of the category trigger.
ctl = ToolsGetFrmObjectPtr(frmP, ListCategoryTrigger);
CategoryGetName (AddrDB, CurrentCategory, CategoryName);
CategorySetTriggerLabel (ctl, CategoryName);

Needless to say, this confused the heck out of the spell checker.  Try it.
 Here is the error I get:

Notice: Undefined index: ToolsGetFrmObjectPtr in
/usr/site/pages/squirrelmail/plugins/squirrelspell/modules/check_me.mod on
line 194

Matthew

-------------------------------------------------------
This SF.net email is sponsored by: Get the new Palm Tungsten T 
handheld. Power & Color in a compact size! 
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
--
squirrelmail-devel mailing list
List Address: squirrelmail-devel <at> lists.sourceforge.net
List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=7139
List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-devel

[PATCH] Message hilighting with regexps

Hi,

I read a message on -users recently that stated users weren't able to
specify more than one 'matchword' in one message hilighting rule. 

For example if you wanted to hilight messages in orange that either
contained 'foo' or 'bar' you'd have to create two rules in the message
hilighting 'configuration screen'.

I made it use 'ereg' and made the code a little more readable by
indenting 'the right way' (SM uses spaces and no tabs, right?) and I
replaced the eccessively long 'message_highlight_list_part' by
'msg_hlt_elem' which also improved readability. ;)

ereg has the nice feature that 'ereg('needle', 'haystack')' functions the
same as strstr('needle', 'haystack'). What I mean to say is that ereg
does not *REQUIRE* a regular expression, therefore, people won't notice
this change in having to change their current highlighting rules.

Patch attached, I hope it can be patched in.

With regards,
Sander.

--

-- 
| One tequila, two tequila, three tequila, floor.
| 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8  9BDB D463 7E41 08CE C94D

--- mailbox_display.php.orig	2002-12-02 21:10:25.000000000 +0100

Re: Spell checker executing my message...

> Needless to say, this confused the heck out of the spell checker.  Try it.
>  Here is the error I get:
>
> Notice: Undefined index: ToolsGetFrmObjectPtr in
> /usr/site/pages/squirrelmail/plugins/squirrelspell/modules/check_me.mod on
> line 194

It's not actually executing your code (thank god), but it is definitely a
bug.  I think I have managed to nail it down, please try the enclosed
patch and let me know if it helps.  It should be applied to
SM_DIR/plugins/squirrelspell/modules/check_me.mod

--

-- 
Chris Hilts
chilts <at> birdbrained.org

Weird behavior

Hi,

If you create a message highlight rule, and then try to delete it,
you end up with a white page telling you 'FOUND! The page has moved
_here_'. 

Investigation shows that $SCRIPT_NAME is empty, at line 64 of
src/options_highlight.php. PHP itself doesn't know about or set this
variable, so I guess somewhere else in the source this variable should
be set but isn't.

I see that crypto_badkey.mod and sqspell_functions.php use the same
variable, they only call global $SCRIPT_NAME; before actually using it.

I tried doing the same in options_highlight.php, but with no effect.
Weird. I hope this message helps to fix this 'problem' ;)

HTH,
Sander
--

-- 
| Does killing time damage eternity?
| 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8  9BDB D463 7E41 08CE C94D

Re: Weird behavior

Quoting Sander Smeenk (ssmeenk <at> freshdot.net):

** FUP to myself, I hate that, but I have to ;)

> Investigation shows that $SCRIPT_NAME is empty, at line 64 of
> src/options_highlight.php. 

The correct way, according to php.net is:

| <?
|  global $_SERVER;
|  header();
|  echo "Server var: " . $_SERVER['SCRIPT_NAME'] . "<br>";
| ?>

Which yields, at my Apache2 system running php4-cgi:

| "Server var: /php4/php4"

So in fact we have two problems now. One: $SCRIPT_NAME being the
incorrect representation of $_SERVER['SCRIPT_NAME'] and the possibility
that an admin is using php4-cgi so SCRIPT_NAME points to the
CGI-program, in this case PHP itself.

Now I was told PHP_SELF usually is the same as SCRIPT_NAME and in my
case, PHP_SELF *does* contain '/test.php'. 

What do you think, do you want me to patch every $SCRIPT_NAME occurance
and make it point to $_SERVER['PHP_SELF'] ? 

Re: Weird behavior

Quoting Sander Smeenk (ssmeenk <at> freshdot.net):

** I keep FUP'ing to my self :) I have no-one else to talk to :p

> What do you think, do you want me to patch every $SCRIPT_NAME occurance
> and make it point to $_SERVER['PHP_SELF'] ? 
> I can't really test what PHP_SELF yields on a native mod_php4 system.

I tested it alright, with the help of my friends Arie Willem Speksnijder
and Robert Krenn.

On PHP 4.0.3 PHP_SELF returned the php script name. This server runs
Apache 1.3.xx with mod_php.so loaded.
On PHP 4.3.2 PHP_SELF returned the php script name. This server runs
Apache 1.3.xx with php compiled in
On PHP 4.3.2 PHP_SELF returned the php script name. This server runs
Apache 2.0.43 with php4 as a CGI-executable.

So I think the reliable way to go is PHP_SELF. 

Problem is that on PHP 4.0.3, this variable is reached by doing:

| global $HTTP_VARS;
| echo $HTTP_VARS['PHP_SELF'];

And with PHP 4.2.3 this variable is reached by doing:

| global $_SERVER;
| echo $_SERVER['PHP_SELF'];