OT: system ignores .forward file

[Res]

On Fri, 16 Mar 2007, Chris Yuzik wrote:

> Hi everyone,
>
> I can't seem to get the system to look at the .forward file in the user's 
> home dir. I've checked the permissions of the .forward file and it seems fine 
> too.
>
>   # pwd
>   /home/domain1.com/homes/someguy
>
>   # ls -lha
>   total 20K
>   drwxr-xr-x 4 someguy at domain1.com <mailto:someguy at domain1.com>
>   domain1.com 4.0K Mar 16 09:23 .
>   drwxr-xr-x 4 domain1.com domain1.com 4.0K Feb 26 20:57 ..
>   -rw-r--r-- 1 someguy at domain1.com <mailto:someguy at domain1.com>
>   domain1.com 21 Mar 16 09:23 .forward
>
>   # cat .forward
>   someotherguy at domain2.com <mailto:someotherguy at domain2.com>
>
> When a message comes in to someguy at domain1.com <mailto:someguy at domain1.com>, 
> rather than the system reading the .forward file and forwarding it over to 
> someotherguy at domain2.com <mailto:someotherguy at domain2.com>, the system just 
> puts it in the mailbox for someguy at domain1.com <mailto:someguy at domain1.com> 
> as though the .forward file wasn't there.

Do any other user forwards work? If not check out whatever you are using to
redirect (special procmail rules? or some vhost code?), Sendmails 
local mailer cant read what it does not know about. Perms should always be 
600 on .forward, unless you need to pipe to a program like vacation in which
case 611 may be needed on some systems.

> The maillog isn't particularly helpful:

Sendmail has looked up your user, seen its valid and passed it off to 
mail.local or procmail, this area is where you need to look at.

You may in sendmail.mc add this to see if it shows anything more :

define(`confLOG_LEVEL',`30')dnl

I warn you, on busy systems your logs will grow huge fast.
So dont define this for more than a few minutes on production boxes.


-- 
Cheers
Res


Let Novell known what you think of their back door deal with the devil.
Sign the petition today:   http://techp.org/p/1/