From: geoff@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] my previous note on vf
Date: Sat, 2 Jun 2007 23:26:26 -0400 [thread overview]
Message-ID: <6c2141e39eabf0aa0def1fb037b5968a@plan9.bell-labs.com> (raw)
In-Reply-To: <13426df10706022014k240d2a96h12dea0548fa6a093@mail.gmail.com>
/mail/tmp needs to be world-writable and setting the temp bit would be
a good idea too:
chmod +trwx /mail/tmp
It isn't this way on sources to avoid having world-writable files in
the distribution.
The error messages about attachments that Ron saw are misleading, but
vf is being conservative and defaulting to not letting mail through
when something goes wrong. Note too that the first error message
was right on the money:
error+ failed with error 'error creating temporary file: '/tmp/vf.00000037245' permission denied
Since errors tend to cascade, it's usually best to fix the first
problem reported and try again.
next prev parent reply other threads:[~2007-06-03 3:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-03 3:14 ron minnich
2007-06-03 3:26 ` geoff [this message]
2007-06-03 3:32 ` ron minnich
2007-06-03 3:43 ` W B Hacker
2007-06-06 8:49 ` Douglas A. Gwyn
2007-06-06 9:07 ` W B Hacker
2007-06-03 4:03 ` erik quanstrom
2007-06-03 8:58 ` Steve Simon
2007-06-03 4:29 geoff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6c2141e39eabf0aa0def1fb037b5968a@plan9.bell-labs.com \
--to=geoff@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).