Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: exim: dev

Testing Exim 4.70 prerelease

 

 

exim dev RSS feed   Index | Next | Previous | View Threaded


tom at duncanthrax

Oct 13, 2009, 8:38 AM

Post #1 of 18 (1852 views)
Permalink
Testing Exim 4.70 prerelease

The release of Exim 4.70 is on the horizon. A lot of stuff has
accumulated in CVS since January 2008. Since we want to give the current
code some wider exposure, please accept this invitation to test a 4.70
pre-release. You can get the current code by pulling a snapshot from
David's GIT shadow:

git clone git://git.exim.org/exim-src.git

Or wget a tarball here:

http://duncanthrax.net/temp/exim-4.70-RC-20091013.tar.gz

Feel free to post testing results to this list - no matter if positive
or negative.

The main new features are:

* Native DKIM support without an external library.
Docs: http://www.exim.org/~tom/doctest/ch54.html

* Experimental DCC support via dccifd (contributed
by Wolfgang Breyha). See further below for docs.


Other changes:

* PCRE removed from Exim distribution. You will need
a separate PCRE library (and matching headers) to
compile Exim.

* Experimental Yahoo! Domainkeys support dropped in
favor of native DKIM support.


Here's the full changelog:

TK/01 Added patch by Johannes Berg that expands the main option
"spamd_servers" if it starts with a dollar sign.

TK/02 Write list of recipients to X-Envelope-Sender header when building
the mbox-format spool file for content scanning (suggested
by Jakob Hirsch)

TK/03 Added patch by Wolfgang Breyha that adds experimental DCC
(http://www.dcc-servers.net/) support via dccifd. Activated by
setting EXPERIMENTAL_DCC=yes in Local/Makefile. Check out
experimental_spec.txt for more documentation.

TK/04 Bugzilla 673: Add f-protd malware scanner support. Patch submitted
by Mark Daniel Reidel <mr [at] df>.

NM/01 Bugzilla 657: Embedded PCRE removed from the exim source tree.
When building exim an external PCRE library is now needed -
PCRE is a system library on the majority of modern systems.
See entry on PCRE_LIBS in EDITME file.

NM/02 Bugzilla 646: Removed unwanted C/R in Dovecot authenticator
conversation. Added nologin parameter to request.
Patch contributed by Kirill Miazine

TF/01 Do not log submission mode rewrites if they do not change the
address.

TF/02 Bugzilla 662: Fix stack corruption before exec() in daemon.c.

NM/03 Bugzilla 602: exicyclog now handles panic log, and creates empty
log files in place. Contributed by Roberto Lima

NM/04 Bugzilla 667: close socket used by dovecot authenticator

TF/03 Bugzilla 615: When checking the local_parts router precondition
after a local_part_suffix or local_part_prefix option, Exim now
does not use the address's named list lookup cache, since this
contains cached lookups for the whole local part.

NM/05 Bugzilla 521: Integrated SPF Best Guess support contributed by
Robert Millan. Documentation is in experimental-spec.txt

TF/04 Bugzilla 668: Fix parallel build (make -j).

NM/05 Bugzilla 437: Prevent Maildix aux files being created with
mode 000

NM/05 Bugzilla 598: Improvement to Dovecot authenticator handling.
Patch provided by Jan Srzednicki

TF/05 Leading white space used to be stripped from $spam_report which
wrecked the formatting. Now it is preserved.

TF/06 Save $spam_score, $spam_bar, and $spam_report in spool files, so
that they are available at delivery time.

TF/07 Fix the way ${extract is skipped in the untaken branch of a
conditional.

TF/08 TLS error reporting now respects the incoming_interface and
incoming_port log selectors.

TF/09 Produce a more useful error message if an SMTP transport's hosts
setting expands to an empty string.

NM/06 Bugzilla 744: EXPN did not work under TLS.
Patch provided by Phil Pennock

NM/07 Bugzilla 769: Extraneous comma in usage fprintf
Patch provided by Richard Godbee

NM/08 Fixed erroneous documentation references to smtp_notquit_acl to be
acl_smtp_notquit, added index entry.

NM/09 Bugzilla 787: Potential buffer overflow in string_format
Patch provided by Eugene Bujak

NM/10 Bugzilla 770: Problem on some platforms modifying the len
parameter to accept()
Patch provided by Maxim Dounin

NM/11 Bugzilla 749: Preserve old behaviour of blanks comparing equal to
zero.
Patch provided by Phil Pennock

NM/12 Bugzilla 497: Correct behaviour of exiwhat when no config exists.

NM/13 Bugzilla 590: Correct handling of Resent-Date headers.
Patch provided by Brad "anomie" Jorsch

NM/14 Bugzilla 614: Added timeout setting to transport filter.
Patch provided by Dean Brooks

TK/05 Add native DKIM support (does not depend on external libraries).



Documentation for experimental dccifd support
---------------------------------------------
*) Building exim

In order to build exim with DCC support add

EXPERIMENTAL_DCC=yes

to your Makefile. (Re-)build/install exim. exim -d should show
EXPERIMENTAL_DCC under "Support for".

*) Configuration

