kpriv/freebsd-ports
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
freebsd-ports/mail/vpopmail/files/patch-README.vdelivermail

13 lines
692 B
Text
Raw Normal View History

Update vpopmail to 5.4.20 after a long delay, mostly due to wondering how to handle the database upgrade and the SpamAssassin patch partial integration. There are several important changes that may affect your vpopmail installation and may need you to handle manually: - THE MYSQL CONNECTION INFORMATION IS NO LONGER DEFINED AT COMPILE-TIME! The WITH_MYSQL_{USER,PASSWD,SERVER,DB} variables should NOT be defined when you build the port; place that information in the vpopmail.mysql file after vpopmail has been installed! - the default domain is also no longer defined at compile time - you need to place it in the defaultdomain file after the installation. - the defaultdomain and vpopmail.mysql files are no longer blindly removed on deinstallation, they are only removed if they have not been modified - in vpopmail 5.4.18, the database schema was changed - some fields were extended from 64 to 96 characters. If you do not apply those changes to your database, as explained in the vpopmail/doc/UPGRADE file, your vpopmail installation may silently fail or lose the trailing portions of domain names and usernames. - in vpopmail 5.4.19, the upstream authors integrated large parts of Alex Dupre's SpamAssassin support, without the SPAM_THRESHOLD part. If you use vpopmail along with the SpamAssassin FreeBSD port support, take extra care to ensure that your installation still processes e-mail messages in the same way. - vpopmail 5.4.19 added support for maildrop as a mail delivery agent. This is available in the FreeBSD port if WITH_MAILDROP is defined. There is also a new user-limit flag for maildrop delivery. - vpopmail 5.4.19 added support for MySQL connections via Unix sockets instead of TCP sockets to the server. To do that, change the second value (the port number) in vpopmail.mysql to the full pathname of the MySQL socket (e.g. /tmp/mysql.sock). - vpopmail 5.4.20 extended the LDAP support; please see README.ldap for more information, and specify the LDAP connection information in the vpopmail/etc/vpopmail.ldap file after the installation.
2007-10-09 15:27:24 +02:00
diff -urN -x .svn ../../vendor/vpopmail/README.vdelivermail ./README.vdelivermail
--- ../../vendor/vpopmail/README.vdelivermail 2007-10-07 23:44:14.000000000 +0300
+++ ./README.vdelivermail 2007-10-08 11:53:30.000000000 +0300
@@ -57,7 +57,7 @@
If you are not sure what you are doing writing .qmail files, and mucking around
the internals of vpopmail, I strongly suggest you leave this file to the programs.
-Qmailadmin is probably the easiset way to manage the .qmail-default file once the
+Qmailadmin is probably the easiest way to manage the .qmail-default file once the
domain has been created.
Due to the requirement that Maildirs accessed by vpopmail must be owned by vpopmail
Reference in a new issue Copy permalink