Victor.Duchovnimorganstanley.com:
> On Tue, 7 May 2002, Matt Soccio wrote:
>
> > I have a user with a .forward that works for all internal tests, internal
> > lists, etc., but when he gets mail from an exteral list (like this one),
> > the .forward seems to be skipped and his mail is delivered locally. I was
> > willing to dismiss this as an odd NFS snafu, until I saw the logs from the
> > mail that was delivered locally yesterday. An external mail list sent
> > data to 10 people in our department, 2 of these folks have .forward files,
> > the one with a procmail pointer worked, while the one with a forwarding
> > address was locally delivered. I don't see ANY logs about nfs servers not
> > responding, let alone ones that coincide with this mail. Is it possible
> > for majordomo mailings to somehow force local delivery? I have looked at
> > the headers of the mail and don't see anything fishy. Is there some way
> > that I can test if the .forward file is actually being read? Are there
> > any circumstances where it would be ignored?
> >
>
> Can "local" running as "root" read the user's home directory and .forward
> file over NFS? I don't think that "local" drops privileges until it begins
> delivery (I could be wrong here). It could be a simple UNIX file
> permissions issue.

Postfix stat(2)s the .forward file as the recipient before deciding
to use it.

    while ((lhs = mystrtok(&next, ", \t\r\n")) != 0) {
        expand_status = local_expand(path, lhs, &state, &usr_attr,
                                     var_fwd_exp_filter);
        if ((expand_status & (MAC_PARSE_ERROR | MAC_PARSE_UNDEF)) == 0) {
            lookup_status =
                lstat_as(STR(path), &st, usr_attr.uid, usr_attr.gid);

        Wietse
-
To unsubscribe, send mail to majordomopostfix.org with content
(not subject): unsubscribe postfix-users

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]