In DBMail 1.2.7, I have no recollection of what the options for
dbmail-util were. Things are now much more consistent in 2.0.1 and will be
even more so in 2.0.2.

If you need me to take a look at 1.2.7, I can do that in the coming weeks.

Aaron


Paul J Stevens <[EMAIL PROTECTED]> said:

> nate wrote:
>> Leonel Nunez wrote:
>> 
>>>hmm, I am runing dbmail 1.2.7 and above and dbmail always >delete messages 
>>>(postgres & mysql)... it delete messages in >two stages, first its mark 
>>>message as deleted and second it >delete message. Maybe I wrong?
>> 
>> 
>> I don't think you are wrong at all.  That's exactly what it is supposed to 
>> do, what I am saying is that it is not deleting the messages.  The messages 
>> never get deleted.  It doesn't matter how many times I run it they never get 
>> deleted.  Is there any log to watch what dmail-util is doing?  I tried 
>> running it with -v added onto -cpd, but to no avail.  It just says 
>> maintenance done and no errors, but nothing ever gets deleted.  Everything 
>> else is working, but this.                
> 
> The man page is clear on this, of only just barely: use the -y switch in your 
> cronjobs. Consider this a bug. 
> If you specify -p you expect the requested action to be taken. I guess Aaron 
> is still working on cleaning up 
> the yes-to-all/no-to-all issue there. But behaviour of dbmail-util seems to 
> be somewhat inconsistent at the 
> moment.
> 
> 
> 
> -- 
>    ________________________________________________________________
>    Paul Stevens                                  mailto:[EMAIL PROTECTED]
>    NET FACILITIES GROUP                     PGP: finger [EMAIL PROTECTED]
>    The Netherlands________________________________http://www.nfg.nl
> _______________________________________________
> Dbmail mailing list
> Dbmail@dbmail.org
> https://mailman.fastxs.nl/mailman/listinfo/dbmail
> _______________________________________________
> Dbmail-dev mailing list
> Dbmail-dev@dbmail.org
> http://twister.fastxs.net/mailman/listinfo/dbmail-dev
> 

-- 



Reply via email to