Is there any way to delay the uploading of attachment files until the user hits "send?" We have an environment with multiple SquirrelMail servers (RHEL 5, SquirrelMail 1.4.17) and we are trying to limit the number of external services, like NFS, that we depend on for SquirrelMail to be fully functional. We use LDAP for to store preferences and address books and a PostgreSQL database for session data. But we still have to use a shared filesystem for attachments, since the attachment request could have been handled by one server and the send request by another. I've heard that old versions of SquirrelMail didn't upload the attachments until the message was sent, which sounds interesting. Was that the case, and is there any way to use that method with the current version? Plugins or code changes are acceptable. The sessions are encrypted, which complicates using a front-end load balancer to "stick" a session to a specific server for its duration. Are there other, better methods for supporting multiple SquirrelMail servers without a shared filesystem? Best regards, John Simpson ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ----- squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@xxxxxxxxxxxxxxxxxxxxx List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
