I'm not sure if it this counts as a bug or just user error..
If exim4 is given an exim3 (or possibly older) style config file which
allowed
file = .forward
in the userforward router
it segfaults. I fully realise that this will not ever happen to most
people but should exim point out the error rather than falling over?
N.B. This is not the fault of the convert4r4 script which had been applied
--
Alan Thew alan.thew@liverpool.ac.uk
Computing Services,University of Liverpool Fax: +44 151 794-4442
If exim4 is given an exim3 (or possibly older) style config file which
allowed
file = .forward
in the userforward router
it segfaults. I fully realise that this will not ever happen to most
people but should exim point out the error rather than falling over?
N.B. This is not the fault of the convert4r4 script which had been applied
--
Alan Thew alan.thew@liverpool.ac.uk
Computing Services,University of Liverpool Fax: +44 151 794-4442