On Fri, Oct 03, 2003 at 11:22:11PM -0400, Greg Folkert wrote:
> [EMAIL PROTECTED]:~$ maildrop -V2 -m .mailfilter
> maildrop: Timeout quota exceeded.
> [EMAIL PROTECTED]:~$ maildrop -V2 -M .mailfilter
> maildrop: Changing to /home/greg
> maildrop: Timeout quota exceeded.
> [EMAIL PROTECTED]:~$ maildrop -V2 .mailfilter
> maildrop: Timeout quota exceeded.
> [EMAIL PROTECTED]:~$ maildrop -V2
> maildrop: Timeout quota exceeded.
I went re-reading old bug reports, and it just struck me - you're getting
the timeout because you aren't passing any data to it.
Pipe something to it, and then test -V something.
> Here is the transport for maildrop run out of EXIM:
>
> maildrop_pipe:
> debug_print = "T: maildrop_pipe for [EMAIL PROTECTED]"
> driver = pipe
> path = "/bin:/usr/bin:/usr/local/bin"
> command = "/usr/bin/maildrop"
> return_path_add
> delivery_date_add
> envelope_to_add
I also noticed that this transport doesn't have a user definition of
any kind. You can add these options:
user = $local_part
group = mail
so that Exim runs maildrop as the user who receives the e-mail.
Otherwise, I'd wager that it would try to deliver mail as the system user
"Debian-exim", which doesn't sound like something you'd want for all users.
--
2. That which causes joy or happiness.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
