headers
Channing | 1 Feb 2007 01:03
Picon
Favicon

Re: Automatic Folder Expiry (plugin?)

Troy Engel wrote:
> Greetings,
>
> I'm migrating an existing Courier IMAP installation to Dovecot 
> (1.0rc19 right now) on a new server; there's one feature I'm not sure 
> if Dovecot supports - but it might and I'm missing it, so I'll ask.
>
Checkout http://wiki.dovecot.org/Plugins.  You can search the mailing 
list archives for details on how to implement it.  Timo has documented 
it a few times on the list.

HTH,
Channing

--

-- 
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
Permalink | Reply | 3 comments |
headers
Troy Engel | 1 Feb 2007 01:13

Re: Automatic Folder Expiry (plugin?)

Channing wrote:
> Checkout http://wiki.dovecot.org/Plugins.  You can search the mailing 
> list archives for details on how to implement it.  Timo has documented 
> it a few times on the list.

I'll assume you're talking about the Trash plugin, yes? I've seen this 
and understand it, but it is quota based -- we don't use quotas, and it 
doesn't do what I want anyways. Something similar but was based on date 
(days) rather than Quota, and didn't empty that mailbox just deleted the 
 > XXX days messages.

thx,
-te

PS: is there a searchable web archives link that I missed? The standard 
Mailman archives have no searching capability.

--

-- 
Troy Engel | Systems Engineer
Fluid, Inc | http://www.fluid.com
Permalink | Reply | 2 comments |
headers
Mick T | 1 Feb 2007 01:16
Picon

Re: Automatic Folder Expiry (plugin?)

Troy Engel wrote:
> Thanks for any help/ideas - I'm not sure if we can live without this 
> feature, the amount of spam is horrendous and users never clean out 
> that folder.

I personally use a shell script to achieve this:

find /var/virtualmail/ -regex 
'.*/\.\(Trash\|Junk\)\(/.*\)?\/\(cur\|new\)/.*' -type f  -mtime +30  
-exec rm '{}'  \;

MT
Permalink | Reply | 6 comments |
headers
Troy Engel | 1 Feb 2007 01:36

Re: Automatic Folder Expiry (plugin?)

Mick T wrote:
> 
> I personally use a shell script to achieve this:
> 
> find /var/virtualmail/ -regex 
> '.*/\.\(Trash\|Junk\)\(/.*\)?\/\(cur\|new\)/.*' -type f  -mtime +30  
> -exec rm '{}'  \;

Nice. :) What's your load like doing this compared to number of users? 
I'm using a Maildir-on-NFS setup here, so there's always that to account 
for as well... I'm guessing you run this at 5am or so daily?

What about the Dovecot indexes -- will they adjust/fix/repair 
automagically when the user logs in? Same with dovecot-uidlist, it's 
self-healing?

-te

--

-- 
Troy Engel | Systems Engineer
Fluid, Inc | http://www.fluid.com
Permalink | Reply | 5 comments |
headers
Mick T | 1 Feb 2007 01:42
Picon

Re: Automatic Folder Expiry (plugin?)

Troy Engel wrote:
> Nice. :) What's your load like doing this compared to number of users? 
> I'm using a Maildir-on-NFS setup here, so there's always that to 
> account for as well... I'm guessing you run this at 5am or so daily?
I have around 5000 mailboxes on local SCSI drives, but yeah I nice -20  
the script, and run early in the morning. It doesn't take too long to run

> What about the Dovecot indexes -- will they adjust/fix/repair 
> automagically when the user logs in? Same with dovecot-uidlist, it's 
> self-healing?
I'm not the best person to answer this question, but its worked for me 
so far  :)

MT
Permalink | Reply | 4 comments |
headers
Scott Alter | 1 Feb 2007 01:44

Re: Automatic Folder Expiry (plugin?)

>> Checkout http://wiki.dovecot.org/Plugins.  You can search the mailing 
>> list archives for details on how to implement it.  Timo has documented 
>> it a few times on the list.
> 
> I'll assume you're talking about the Trash plugin, yes? I've seen this 
> and understand it, but it is quota based -- we don't use quotas, and it 
> doesn't do what I want anyways. Something similar but was based on date 
> (days) rather than Quota, and didn't empty that mailbox just deleted the 
>  > XXX days messages.

Actually, the plugin you are looking for is named Expire, but it does 
not work with the current Dovecot version.  You need the CVS head 
version, which I do not believe is recommended for use in production. 
The Trash plugin is completely separate.

