>Number:         19270
>Category:       pkg
>Synopsis:       exim configuration changes between versions
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    pkg-manager
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Wed Dec 04 08:47:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     
>Release:        NetBSD 1.6
>Organization:
http://bsd.reedmedia.net/
>Environment:
	
	
System: NetBSD rainier.reedmedia.net 1.6 NetBSD 1.6 (JCR-20020927) #3: Sat Sep 28 13:40:20 PDT 2002 reed@rainier.reedmedia.net:/usr/src/sys/arch/i386/compile/JCR-20020927 i386
Architecture: i386
Machine: i386
>Description:
I noticed that exim pkgsrc is for Exim version 4. This changed back in
June. This is good to have the official Exim.

The problem is that the configurations are not compatible.
>How-To-Repeat:
Use exim with your custom config. Upgrade to new package.
>Fix:
Create new pkgsrc/mail/exim3 pkgsrc from mail/exim (before June 19)
and update to use exim-3.36 (and probably change MASTER_SITES
to add /exim3 to end of URLs).

(It is too late to have a exim4 package, unless it is just a metapackage.)

The DESCR for both should mention the other package and has different
configuration.
For exim3:

-=-=-=-
Exim3 is phased out. The author suggests updating to Exim 4,
although security updates may be fixed in the Exim version 3 code.

It is important to note that many configurations change between
Exim 3 and Exim 4. Exim 3 configurations may be incompatible.

The new Exim version 4 is in the mail/exim package.
-=-=-=-

For exim:

-=-=-=-
The Exim 3 version is available in the mail/exim3 package.
It has a different configuration syntax.
-=-=-=-

In addition, the ./build-version/convert4r4 needs to be installed too.
Then the MESSAGE and DESCR could have:

A tool for converting from Exim 3 to Exim format is available.

Use the ${PREFIX}/bin/exim-convert4r4 to convert configurations
to newer version.

>Release-Note:
>Audit-Trail:
>Unformatted: