I don't remember writing this to the list before, so I will write it
now... I just tried 3.14 on several machines and saw some strange
behaviour comapred to 3.02 -> 3.13
I used the EXIM_UID and EXIM_GID flag in the makefile so that Exim would
run as user exim if at all possible and noticed some serious problems.
It apepar to run as user exim for *almost* everything it does, except
creation of spool files. I am using split spools from a Exim 3.02 and
upgraded to 3.14 and no, no matter what I set my permissions to in the
Makefile, all my spool files are created:
OWNER: root, GROUP: exim, PERM: 600
I poked around for a bit, but didn't find anything that would fix it. I
had 10's of thousands of messages bouncing, so I didn't have liberty to
trouble shoot it too much.
I tried to change the define in the makefile to create them with 660
permissions, which would have been a good temporary fix, but that didn't
work. I had to comment out the EXIM_UID line in the Makefile and
recompile.
I did not try this without split spools (we handle too much mail on ext2
to do that :)
> Shortly after exim-3.14 was released, I thought I saw messages on this
> mailing list which suggested that there was some problem with respect to
> a behavioral change from exim-3.13 that bit some people. I seem to
> remember it having something to do with filters.
>
> I've spent a little time looking at the archives for the list, but I
> can't find anything to support my suspicion.
>
> I've had a request to update the FreeBSD port for Exim from 3.13 to
> 3.14. Before I do, I'd like to ask whether anyone remembers an issue
> that might have led me to believe what I do, or whether I picked up on a
> red herring.
