upgrade mail/exim to 4.77, due changes into match_* function this upgrade maybe unsafe on some installations, maybe this fact should be noted on UPDATING document and/or into pkg-install file. ftp://ftp.exim.org/pub/exim/ChangeLogs/ChangeLog-4.77 Added option LISTMATCH_RHS for old compatibility and turned off by default due security reason. Removed src/exiqgrep.src patch, since it was builtin into 4.77 How-To-Repeat: -
Responsible Changed From-To: freebsd-ports-bugs->rea Over to maintainer (via the GNATS Auto Assign Tool)
I am already testing slightly different version of port for 4.77. I'll incorporate LISTMATCH_RHS into it. Stay tuned. -- Eygene Ryabinkin ,,,^..^,,, [ Life's unfair - but root password helps! | codelabs.ru ] [ 82FE 06BC D497 C0DE 49EC 4FF0 16AF 9EAE 8152 ECFB | freebsd.org ]
The patch is at http://codelabs.ru/fbsd/ports/exim/update-4.76-to-4.77.diff Here is the QA page: http://codelabs.ru/fbsd/ports/qa/mail/exim/4.77 It will be updated if any new information regarding the port quality will be received. I am doing call for testing at freebsd-ports@ list and I think I will commit the new port version at Monday, 17.10.2011, if everything will go fine. -- Eygene Ryabinkin ,,,^..^,,, [ Life's unfair - but root password helps! | codelabs.ru ] [ 82FE 06BC D497 C0DE 49EC 4FF0 16AF 9EAE 8152 ECFB | freebsd.org ]
Eygene, thanks for your quick updates to the exim port! Your patch works great = here (FreeBSD hotzenplotz.wittig.name 9.0-BETA3 FreeBSD 9.0-BETA3 #0: = Wed Oct 5 03:22:57 CEST 2011 = root@hotzenplotz.wittig.name:/usr/obj/usr/src/sys/ALEX amd64), with no = problems in production for the last 24 hours. I had to make small config changes to compensate for the new match_* = behavior, but fortunately you put in a warning about that :-) Just out of curiosity: is there any particular reason beyond historic = reasons why the exim Makefile does its own "pw groupadd ..." stuff = instead of using USERS and GROUPS = (http://www.freebsd.org/doc/en/books/porters-handbook/users-and-groups.htm= l)? Cheers, Alex
Fri, Oct 14, 2011 at 11:50:32AM +0400, Eygene Ryabinkin wrote: > The patch is at > http://codelabs.ru/fbsd/ports/exim/update-4.76-to-4.77.diff > > Here is the QA page: > http://codelabs.ru/fbsd/ports/qa/mail/exim/4.77 > It will be updated if any new information regarding the port quality > will be received. I had updated both the patch and QA page: - the patch for XCLIENT was updated to match the latest sources; - I had added UPDATING entry. Now Exim builds even with the XCLIENT knob turned on. -- Eygene Ryabinkin ,,,^..^,,, [ Life's unfair - but root password helps! | codelabs.ru ] [ 82FE 06BC D497 C0DE 49EC 4FF0 16AF 9EAE 8152 ECFB | freebsd.org ]
Alexander, good day. Sat, Oct 15, 2011 at 12:00:31AM +0000, Alexander Wittig wrote: > thanks for your quick updates to the exim port! Your patch works great = > here (FreeBSD hotzenplotz.wittig.name 9.0-BETA3 FreeBSD 9.0-BETA3 #0: = > Wed Oct 5 03:22:57 CEST 2011 = > root@hotzenplotz.wittig.name:/usr/obj/usr/src/sys/ALEX amd64), with no = > problems in production for the last 24 hours. Thanks for testing! > I had to make small config changes to compensate for the new match_* = > behavior, but fortunately you put in a warning about that :-) Well, in the second modification of the patch I had even added the UPDATING entry: this should help more people to catch this modification. > Just out of curiosity: is there any particular reason beyond historic = > reasons why the exim Makefile does its own "pw groupadd ..." stuff = > instead of using USERS and GROUPS = > (http://www.freebsd.org/doc/en/books/porters-handbook/users-and-groups.htm= > l)? Well, currently I don't quite understand how can one override the default user/group with its own one: there are some historical setups that are overriding EXIM_USER and EXIM_GROUP. I should test this stuff and, probably, extend the current logics for USERS and GROUPS to handle local overrides. But my current intention is to leave this stuff for the next commit that will come after update to 4.77. -- Eygene Ryabinkin ,,,^..^,,, [ Life's unfair - but root password helps! | codelabs.ru ] [ 82FE 06BC D497 C0DE 49EC 4FF0 16AF 9EAE 8152 ECFB | freebsd.org ]
rea 2011-10-18 08:55:44 UTC FreeBSD ports repository Modified files: mail/exim Makefile distinfo options pkg-message pkg-plist mail/exim/files extra-patch-xclient Removed files: mail/exim Makefile.options mail/exim/files patch-exiqgrep.src Log: mail/exim: upgrade to 4.77 New stuff (from ftp://exim.inode.at/exim/ChangeLogs/NewStuff-4.77): 1. New options for the ratelimit ACL condition: /count= and /unique=. The /noupdate option has been replaced by a /readonly option. 2. The SMTP transport's protocol option may now be set to "smtps", to use SSL-on-connect outbound. 3. New variable $av_failed, set true if the AV scanner deferred; ie, when there is a problem talking to the AV scanner, or the AV scanner running. 4. New expansion conditions, "inlist" and "inlisti", which take simple lists and check if the search item is a member of the list. This does not support named lists, but does subject the list part to string expansion. 5. Unless the new EXPAND_LISTMATCH_RHS build option is set when Exim was built, Exim no longer performs string expansion on the second string of the match_* expansion conditions: "match_address", "match_domain", "match_ip" & "match_local_part". Named lists can still be used. Relevant entries from ChangeLog at ftp://exim.inode.at/exim/ChangeLogs/ChangeLog-4.77: TK/01 DKIM Verification: Fix relaxed canon for empty headers w/o whitespace trailer TF/02 Fix a couple more cases where we did not log the error message when unlink() failed. See also change 4.74-TF/03. TF/03 Make the exiwhat support code safe for signals. Previously Exim might lock up or crash if it happened to be inside a call to libc when it got a SIGUSR1 from exiwhat. The SIGUSR1 handler appends the current process status to the process log which is later printed by exiwhat. It used to use the general purpose logging code to do this, but several functions it calls are not safe for signals. The new output code in the SIGUSR1 handler is specific to the process log, and simple enough that it's easy to inspect for signal safety. Removing some special cases also simplifies the general logging code. Removing the spurious timestamps from the process log simplifies exiwhat. PP/02 Raise smtp_cmd_buffer_size to 16kB. Bugzilla 879. Patch from Paul Fisher. PP/07 Make maildir_use_size_file an _expandable_ boolean. Bugzilla 1089. Patch from Heiko Schlittermann. PP/08 Handle ${run} returning more data than OS pipe buffer size. Bugzilla 1131. Patch from Holger Weitz. PP/09 Handle IPv6 addresses with SPF. Bugzilla 860. Patch from Wolfgang Breyha. PP/10 GnuTLS: support TLS 1.2 & 1.1. Bugzilla 1156. Use gnutls_certificate_verify_peers2() [patch from Andreas Metzler]. Bugzilla 1095. PP/12 fix uninitialised greeting string from PP/03 (smtps client support). PP/13 shell and compiler warnings fixes for RC1-RC4 changes. PP/14 fix log_write() format string regression from TF/03. Bugzilla 1152. Patch from Dmitry Isaikin. Other changes: - the patch for XCLIENT was updated to match the latest Exim sources; - removed already incorporated patch for exiqgrep; - removed Makefile.options and simplified OPTIONS handling. PR: ports/161095, ports/161482, ports/157180 Revision Changes Path 1.260 +21 -6 ports/mail/exim/Makefile 1.6 +0 -153 ports/mail/exim/Makefile.options (dead) 1.105 +2 -2 ports/mail/exim/distinfo 1.2 +8 -9 ports/mail/exim/files/extra-patch-xclient 1.2 +0 -15 ports/mail/exim/files/patch-exiqgrep.src (dead) 1.18 +46 -45 ports/mail/exim/options 1.9 +13 -0 ports/mail/exim/pkg-message 1.50 +1 -3 ports/mail/exim/pkg-plist _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org"
State Changed From-To: open->closed Update committed. Thanks to everyone for testing and extending the update!