Dbmail is the name of a group of programs that enable the possibility of
storing and retrieving mail messages from a database (currently MySQL,
PostgreSQL or SQLite).
* Scalability.
Dbmail is as scalable as the database system that is used for the mail
storage. In theory millions of accounts can be managed using dbmail. One
could, for example, run 4 different servers with the pop3 daemon each
connecting to the same database (cluster) server.
* Manageability.
Dbmail is based upon a database. Dbmail can be managed by changing settings
in the database (f.e. using PHP/Perl/SQL), without needing shell access.
* Speed.
Dbmail uses very efficient, database specific queries for retrieving mail
information. This is much faster then parsing a filesystem.
* Security.
Dbmail has got nothing to do with the filesystem or interaction with other
programs in the Unix environment which need special permissions. Dbmail is
as secure as the database it's based upon.
* Flexibility.
Changes on a Dbmail system (adding of users, changing passwords etc.) are
effective immediately.
WWW: http://www.dbmail.org/
===> The following configuration options are available for dbmail-2.3.6_3:
MYSQL=on (default) "Build with MySQL support"
POSTGRESQL=off (default) "Build with PostgreSQL support"
SQLITE=off (default) "Build with SQLite support"
SIEVE=off (default) "Build w. support for Sieve mail sorting language"
LDAP=off (default) "Build with support for LDAP authentication"
MANPAGES=on (default) "Install man pages"
===> Use 'make config' to modify these settings
2012-04-18 mail/dbmail20: No more supported upstream. No ports depend on this
2012-04-18 mail/dbmail21: No more supported upstream. No ports depend on this
2012-04-18 mail/dbmail23: No more supported upstream. No ports depend on this
- Mark as deprecated. Set expiration date to 2012-04-18.
This versions of dbmail no more supported upstream. This ports are
unmaintained and not required by other ports.
Additionally, reset maintainer for mail/dbmail20 because of mail bounce.
Feature safe: yes
In the rc.d scripts, change assignments to rcvar to use the
literal name_enable wherever possible, and ${name}_enable
when it's not, to prepare for the demise of set_rcvar().
In cases where I had to hand-edit unusual instances also
modify formatting slightly to be more uniform (and in
some cases, correct). This includes adding some $FreeBSD$
tags, and most importantly moving rcvar= to right after
name= so it's clear that one is derived from the other.
- Add LDFLAGS to CONFIGURE_ENV and MAKE_ENV (as it was done with LDFLAGS)
- Fix all ports that add {CPP,LD}FLAGS to *_ENV to modify flags instead
PR: 157936
Submitted by: myself
Exp-runs by: pav
Approved by: pav
-Repocopy devel/libtool15 -> libtool22 and libltdl15 -> libltdl22.
-Update libtool and libltdl to 2.2.6a.
-Remove devel/libtool15 and devel/libltdl15.
-Fix ports build with libtool22/libltdl22.
-Bump ports that depend on libltdl22 due to shared library version change.
-Explain what to do update in the UPDATING.
It has been tested with GNOME2, XFCE4, KDE3, KDE4 and other many wm/desktop
and applications in the runtime.
With help: marcus and kwm
Pointyhat-exp: a few times by pav
Tested by: pgollucci, "Romain Tartière" <romain@blogreen.org>, and
a few MarcusCom CVS users. Also, I might have missed a few.
Repocopy by: marcus
Approved by: portmgr
Fix a few "bad example" problems in the rc.d scripts that have been
propogated by copy and paste.
1. Primarily the "empty variable" default assignment, which is mostly
${name}_flags="", but fix a few others as well.
2. Where they are not already documented, add the existence of the _flags
(or other deleted empties) option to the comments, and in some cases add
comments from scratch.
3. Replace things that look like:
prefix=%%PREFIX%%
command=${prefix}/sbin/foo
to just use %%PREFIX%%. In many cases the $prefix variable is only used
once, and in some cases it is not used at all.
4. In a few cases remove ${name}_flags from command_args
5. Remove a long-stale comment about putting the port's rc.d script in
/etc/rc.d (which is no longer necessary).
No PORTREVISION bumps because all of these changes are noops.
Dbmail is the name of a group of programs that enable the possibility of storing
and retrieving mail messages from a database (currently MySQL, PostgreSQL or
SQLite).
WWW: http://www.dbmail.org/
PR: ports/121908
Submitted by: Mark Starovoytov <mark_sf@kikg.ifmo.ru>
Approved by: gabor (mentor)
