uhhh, I see.
now I understand, I though that
message is kept only for second, third... confirmations.
hmm, but how TMDA is moving confirmed message
from ./pending directory?
Is it like: "mv ./.tmda/pending/000.000.msg ./Maildir/new/" or
message is injected through .qmail{.forward} file?
Is it ok to run cron every 10min which grep confirmed messages
in .delivered_cache and then delete them? we are using Maildirs and Qmail.
And just one more question :)
what about entries in .delivered_cache?
I'm running from crom "tmda-pending -bd -O4w"
but confirmed history is still in the .delivered_cache file:
> sa(dp4
> S'1039422370.17961.msg'
> S'c'
...
.....
Artis
http://www.ltn.lv/~ac
----- Original Message -----
From: "Jason R. Mastaler" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: pirmdiena, 2002. gada 9. decembri 21:57
Subject: Re: .delivered_cache
> "Artis Caune" <[EMAIL PROTECTED]> writes:
>
> > I'm not Python guru, but I played with ./pending directory and found
> > that there is no need to keep body of the confirmed message.
>
> This isn't quite true, but it's not very obvious why.
>
> The problem is that there is no way for TMDA to know whether the
> delivery to the user's inbox succeeded, so it isn't safe to remove the
> message contents in case that fails.
>
> The reason is because of how .qmail files work.
>
> Say the user has in his .qmail:
>
> |preline tmda-filter
> ./Mailbox
>
> When TMDA exits to let qmail deliver to ./Mailbox, control is never
> returned to TMDA, so it doesn't know whether it succeeded or not.
>
> If TMDA didn't support .qmail files, this would be easier to handle,
> but this is not the case.
_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users
