>>>> 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. ;) > > That's the one... remove it and the errors go away. Seems to also reduce > the bouncing around the focus was taking when entering a reply window.
look for a new version quite soon >>> 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. > > The autoresponder we have controled through a custom perl we put together. > It takes care of password changes, forwarding, spam assassin settings > etc... > > But I am not entirely disagreeable with moving some of those functions > into squirrel. It just needs to be done in a way that maintains our > security. I don't want to have apache run as the vpopmail user in order to > write files into the user's virtual mailbox directory under > /var/vpopmail/domains/... Having the tiny perl we use running as setuid is > sufficiently dangerous. You could easily design a plugin around such a system, as long as it takes command-line type input. (see plugins that use similar suid scripts, the change_passwd plugin being one such) > What filtering system can you suggest that would work well with a fully > virtualized qmail/vpopmail where all user info is in a MySQL database. It > would need to be compatable with using the .qmail file to do forwarding > and autoresponder stuff as well as allow spamassassin to function. > Currently we use maildrop to do our filtering but the only filtering the > users are allowed to configure is to send to spam assassin and optionally > to deliver spam email to a spam folder. I could see making an include file > for the user's rules to come in after the spam assassin filter and > optional deliver. the server side filters plugin (see plugins filter/spam category) is made to work with maildrop (as well as others). there is a maildrop autoresponder plugin also available. your system is ripe for use with many SM plugins. - 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
