Yes but in the dbmail-util you're not right, at least in my point.

if you use the sintax that you is going to happen:

dbmail-util -dpy (delete then purge, but it doesn't folow this order)
it is going to purge and then delete

dbmail-util -dpy
Opening connection to database...
Opening connection to authentication...
Ok. Connected.

Deleting messages with DELETE status...
Ok. [0] messages deleted.

Setting DELETE status for deleted messages...
Ok. [458] messages set for deletion.
Re-calculating used quota for all users...
Ok. Used quota updated for all users.

Maintenance done. No errors found.
lira:~# dbmail-util -dpy
Opening connection to database...
Opening connection to authentication...
Ok. Connected.

Deleting messages with DELETE status...
Ok. [458] messages deleted.

Setting DELETE status for deleted messages...
Ok. [3] messages set for deletion.
Re-calculating used quota for all users...
Ok. Used quota updated for all users.

Maintenance done. No errors found.



it's better to do separated

lira:~# dbmail-util -dy
Opening connection to database...
Opening connection to authentication...
Ok. Connected.

Setting DELETE status for deleted messages...
Ok. [1] messages set for deletion.
Re-calculating used quota for all users...
Ok. Used quota updated for all users.

Maintenance done. No errors found.
lira:~# dbmail-util -py
Opening connection to database...
Opening connection to authentication...
Ok. Connected.

Deleting messages with DELETE status...
Ok. [1] messages deleted.

Maintenance done. No errors found.
lira:~#





----- Original Message ----- From: "Casper Langemeijer" <[EMAIL PROTECTED]>
To: "DBMail mailinglist" <[email protected]>
Sent: Wednesday, August 30, 2006 3:47 PM
Subject: Re: [Dbmail] purge with dbmail-utils


okay, so I got it right the first time:

To fully delete an email you:
- delete a message in outlook
- press the purge button in outlook
- run dbmail-util -dpy to set a message for deletion.
- run dbmail-util -dpy to purge the message marked deleted.

Except that you use -dy and -py separately...
I run a daily -dpy, so that emails are not erased from the db, but kept
another day (but entirely hidden from any client).
This is suggested in the dbmail-util man page:

"-p  Purge messages with DELETE status. To purge messages currently
marked \Deleted, run with the -pd options twice. This is not
recommended; it is better to leave a grace period for old messages
before permanently wiping them from the database."

Cool, finally got it then. deleted_flag has nothing to do with status 2
(MESSAGE_STATUS_DELETE)

What is the status field used for, except for that?

MESSAGE_STATUS_NEW
MESSAGE_STATUS_SEEN
MESSAGE_STATUS_DELETE
MESSAGE_STATUS_PURGE
MESSAGE_STATUS_UNUSED
MESSAGE_STATUS_INSERT
MESSAGE_STATUS_ERROR

To me only NEW, DELETED and PURGE make sense because it enables dbmail to
keep messages out of sight for a while for recovery purposes. (even
though IMAP aparently has it's own way to do that, a 2 step deleting
process is already there, but that's cool!)

isn't MESSAGE_STATUS_SEEN redundant with seen_flag? Should these fields
always be kept in sync? They aren't on my install. The only status =
MESSAGE_STATUS_SEEN I have are the emails in my sent-mail folder.

What are UNUSED, INSERT and ERROR used for? I didn't find any records
with these values in my db.


Op 30/8/2006 schreef "Jorge Bastos" <[EMAIL PROTECTED]>:

you still need the purge in the client
purge in outlook express is the same that, for example, the "bypass trash"
in squirrelmail

then you have to do the -dy and next -py

maybe Paul will explain this better than i


----- Original Message -----
From: "Casper Langemeijer" <[EMAIL PROTECTED]>
To: "DBMail mailinglist" <[email protected]>
Sent: Wednesday, August 30, 2006 2:45 PM
Subject: Re: [Dbmail] purge with dbmail-utils


That's what I thought...

So what _should_ happen is:
- delete a message in mail client.
- run dbmail-util -dy to set a message for deletion.
- run dbmail-util -py to purge the message marked deleted.

Pressing the purge button in outlook shouldn't be necessery then, the
first unix command -dy should be the equivalant to the purge button in
outlook. Am I right here?

That doesn't work in my setup.
I found out what happened:
Deleting a message sets deleted_flag to 1 AND _should_ set status to 2.
(Outlook Express doesn't do this!!)
dbmail-util -dy sets status to 3 if status = 2
dbmail-util -py executes a DELETE FROM query

In contrast to outlook express, my webmail client sets the status to 2
correctly!

Because Outlook Express doesn't, it messes up the mailcount that is used
my webmail client. Because the message has deleted_flag set to 1 it
doesn't display the message, but the mailcount includes deleted
messages that are not status=2.

What is the story about status and *_flag??

It seems pretty redundant to me...

Grtz, Casper

Op 29/8/2006 schreef "Jorge Bastos" <[EMAIL PROTECTED]>:

No Casper,

You just have to run:

dbmail-util -dy <= to set delete status for deleted messages in the imap
client
(-d        set DELETE status for deleted messages)

and next

dbmail-util -py <= to purge them for good from the database
(-p        purge messages have the DELETE status set)


so, at least me, in my example, i run a cron script once a day at night, 3
ou 4 AM i don't know with:

#!/bin/bash
/usr/local/sbin/dbmail-util -d -y
/usr/local/sbin/dbmail-util -p -y


and that's it

Give it a try and tell me something :P



----- Original Message -----
From: "Casper Langemeijer" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, August 29, 2006 12:52 PM
Subject: Re: [Dbmail] purge with dbmail-utils



Hehehe...

I'm sorry, my example was wrong, I've always included the -y switch.
The notice is a good thing anyway :-)

Even with the -y switch, it is still not working like I expected it to
work.

I just noticed that to fully delete an email you:
- delete a message in outlook
- press the purge button in outlook
- run dbmail-util -dpy to set a message for deletion.
- run dbmail-util -dpy to purge the message marked deleted.

Is it supposed to work like this?

Ltrz, Casper


_______________________________________________
Dbmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail


_______________________________________________
Dbmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail


_______________________________________________
Dbmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail


_______________________________________________
Dbmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail


_______________________________________________
Dbmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail


Reply via email to