EXIM 4.66 build failing ?

Trying to build EXIM 4.66 on a freebsd box and when it runs in upcp or eximup here is a snippet:

===> Cleaning for exim-4.66
===> Vulnerability check disabled, database not found
=> exim-4.66.tar.bz2 doesn't seem to exist in /usr/ports/distfiles/exim.
=> Attempting to fetch from ftp://ftp.csx.cam.ac.uk/pub/software/email/exim/exim4/.
=> FAQ.txt.bz2 doesn't seem to exist in /usr/ports/distfiles/exim.
=> Attempting to fetch from ftp://ftp.csx.cam.ac.uk/pub/software/email/exim/exim4/.
fetch: ftp://ftp.csx.cam.ac.uk/pub/software/email/exim/exim4/FAQ.txt.bz2: File unavailable (e.g., file not found, no access)
=> Attempting to fetch from ftp://ftp.exim.org/pub/exim/exim4/.
fetch: ftp://ftp.exim.org/pub/exim/exim4/FAQ.txt.bz2: File unavailable (e.g., file not found, no access)
=> Attempting to fetch from http://public.planetmirror.com/pub/exim/exim/exim4/.
===> Extracting for exim-4.66
=> MD5 Checksum OK for exim/exim-4.66.tar.bz2.
=> SHA256 Checksum OK for exim/exim-4.66.tar.bz2.
===> exim-4.66 depends on file: /usr/local/bin/perl5.8.8 - found
bzcat: /usr/ports/distfiles/exim/FAQ.txt.bz2 is not a bzip2 file.
*** Error code 2

Stop in /usr/ports/mail/exim.
** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.16319.0 env make FETCH_BEFORE_ARGS=-q
** Fix the problem and try again.
---> Build of mail/exim ended at: Wed, 28 Mar 2007 23:34:12 -0400 (consumed 00:00:20)
---> Fresh installation of mail/exim ended at: Wed, 28 Mar 2007 23:34:12 -0400 (consumed 00:00:20)
---> ** Install tasks 1: 0 done, 0 ignored, 0 skipped and 1 failed
---> Listing the results (+:done / -:ignored / *:skipped / !:failed)
! mail/exim (unknown build error)
---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed
---> Session ended at: Wed, 28 Mar 2007 23:34:12 -0400 (consumed 00:00:35)
Running post install scripts for exim....Done


Seems like it is trying to unzip a file called FAQ.txt.bz2 which it THINKS is a bz2 file but just appears to be a text file of html code.

Anyone else getting this problem ???

 

Nope, it seems to be downloading a "bz2" file that is really a text file. It dies because of this, so its not the ports, its where the ports yank the files from OR that the 4.66 distribution is screwed up everywhere. Doing a manual build in the ports produces the same error.

 

Well how do you suggest updating the ports?. UPCP showed it updated the ports and doing a manual "make deinstall" and "make install clean" didnt change the problem.