The Expire plugin is currently only mentioned in the Wiki in a paragraph 
at the bottom of the Lazy Expunge plugin.  For some documentation on its 
use, see:
http://www.dovecot.org/list/dovecot/2006-June/013864.html
http://www.dovecot.org/list/dovecot/2006-November/017408.html

Scott
Permalink | Reply | 1 comment |
headers
Carl Mason --- Director Demography Lab | 1 Feb 2007 02:25
Picon

Mail Answered status flag in pine stopped working in rc19


The Flag indicating that a message has been Answered  does not work in
pine. The  status flags for New and Deleted work as always. The Answered 
flag worked properly in dovecot 0.99, but after upgrading to 1.0rc19 it 
stopped working.  Interestingly, mail that was answered before upgrading 
to rc19 still shows the proper flag.

I have tried with mbox_dirty_syncs turned on and off and I have tried 
putting "flags" in mail_cache_fields.  Obviously I am wandering in the 
dark.

Here is the setup:

pine 4.64
dovecot 1.0rc19 (installed from rpm dovecot-1.0-2_40.rc19.el4.at.i386.rpm)
Centos 4.4.2
x86

mail_location = 
mbox:~/mail/:INBOX=%h/.mailspool/%u:INDEX=/var/dovecot_indexes\/%d/%n

Inbox is NFS mounted, INDEX is on local disk

Thanks.
Permalink | Reply | 0 comments |
headers
Nate | 1 Feb 2007 02:39
Favicon

Indexing Performance Question (was tpop3d vs dovecot)

Since posting the previous thread we've setup a new system (Opteron 
2.0ghz, 1gb ram, Fedora 6) for testing.  I am hoping somebody very 
familiar with the indexing portion of dovecot can shed some light on 
this for me.

After much testing, I've come to one primary conclusion that dovecot 
is possibly unnecessarily scanning or reading files within the 
maildir directories.  Take a mailbox for instance (my test one has 
71570 emails in the cur/ folder so the process runs long enough to 
get data of what it's doing).  Follow these steps:

1.  First pop3 connection.  With no index files whatsoever, it takes 
nearly a full 10 minutes at 100% io load to scan the 71570 files 
(748M) directory and build the index files from scratch which look like this:
-rw------- 1 postfix postdrop 839K Feb  1 00:43 dovecot.index
-rw------- 1 postfix postdrop 1.9M Feb  1 00:57 dovecot.index.cache
-rw------- 1 postfix postdrop 560K Feb  1 00:43 dovecot.index.log
-rw------- 1 postfix postdrop 3.1M Feb  1 00:43 dovecot-uidlist

While it's building index i see a lot of these fly by in lsof
pop3    2023 postfix    8r   REG    8,3   14425 285947 
/var/spool/mail/test.visp.net/natetest/cur/1128488047.V902I7d42e.s3.visp.net:2,

No problem here, the disk can only go as fast as the disk can go and 
thats a *lot* of mail.  Although, one curious thing here, it appears 
that dovecot is reading or at least scanning the entire contents of 
the files within the cur/ directory to generate an index.  I assume 
this by watching my disk cache go from 100MB to 600MB.  Is it 
necessary to do that or only read the top X lines of each file, is 
that even possible?
(Continue reading)

Permalink | Reply | 27 comments |
headers
lenny | 1 Feb 2007 02:56

Re: read/unread flags broken in rc19 ?

same here. rc19 on solaris 9. sparc. read/unread/replied flags disappear,
reappear and don't work. test in tbird and squirrel.

 Hi,
>
> I'm posting to relate that on debian unstable dovecot imap 1.0rc19 I'm
> experiencing exactly the same as seen on this thread:
> http://www.dovecot.org/list/dovecot/2007-January/018937.html
> All mail dating from last sunday (only that day it seems) gets reset to
> unread after I mark them as read after a period of time. This with
> thunderbird.
> Thanks for any help on this topic :)
> --
> Stéphane Epardaud
>
>
Permalink | Reply | 10 comments |
headers
Dean Brooks | 1 Feb 2007 04:21
Favicon

Re: read/unread flags broken in rc19 ?

On Wed, Jan 31, 2007 at 08:56:31PM -0500, lenny <at> edpausa.com wrote:

> same here. rc19 on solaris 9. sparc. read/unread/replied flags disappear,
> reappear and don't work. test in tbird and squirrel.

As a temporary work-around, you can turn off lazy writes.

There is something broken in RC19 that corrupts read/unread counts
when lazy writes are enabled.

At least it worked for me.

--
Dean Brooks
dean <at> iglou.com
Permalink | Reply | 9 comments |

Gmane