On Sunday 13 March 2005 12:58 pm, Paul Oehler wrote:
> I've seen Jeremy Kitchen post to the maildrop list, which makes me hopeful
> that the Inter7 folks may be running Maildrop + vdelivermail internally.
no, I run maildrop on my system account on my mail server.
-Jeremy
--
Jeremy Kitchen ++ S
A unified diff (diff -u) is better, since it provides context for the
changes and makes it easier for someone to manually make the change.
Here's a unified diff against the 5.4.9 version. Let me know if you need
anything different.
Paul
--
Paul Oehler
NEXCESS.NET Internet Solutions
http://nexce
On Mar 13, 2005, at 2:08 PM, Paul Oehler wrote:
Tom, thanks for the response. I made the change to vdelivermail.c,
recompiled, and the problem does indeed appear to have disappeared. I
don't know if there's a specific way to make a patch, but here's a
diff of the 5.4.9 vdelivermail.c against t
To sum up again, he says the problem "is because vdelivermail exits,
before it read the pipe completly. vdelivermail simply checks whether
the receipient is valid, and if not,
exits at once, causing a SIGPIPE in maildrop."
It should be possible to update vdelivermail to scan through to the end
On Mar 13, 2005, at 10:58 AM, Paul Oehler wrote:
To sum up, the problem occurs at seemingly random times (but often),
when running vdelivermail from the Maildrop filter file. As Matt
described, the error as it appears in the qmail-send log looks like:
2005-02-18 21:58:22.285783500 delivery 18
I just started testing out Maildrop with Vpopmail this weekend, and found
some interesting problems.
Versions: maildrop 1.8.0, vpopmail 5.4.9
The problem I had is the same as Matt Kern describes here:
http://www.mail-archive.com/vchkpw@inter7.com/msg20582.html
To sum up, the problem occurs at see