In the main section of exim.conf add at least

dccifd_address = /usr/local/dcc/var/dccifd

or

dccifd_address = <ip> <port>

In the DATA ACL you can use the new condition

dcc = *

After that "dcc_header" contains the X-DCC-Header.

*** WARNING: return codes changed from previous releases!

Return values are:
"fail" for overall "R", "G" from dccifd
"defer" for overall "T" from dccifd
"accept" for overall "A", "S" from dccifd

dcc = */defer_ok works as for spamd.

dcc_result contains the overall result from DCC answer

usually you'll use

defer !dcc = *

to greylist with DCC. If

dcc_direct_add_header = true

is set, then the dcc header will be added "in deep" and if the spool
file was already written it gets removed. This forces exim to write it
again if needed.
This helps to get the DCC Header through to eg. SpamAssassin.

If you want to pass even more headers in the middle of the DATA stage
you can use $acl_m_dcc_add_header to add information from eg. ClamAV.

Be careful. Header syntax is not checked and added "as is".

--
## List details at http://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##


renaud at allard

Oct 13, 2009, 11:56 AM

Post #2 of 18 (1790 views)
Permalink
Re: [exim] Testing Exim 4.70 prerelease [In reply to]

Tom Kistner wrote:
> The release of Exim 4.70 is on the horizon. A lot of stuff has
> accumulated in CVS since January 2008. Since we want to give the current
> code some wider exposure, please accept this invitation to test a 4.70
> pre-release. You can get the current code by pulling a snapshot from
> David's GIT shadow:
>
> git clone git://git.exim.org/exim-src.git
>
> Or wget a tarball here:
>
> http://duncanthrax.net/temp/exim-4.70-RC-20091013.tar.gz
>

How do you need it tested the most?
I can compile the code (and run it at low load) on multiple platforms,
but this will clearly take me some time, so a priority would be nice.
SUN Sparc running either Solaris, linux or OpenBSD
SGI MIPS running Irix, linux or OpenBSD
Alpha running TRU64, linux, OpenBSD and maybe HP-UX too

If there is a test suite, I would be happy to run it on most platforms.
Attachments: smime.p7s (3.22 KB)


Dan_Mitton at YMP

Oct 13, 2009, 1:44 PM

Post #3 of 18 (1789 views)
Permalink
Re: Testing Exim 4.70 prerelease [In reply to]

I played with DK and DKIM a bit under Exim 4.69, but I haven't kept up, so
I'm new to the current RC. Looking through the new doc for DKIM under
4.70, it seems like the DK concept of 'signsall' has been lost. If I get
a DKIM '$dkim_verify_status' result of 'none', how do I know if the
message SHOULD have been signed? Yes, there is the 'dkim_verify_signers'
option, but how does that stay up to date as more and more (hopefully)
people adopt? How can a domain tell me, that any message I receive from
them had better be signed and pass?

Dan
--
## List details at http://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##


tom at duncanthrax

Oct 13, 2009, 1:49 PM

Post #4 of 18 (1792 views)
Permalink
Re: Testing Exim 4.70 prerelease [In reply to]

Dan_Mitton [at] YMP schrieb:

> 'dkim_verify_signers' option, but how does that stay up to date as more
> and more (hopefully) people adopt? How can a domain tell me, that any
> message I receive from them had better be signed and pass?

