I just got an answer from tech support.
Basically, procmail doesn't handle the symbolic link well on this system,
so I changed it to another directory $HOME/Mail, and I do not get the
error message.
No data waqs lost in either case.
--
Matthew G. Saroff
Owings Mills, MD
On Sun, 10 Oct 2010, Professional Software Engineering wrote:
At 13:37 2010-10-10, Matthew G. Saroff wrote:
I moved to a new ISP, and I started to get this error in my
procmail log.
Well, for one, that's not a procmail error, it's an error being kicked up by
sh.
Chances are, there's an intermediate directory that you don't have
permissions to. Perhaps the mail directory is mounted NFS?
lrwxrwxrwx 1 root wheel 43 Sep 24 2007 .maildir ->
/net/mail/spool/panix/0/5/msaroff(_at_)panix(_dot_)com
What are the perms of the target itself -- the perms and ownership you see
here are for the symlink.
Q: is procmail the LDA, or are you invoking it from a .forward? Are these
the only recipes you have that are invoking shell? Is it possible that your
new ISP has smrsh (sendmail restricted shell)?
---
Sean B. Straw / Professional Software Engineering
Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
Please DO NOT carbon me on list replies. I'll get my copy from the list.
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)de
http://mailman.rwth-aachen.de/mailman/listinfo/procmail
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)de
http://mailman.rwth-aachen.de/mailman/listinfo/procmail