Changes since 2.2.11:
* Backport IPv6 support
* Remove generated autoconf files from the release. Please install
automake-1.9 and run autoreconf -i before running configure
* Backport the fix for duplicate mailboxes in LIST/LSUB responses
* Backport for internaldate as UTC
* Fix for file descriptor leakage
Bugs fixed since 2.2.10:
0000742: [Authentication layer] PATCH: authldap.c - multiple attributes
for field_mail (Toast) - resolved.
0000731: [Documentation] Missing documentation of database layer logging
control (paul) - resolved.
0000723: [Database layer] simultaneous mailbox creation (paul) -
resolved.
0000709: [Database layer] Some sql optimizations (paul) - resolved.
0000721: [Authentication layer] mail quota in ldap not used during
delivery (paul) - resolved.
0000698: [IMAP daemon] PostgreSQL 8.3.1 can't execute query (paul) -
resolved.
0000712: [General] traces to stderr may cause core dumps if hostname
>=16 (paul) - resolved.
0000710: [IMAP daemon] eliminate annoying "[Illegal seek] on
read-stream" message from imap4d - resolved.
0000704: [IMAP daemon] IMAP TEXT searches stop at headers - resolved.
0000670: [IMAP daemon] IMAP TEXT searches only seem to search headers
(paul) - resolved.
While here, pkglint clean and add DESTDIR support.
This is strictly a maintenance release. No new functionality was added.
Changes since 2.2.8-rc1
none
Bugs fixed since 2.2.7
0000655: [Database layer] MIME headers are incorrectly parsed into cached tables (paul)
0000656: [Command-Line programs (dbmail-users, dbmail-util)] dbmail-export: bogus date in "From_" lines (paul)
* Honor PKG_SYSCONFDIR and VARBASE.
* Added sqlite and ldap option.
* Fixes PLIST when db driver != mysql.
* Install more documentation.
* Install initial create tables sql script files.
* Rename timsieved's rc script to similar name with other scripts.
Bump PKGREVISION.
branch. There are a number of changes, see the ChangeLog for details.
Note that in the meantime, 2.2.x is the new stable release series, bringing
many new features e.g. LDAP authentication, header caching, Sieve mail
filtering, ... but I'll leave that update to a more experience DBMail user.
INSTALLATION_DIRS, as well as all occurrences of ${PREFIX}/man with
${PREFIX}/${PKGMANDIR}.
Fixes PR 35265, although I did not use the patch provided therein.
2.0.2:
* Bug 115: MAX_LINESIZE consistency.
* Bug 119: Memory leak in dbmail-lmtpd.
* Bug 131: Determine DBMail version (for now, only via command line -V).
* Bug 132: dbmail-util had a few incorrect stdout/stderr messages.
* Bug 135: Delivery chain fails to set is_header on header rows.
* Bug 143: Sort.c compiles without CFLAGS.
* Bug 142: Merge preforking with the 2.0 codebase.
* Bug 118: dbmail-users -c username -W does not prompt for password
on FreeBSD. WORKAROUND: Use -W "" (double quotes) to fool getopt
and prompt for a password.
* Bug 91: Infinite loops in both imapd and pop3d.
2.0.4:
* Bug 163: dbmail-users -l nonexistantuser should return non-zero value
* Bug 153: dbmail-util cannot remove unconnected mailboxes.
* Bug 118: dbmail-users -c username -W does not prompt for password on FreeBSD.
* Bug 131: determine dbmail version only shows major.minor, not micro.
* Bug 159: alias bug: if user exists, auth_check_user is skipped.
* Bug 149: Improved imap search performance using weighted search lists.
* Bug 171: max() is indexable in mysql but not in postgresql causing
extreme slowness
* Bug 134: Some MySQL tweaks to be applied.
* Bug 180: dbmail-user -e someuser does not clear the mailboxes
* improved performance on postgresql when opening mailboxes (imapd)
by avoiding SUM() calls.
* Bug 177: compile fails on FreeBSDs getopt.h
* Bug 164: No more mailbox full. Mail bounced with user unknown.
* Bug 181: Error in SQL using SuSE Linux 9, max value for int8 is
exceeded, PostgreSQL 8 + Postfix
2.0.5:
* bug 177: compile fails on FreeBSDs getopt.h
* bug 182: compile fails on FreeBSDs sort.c
* bug 158: a sig term to the root process e.g. the pid from the
pidfile doesn't shutdown imapd/pop3d
* bug 154: dbmail-util outputing "-r" error when -r is no longer valid
* bug 201: Unix socket support for lmtpd
* bug 199: spare child creates zombie
* bug 190: huge load if database crash
* bug 145: LMTP loses return-path
* bug 162: dbmail-pop3d zombies galore..
* bug 213: pop3d sends SIGKILL to init's process group
* bug 185: segfault if user is over-quota in lmtp delivery
* bug 189: if alias == deliver_to, dbmail-smtp hogs mem until killed
by oom or queue gives up
2.0.6:
* corrected reported version (closes#247)
* fixes fatal error in process pool
2.0.7:
* Removed all unsafe code from the signal handlers. This should
mostly benefit FreeBSD users which may have suffered from
unreliable behaviour in the process pool code.
* Added 'ON UPDATE CASCADE' to all foreign key restraints in the
MySQL (InnoDB) and Postgresql create_table files.
* POP3 AUTH command no longer returns list of supported authentication
mechanisms when issued without arguments.
And always is defined as share/examples/rc.d
which was the default before.
This rc.d scripts are not automatically added to PLISTs now also.
So add to each corresponding PLIST as required.
This was discussed on tech-pkg in late January and late April.
Todo: remove the RCD_SCRIPTS_EXAMPLEDIR uses in MESSAGES and elsewhere
and remove the RCD_SCRIPTS_EXAMPLEDIR itself.
Dbmail is the name of a group of programs that enable the possiblilty
of storing and retrieving mail messages from a database. Currently
MySQL and PostgreSQL can be used as database backends.
DBMail is made up of several components. A normal MTA (Postfix,
SendMail, QMail, Exim) is used for accepting messages. The MTA
hands the messages over to dbmail-smtp, using a pipe interface, or
dbmail-lmtpd, using LMTP (Local Mail Transport Protocol). These
programs take care of delivering the message into the database.
Messages can be retreived from the database using dbmail-pop3d,
using the POP3 protocol, and dbmail-imapd, using the IMAP4Rev1
protocol.
The whole email is stored in the database. That includes attachments.
The DBMail programs do not have to touch the filesystem to retreive
or insert emails. User information is also stored in the database,
so users do not need an account on the machines DBMail is running
on.