This is done in ADSP
(http://en.wikipedia.org/wiki/Author_Domain_Signing_Practices).

Since the standard was only recently turned into an RFC, actual
deployment is still very low.

I'll add ADSP to Exim.

/tom

--
## List details at http://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##


Dan_Mitton at YMP

Oct 13, 2009, 2:36 PM

Post #5 of 18 (1789 views)
Permalink
Re: [exim] Testing Exim 4.70 prerelease [In reply to]

Tom,

That would be great !!



Sent by: exim-users-bounces [at] exim
To: Dan_Mitton [at] YMP
cc: Exim Users <exim-users [at] exim>, exim-dev [at] exim
Subject: Re: [exim] [exim-dev] Testing Exim 4.70 prerelease
LSN: Not Relevant - Not Privileged
User Filed as: Excl/AdminMgmt-14-4/QA:N/A

Dan_Mitton [at] YMP schrieb:

> 'dkim_verify_signers' option, but how does that stay up to date as more
> and more (hopefully) people adopt? How can a domain tell me, that any
> message I receive from them had better be signed and pass?

This is done in ADSP
(http://en.wikipedia.org/wiki/Author_Domain_Signing_Practices).

Since the standard was only recently turned into an RFC, actual
deployment is still very low.

I'll add ADSP to Exim.

/tom

--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/


--
## List details at http://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##


D.H.Davis at bath

Oct 14, 2009, 2:35 AM

Post #6 of 18 (1781 views)
Permalink
Re: [exim] Testing Exim 4.70 prerelease [In reply to]

On Tue, 13 Oct 2009, Tom Kistner wrote:

> From: Tom Kistner <tom [at] duncanthrax>
> To: Exim Users <exim-users [at] exim>
> Cc: exim-dev [at] exim
> Date: Tue, 13 Oct 2009 16:38:49
> Subject: [exim] Testing Exim 4.70 prerelease
>
> The release of Exim 4.70 is on the horizon...

...
> Other changes:
>
> * PCRE removed from Exim distribution. You will need
> a separate PCRE library (and matching headers) to
> compile Exim.

The file NOTICE needs a trivial change to remove the reference to
the cut-down version of PCRE that was previously included with exim:


--- NOTICE.orig Wed Jan 4 11:55:50 2006
+++ NOTICE Wed Oct 14 10:05:13 2009
@@ -39,14 +39,6 @@

A number of pieces of external code are included in the Exim distribution.

- . Regular expressions are supported in the main Exim program and in the
- Exim monitor using the freely-distributable PCRE library, copyright (c)
- 2003 University of Cambridge. The source is distributed in the directory
- src/pcre. However, this is a cut-down version of PCRE. If you want to use
- the PCRE library in other programs, you should obtain and install the
- full version from ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre.
-
-
. Support for the cdb (Constant DataBase) lookup method is provided by code
contributed by Nigel Metheringham of Planet Online Ltd. which contains
the following statements:
--
Dennis Davis, BUCS, University of Bath, Bath, BA2 7AY, UK
D.H.Davis [at] bath Phone: +44 1225 386101

--
## List details at http://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##


iane at sussex

Oct 14, 2009, 5:07 AM

Post #7 of 18 (1781 views)
Permalink
Re: [exim] Testing Exim 4.70 prerelease [In reply to]

--On 13 October 2009 17:38:49 +0200 Tom Kistner <tom [at] duncanthrax> wrote:

> The release of Exim 4.70 is on the horizon. A lot of stuff has
> accumulated in CVS since January 2008. Since we want to give the current
> code some wider exposure, please accept this invitation to test a 4.70
> pre-release.

This is great news. And SO nice not to have to go hunting for the
changelist! Thanks, Tom!

> You can get the current code by pulling a snapshot from
> David's GIT shadow:
>
> git clone git://git.exim.org/exim-src.git
>
> Or wget a tarball here:
>
> http://duncanthrax.net/temp/exim-4.70-RC-20091013.tar.gz
>
> Feel free to post testing results to this list - no matter if positive
> or negative.
>
> The main new features are:
>
> * Native DKIM support without an external library.
> Docs: http://www.exim.org/~tom/doctest/ch54.html
>
> * Experimental DCC support via dccifd (contributed
> by Wolfgang Breyha). See further below for docs.
>
>
> Other changes:
>
> * PCRE removed from Exim distribution. You will need
> a separate PCRE library (and matching headers) to
> compile Exim.
>
> * Experimental Yahoo! Domainkeys support dropped in
> favor of native DKIM support.
>
>
> Here's the full changelog:
>
> TK/01 Added patch by Johannes Berg that expands the main option
> "spamd_servers" if it starts with a dollar sign.
>
> TK/02 Write list of recipients to X-Envelope-Sender header when building
> the mbox-format spool file for content scanning (suggested
> by Jakob Hirsch)
>
> TK/03 Added patch by Wolfgang Breyha that adds experimental DCC
> (http://www.dcc-servers.net/) support via dccifd. Activated by
> setting EXPERIMENTAL_DCC=yes in Local/Makefile. Check out
> experimental_spec.txt for more documentation.
>
> TK/04 Bugzilla 673: Add f-protd malware scanner support. Patch submitted
> by Mark Daniel Reidel <mr [at] df>.
>
> NM/01 Bugzilla 657: Embedded PCRE removed from the exim source tree.
> When building exim an external PCRE library is now needed -
> PCRE is a system library on the majority of modern systems.
> See entry on PCRE_LIBS in EDITME file.
>
> NM/02 Bugzilla 646: Removed unwanted C/R in Dovecot authenticator
> conversation. Added nologin parameter to request.
> Patch contributed by Kirill Miazine
>
> TF/01 Do not log submission mode rewrites if they do not change the
> address.
>
> TF/02 Bugzilla 662: Fix stack corruption before exec() in daemon.c.
>
> NM/03 Bugzilla 602: exicyclog now handles panic log, and creates empty
> log files in place. Contributed by Roberto Lima
>
> NM/04 Bugzilla 667: close socket used by dovecot authenticator
>
> TF/03 Bugzilla 615: When checking the local_parts router precondition
> after a local_part_suffix or local_part_prefix option, Exim now
> does not use the address's named list lookup cache, since this
> contains cached lookups for the whole local part.
>
> NM/05 Bugzilla 521: Integrated SPF Best Guess support contributed by
> Robert Millan. Documentation is in experimental-spec.txt
>
> TF/04 Bugzilla 668: Fix parallel build (make -j).
>
> NM/05 Bugzilla 437: Prevent Maildix aux files being created with
> mode 000
>
> NM/05 Bugzilla 598: Improvement to Dovecot authenticator handling.
> Patch provided by Jan Srzednicki
>
> TF/05 Leading white space used to be stripped from $spam_report which
> wrecked the formatting. Now it is preserved.
>
> TF/06 Save $spam_score, $spam_bar, and $spam_report in spool files, so
> that they are available at delivery time.
>
> TF/07 Fix the way ${extract is skipped in the untaken branch of a
> conditional.
>
> TF/08 TLS error reporting now respects the incoming_interface and
> incoming_port log selectors.
>
> TF/09 Produce a more useful error message if an SMTP transport's hosts
> setting expands to an empty string.
>
> NM/06 Bugzilla 744: EXPN did not work under TLS.
> Patch provided by Phil Pennock
>
> NM/07 Bugzilla 769: Extraneous comma in usage fprintf
> Patch provided by Richard Godbee
>
> NM/08 Fixed erroneous documentation references to smtp_notquit_acl to be
> acl_smtp_notquit, added index entry.
>
> NM/09 Bugzilla 787: Potential buffer overflow in string_format
> Patch provided by Eugene Bujak
>
> NM/10 Bugzilla 770: Problem on some platforms modifying the len
> parameter to accept()
> Patch provided by Maxim Dounin
>
> NM/11 Bugzilla 749: Preserve old behaviour of blanks comparing equal to
> zero.
> Patch provided by Phil Pennock
>
> NM/12 Bugzilla 497: Correct behaviour of exiwhat when no config exists.
>
> NM/13 Bugzilla 590: Correct handling of Resent-Date headers.
> Patch provided by Brad "anomie" Jorsch
>
> NM/14 Bugzilla 614: Added timeout setting to transport filter.
> Patch provided by Dean Brooks
>
> TK/05 Add native DKIM support (does not depend on external libraries).
>
>
>
> Documentation for experimental dccifd support
> ---------------------------------------------
> *) Building exim
>
> In order to build exim with DCC support add
>
> EXPERIMENTAL_DCC=yes
>
> to your Makefile. (Re-)build/install exim. exim -d should show
> EXPERIMENTAL_DCC under "Support for".
>
> *) Configuration
>
> In the main section of exim.conf add at least
>
> dccifd_address = /usr/local/dcc/var/dccifd
>
> or
>
> dccifd_address = <ip> <port>
>
> In the DATA ACL you can use the new condition
>
> dcc = *
>
> After that "dcc_header" contains the X-DCC-Header.
>
> *** WARNING: return codes changed from previous releases!
>
> Return values are:
> "fail" for overall "R", "G" from dccifd
> "defer" for overall "T" from dccifd
> "accept" for overall "A", "S" from dccifd
>
> dcc = */defer_ok works as for spamd.
>
> dcc_result contains the overall result from DCC answer
>
> usually you'll use
>
> defer !dcc = *
>
> to greylist with DCC. If
>
> dcc_direct_add_header = true
>
> is set, then the dcc header will be added "in deep" and if the spool
> file was already written it gets removed. This forces exim to write it
> again if needed.
> This helps to get the DCC Header through to eg. SpamAssassin.
>
> If you want to pass even more headers in the middle of the DATA stage
> you can use $acl_m_dcc_add_header to add information from eg. ClamAV.
>
> Be careful. Header syntax is not checked and added "as is".



--
Ian Eiloart
IT Services, University of Sussex
01273-873148 x3148
For new support requests, see http://www.sussex.ac.uk/its/help/

--
## List details at http://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##


renaud at allard

Oct 14, 2009, 5:14 AM

Post #8 of 18 (1781 views)
Permalink
Re: [exim] Testing Exim 4.70 prerelease [In reply to]

Tom Kistner wrote:
> The release of Exim 4.70 is on the horizon. A lot of stuff has
> accumulated in CVS since January 2008. Since we want to give the current
> code some wider exposure, please accept this invitation to test a 4.70
> pre-release. You can get the current code by pulling a snapshot from
> David's GIT shadow:
>
> git clone git://git.exim.org/exim-src.git
>
> Or wget a tarball here:
>
> http://duncanthrax.net/temp/exim-4.70-RC-20091013.tar.gz
>

I just installed it on 2 of my production servers running OpenBSD amd64.

It verifies DKIM fine (well, at least it seems so)
2009-10-14 14:09:03 [8704] H=sendmail.net [209.246.26.21]:63769
I=[206.251.244.95]:25 Warning: CSA status: unknown
2009-10-14 14:09:04 [8704] 1My2f9-0002GO-W3 DKIM: d=sendmail.net
s=gatsby c=relaxed/simple a=rsa-sha256 t=1255522141 [verification succeeded]


It sends correct DKIM (although, now I get an error with DK because they
are not present anymore)
Authentication System: DomainKeys Identified Mail
Result: DKIM signature confirmed GOOD
Description: Signature verified, message arrived intact
Reporting host: sendmail.net
More information: http://mipassoc.org/dkim/
Sendmail milter: https://sourceforge.net/projects/dkim-milter/

Authentication System: Domain Keys
Result: DK signature confirmed BAD
Description: Signature verification failed, message may
have been tampered with or corrupted
Reporting host: sendmail.net
More information: http://antispam.yahoo.com/domainkeys
Sendmail milter:
https://sourceforge.net/projects/domainkeys-milter/
Attachments: smime.p7s (5.01 KB)


iane at sussex

Oct 14, 2009, 5:15 AM

Post #9 of 18 (1782 views)
Permalink
Re: [exim] Testing Exim 4.70 prerelease [In reply to]

--On 13 October 2009 14:36:24 -0700 Dan_Mitton [at] YMP wrote:

> Tom,
>
> That would be great !!

A word of caution regarding ADSP. It allows you to assert that some or all
of messages with a From: header address in your domain are signed. Clearly
"some" isn't very useful. It also allows you to say messages From: your
domain are discardable if they don't carry a valid signature.

There's currently great debate about how one should handle such messages
when they've been broken by mailing lists. My view is that lists should not
forward "discardable" messages if they're about to break the signature, but
should forward other messages. Lists should also re-sign, after checking
the inbound message. And recipients should attempt to validate the list,
not the original sender.

>
>
> Sent by: exim-users-bounces [at] exim
> To: Dan_Mitton [at] YMP
> cc: Exim Users <exim-users [at] exim>, exim-dev [at] exim
> Subject: Re: [exim] [exim-dev] Testing Exim 4.70 prerelease
> LSN: Not Relevant - Not Privileged
> User Filed as: Excl/AdminMgmt-14-4/QA:N/A
>
> Dan_Mitton [at] YMP schrieb:
>
>> 'dkim_verify_signers' option, but how does that stay up to date as more
>> and more (hopefully) people adopt? How can a domain tell me, that any
>> message I receive from them had better be signed and pass?
>
> This is done in ADSP
> (http://en.wikipedia.org/wiki/Author_Domain_Signing_Practices).
>
> Since the standard was only recently turned into an RFC, actual
> deployment is still very low.
>
> I'll add ADSP to Exim.
>
> /tom
>
> --
>## List details at http://lists.exim.org/mailman/listinfo/exim-users
>## Exim details at http://www.exim.org/
>## Please use the Wiki with this list - http://wiki.exim.org/



--
Ian Eiloart
IT Services, University of Sussex
01273-873148 x3148
For new support requests, see http://www.sussex.ac.uk/its/help/

--
## List details at http://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##


renaud at allard

Oct 14, 2009, 5:32 AM

Post #10 of 18 (1785 views)
Permalink
Re: [exim] Testing Exim 4.70 prerelease [In reply to]

Renaud Allard wrote:

>
> I just installed it on 2 of my production servers running OpenBSD amd64.
>
> It verifies DKIM fine (well, at least it seems so)
> 2009-10-14 14:09:03 [8704] H=sendmail.net [209.246.26.21]:63769
> I=[206.251.244.95]:25 Warning: CSA status: unknown
> 2009-10-14 14:09:04 [8704] 1My2f9-0002GO-W3 DKIM: d=sendmail.net
> s=gatsby c=relaxed/simple a=rsa-sha256 t=1255522141 [verification succeeded]
>
>
> It sends correct DKIM (although, now I get an error with DK because they
> are not present anymore)
> Authentication System: DomainKeys Identified Mail
> Result: DKIM signature confirmed GOOD
> Description: Signature verified, message arrived intact
> Reporting host: sendmail.net
> More information: http://mipassoc.org/dkim/
> Sendmail milter: https://sourceforge.net/projects/dkim-milter/
>
> Authentication System: Domain Keys
> Result: DK signature confirmed BAD
> Description: Signature verification failed, message may
> have been tampered with or corrupted
> Reporting host: sendmail.net
> More information: http://antispam.yahoo.com/domainkeys
> Sendmail milter:
> https://sourceforge.net/projects/domainkeys-milter/


In the light of this, is there a way to specify that DKIM is mandatory
while DK will not be present?
Attachments: smime.p7s (5.01 KB)


renaud at allard

Oct 14, 2009, 5:50 AM

Post #11 of 18 (1788 views)
Permalink
Re: [exim] Testing Exim 4.70 prerelease [In reply to]

I would suggest updating the README.UPDATING to show major uncompatible
changes, like domainkeys being removed.
Attachments: smime.p7s (5.01 KB)


renaud at allard

Oct 14, 2009, 8:53 AM

Post #12 of 18 (1782 views)
Permalink
Re: [exim] Testing Exim 4.70 prerelease [In reply to]

Tom Kistner wrote:
> The release of Exim 4.70 is on the horizon. A lot of stuff has
> accumulated in CVS since January 2008. Since we want to give the current
> code some wider exposure, please accept this invitation to test a 4.70
> pre-release. You can get the current code by pulling a snapshot from
> David's GIT shadow:
>
> git clone git://git.exim.org/exim-src.git
>
> Or wget a tarball here:
>
> http://duncanthrax.net/temp/exim-4.70-RC-20091013.tar.gz
>
> Feel free to post testing results to this list - no matter if positive
> or negative.

Got it to compile and install without any problems on OpenBSD 4.4 with
an alpha CPU. I can send and receive mails.
Attachments: smime.p7s (5.01 KB)


cmeerw at cmeerw

Oct 14, 2009, 1:09 PM

Post #13 of 18 (1785 views)
Permalink
Re: Testing Exim 4.70 prerelease [In reply to]

On Tue, 13 Oct 2009 17:38:49 +0200, Tom Kistner wrote:
[...]
> Feel free to post testing results to this list - no matter if positive
> or negative.

My gcc 4.2 doesn't like the ||= in src/lookups/lsearch.c (line 290) - and I
don't think it is a standard C99 assignment operator...


Christof

--

http://cmeerw.org sip:cmeerw at cmeerw.org
mailto:cmeerw at cmeerw.org xmpp:cmeerw at cmeerw.org

--
## List details at http://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##


jpm at retail-sc

Oct 16, 2009, 4:24 AM

Post #14 of 18 (1737 views)
Permalink
Re: [exim] Testing Exim 4.70 prerelease [In reply to]

> git clone git://git.exim.org/exim-src.git

Compiles (with a few warnings) fine on Mac OS/X 10.6.1, including
eximon.

-JP



--
## List details at http://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##


jh at plonk

Oct 16, 2009, 5:44 AM

Post #15 of 18 (1768 views)
Permalink
Re: Testing Exim 4.70 prerelease [In reply to]

Tom Kistner, 2009-10-13 17:38:

> The release of Exim 4.70 is on the horizon. A lot of stuff has

Thanks! :)

And while we are at it, I updated the bug about over-sensible
mime-decoding: http://bugs.exim.org/show_bug.cgi?id=39

There's no need to hurry with the release, so that's probably a good
time to let this test by a wider audience...



--
## List details at http://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##


toddr at cpanel

Oct 29, 2009, 12:09 PM

Post #16 of 18 (1458 views)
Permalink
Re: [exim] Testing Exim 4.70 prerelease [In reply to]

Tom Kistner, 2009-10-13 17:38:

> The release of Exim 4.70 is on the horizon. A lot of stuff has

Concerning PCRE, We generate exim RPMs for many platforms. We made a
decision to compile PCRE in staticly due to the fact that PCRE just
isn't going to be consistently available on some of the older platforms.

I had to use the --disable-cpp option with PCRE's configure in order
to prevent a linker hang on Redhat AS 2.1, which uses gcc 2.96. This
doesn't seem to be an across the board problem for gcc 2.96, but I
thought I'd let everyone know in the event someone else is banging
their head against that paticular wall.

Exim 4.70 is now compiling for us on:
32bit:
caos/2
centos/3.1
centos/4.0
centos/5.0
debian/3.0-r2
debian/3.1
fedora/1
fedora/10
fedora/11
fedora/2
fedora/3
fedora/4
fedora/5
fedora/6
fedora/7
fedora/8
fedora/9
mandrake/10.0
mandrake/2006
mandrake/8.2
mandrake/9.0
mandrake/9.2
mandrake/9.2.1
redhat/7.3
redhat/9
redhat/AS-2.1
redhat/AS-3
redhat/AS-5
redhat/ES-4
suse/10.0
suse/11.0
suse/9.0
suse/9.1
suse/9.3
trustix/2
trustix/2.2
whitebox/3.0
whitebox/3-fixed
whitebox/3-respin-1

64bit:
centos/4.0
centos/5.0
fedora/1
fedora/10
fedora/11
fedora/2
fedora/3
fedora/4
fedora/5
fedora/6
fedora/7
fedora/8
fedora/9
mandrake/2006
redhat/AS-3
redhat/AS-5
redhat/ES-4
suse/10.0
suse/11.0
suse/9.1
suse/9.3
whitebox/3.0


--
## List details at http://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##


tom at duncanthrax

Oct 30, 2009, 2:52 AM

Post #17 of 18 (1428 views)
Permalink
Re: [exim] Testing Exim 4.70 prerelease [In reply to]

Todd Rinaldo wrote:

> Exim 4.70 is now compiling for us on:

Thanks for the heads-up. The list is quite impressive :)

/tom



> 32bit:
> caos/2
> centos/3.1
> centos/4.0
> centos/5.0
> debian/3.0-r2
> debian/3.1
> fedora/1
> fedora/10
> fedora/11
> fedora/2
> fedora/3
> fedora/4
> fedora/5
> fedora/6
> fedora/7
> fedora/8
> fedora/9
> mandrake/10.0
> mandrake/2006
> mandrake/8.2
> mandrake/9.0
> mandrake/9.2
> mandrake/9.2.1
> redhat/7.3
> redhat/9
> redhat/AS-2.1
> redhat/AS-3
> redhat/AS-5
> redhat/ES-4
> suse/10.0
> suse/11.0
> suse/9.0
> suse/9.1
> suse/9.3
> trustix/2
> trustix/2.2
> whitebox/3.0
> whitebox/3-fixed
> whitebox/3-respin-1
>
> 64bit:
> centos/4.0
> centos/5.0
> fedora/1
> fedora/10
> fedora/11
> fedora/2
> fedora/3
> fedora/4
> fedora/5
> fedora/6
> fedora/7
> fedora/8
> fedora/9
> mandrake/2006
> redhat/AS-3
> redhat/AS-5
> redhat/ES-4
> suse/10.0
> suse/11.0
> suse/9.1
> suse/9.3
> whitebox/3.0
>
>


--
## List details at http://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##


serge at srv0

Oct 30, 2009, 3:09 AM

Post #18 of 18 (1428 views)
Permalink
Re: [exim] Testing Exim 4.70 prerelease [In reply to]

Le Friday 30 October 2009 10:52:14 Tom Kistner, vous avez écrit :
> Todd Rinaldo wrote:
> > Exim 4.70 is now compiling for us on:
>
> Thanks for the heads-up. The list is quite impressive :)
>
> /tom
>
> > 32bit:
Caos Linux NSA :: <http://mirror.caosity.org/Caos-NSA-1.0/testing/i386/>
exim-4.70-0.RC20091028.1.caos.i386.rpm
exim-devel-4.70-0.RC20091028.1.caos.i386.rpm
exim-monitor-4.70-0.RC20091028.1.caos.i386.rpm
exim-plugin-spamassassin-4.2.1-4.70-0.RC20091028.1.caos.i386.rpm
> > centos/3.1
> > centos/4.0
> > centos/5.0
> > debian/3.0-r2
> > debian/3.1
> > fedora/1
> > fedora/10
> > fedora/11
> > fedora/2
> > fedora/3
> > fedora/4
> > fedora/5
> > fedora/6
> > fedora/7
> > fedora/8
> > fedora/9
> > mandrake/10.0
> > mandrake/2006
> > mandrake/8.2
> > mandrake/9.0
> > mandrake/9.2
> > mandrake/9.2.1
> > redhat/7.3
> > redhat/9
> > redhat/AS-2.1
> > redhat/AS-3
> > redhat/AS-5
> > redhat/ES-4
> > suse/10.0
> > suse/11.0
> > suse/9.0
> > suse/9.1
> > suse/9.3
> > trustix/2
> > trustix/2.2
> > whitebox/3.0
> > whitebox/3-fixed
> > whitebox/3-respin-1
> >
> > 64bit:
Caos Linux NSA :: <http://mirror.caosity.org/Caos-NSA-1.0/testing/x86_64/>
exim-4.70-0.RC20091028.1.caos.x86_64.rpm
exim-devel-4.70-0.RC20091028.1.caos.x86_64.rpm
exim-monitor-4.70-0.RC20091028.1.caos.x86_64.rpm
exim-plugin-spamassassin-4.2.1-4.70-0.RC20091028.1.caos.x86_64.rpm
> > centos/4.0
> > centos/5.0
> > fedora/1
> > fedora/10
> > fedora/11
> > fedora/2
> > fedora/3
> > fedora/4
> > fedora/5
> > fedora/6
> > fedora/7
> > fedora/8
> > fedora/9
> > mandrake/2006
> > redhat/AS-3
> > redhat/AS-5
> > redhat/ES-4
> > suse/10.0
> > suse/11.0
> > suse/9.1
> > suse/9.3
> > whitebox/3.0



--
(o_
(/)_
S e r g e

--
## List details at http://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##

exim dev RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.