>>> > You have abook_take and address_add. Both provide same function. >>> >>> Wasn't sure if they did the same things or not... which is the better > solution? >> >> you choose. one provides button at the bottom of window. Other provides > link near sender's name. > > OK... will wait for the reports back from the users to see which they > prefer.
As I just stated in my previous email, they are different in where the link/button is and what email addresses they parse out of the message. They run together just fine. This is not your problem. >> line 29 in page_header.php creates beginning of html page. line 129 in > global.php is part of code invoked by running sqsession_register > function. > > OK... I'll try to look at what plugins might be doing it... is there a > trace mode that would trace entrance and exit of every function? > >> sqsession_register function should be run before any html output starts. >> >> you somehow loose your session information and system tries to start new > session, or some plugin includes global.php in the wrong place. Or some > combination causes plugin to think that you've lost session information. >> >> Enable plugins one by one. Only if you really need them. If the errors are appearing at the bottom of the compose screen, try only removing sent_confirmation. I believe I introduced a non-critical error in the last release that causes such notices to be displayed. They shouldn't stop things from working, however. Will be making a new release when I have a spare minute for not answering emails. ;) Also, get a snapshot of 1.4.3 and GET RID of compose_fix. It is buggy, and if your errors are on the compose page, this plugin will definitely be part of the problem. Fixes in 1.4.3 include at least half of what this plugin does, but they do it "the right way" > Right now we are in the stage where our user services consultants are > kicking the tires and seeing what functions they want me to persue and > which we can get rid of. > >> If you have server with 5K users, enabling filters plugin is the last > thing that you would do. It would take only several advanced email users > to overload your server. Make sure that interface is responsive and > optimized. Only then add extra features. > > Believe me I'd much rather enable something that could create and maintain > a maildrop file for each user. However as a virtual system there is no > home directory nor a .forward for each user. There is a qmail/vpopmail > directory and I could put a .qmail file into the system but I would still > need something that can handle creating maildrop files. Anyone know of a > plugin for Squirrel that can handle it? If not does anyone know of any > other web interface for a user to create a maildrop filter file? You can still create "home" directories for virtual users. Filtering and autoresonder plugins all work great in this way. - paul ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click -- squirrelmail-users mailing list List Address: [EMAIL PROTECTED] List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id)95 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
