Maybe try
fts_autoindex_exclude = \EXPUNGED
I just tried, it doesn't work... It should not have worked, the
documentation says that names starting with a backslash are for IMAP
flags, like \Junk or \Trash.
I have both lazy_expunge and fts_autoindex activated (with fts-xapian)
Maybe try
fts_autoindex_exclude = \EXPUNGED
On 2020-08-29 14:34, Gregory Heytings wrote:
Hi list,
I have both lazy_expunge and fts_autoindex activated (with fts-xapian),
as follows:
plugin {
lazy_expunge = EXPUNGED/
}
plugin {
fts = xapian
fts_xapian = partial=2 full=20 attachments=1
Hi list,
I have both lazy_expunge and fts_autoindex activated (with fts-xapian), as
follows:
plugin {
lazy_expunge = EXPUNGED/
}
plugin {
fts = xapian
fts_xapian = partial=2 full=20 attachments=1 verbose=0
fts_autoindex = yes
fts_enforced = yes
fts_autoindex_exclude = EXPUNGED
clude = \Junk
> fts_autoindex_exclude2 = \Trash
> fts_autoindex_exclude3 = .EXPUNGED
> fts_autoindex_exclude4 = .EXPUNGED/*
>
> Aki
>
>>> Matt Bryant <mailto:m...@the-bryants.net>
>>> 23 May 2018 at 8:29 pm
>>> So digging a little deeper it seems this
u should use:
fts_autoindex_exclude = \Junk
fts_autoindex_exclude2 = \Trash
fts_autoindex_exclude3 = .EXPUNGED
fts_autoindex_exclude4 = .EXPUNGED/*
Aki
>> Matt Bryant <mailto:m...@the-bryants.net>
>> 23 May 2018 at 8:29 pm
>> So digging a little deeper it seems this m
toindex_exclude = .DUMPSTER
> quota_ruleN = .DUMPSTER:ignore
> }
> Aki
>
> On 23.05.2018 13:29, Matt Bryant wrote:
>
> Matt Bryant <mailto:m...@the-bryants.net>
> 23 May 2018 at 8:29 pm
> So digging a little deeper it seems this maybe an issue between
> fts/fts_l
EXPUNGED/*
but at least dont get internal server error ..
rgds
Matt
> Matt Bryant <mailto:m...@the-bryants.net>
> 23 May 2018 at 8:29 pm
> So digging a little deeper it seems this maybe an issue between
> fts/fts_lucene and lazy_expunge .. if I disable the fts plugin
You should probably exclude the .DUMPSTER folder from quota and FTS
plugin {
fts_autoindex_exclude = .DUMPSTER
quota_ruleN = .DUMPSTER:ignore
}
Aki
On 23.05.2018 13:29, Matt Bryant wrote:
> So digging a little deeper it seems this maybe an issue between
> fts/fts_lucene and lazy_e
So digging a little deeper it seems this maybe an issue between
fts/fts_lucene and lazy_expunge .. if I disable the fts plugin
[root@stargate dovecot.rawlog]# doveadm search -u m...@the-bryants.net
mailbox .EXPUNGED/Trash from nore...@apress.com
6156a416748c035b5c0bef794dd1 1
search works
So I decided to configure this plugin and take it for a test drive ..
configured using mdbox (main namespace is
Maildir) .. So as per Wiki have the following namespaces defined ...
location is held within db ... but basically Maildir:~/Maildir for inbox
namespace
8< ===
namespac
Hi,
I'm using autoexpunge to clean my users' Trash and Spam mailboxes.
But I'm also using lazy_expunge to keep a copy of deleted messages. Is
there any to configure lazy_expunge namespace to be autoexpunged too?
My lazy_expunge configuration is the "1 Namespace&
On 18 Sep 2017, at 21.19, Mark Moseley wrote:
>>> I just ran into the same thing myself. For me, when I added this to the
>>> "location" in the expunged namespace, it started working again:
>>>
>>> ...:LISTINDEX=expunged.list.index
>>>
>>> I can't tell you why exactly (presumably has somet
On Fri, Sep 15, 2017 at 1:42 PM, Harald Leithner
wrote:
> Am 2017-09-15 21:25, schrieb Mark Moseley:
>
>> On Wed, Sep 6, 2017 at 2:01 AM, Harald Leithner
>> wrote:
>>
>> Any idea why this doesn't setup work anymore in 2.2.32?
>>>
>>> thx
>>>
>>> Harald
>>>
>>>
>>>
>> I just ran into the same thi
Am 2017-09-15 21:25, schrieb Mark Moseley:
On Wed, Sep 6, 2017 at 2:01 AM, Harald Leithner
wrote:
Any idea why this doesn't setup work anymore in 2.2.32?
thx
Harald
I just ran into the same thing myself. For me, when I added this to the
"location" in the expunged namespace, it started w
On Wed, Sep 6, 2017 at 2:01 AM, Harald Leithner wrote:
> Any idea why this doesn't setup work anymore in 2.2.32?
>
> thx
>
> Harald
>
>
I just ran into the same thing myself. For me, when I added this to the
"location" in the expunged namespace, it started working again:
...:LISTINDEX=expunged.
:
Hi,
it seams that the lazy_expunge plugin doesn't work for me after the
upgrade...
2.2.32 cry's about
plugin { lazy_expunge_only_last_instance=no } is most likely handled
as 'yes' - remove the setting completely to disable it. If this is
intentional, ad
Ok thx for the info, anyway there are no mail copied to #EXPUNGED/
namespace.
Am 04.09.2017 um 13:40 schrieb Aki Tuomi:
Hi!
On 04.09.2017 14:38, Harald Leithner wrote:
Hi,
it seams that the lazy_expunge plugin doesn't work for me after the
upgrade...
2.2.32 cry's abo
Hi!
On 04.09.2017 14:38, Harald Leithner wrote:
> Hi,
>
> it seams that the lazy_expunge plugin doesn't work for me after the
> upgrade...
>
> 2.2.32 cry's about
>
> plugin { lazy_expunge_only_last_instance=no } is most likely handled
> as 'yes' -
Hi,
it seams that the lazy_expunge plugin doesn't work for me after the
upgrade...
2.2.32 cry's about
plugin { lazy_expunge_only_last_instance=no } is most likely handled as
'yes' - remove the setting completely to disable it. If this is
intentional, add quo
Hi all,
I stumbled upon the lazy_expunge plugin and thought that it might be useful in
some cases. It works fine if I delete mails from my inbox. But it doesn't do
anything if I deleted mails from a public folder (and for the server I am
currently working on the public folder is _the_ _
Hi list,
I have a problem I was not able to resolve with my current setup (quite basic,
the relevant part appended [1]).
When userA shares a folder with userB then userB cannot access his mailbox.
It's the same problem others have mentioned in
*) http://www.dovecot.org/list/dovecot/2014-August/09
; plugin {
> lazy_expunge = .EXPUNGED/
> lazy_expunge_ignore_namespace_not_found = TRUE
> }
Patch:
> diff -C3 -d -p -r -xMakefile -x.deps -x.libs -x.lo -x.o
> ../dovecot/src/plugins/lazy-expunge/lazy-expunge-plugin.c
> ./src/plugins/lazy-expunge/lazy-expunge-plugin.c
> **
Hello.
Before going into deep testing of 2.2.16 (clean install tbd), I would like
to know if someone is using succesfully both ACL and Lazy_expunge plugins.
Perhaps I had a config error?
Thanks,
Paolo
> Il 3 marzo 2015 alle 16.36 Paolo Cravero ha
> scritto:
>
>
> Hello list.
Hello everybody,
I have a question about lazy_expunge plugin.
I set up Dovecot with lazy_expunge plugin on a Debian Wheezy machine; I
setup also a global acl to keep .expunged namespace readonly for all
users. Imap client is Horde Webmail Edition 5.2.3
When I try to delete folders containing
Hello list.
Following two previous unanswered requests
(http://www.dovecot.org/list/dovecot/2014-August/097449.html and
http://www.dovecot.org/list/dovecot/2014-May/096261.html), I fell into the
same problem: ACL and lazy_expunge plugins do not work together.
I had lazy_expunge enabled working OK
It appears to me that this issue is related to how lazy_expunge and
last_instance work with mdbox - that is different from maildir.
With maildir, the message is moved to the expunged namespace only when the last
copy is removed (example: from trash folder).
With mdbox, first time when you
Hi,
I'm studying an issue related to mdbox and lazy_expunge. If it is active in the
imap configuration, when you delete a message (copy to new folder + expunge old
folder), a copy is also sent to the expunge namespace.
I realize that is something related to mdbo
Hello Timo, Hello Dovecot Developers, Hello everyone on the list,
I think I have some bug, because I haven't found a working configuration
till now.
I use latest dovecot 2.2.13 from the dovecot-ee repository, with acl and
the lazy_expunge plugin.
My configuration for shared folders
Am 12.08.2014 um 15:52 schrieb Philipp Faeustlin:
Hello List,
with dovecot version 2.2.13.9, I actually have a problem using
lazy_expunge and acl together.
Shared/Public Folders work fine with lazy_expunge disabled.
If lazy_expunge is enabled and userA got a shared folder form userB,
then
Hello List,
with dovecot version 2.2.13.9, I actually have a problem using
lazy_expunge and acl together.
Shared/Public Folders work fine with lazy_expunge disabled.
If lazy_expunge is enabled and userA got a shared folder form userB,
then there is the error shown in subject.
My test case
Hi,
i've had the save problem.
This is /quick/ and /dirty/ fix for this problem [gzipped patch file
attached]
After patching source, recompile lazy_expunge plugin (make -C
src/plugins/lazy_expunge all install)
AND add this to the configuration:
>
files in a
cron job. They will get recreated as soon as they are needed.
A question because you mention 2.2.13, is acl + lazy_expunge working for you
with 2.2.13???
Actually we are not using 2.2 on our main mail servers. Before I
reported this bug, I reproduced it with the current 2.1 and 2.2
Am Donnerstag, 12. Juni 2014, 11:53:26 schrieb Christoph Bußenius:
> Hi,
>
> I think I found a bug in Dovecot 2.1.17 and 2.2.13.
>
> In our setup, sometimes ACLs stop working because "dovecot-acl-list" is
> replaced by an empty file. We found that lazy_expunge is
Hi,
I think I found a bug in Dovecot 2.1.17 and 2.2.13.
In our setup, sometimes ACLs stop working because "dovecot-acl-list" is
replaced by an empty file. We found that lazy_expunge is connected to this.
To reproduce, create ACLs for "user1" in a folder. Put a mail
Am Dienstag, 20. Mai 2014, 14:00:11 schrieben Sie:
> Hi,
>
> since migration to Dovecot 2.2 I have troubles with lazy_expunge as soon
> as a user shares a folder. The user the folder is shared to cannot login
> anymore, dovecot logs Fatal: lazy_expunge: Unknown namespac
Am Dienstag, 20. Mai 2014, 14:10:01 schrieben Sie:
> Am 20.05.2014 14:00, schrieb Florian:
> > Hi,
> >
> > since migration to Dovecot 2.2 I have troubles with lazy_expunge as soon
> > as a user shares a folder. The user the folder is shared to cannot
> >
Am 20.05.2014 14:00, schrieb Florian:
> Hi,
>
> since migration to Dovecot 2.2 I have troubles with lazy_expunge as soon as
> a user shares a folder. The user the folder is shared to cannot login
> anymore, dovecot logs Fatal: lazy_expunge: Unknown namespace: '.EXPUNGED/&#x
Hi,
since migration to Dovecot 2.2 I have troubles with lazy_expunge as soon as
a user shares a folder. The user the folder is shared to cannot login
anymore, dovecot logs Fatal: lazy_expunge: Unknown namespace: '.EXPUNGED/'
- When no folder is shared lazy_expunge is working fin
ormat.
>
> To migrate mailboxes I'm using dsync as explained at
> http://wiki2.dovecot.org/Tools/Dsync. The command I'm running in the
> newer server is:
>
> sudo dsync -o mailbox_list_index=no mirror -R -u imapc:
>
> The mailbox of the user is correctly
.org/Tools/Dsync. The command I'm running in the
newer server is:
sudo dsync -o mailbox_list_index=no mirror -R -u imapc:
The mailbox of the user is correctly synced to the newer server, except
the lazy_expunge namespace, which is not synced at all.
The config in my old server
Hi,
When using both lazy_expunge and virtual mailboxes (with, for instance, a "All
Messages" virtual mailbox) as soon as a user deletes/expunges a mail in one of
its mailbox, Dovecot is saving two mails to the lazy_expunge namespace (the
one in the user mailbox and the one in t
Hi Timo, hi all,
Sep 26 12:27:55 imap(testuser): Error: lazy_expunge: Couldn't open
expunge mailbox: Character not allowed in mailbox name: '.'
try
http://wiki2.dovecot.org/Plugins/Listescape
It works now with
"mail_plugins = $mail_plugins ... lazy_expunge liste
On 26.9.2012, at 17.15, Andreas Kossack wrote:
>>> If there is an expunge activity on e.g. ".INBOX.SPAM" directory we get an
>>> error message in dovecot log:
>>> Sep 26 12:27:55 imap(testuser): Error: lazy_expunge: Couldn't open
>>> exp
Hi Robert,
If there is an expunge activity on e.g. ".INBOX.SPAM" directory we get an
error message in dovecot log:
Sep 26 12:27:55 imap(testuser): Error: lazy_expunge: Couldn't open
expunge mailbox: Character not allowed in mailbox name: '.'
sorry didnt tested
Am 26.09.2012 12:50, schrieb Andreas Kossack:
> Hi Timo, hi all,
>
> we want to use the "lazy_expunge" plugin (from dovecot 2.1.10) and had
> configured it in a test environemnt like described in
> "http://wiki2.dovecot.org/Plugins/Lazyexpunge"; (1 namespace)
Hi Timo, hi all,
we want to use the "lazy_expunge" plugin (from dovecot 2.1.10) and had
configured it in a test environemnt like described in
"http://wiki2.dovecot.org/Plugins/Lazyexpunge"; (1 namespace)
There are some subfolders from "INBOX" (like "INBOX/SP
On 11.4.2012, at 18.34, James Devine wrote:
> It looks like 3 namespace support in the lazy expunge plugin was removed in
> 2.1+ ?
Yeah, so it seems. Updated the wiki2.
On Wed, Apr 11, 2012 at 12:01 AM, Timo Sirainen wrote:
> On 10.4.2012, at 23.19, James Devine wrote:
>
> > I'm messing around with lazy expunge and I just had a couple of
> questions.
> >
> > If I delete messages or folders with messages, I see them being moved to
> > the expunge namespace, but i
On 10.4.2012, at 23.19, James Devine wrote:
> I'm messing around with lazy expunge and I just had a couple of questions.
>
> If I delete messages or folders with messages, I see them being moved to
> the expunge namespace, but if I delete an empty folder, all traces of it
> seem to disappear. Is
I'm messing around with lazy expunge and I just had a couple of questions.
If I delete messages or folders with messages, I see them being moved to
the expunge namespace, but if I delete an empty folder, all traces of it
seem to disappear. Is there a way to move empty folders to the expunge
names
On Wed, 2011-12-07 at 17:12 +0100, Jürgen Obermann wrote:
> Hello,
> I wanted to test the lazy expunge plugin together with mdbox. It seems
> to me that the folder subscriptions file in the mdbox directory was
> overwritten with only a few folder names every time I added or removed
> somethin
imap folder subscription feature off and on. Here is my setup:
# 2.0.16: /opt/local/etc/dovecot/dovecot.conf
# OS: SunOS 5.10 sun4v
mail_location = mdbox:~/mdbox
mail_plugins = mail_log notify quota lazy_expunge zlib
mdbox_rotate_interval = 1 days
mdbox_rotate_size = 16 M
namespace {
inbox = yes
the same folder without INDEX in mail_location.
Without this option it works.
Alternatively you could add INDEX path to lazy_expunge namespaces and it
would work. The important thing is that both source and destination
either have or don't have INDEX path specified, but it can't be
thout INDEX in mail_location.
> Without this option it works.
Alternatively you could add INDEX path to lazy_expunge namespaces and it
would work. The important thing is that both source and destination
either have or don't have INDEX path specified, but it can't be mixed.
(Looks like I
El 16/09/11 12:08, Timo Sirainen escribió:
With http://hg.dovecot.org/dovecot-2.0/rev/e57bd3e2ec27 it'll now log
the reason why it's not possible.
These are the logs reported with this patch:
ep 16 13:21:00 myotis30 dovecot: imap(angel.luis): Debug: Namespace
.DELETED/: Using permis
El 16/09/11 12:08, Timo Sirainen escribió:
On Fri, 2011-09-16 at 11:51 +0200, Angel L. Mateo wrote:
Hello,
I'm trying to configure lazy_expunge plugin (as a way to provide easy
backup for mails). This is my configuration (as explained in dovecot wiki):
dovecot -n output would
On Fri, 2011-09-16 at 11:51 +0200, Angel L. Mateo wrote:
> Hello,
>
> I'm trying to configure lazy_expunge plugin (as a way to provide easy
> backup for mails). This is my configuration (as explained in dovecot wiki):
dovecot -n output would have been better. W
Hello,
I'm trying to configure lazy_expunge plugin (as a way to provide easy
backup for mails). This is my configuration (as explained in dovecot wiki):
# Default namespace
namespace {
prefix =
separator = /
inbox = yes
}
# namespaces for lazy_expunge p
On 1.3.2011, at 14.36, Hajo Locke wrote:
> do some tests with lazy_expunge
> i have 2 short questions.
> is it possible to set folder for expunged messages to read-only so no user is
> possible to really delete them?
Currently there's no easy way to do this. You can of cour
Hello List,
do some tests with lazy_expunge
i have 2 short questions.
is it possible to set folder for expunged messages to read-only so no user
is possible to really delete them?
i can use mdbox for expunged-folder. but would'nt it be more functional to
use maildir to have possibili
AP flag?), and then really expunge messages with this
> > flag set. What do you think?
>
> Tricky. Deleting messages is done by many clients by moving to Trash. In
> such situation it's better to have the original messages in the original
> mailbox, otherwise everything wou
On Fri, 2010-10-08 at 13:29 +0200, Lutz Preßler wrote:
> As moving messages from one folder to another has to be done by
> clients with the IMAP command sequence COPY STORE EXPUNGE, every moved
> message is also put into the "shadow folder" of the source folder.
Yeah..
> Maybe it's possible to e
Hello,
testing the lazy_expunge plugin (with 2.0.5), I realized the
following effect, which users may not expect/understand:
As moving messages from one folder to another has to be done by
clients with the IMAP command sequence COPY STORE EXPUNGE, every moved
message is also put into the "s
Is that something we can look forward to in the near future?
I had originally intended to just hack in my own fast-and-dirty patch to
add a "purged" directory alongside cur, new, and tmp in each maildir,
and have expunged mails get mv'ed into ../pur rather than get rm'ed.
On Sun, 2010-07-25 at 15:37 -0400, Jim Salter wrote:
> How can I use Lazy_Expunge to completely PREVENT users from deleting
> email permanently?
I guess currently there is no easy way to do it. You could use
non-guessable prefixes, but that's security through obscurity..
I was fir
On 7/25/10 3:37 PM -0400 Jim Salter wrote:
How can I use Lazy_Expunge to completely PREVENT users from deleting
email permanently?
Don't list the namespace at all. Users then will not be able to get
to it.
Alternatively, create an ACL denying delete/expunge permission. Then
users can
Hi,
I've been experimenting with using Lazy_Expunge as a tool to enforce
document retention policies (by keeping users from deleting emails
forever, instead expiring them after a set time). My problem is, how do
I keep the user from deleting/expunging mails *inside the expunge folder
i
On Fri, 2010-02-19 at 17:17 +0100, Baptiste Malguy wrote:
> - But there, lazy_expunge_mail_storage_created() is called after
> quota_mail_storage_created() because names of the library files are
> lib10_quota_plugin.so and lib02_lazy_expunge_plugin.so.
Uh oh. This is completely the reverse of how
it as such before
- quota plugin sees it */
- p = t_strsplit_spaces(getenv("LAZY_EXPUNGE"), " ");
- for (i = 0; i < LAZY_NAMESPACE_COUNT && *p != NULL; i++, p++) {
- if (strcmp(storage->ns->prefix, *p) == 0) {
- storage->ns->flags |= NAMESPACE_FLAG_
Hello,
I may have missed a point, but I could have found an issue between plugins
quota and lazy_expunge.
I have noticed that the "lazy_expunge"d mails are counted as part of the
quota, while the documentation says it should not be. I have first tried to
find out if this was a con
On December 29, 2009 5:20:40 PM -0500 Timo Sirainen wrote:
That's not intentional. Even if they were in same filesystem, it
shouldn't do that. Fixed:
http://hg.dovecot.org/dovecot-1.2/rev/029c3afcfbd0
works for me
On December 29, 2009 5:20:40 PM -0500 Timo Sirainen wrote:
That's not intentional. Even if they were in same filesystem, it
shouldn't do that. Fixed:
http://hg.dovecot.org/dovecot-1.2/rev/029c3afcfbd0
looks great. i won't be able to test until after the weekend but it
sure looks like how i wa
On Mon, 2009-12-28 at 17:57 -0500, Frank Cusack wrote:
> How to disable lazy_expunge for certain mailboxes?
>
> My problem is I have a public namespace, whose mail is on a different
> filesystem than user mails. Some users are allowed to expunge on this
> shared mailbox, but
How to disable lazy_expunge for certain mailboxes?
My problem is I have a public namespace, whose mail is on a different
filesystem than user mails. Some users are allowed to expunge on this
shared mailbox, but lazy_expunge is stopping that from working since
the mail has to cross a filesystem
On Sat, 2008-11-22 at 17:59 +0300, Anton Zakatov wrote:
> Hello all!
> dovecot 1.1.6
> Use lazy_expunge plugin call core on connect.
>
> Core:
> bt full
> #0 lazy_expunge_mail_expunge (_mail=0x2ac06e9b89e8) at
> lazy-expunge-plugin.c:103
> lt = (stru
Hello all!
dovecot 1.1.6
Use lazy_expunge plugin call core on connect.
Core:
bt full
#0 lazy_expunge_mail_expunge (_mail=0x2ac06e9b89e8) at
lazy-expunge-plugin.c:103
lt = (struct lazy_expunge_transaction *) 0x2ac06e9b86e0
deststorage =
#1 0x0041cefc in imap_expunge (box
andle
> > this:
> >
> > 1) Copy the message to the other filesystem. This is slow.
> > 2) Just unlink() the message.
>
> So, if I'm right, lazy_expunge is not usable with quota=fs. Is this correct?
If your plan was that the quota would decrease when mail was ex
command?
> >
> >>A04 NO BUG: Unknown internal error
http://hg.dovecot.org/dovecot-1.0/rev/f0ea8a04225d changes this to a
proper error message.
> EXPUNGE fails only with "lazy_expunge" enabled, and you have symlinked a
> folder to a different file system:
>
&g
l
or quota plugins?
OK, we can still reproduce this error even without quota's or ACL's, but
we were able to narrow it down.
EXPUNGE fails only with "lazy_expunge" enabled, and you have symlinked a
folder to a different file system:
ln -s /mailstore/user/Maildir/.Jun
On Wed, 2007-08-29 at 09:04 -0700, Rich at Whidbey Telecom wrote:
> Hi all,
>
> Using Dovecot 1.0.3 on RedHat Enterprise 5 (kernel 2.6.18-8.1.6.el5PAE),
> and NFS storage, we symlinked a Maildir folder:
>
> /mailstore/user/Maildir/.Junk -> /junkstore/user/Junkmaildir
>
> Everything works fine,
ror
This only happens if "lazy_expunge" is enabled:
mail_plugins = quota imap_quota acl lazy_expunge
lazy_expunge = .EXPUNGED/ .EXPUNGED/ .EXPUNGED/
Lazy_expunge works great on non-symlinked folders. We tried version 1.1
alpha2, which actually crashes in this scenario.
The o
I'm seeing a crash in 1.1alpha2 when trying to expunge a folder when
"lazy_expunge" is enabled:
namespace private {
separator = .
prefix = .EXPUNGED/
location = maildir:/mailstore/%u/Expunged
hidden = yes
}
...
lazy_expunge = .EXPUNGED/ .EXPUNGED/ .EXPUNGED/
Charles Marcus wrote:
> Curious... was this copy/pasted from dovecot -n output? Or was that last
> line misspelling of 'maildur' a typo?
>
> Just one reason why copy/pasted output of dovecot -n is preferred...
It was manually retyping. I was rebuilding a new server which I did by
putting a new h
On 6/9/2007, Roger Binns ([EMAIL PROTECTED]) wrote:
namespace private {
prefix = DELETED.
seperator = .
location = maildur:~/Maildir/deleted
}
Curious... was this copy/pasted from dovecot -n output? Or was that last
line misspelling of 'maildur' a typo?
Just one reason why copy/pasted
On Sun, 2007-06-10 at 15:13 -0700, Roger Binns wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Timo Sirainen wrote:
> > On Sat, 2007-06-09 at 14:23 -0700, Roger Binns wrote:
> >> namespace private {
> >> prefix = DELETED.
> >> seperator = .
> >> location = maildur:~/Maildir/dele
the day when courier style Trash is implemented :-)
>
>> lazy_expunge = DELETED. DELETED. DELETED.
>
> Have you tried what happens if you try to expunge mails from
> DELETED.mailbox? When I wrote the code I assumed all those namespaces
> would be different.
It works fine.
On Sat, 2007-06-09 at 14:23 -0700, Roger Binns wrote:
> namespace private {
> prefix = DELETED.
> seperator = .
> location = maildur:~/Maildir/deleted
inbox = no
> }
Does that help?
> lazy_expunge = DELETED. DELETED. DELETED.
Have you tried what happens if you tr
n the
documentation:
namespace private {
prefix = INBOX.
seperator = .
inbox = yes
}
namespace private {
prefix = DELETED.
seperator = .
location = maildur:~/Maildir/deleted
}
lazy_expunge = DELETED. DELETED. DELETED.
This all works fine except for messages that were deleted from the
On April 17, 2007 11:21:14 AM +0300 Timo Sirainen <[EMAIL PROTECTED]> wrote:
On 17.4.2007, at 9.06, Frank Cusack wrote:
Your problem anyway is that hidden=yes makes the namespaces
invisible to
clients. I'll go remove them.
Sure, I realize that. But in the "Display Hierarchy" dialog,
Mulberry
On 17.4.2007, at 9.06, Frank Cusack wrote:
Your problem anyway is that hidden=yes makes the namespaces
invisible to
clients. I'll go remove them.
Sure, I realize that. But in the "Display Hierarchy" dialog,
Mulberry has
a part to enter additional hierarchies (I guess this is
namespaces)
On April 16, 2007 3:20:10 PM +0300 Timo Sirainen <[EMAIL PROTECTED]> wrote:
On Sun, 2007-04-15 at 23:40 -0700, Frank Cusack wrote:
I've configured the lazy_expunge plugin exactly like it says on the wiki.
I can't seem to configure Mulberry to find the new namespaces. Any
hints
On Sun, 2007-04-15 at 23:40 -0700, Frank Cusack wrote:
> I've configured the lazy_expunge plugin exactly like it says on the wiki.
> I can't seem to configure Mulberry to find the new namespaces. Any hints?
>
> I notice that the wiki says to use / as the separator. Mulber
I've configured the lazy_expunge plugin exactly like it says on the wiki.
I can't seem to configure Mulberry to find the new namespaces. Any hints?
I notice that the wiki says to use / as the separator. Mulberry has a
setting for this, and the default is '.'. Leaving thi
93 matches
Mail list logo
