We didn't test iRedMail-0.6.0-beta1 in Jailed env before.

Is it possible to install iRedMail first, and then use ezjail or whatever to create a jail?

well I dont really want to dedicate a machine too it yet. Bit puzzled because of mkstemp is trying to write to /tmp which should be fine
I am running it again today to see if it stops in the same place.

Is it possible to install iRedMail first, and then use ezjail or whatever to create a jail?

iRedMail-0.5.1 doesn't support FreeBSD, but the -current version supports it.

I created a snapshot version for you:
http://iredmail.googlecode.com/hg/snapshots/

You can use it to deploy iRedMail on FreeBSD, it supports FreeBSD 7.2 & 8.0 release, and i386 & amd64.

Thank you for that it ran fine upto this point

< INFO > Add user and group for policyd: policyd:policyd.
< INFO > Initialize MySQL database of policyd.
mktemp: mkstemp failed on iRedMail.iWZbxY: Read-only file system
/home/test/iRedMail-0.6.0-beta1/functions/policy_service.sh: line 78: ${tmp_sql}: ambiguous redirect
/home/test/iRedMail-0.6.0-beta1/functions/policy_service.sh: line 91: ${tmp_sql}: ambiguous redirect
/home/test/iRedMail-0.6.0-beta1/functions/policy_service.sh: line 116: ${tmp_sql}: ambiguous redirect

I was using a jail created with ezjail which of course mounts some shared parts as read only.
On the other hand it ideal for testing because I dont have to worry about breaking any thing.
It just sat at that point rather than bailing out all together

I created a snapshot version for you:
http://iredmail.googlecode.com/hg/snapshots/

You can use it to deploy iRedMail on FreeBSD, it supports FreeBSD 7.2 & 8.0 release, and i386 & amd64.

uname -a
FreeBSD iredmail 8.0-RELEASE
iRedMail-0.5.1.tar.bz2
so bit stumped all ready