Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 48281 - sendmail fails to validate users home directory on checking for .forward
sendmail fails to validate users home directory on checking for .forward
Product: Red Hat Linux
Classification: Retired
Component: sendmail (Show other bugs)
i386 Linux
high Severity high
: ---
: ---
Assigned To: Thomas Woerner
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2001-07-09 20:55 EDT by Ben LaHaise
Modified: 2005-10-31 17:00 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-10-21 10:35:38 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ben LaHaise 2001-07-09 20:55:01 EDT
In more complicated system setups where /home is mounted via NFS, sendmail
fails to check  for the existence of the user's home directory when
checking if a .forward file exists.  This causes misdelivery of mail when
there is a temporary problem with the home directory (eg if the NFS server
is offline).  A suitable fix should involve checking that the home
directory exists and is readable on failure to open ~/.forward.
Comment 1 David Woodhouse 2001-07-11 08:38:37 EDT
The suggested fix is implemented and works fine in Exim and Postfix.
Comment 2 Ben LaHaise 2001-09-26 17:48:47 EDT
Is anything being done about this?
Comment 3 Florian La Roche 2002-04-07 09:56:25 EDT
sendmail itself does not do any local mail delivery. Our default local
delivery is procmail, so I re-assign to this component in bugzilla.

Florian La Roche
Comment 4 Ben LaHaise 2002-04-07 17:20:10 EDT
procmail does not perform .forward parsing.  Reassigned to sendmail.
Comment 5 Thomas Woerner 2004-10-21 10:35:38 EDT
Please verify this with a newer version of Red Hat Enterprise Linux or
Fedora Core and reopen it against the new version if it still occurs.

Closing as "not a bug" for now.

Note You need to log in before you can comment on or make changes to this bug.