remove entry from deliver.db

Andrew Morgan morgan at
Fri Apr 13 14:25:08 EDT 2007

On Fri, 13 Apr 2007, Derek T. Yarnell wrote:

> On Thu, 2007-04-12 at 13:40 -0400, Greg A. Woods wrote:
>> At Thu, 12 Apr 2007 11:32:49 -0400, Derek T. Yarnell wrote:
>> Subject: remove entry from deliver.db
>>> Is there a way to remove an entry from the deliver.db?  Like a
>>> spam/virus solution quarantined a message, we delivered it into the
>>> cyrus mailbox and user deleted it.  We tried to re-deliver the message
>>> and it now gets caught in the duplicate checker.
>> That sounds like a design flaw in your spam/virus system.
>> The delivery of a message to Cyrus should only ever have to happen once.
>> The "quarantine" area could just be another folder.
> Well I am not really here to debate the design of the spam/virus system
> because it is coming from another department. But it may be a design
> flaw not to allow a management of of the deliver.db so my initial
> question stands, is there a way to delete entries out of the deliver.db
> before they are just purged in the normal (3day in redhat) cycle?

There are no tools shipping with Cyrus to modify deliver.db.  You'd have 
to write your own, unless someone else in Cyrus land has already done so.

>> If the user accidentally deletes a message then restoring it from
>> backups should be no different for a message in the "Junk" folder
>> vs. one in any other folder, no?
> Depends, you need to know more of the circumstances and in this case it
> happened minutes after it was delivered so yeah, backups won't help.

The delayed expunge feature of Cyrus 2.3 could help in this case.

>> Alternately the quarantine system could simply send a separate unique
>> notification message to the user and then only deliver the quarantined
>> message if the user requests it somehow.  I really don't like that idea
>> for many reasons though.
> The message is untouched by the quarantine, so to munge a new message id
> would be the wrong way to approach this IMHO.

I'm still a little confused why you are trying to deliver the same message 
a second time...

If you expect to be delivering duplicate messages on a regular basis, then 
you should probably turn of duplicate delivery suppression in Cyrus.  :)


More information about the Info-cyrus mailing list