|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Alex van den Bogaerdt (alex_at_ergens.op.HET.NET)
Date: Wed Jul 24 2002 - 11:03:36 CDT
Wietse Venema wrote:
> > Then what would be a safe way to create a directory.
>
> If I knew the answer then we would not have this discussion.
OK, you don't know how it can be made safe. Obviously you *do*
know why certain tactics are unsafe. Maybe you want to share
some of that information so maybe I, or someone else, can make
a proposal that actually works for you ?
> > Me personally only need this to change inside the default spool dir
> > and only for a root-owned directory that isn't writable by others.
> > Maybe that helps?
>
> See above.
Now I must conclude that you don't know if it's safe to create
a directory inside $spool_dir. What can go wrong?
> What is the problem with setting up proper user management procedures
> that create mailboxes when an account is created or when an account
> is migrated? This should be routine sysadmin stuff.
Like I said: People make mistakes.
From a user perspective there's little difference between mailbox
and maildir. Can you explain why postfix *does* create mailboxes?
> For example, the login program does not create a home directory on
> the fly, either. No-one complains about that.
That's something completely different. For one, a user may be
able to login if the sysadmin accidentally removes the home dir
or makes a similar mistake, while the user does not receive mail
when that same admin accidentally (re)moves the maildir.
Why are you so aggresive about this stuff? Is it too much to ask
for a decent, polite answer? Like I said before: I want to help.
Your attitude doesn't contribute to the program.
-
To unsubscribe, send mail to majordomo
postfix.org with content
(not subject): unsubscribe postfix-users
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]