Up to [cvs.NetBSD.org] / pkgsrc / mail / dbmail
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
dbmail: update to 3.5.5 pkgsrc changes: package now creates an unprivileged user conf file subsitutions for sane pgksrc defaults 3.5.5 DBMail 3.5.5 offers new features and a few bug fixes, including a new authentication method, improved support for Postfix, logging improvements and listing forwarders. DBMail 3.5.4 Te main changes are better support for docker and systemd, MySQL compression and an anomaly in how libzdb handles NULLs. Version 3.5.3 Various memory leaks fixed Fix invalid free and invalid read sieve port changed to 4190 as per rfc5804 3.5.2 This release focuses on ease of use: Long options added Man pages updated Help refactored 3.5.1 This release has focused on reliability plus making DBMail easier to install and manage with significant improvements in documentation and logging. 3.5.0 automatic table creation on first install Improved logging config Required header names added if required curl library added for SMTP forwarding dbmail-sieved for starttls (deprecated dbmail-timsieved removed) Checks refactored for gmime3 dbmail-announce mailing list added for release and other announcements dbmail-general mailing list added for general discussion Numerous bug fixes
dbmail: update to 3.3.1
3.3.1:
MySQL 8 is supported and fixes an issue with 8.0.31 and libzdb
3.3.0:
This release bumps gmime to version 3.0 (3.2), all other requirements
are the same.
3.2.6:
The maintenance(dbmail-util) process should be issued in a maintenance
window do to massive changes on database
compatibility compiler standard was raised to C17
Added
IMAP Daemon: added switch to control the sequence update strategy
IMAP Daemon: added switch to control the sync between DELETE flag and
the actual state of the message (deleted)
Build: automatic installation script (v 0.5)
Maintenance(dbmail-util): added option to upgrade to
utf8mb4(MariaDB/MySQL)
Optimizations
IMAP: optimizing differential state
+ bugfixes
dbmail: update to 3.2.5
3.2.5
Added
IMAP Daemon: added switch to control the diffential state reload
(mailbox_update_strategy=2), more information in dbmail.conf,
mailbox_update_strategy_2_max_iterations [#81]
IMAP Daemon: added switch to control UNSEEN first message in SELECT commands
Changed
IMAP Daemon: allow reporting UID COPY success in case of various failures
(except quota), reporting issues are sent to error log as warnings [#87]
Optimizations
optimizing differential state [#81]
optimizing fetch message headers [#85]
Issues
fixing issue related to copy message in regard to RFC 3501, section 6.4.8
fixing issues related group_concat for PostgreSql [#75], [#78]
fixing issue related to lastRowId [#71]
fixing issues related with differential update [#70], [#73]
fixing proc not being used in BSD systems [#74]
IMAP Daemon: segmentation fault [#68]
3.2.4
Added
IMAP Daemon: mailbox-update-strategy switch (see dbmail.conf), experimental
support for application_name in database connection uri
IMAP Daemon: mailbox_search_strategy switch (see dbmail.conf)
Changed
systemd unit changed to type notify
mailbox state is build using only valid messages [#39]
Optimizations
IMAP Daemon: optimization of sql queries in relation to message headers
libevent increased priority on accepting new connections
libevent optimization on reading and writing to sockets
simplify libzdb configuration (AC_CHECK_HEADERS)
Issues
fix segmentation fault in imap_append_hash_as_string [#12]
dbmail-users: sql issue on deleting alias user [#18]
IMAP Daemon: generation of invalid BODYSTRUCTURE in Content-Type field [#23]
fix support for jemalloc latest version [#35]
IMAP Deamon: BYE Command now offers optional message even on normal operations
IMAP Deamon: idle message now offers optional message (* OK Still Here)
IMAP Daemon: random hangs when single user is connected [#37]
fix fd leaks
IMAP Daemon: fix MODIFIED keyword, too many '[' and ']'
fix segmentation fault in find_end_of_header
fix gcc 10 compilation issue, duplicated definition
Remove options for database backend selection. Database access is now fully abstracted through databases/libzdb and dbmail itself is agnostic about which backend support is present. Bump PKGREVSION.
Update to 3.2.3. Next major version, no good changelog found.
Remove example rc.d scripts from PLISTs. These are now handled dynamically if INIT_SYSTEM is set to "rc.d", or ignored otherwise.
Remove @dirrm entries from PLISTs
Convert to use PLIST_VARS instead of manually passing "@comment " through PLIST_SUBST to the plist module.
Update DBMail to 2.2.8. 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)
Merge with wip/dbmail. * 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.
Update to 2.2.7 release. The 2.2 series of dbmail adds LDAP integration, fast searches and sieve filtering. Users upgrading from an earlier release will need to follow these upgrading instructions: http://www.dbmail.org/dokuwiki/doku.php?id=upgrading_to_2.1
Sort.
RCD_SCRIPTS_EXAMPLEDIR is no longer customizable. 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.
A config file and some rc.d scripts might help. Bump PKGREVISION.
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.
Initial revision