DBMA V2.4.x - GUI Administrator for DbMail Plus MTA Mail System http://www.dbma.ca/ Moving DbMailAdministrator to its own domain : dbma.ca http://www.dbma.ca/index.htm * further changes made to PostgreSQL functionality to allow DBMail users to exploit the significant new functionality and performance enhancements of PostgreSQL 8.3.1 and beyond. http://www.dbma.ca/index.htm * a few minor bug fixes including syntax management for 'SQL-illegal' characters in Auto reply Messages * reminders for configuring dbmail.conf to use AutoNotify and AutoReply * speed increase http://www.dbma.ca/ * This release contains substantial code modifications throughout. * DBMA is now more "Group-aware" as in groups of mail users delineated by dbmail_users.client_idnr. * In the "My Groups" section of the Main window, the number of users in each group is set out when this Configuration option has been turned on. Note that this is resource expensive and on large systems with many groups of users it can slow DBMA Main window considerably. (Working on that.) * A configuration setting is now provided to limit the number of users per mail group. In the RestrictGroup regime this would mean that the maximum number of users would be fixed and only a "root" administrator could reset the maximum once arrangements were made (i.e.: payment). * In the global configuration (full configuration authority) the maximum number of users per group is a healthy reminder that keeping unique client_idnr numbers to a manageable level is good practise. The default is set at 1000 per group. There is no limit to the number of groups. * Setting the Default Mailbox size now sets the maximum mailbox size for the RestrictGroup Admin mode This can only be overridden in the configuration window by a root administrator. * A bug which applied to later versions of Mysql has been fixed where in the case of a plain password being used, a space was injected into the encryption type field http://www.dbma.ca/ * Changes have been made to the allow_read_mail regime such that turning off the ability to read mail does not prevent the display of mailboxes in the user account window and searches can be done to locate messages even based on message block content but selecting the message will return headers only and maintain the privacy of the message. This applies to DBMail Version 2.2 (Pending) and its precursor SVN Trunk and recent DBMail 2.1.x unstable. * Minor changes and updates to documentation http://dbma.ca/ * Further changes for the pending DBMail V2.2 release including incorporation of new table structure for dbmail_users: a step toward DBMA managing sieve scripts. * cursieve and maxsieve displayed in User Account Window * DBMA MTA Admin upgrades. MTA Domain Transport GUI has been completely overhauled and now more feature-rich for the management of MTA virtual domains and transports. * If you use DBMail SVN/Trunk or if you use MTA Domain with Transport features, V2.4.7 is a must have. Upgrade is simplified by typing perl update.pl in dbmailadministrator/ http://dbma.ca/ * a mem problem with DBD-mysql-3.0002_4 required a workaround. Now that DBD-mysql-3.0002 is fixed, the workaround is dropped and LONGBLOBs are reinstated for DBMAIL 2.0.8/9/10 dbmail_messageblks.messageblk to allow read and search mail * numerous minor changes prevent illegal search terms to cause a fatals_to_browser error message when the not-so-learned administrator searches for illegal control characters and such things (RFC2822 and RFC2821) * the Allow_Read_Mail function is now available for newer databases (even with older DBMail binary versions) where LONGTEXT has been replaced with LONGBLOB binaries for dbmail_messageblks.messageblk * a collection of little changes/improvements makes 2.4.6 a "must have" if you are using recent versions of DBMail http://www.dbma.ca/index.htm upgrade.pl has been working on dozens of different xNIX systems and users like it! The simple perl code preserves all exisitng configurations and fully downloads and installs the new version of DBMA. http://www.dbma.ca/ There are some features in this version that make it a "must have". It's truly worth taking the time to upgrade your installation. * Numerous changes/improvements for all versions * Dropped config options for DBMail 2.1 SVN Trunk User Search feature now also searches aliases and serves an Account Window for the user having that email address (alias) if so found. This particularly favours systems where user account names are first_part (first_part@last_part) but applies to either or a combined environment of "first_part" and or "first_part@last_part" user naming. (DBMA Interimly treats SVN 2.1 as if it were 2.2.rel) * Dropped "use strict" for production releases * Added configs for pending release of DBMail 2.2 (You can test on 2.1.x) * Added read mail option for DBMail 2.2 * Updated Auto Replies for DBMail 2.2 * Added start/stop dates for auto replies * Created groundwork for new DBMail Sieve config + (Not implemented .. too early.) * DBMA MTA Admin :: Domains and Transports is now able to take over and automate virtual hosting. After add an alias on a new domain, the MTA config is automatically updated and the new MTA domain is added as a destination. This relies on the extensibility of DBMail and Postfix compiled with xxsql. * A few enhanced installation aids workaround some typical (from feedback) Apache config mistakes and get DBMA diagnostics running enough to serve a diag window for those just starting out and who need to understand permissions a little better. http://www.dbma.ca/dbmailadmin-readme.htm A number of users created 'fetching scripts' to get and install new DBMA code releases. To avoid breaking things people have come to rely on the *CURRENT* naming convention for the DBMA package remains unchanged but now has additions. CURRENT is still available in DBMA_SQL_V2.tar (tarball) and DBMA_SQL_V2.tar.gz (Compressed) A new package naming convention in lower case is also added to the DBMA site: ** dbma-2.3.3.tar.gz ** A compressed tarball is named with the acronym in lower case followed by a hyphen and one major plus two sub version numbers seperated by periods for a total of three version integers. It will always be three numbers (i.e.: "dbma-2.0.0.tar.gz"). http://dbma.ca/archive/ For a future version of DbMailAdministrator (DBMA) to administer DBMail2.2.x -- DBMail system users are asked to think a little about how you might use the marriage of LDAP and MySQL/PostgreSQL/SQLite user/alias mapping, if at all, in your future mail systems. The goal here is to determine how extensive and redundant should be the LDAP and SQL user data (name/alias/password) interface (GUI) -- or not. * Feature requests for future versions of DbMailAdministrator are most welcome and appreciated. * Comments can be transmitted by visiting http://dbma.ca/DBMA_contact.htm http://dbma.ca/DBMA_contact.htm Every circumstance has its own unique advantages and deficiencies including public physical plant access, ex-or-disgruntled employees, pranksters and dare it be said, DMZ breakdowns or penetration. Securing any system is a living, dynamic process -- checking for and applying operating system updates, program fixes and patches, scanning programme revisions for desirable feature additions, reviewing user security and permissions, and generally applying common sense. http://www.dbma.ca/security-notes.htm An extensive set of help notes pertaining to both DBMA and DBMail. Platform notes. DBMA was built on Unix servers and tested and tuned on several Windows variants. You can fully administer your DbMail IMAP / POP3 system using DBMA on a Win32 host (NT4Server, W2kServer, WinServer-2003). On either Unix or Windows, DBMA will start up instantly and fly up a configuration window or just login to the database if the default configurations match yours. http://www.dbma.ca/demo/dbmailadministrator/DBMA_help.htm