Re: [Exim] Classic lock file hitching post problem

Top Page
Delete this message
Reply to this message
Author: Philip Hazel
Date:  
To: Sheldon Hearn
CC: exim-users
Subject: Re: [Exim] Classic lock file hitching post problem
On Mon, 5 Mar 2001, Sheldon Hearn wrote:

> The reason I did this was that Exim didn't like delivering to a user
> without a home directory:
>
>    2001-02-05 19:45:25 14Pphc-000HCz-00 == arbuser@??? D=userforward defer (-1): failed to stat /nonexistent (No such file or directory)


There is usually a way round this. Maybe set

file_directory=/

on the director to make it stat a different directory. Wait a minute.
You are talking about /etc/aliases, but that line mentions userforward,
which is looking for a .forward file. How has that happened? An entry in
/etc/alias would, with a conventional configuration, take precedence.

> Using /nonexistent as a home directory for users who aren't allowed
> shell sessions is quite normal in the BSD environment.
>
> However, even with ``group = mail'' in the address_file transport, I
> still get the hitching post permissions problem, which stumps me. If I
> make the /var/mail directory world-writable, arbuser's mailbox is
> created by user nobody, group nobody!


Sounds like you need a user= on the aliasing director. Have you tried
running with -d9 to see what is actually happening.

-- 
Philip Hazel            University of Cambridge Computing Service,
ph10@???      Cambridge, England. Phone: +44 1223 334714.