Your message dated Mon, 20 Feb 2012 23:22:45 +0900
with message-id <20120220142245.GA6130@localhost>
and subject line maildrop says that directories will not be created
has caused the Debian Bug report #198165,
regarding maildrop: must say that directories will not be created
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
198165: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=198165
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: maildrop
Version: 1.5.2-1
Severity: normal
File: /usr/share/man/man5/maildropfilter.5.gz
Tags: upstream
man says:
TO - DELIVER MESSAGE TO A MAILBOX
to expression
The to statement delivers the message to a mailbox. expression must
evaluate to a valid mailbox. A valid mailbox is either a mailbox file,
a maildir, or an external program (which includes forwarding to another
address).
OK, but then add:
Note, unlike procmail, the maildir directories will not be created if
they don't exist already. They must already exists, along with their
subdirectories, or else the sender will get /usr/bin/maildrop: Unable to open
mailbox.
or etc. dot file warnings.
In summary, unless you just do
to "plainfile"
you had better have all the dirs ready [why can't it make them if they
don't exist?!?!]
e.g.
to "somedir/"
Otherwise, expression names the mailbox where maildrop delivers the
message. If expression is a directory, maildrop assumes that the
directory is a maildir directory. Otherwise, maildrop will deliver the
message to a file, formatted in traditional mailbox format. maildrop
will use either dot-locking, or flock()-locking when delivering the
message to the file.
yeah, but if the dir doesn't exist yet, you are in big trouble,
if the file doesn't exist yet, maildrop will create it.
why the difference, who knows.
Oh on maildropex man page, we see
You can create a maildir using the maildirmake command.
OK, but no examples of how to write a script that makes one if it
doesn't exist...
And, maildirmake is not mentioned on the other man pages SEE ALSO parts.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux debian 2.4.20-k7 #1 Tue Jan 14 00:29:06 EST 2003 i686
Locale: LANG=zh_TW.Big5, LC_CTYPE=zh_TW.Big5
Versions of packages maildrop depends on:
ii exim [mail-transport-agent] 3.36-4 An MTA (Mail Transport Agent)
ii libc6 2.3.1-10 GNU C Library: Shared libraries an
ii libgcc1 1:3.3-0pre7 GCC support library
ii libgdbmg1 1.7.3-27.1 GNU dbm database routines (runtime
ii libstdc++5 1:3.3-0pre7 The GNU Standard C++ Library v3
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
I am going over BTS.
This is well documented and proper usage method exist.
So there is no bug as reported in the title:
maildrop: must say that directories will not be created
I am closing this.
Osamu
--- End Message ---
