At 12:03 PM 8/27/99 -0700, Jeff Grossman wrote:
I am having a problem with Procmail. Here is the log message that I am
getting:
procmail: Couldn't determine implicit lockfile from "/usr/bin/dmail"
That message is because there's no default filename implied when
the action specified is a pipe. Put a lockfile name after the
second colon
:0:
Or omit the second colon (does dmail really require locking?)
I decided to remove the colon. I no longer get this error message.
delivery to /mail/Mailing Lists unsafe: No such file or directory
invalid mailbox name root+mail/Mailing Lists
delivered to /INBOX
I would avoid filenames with spaces in them like the plague!!!
Every time you use them, including in variable names, you need to be
super-careful about the quoting rules. It's not worth the trouble
when you control the filenames!
I am not quite sure from your recipe what you are *trying* to do...
I have decided to remove the space from the mailbox. But I do not think
that was causing my problem. I might experiment later and add a space in.
From owner-news-dispatch-html(_at_)DISPATCH(_dot_)CNET(_dot_)COM Fri Aug 27
11:28:08 1999
Subject: Amazon grants new COO hefty stock package/Now Linux gets its
own
Folder: /usr/bin/dmail +mail/Mailing Lists
24364
Here is my Procmail recipe file:
VERBOSE=off
MAILDIR=mail
Trouble lurks here... I think you wanted
MAILDIR=$HOME/mail
Nope, I did not need to add that. I kept it at MAILDIR=mail and everything
works fine.
PMDIR=$HOME/.procmail
LOGFILE=$PMDIR/procmail.log
INCOMING=mail
DELIVER=/usr/bin/dmail
DROP="$DELIVER +$INCOMING" # Usage: "| $DROP/foldername"
the purpose of doing this is what?
I am not really sure. It was recommended from me from somebody. Since it
is working, I will leave it the way it is.
:0:
* ^Subject:.*linux
* !^Subject:(_dot_)*root(_at_)apple
| $DROP/'Mailing Lists'
Are you trying to have DROP contain a command plus
half of a pathname, the other half of which has a space
in it? If so, why? If not, well, that's what it looks like
you're doing.
[snip]
It says that the message is being delivered to INBOX, but that is not the
case, so I have temporarily removed my .procmailrc file so I do not lose any
mail. My mail files are in $HOME/mail. My Inbox is in $HOME.
No, that is not what it said. It said "delivered to /INBOX",
not $HOME/INBOX. "/INBOX" is a specific pathname (see the slash on
the front?), not a generic term. So, look there (on the mail machine,
which could possibly be different from the one you normally log into);
your mail is probably not lost.
I can't quite see how you got "root" in the message above
(repeated here for convenience):
Okay, I will take a look and see if I can find a /INBOX folder which
contains my messages that were lost.
invalid mailbox name root+mail/Mailing Lists
whereas I'd have expected to see
invalid mailbox name +mail/Mailing Lists
Does "dmail" (whatever that is) prepend the user name to generate
the message, perhaps? Or I am missing something (which is
quite possible due to limited time I can spend on this)? In any
case, keep it simple: don't put spaces in filenames, and
don't put spaces in variables. Even if this doesn't help you sleep
better at night, you will get better help when you ask for it. :-)
Okay, here is where all of my problems were. I was originally going to
switch from Procmail to Tmail as my local delivery agent in Sendmail, but
found out that Tmail needed to be setuid root. For some strange reason, I
was under the impression that I needed to do that for Dmail also. So, that
is what I did wrong. I have since done a chmod on Dmail to 755, and now
everything is working as planned. I can't believe I made such a stupid
mistake. That whole thing about root was throwing me too. I wish I knew
enough to realize that was my problem.
Thank you very much for your help.
Jeff
--
Jeff Grossman (jeff(_at_)stikman(_dot_)com)
Hope that helps some.
Stan
ps - I'm not subscribed to linux list, will not see any response there.