Commit graph

4 commits

Author SHA1 Message Date
schmonz
4fadbad294 Update to 2.0.7. Bugs fixed, from the changelog:
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.
2006-01-13 21:43:54 +00:00
ghen
9598e44942 Use mk/mysql.buildlink3.mk instead of databases/mysqlX-client/bl3.mk,
same for pgsql.bl3.mk.  Bump PKGREVISION.  Ok by wiz.
2006-01-10 12:39:03 +00:00
dillo
f81ae835ad Packages have no business modifying PKG_DEFAULT_OPTIONS -- it's a
user settable variable.  Set PKG_SUGGESTED_OPTIONS instead.  Also,
make use of PKG_OPTIONS_LEGACY_VARS.

Reviewed by wiz.
2005-05-31 10:01:36 +00:00
schmonz
e0976769fc Initial import of dbmail-2.0.1.
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.
2005-01-09 03:21:07 +00:00