|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Matthias Andree (ma
dt.e-technik.uni-dortmund.de)Date: Fri Feb 09 2001 - 03:43:17 CST
Preface: Don't use ReiserFS and NFSv3 on Linux 2.2.
Disclaimer: Massive Kernel patching may work around these issues.
Okay, NFS is unsupported, yet, I'm reporting this since it may be a more
general problem that's only easily seen with these NFS issues.
The actual cause for the errors is the inconsistent inode number bit width in
ReiserFS and NFSv3. The lookup for Maildir/ fails and report EACCES.
Okay, when a mail to root arrives, it is aliased to five real,
unprivileged users which do not themselves forward back to root. Three
of them are delivered properly (two via NFS on different servers, one
locally), two report error condition (excerpt from mailq, user name made
up):
(can't create user output file. Command output: procmail: Unable to
treat as directory "/home/SOME_USER/Maildir" procmail: Couldn't create
"/home/SOME_USER/Maildir" procmail: Unable to treat as directory
"/home/SOME_USER/Maildir" procmail: Error while writing to
"/home/SOME_USER/Maildir")
Usually, Postfix would bounce, which I suppress using soft_bounce.
The interesting part is in mailq output, which follows this scheme:
QUEUEID size date ENVELOPE-FROM
ERROR as above
SOME_USER
dt.e-technik...
ERROR as above
SOME_OTHER_USER
dt.e-technik...
root
dt.e-technik...
Now, since root has been alias expanded, why is it still there? Okay, it's in
the original envelope information (shown by postcat), but I feel this causes
duplicates for the users which get their mail.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]