[Dovecot] doveadm purge output
Running "doveadm purge" with both -D and -v parms, and both -A and -u options, I don't see much in the way of output. doveadm -v purge -u username just returns with no output doveadm -v purge -A returns no output for most users - for my own mailbox it yields "20 / 21" -D returns the same, along with messages about skipping plugin modules. Is this normal? I'm thinking not - since after deleting messages in the client, emptying the trash, compacting from the client, and then performing a purge - I see no difference in mailbox files. -- Daniel
Re: [Dovecot] ldap passdb + mdbox
On 11/22/2010 10:43 AM, Timo Sirainen wrote:
On Sun, 2010-11-21 at 19:15 -0800, Daniel L. Miller wrote:
I previously had a static userdb and an ldap passdb. Everything's been
working fine, both 1.2 and 2.0 - but now I need to support the nightly
mdbox purge operation. I added the iterate params to my ldap
configuration, but (I'm guessing) that with a defined static userdb it
won't work.
You could add userdb ldap after the userdb static. I think only
iteration will use it.
I think I got it - probably by accident. Just because it's actually
working doesn't mean it's *correct* - does this look right? Do I have
redundant/obsolete parms specified?
passdb {
driver = ldap
args = /usr/local/etc/dovecot/dovecot-ldap.conf
}
userdb {
driver = prefetch
}
userdb {
driver = ldap
# symlink to dovecot-ldap.conf
args = /usr/local/etc/dovecot/dovecot-ldap-userdb.conf
}
## static userdb removed
/usr/local/etc/dovecot/dovecot-ldap.conf
hosts = ldap.amfeslan.local
dn = xxx
dnpass = xxx
auth_bind = yes
auth_bind_userdn = uid=%n,ou=users,dc=amfeslan,dc=local
ldap_version = 3
base = ou=Users, dc=amfeslan, dc=local
user_attrs = =home=/var/mail/%d/%n, \
=mail=mdbox:/var/mail/%d/%n/mdbox, \
=uid=vmail, \
=gid=mail
user_filter = (&(objectClass=inetOrgPerson)(mail=%u))
pass_attrs = mail=user, \
userPassword=password, \
=userdb_home=/var/mail/%d/%n, \
=userdb_mail=mdbox:/var/mail/%d/%n/mdbox, \
=userdb_uid=vmail, \
=userdb_gid=mail
pass_filter = (&(objectClass=inetOrgPerson)(mail=%u))
iterate_attrs = mail=user
iterate_filter = (&(objectClass=inetOrgPerson)(mail=*))
--
Daniel
Re: [Dovecot] Namespace help
You can't force clients to do anything, but you can force users of course. If you just configure Dovecot to only have prefix="" namespace, users who had their clients previously configured with namespace=INBOX. will have to clear the namespace so that they'll see their folders. I didn't understand what you meant in your original post about the post-login script. I can't think of how that would help here. On 23.11.2010, at 4.54, Joy wrote: > Thanks Charles but i want to force all users to use the dovecot's > default namespace. Is it possible ?? > > > On Mon, Nov 22, 2010 at 11:50 PM, Charles Marcus > wrote: >> On 2010-11-22 12:16 AM, Joy wrote: >>> I know that i can change the default namespace configuation of dovecot >>> to work with courier-imap namespace but not willing to do that so >>> suggest me something which can help me doing the same. >> >> Just setup both - the ones already configured to use INBOX. will >> continue to use it, and new ones won't have to specify it... >> >> http://wiki2.dovecot.org/Namespaces >> >> Scroll down to the section: Backwards Compatibility: Courier IMAP >> >> -- >> >> Best regards, >> >> Charles >> >
Re: [Dovecot] Namespace help
Thanks Charles but i want to force all users to use the dovecot's default namespace. Is it possible ?? On Mon, Nov 22, 2010 at 11:50 PM, Charles Marcus wrote: > On 2010-11-22 12:16 AM, Joy wrote: >> I know that i can change the default namespace configuation of dovecot >> to work with courier-imap namespace but not willing to do that so >> suggest me something which can help me doing the same. > > Just setup both - the ones already configured to use INBOX. will > continue to use it, and new ones won't have to specify it... > > http://wiki2.dovecot.org/Namespaces > > Scroll down to the section: Backwards Compatibility: Courier IMAP > > -- > > Best regards, > > Charles >
Re: [Dovecot] multiple IMAP ports, each announcing different capabilities
>> is it syntacticly possible to define different "imap_capability" settings
>> per each inet-listener?
>
> local 10.0.0.1 {
> imap_capability = a
> }
> local 10.0.0.2 {
> imap_capability = b
> }
Understood. How would that work for different /ports/ (i.e., 143 vs. 10143)?
Thanks again for the quick response
Clemens
Re: [Dovecot] (Dis)advantage of using lmtp?
On 22.11.2010, at 21.10, Christian Schmidt wrote: > are there any (dis)advantages in "connecting" dovecot and an MTA (in our > case: exim) using LMTP over using other methods (e.g. the exim > transports definitions that can be found in the wiki)? LMTP should have better performance, since less processes are started. LMTP doesn't have equivalent of some dovecot-lda parameters, but you probably won't need them.
Re: [Dovecot] multiple IMAP ports, each announcing different capabilities
On 22.11.2010, at 20.33, Clemens Schrimpe wrote:
> is it syntacticly possible to define different "imap_capability" settings per
> each inet-listener?
local 10.0.0.1 {
imap_capability = a
}
local 10.0.0.2 {
imap_capability = b
}
[Dovecot] (Dis)advantage of using lmtp?
Hi all, are there any (dis)advantages in "connecting" dovecot and an MTA (in our case: exim) using LMTP over using other methods (e.g. the exim transports definitions that can be found in the wiki)? Thank you very much! Gruss/Regards, Christian Schmidt
[Dovecot] multiple IMAP ports, each announcing different capabilities
Hello - is it syntacticly possible to define different "imap_capability" settings per each inet-listener? I might have to provide a service through a caching proxy sitting in front of dovecot, which might involve restrictions re: the announced imap capabilities. Any hint is highly appreciated! Greetings, Clemens
Re: [Dovecot] "list" ACL privilege ignored for LSUB command?
Timo Sirainen wrote: On Mon, 2010-11-22 at 12:22 -0700, Willie Gillespie wrote: Two things I noticed though: SUBSCRIBE-ing to the mailbox is still successful Hmm. I kind of disagree with the RFC there.. If you have 'r' rights to the mailbox, you can select it. You know that it exists then. Why couldn't you be able to subscribe to it? It even makes sense to me that if there are mailboxes that +r-l that user should be able to subscribe to them to make it easier to access them. Makes sense. And it's strange because the RFC states that SUBSCRIBE and LSUB only require rights "if the server checks for mailbox existence when performing SUBSCRIBE." (page 14 of RFC 4314) So the fact that you can SUBSCRIBE/LSUB to mailboxes without the lookup ACL isn't too far off anyway. LSUB will list mailboxes which I do not have lookup rights to This is intentional. If you have ever subscribed to a mailbox, it's in your subscriptions list and it won't go away until UNSUBSCRIBE. It doesn't matter if the mailbox is deleted or its ACLs change. But, yes, I should restrict the SUBSCRIBE more. Currently it's possible to subscribe as long as there is any rights to the mailbox. (But if there are no rights, it's not possible to subscribe, so I don't really consider this a security hole.) I should probably change it to "l" or "r". I'll anyway ask what other IMAP people think about this. I actually ran into this originally with an unusual setup: We wanted a public namespace which handled it's own subscriptions... but then we wanted to restrict the namespace to a subset of users. ACLs restricted this properly for the most part, but LSUB still listed all the mailboxes to everyone regardless of whether or not they had any rights. So that didn't work for us. =) Not a big deal, we have other ways we can make things work for our situation. If somehow LSUB filtered out mailboxes for which it had no rights to, it would fix that unique problem though. Is there a better way to provide a set of mailboxes to a subset of users with a shared subscription list (subscriptions = yes)?
Re: [Dovecot] "list" ACL privilege ignored for LSUB command?
On Mon, 2010-11-22 at 12:22 -0700, Willie Gillespie wrote: > Hello, I am new to this list, so feel free to correct me if I do > something wrong. I don't have a problem, just a question. > > The RFC which covers IMAP ACLs [1] states that one of the standard > rights is: > l - lookup (mailbox is visible to LIST/LSUB commands, SUBSCRIBE > mailbox) > > If I have a shared or public namespace and have a mailbox for which I do > not have lookup rights, Dovecot seems to do great with the LIST commands > at not showing it to me. > > Two things I noticed though: > SUBSCRIBE-ing to the mailbox is still successful Hmm. I kind of disagree with the RFC there.. If you have 'r' rights to the mailbox, you can select it. You know that it exists then. Why couldn't you be able to subscribe to it? It even makes sense to me that if there are mailboxes that +r-l that user should be able to subscribe to them to make it easier to access them. > LSUB will list mailboxes which I do not have lookup rights to This is intentional. If you have ever subscribed to a mailbox, it's in your subscriptions list and it won't go away until UNSUBSCRIBE. It doesn't matter if the mailbox is deleted or its ACLs change. But, yes, I should restrict the SUBSCRIBE more. Currently it's possible to subscribe as long as there is any rights to the mailbox. (But if there are no rights, it's not possible to subscribe, so I don't really consider this a security hole.) I should probably change it to "l" or "r". I'll anyway ask what other IMAP people think about this.
[Dovecot] "list" ACL privilege ignored for LSUB command?
Hello, I am new to this list, so feel free to correct me if I do something wrong. I don't have a problem, just a question. The RFC which covers IMAP ACLs [1] states that one of the standard rights is: l - lookup (mailbox is visible to LIST/LSUB commands, SUBSCRIBE mailbox) If I have a shared or public namespace and have a mailbox for which I do not have lookup rights, Dovecot seems to do great with the LIST commands at not showing it to me. Two things I noticed though: SUBSCRIBE-ing to the mailbox is still successful LSUB will list mailboxes which I do not have lookup rights to I imagine the first issue is easy enough to correct since it's just another check before actually subscribing. The second issue seems a little more difficult in my mind since Dovecot seems to just dump the subscription files to the client without checking whether the mailbox is allowed or not. I imagine a similar issue popped up with the LIST command and that's why the dovecot-acl-list files exist. Anyway, am I right in my observations, or am I completely overlooking something obvious? Thanks! Willie [1] http://tools.ietf.org/html/rfc4314#section-2.1 Dovecot's wiki also indicates support for this in http://wiki1.dovecot.org/ACL#ACL_files I'm using version 1.2.9 with the acl and imap_acl mail_plugins in case that matters.
Re: [Dovecot] Quota on unlimited mailboxes (More info)
Thanks Timo! That patch did the trick!
Its great that you are so quick with changes that affect your users.
Tim
On 11/22/2010 10:36 AM, Timo Sirainen wrote:
> It wasn't really a bug, more like a feature I thought would have been a
> good idea, but wasn't really. Instead of using 100M, you could use e.g.
> 10% (10% of 0 is 0 = unlimited). Or apply this patch:
> http://hg.dovecot.org/dovecot-2.0/rev/3a93121f652a
>
> On Sun, 2010-11-21 at 23:51 -0800, Tim Traver wrote:
>> ok, more info on this one. When I took out the quota_rule that added the
>> extra 100M to the trash quota, the unlimited accounts started working
>> properly again.
>>
>> So you know, I retrieve the quota values from the userdb lookups instead
>> of having a default configured in the dovecot config files, because they
>> could be all over the map depending on how each of our users is set up.
>>
>> and of course, from the dovecot -n output, you can see that I'm using
>> Maildirs and the maildirsize file for keeping track of quotas.
>>
>> Have I run into a possible bug with accounts that return 0 values for
>> the quota? does it accidentally think that the quota is actually 0 when
>> there is a quota_rule?
>>
>> Thanks,
>>
>> Tim.
>>
>>
>> On 11/21/2010 11:39 PM, Tim Traver wrote:
>>> Hi all,
>>>
>>> ok, I implemented the feature to allow 100 more MB in the trash, and it
>>> appears to work for accounts that have a standard quota, but it appears
>>> it doesn't work with an account that comes back with a 0 quota (meaning
>>> unlimited).
>>>
>>> So, I seemed to have fixed one issue, but then on accounts that have an
>>> unlimited quota, I now cannot even move items to the trash.
>>>
>>> Help!
>>>
>>> So, here's the situation. I now have some accounts that have much more
>>> than 100Mb in them with an unlimited quota level (ie 0S in the
>>> maildirsize file), and I can't simply delete a message now...
>>>
>>> here's my dovecot -n again if its needed :
>>>
>>> # 2.0.7: /usr/local/etc/dovecot/dovecot.conf
>>> # OS: FreeBSD 8.1-STABLE i386
>>> auth_username_format = %Lu
>>> auth_username_translation = %@
>>> auth_verbose = yes
>>> disable_plaintext_auth = no
>>> dotlock_use_excl = yes
>>> first_valid_uid = 100
>>> listen = *
>>> lock_method = dotlock
>>> log_path = /local/logs/dovecot.errors
>>> mail_fsync = always
>>> mail_gid = 100
>>> mail_location = maildir:%h/Maildir
>>> mail_nfs_index = yes
>>> mail_nfs_storage = yes
>>> mail_plugins = " quota"
>>> mail_uid = 100
>>> managesieve_notify_capability = mailto
>>> managesieve_sieve_capability = fileinto reject envelope
>>> encoded-character vacation subaddress comparator-i;ascii-numeric
>>> relational regex imap4flags copy include variables body enotify
>>> environment mailbox date imapflags notify
>>> mmap_disable = yes
>>> passdb {
>>> args = /bin/checkpassword_dovecot_auth
>>> driver = checkpassword
>>> }
>>> plugin {
>>> quota = maildir:User quota
>>> quota_rule = Trash:storage=+100M
>>> sieve = ~/.dovecot.sieve
>>> sieve_after = /home/mailboxes/sieve/to_spam_folder.sieve
>>> sieve_dir = ~/Maildir/sieve
>>> sieve_extensions = +notify +imapflags
>>> }
>>> protocols = imap pop3 sieve
>>> service auth {
>>> unix_listener auth-userdb {
>>> group = sn
>>> mode = 0600
>>> user = sn
>>> }
>>> }
>>> ssl_cert = >> ssl_key = >> userdb {
>>> driver = prefetch
>>> }
>>> userdb {
>>> args = /bin/checkpassword_dovecot_deliver
>>> driver = checkpassword
>>> }
>>> verbose_proctitle = yes
>>> protocol pop3 {
>>> pop3_client_workarounds = outlook-no-nuls oe-ns-eoh
>>> }
>>> protocol lda {
>>> info_log_path = /local/logs/dovecot-deliver.log
>>> log_path = /local/logs/dovecot-deliver-errors.log
>>> mail_plugins = " quota sieve"
>>> }
>>> protocol imap {
>>> mail_plugins = " quota imap_quota"
>>> }
>>> protocol sieve {
>>> managesieve_sieve_capability = comparator-i;ascii-numeric fileinto
>>> reject vacation imap4flags notify include envelope body relational regex
>>> subaddress copy
>>> }
>>>
>>>
>>> On 11/21/2010 3:11 AM, Patrick Westenberg wrote:
Miha Vrhovnik schrieb:
> "Patrick Westenberg" wrote on 20.11.2010 23:46:14:
>> You can give additional space to e.g. Trash mailbox:
>> quota_rule2 = Trash:storage=100M
>>
> Patrick you sure, that doesn't mean that the trash quota is 100M?
> Haven't tested your version, but for sure I know, that the one below
> is most definitely full quota + 100M
> Trash:storage=+100M
As far as I remember the "+" is obsolete now.
My logfile told me ;-)
And the wiki also says "additional space".
>
Re: [Dovecot] Doveadm
Tks, now it's working, i need to send every in one "write", (header+command) 2010/11/22 Timo Sirainen > On Mon, 2010-11-22 at 13:38 -0200, Alex Baule wrote: > > > Im have a situation here with the syntax for doveadm in a unix socket. > > > > My string have it: > > > > std::string ask = "d\texpunge\tu\ta...@exemplo.com.br > > \tmailbox\t\\*\tsavedbefore\t1s\n"; > > Looks like there was also a bug, fixed: > http://hg.dovecot.org/dovecot-2.0/rev/b724ef3bdc0a > > So what you need to send is: > > VERSION\tdoveadm-server\t1\t0 > d\tu...@domain\texpunge\tmailbox\t*\tsavedbefore\t1s > > There is no escaping for '*', in command line you need to do that only > because shell otherwise expands it. > >
Re: [Dovecot] Workaround for evolution?
On Fri, 2010-11-19 at 11:45 +0200, Axel Thimm wrote:
> evolution has a bug when it comes to closing and IDLE' connection:
>
> https://bugzilla.gnome.org/show_bug.cgi?id=628515
>
> evolution does not send a DONE command, and dovecot properly answers
> with an error. evolution ignores this and seems to wait on another
> response.
>
> Timo, do you think there could be a setting for tolerating missing
> DONEs? Thanks!
Well .. the attached patch should do it, but looks like a lot more code
just to fix a client..
I also tested that Cyrus at least works the same way as Dovecot.
diff -r 3a93121f652a src/imap/cmd-idle.c
--- a/src/imap/cmd-idle.c Mon Nov 22 18:35:07 2010 +
+++ b/src/imap/cmd-idle.c Mon Nov 22 18:58:15 2010 +
@@ -55,10 +55,27 @@
client_command_free(&ctx->cmd);
}
+static int idle_is_done(const unsigned char *data, size_t size)
+{
+ if (i_memcasecmp(data, "DONE", I_MIN(size, 4)) != 0)
+ return -1;
+ if (size > 4) {
+ if (data[4] == '\n')
+ return 5;
+ if (data[4] != '\r')
+ return -1;
+ if (size > 5)
+ return data[5] == '\n' ? 6 : -1;
+ }
+ return 0;
+}
+
static void idle_client_input_more(struct cmd_idle_context *ctx)
{
struct client *client = ctx->client;
- char *line;
+ const unsigned char *data;
+ size_t size;
+ int ret;
client->last_input = ioloop_time;
timeout_reset(client->to_idle);
@@ -82,13 +99,17 @@
return;
}
- while ((line = i_stream_next_line(client->input)) != NULL) {
- if (client->input_skip_line)
- client->input_skip_line = FALSE;
- else {
- idle_finish(ctx, strcasecmp(line, "DONE") == 0, TRUE);
- break;
- }
+ if (client->input_skip_line) {
+ if (i_stream_next_line(client->input) == NULL)
+ return;
+ client->input_skip_line = FALSE;
+ }
+
+ data = i_stream_get_data(client->input, &size);
+ if ((ret = idle_is_done(data, size)) != 0) {
+ idle_finish(ctx, ret > 0, TRUE);
+ if (ret > 0)
+ i_stream_skip(client->input, ret);
}
if (!client->disconnected && !client->handling_input)
client_continue_pending_input(client);
Re: [Dovecot] Managesieve + procmail
On Sat, 2010-11-20 at 17:02 +1100, Lox wrote: > dovecot: deliver(virtuser_537): file_dotlock_create(/var/mail/virtuser_537) > failed: Permission denied (euid=537(virtuser_537) egid=518(neaevents) > missing +w perm: /var/mail) (set mail_privileged_group=mail) See http://wiki.dovecot.org/MailLocation/Mbox#Locking And especially see the first NOTE.
Re: [Dovecot] ldap passdb + mdbox
On Sun, 2010-11-21 at 19:15 -0800, Daniel L. Miller wrote: > I previously had a static userdb and an ldap passdb. Everything's been > working fine, both 1.2 and 2.0 - but now I need to support the nightly > mdbox purge operation. I added the iterate params to my ldap > configuration, but (I'm guessing) that with a defined static userdb it > won't work. You could add userdb ldap after the userdb static. I think only iteration will use it.
Re: [Dovecot] Troube with GSSAPI auth
On Mon, 2010-11-22 at 15:33 +0300, asd dsa wrote: > > auth: Debug: gssapi(?,192.168.1.2): Obtaining credentials for imap@ > auth: Info: gssapi(?,192.168.1.2): While acquiring service > credentials: An invalid name was supplied Maybe you need to set auth_gssapi_hostname?
Re: [Dovecot] What is that error all about: "Timeout leak: 0x4bd230"
On Mon, 2010-11-22 at 13:45 +0100, Christian Rohmann wrote: > we are running dovecot 1.2.15 and are seeing some odd errors in our > logfiles: > > --- dovecot.log --- > 2010-11-22 12:34:56 imapserver local2.warning dovecot dovecot: > IMAP(usern...@domain.tld): Timeout leak: 0x4bd230 It's not really anything to worry about. Dovecot just notices at exit that the code didn't remove one timeout handler. It would be good to fix it though. You could see what function that address points to with gdb: gdb /usr/local/libexec/dovecot/imap x 0x4bd230
Re: [Dovecot] dovecot/imap-login TLS?
On Sun, 2010-11-21 at 20:23 +0100, Ralf Hildebrandt wrote: > # ps auxwww|egrep -i imap-login > dovenull 11879 1.4 0.9 83484 77656 ?SNov20 19:12 > dovecot/imap-login [822 connections (822 TLS)] > > What exactly is TLS in this context? > All connections from imap -> imap-login? > All clients connecting to an imap process? 822 IMAP client connections using TLS/SSL. So client -> imap-login. imap-login then proxies it to imap process in plaintext.
Re: [Dovecot] Quota on unlimited mailboxes (More info)
It wasn't really a bug, more like a feature I thought would have been a
good idea, but wasn't really. Instead of using 100M, you could use e.g.
10% (10% of 0 is 0 = unlimited). Or apply this patch:
http://hg.dovecot.org/dovecot-2.0/rev/3a93121f652a
On Sun, 2010-11-21 at 23:51 -0800, Tim Traver wrote:
> ok, more info on this one. When I took out the quota_rule that added the
> extra 100M to the trash quota, the unlimited accounts started working
> properly again.
>
> So you know, I retrieve the quota values from the userdb lookups instead
> of having a default configured in the dovecot config files, because they
> could be all over the map depending on how each of our users is set up.
>
> and of course, from the dovecot -n output, you can see that I'm using
> Maildirs and the maildirsize file for keeping track of quotas.
>
> Have I run into a possible bug with accounts that return 0 values for
> the quota? does it accidentally think that the quota is actually 0 when
> there is a quota_rule?
>
> Thanks,
>
> Tim.
>
>
> On 11/21/2010 11:39 PM, Tim Traver wrote:
> > Hi all,
> >
> > ok, I implemented the feature to allow 100 more MB in the trash, and it
> > appears to work for accounts that have a standard quota, but it appears
> > it doesn't work with an account that comes back with a 0 quota (meaning
> > unlimited).
> >
> > So, I seemed to have fixed one issue, but then on accounts that have an
> > unlimited quota, I now cannot even move items to the trash.
> >
> > Help!
> >
> > So, here's the situation. I now have some accounts that have much more
> > than 100Mb in them with an unlimited quota level (ie 0S in the
> > maildirsize file), and I can't simply delete a message now...
> >
> > here's my dovecot -n again if its needed :
> >
> > # 2.0.7: /usr/local/etc/dovecot/dovecot.conf
> > # OS: FreeBSD 8.1-STABLE i386
> > auth_username_format = %Lu
> > auth_username_translation = %@
> > auth_verbose = yes
> > disable_plaintext_auth = no
> > dotlock_use_excl = yes
> > first_valid_uid = 100
> > listen = *
> > lock_method = dotlock
> > log_path = /local/logs/dovecot.errors
> > mail_fsync = always
> > mail_gid = 100
> > mail_location = maildir:%h/Maildir
> > mail_nfs_index = yes
> > mail_nfs_storage = yes
> > mail_plugins = " quota"
> > mail_uid = 100
> > managesieve_notify_capability = mailto
> > managesieve_sieve_capability = fileinto reject envelope
> > encoded-character vacation subaddress comparator-i;ascii-numeric
> > relational regex imap4flags copy include variables body enotify
> > environment mailbox date imapflags notify
> > mmap_disable = yes
> > passdb {
> > args = /bin/checkpassword_dovecot_auth
> > driver = checkpassword
> > }
> > plugin {
> > quota = maildir:User quota
> > quota_rule = Trash:storage=+100M
> > sieve = ~/.dovecot.sieve
> > sieve_after = /home/mailboxes/sieve/to_spam_folder.sieve
> > sieve_dir = ~/Maildir/sieve
> > sieve_extensions = +notify +imapflags
> > }
> > protocols = imap pop3 sieve
> > service auth {
> > unix_listener auth-userdb {
> > group = sn
> > mode = 0600
> > user = sn
> > }
> > }
> > ssl_cert = > ssl_key = > userdb {
> > driver = prefetch
> > }
> > userdb {
> > args = /bin/checkpassword_dovecot_deliver
> > driver = checkpassword
> > }
> > verbose_proctitle = yes
> > protocol pop3 {
> > pop3_client_workarounds = outlook-no-nuls oe-ns-eoh
> > }
> > protocol lda {
> > info_log_path = /local/logs/dovecot-deliver.log
> > log_path = /local/logs/dovecot-deliver-errors.log
> > mail_plugins = " quota sieve"
> > }
> > protocol imap {
> > mail_plugins = " quota imap_quota"
> > }
> > protocol sieve {
> > managesieve_sieve_capability = comparator-i;ascii-numeric fileinto
> > reject vacation imap4flags notify include envelope body relational regex
> > subaddress copy
> > }
> >
> >
> > On 11/21/2010 3:11 AM, Patrick Westenberg wrote:
> >> Miha Vrhovnik schrieb:
> >>> "Patrick Westenberg" wrote on 20.11.2010 23:46:14:
> You can give additional space to e.g. Trash mailbox:
> quota_rule2 = Trash:storage=100M
>
> >>> Patrick you sure, that doesn't mean that the trash quota is 100M?
> >>> Haven't tested your version, but for sure I know, that the one below
> >>> is most definitely full quota + 100M
> >>> Trash:storage=+100M
> >> As far as I remember the "+" is obsolete now.
> >> My logfile told me ;-)
> >>
> >> And the wiki also says "additional space".
> >>
>
Re: [Dovecot] Doveadm
On Mon, 2010-11-22 at 13:38 -0200, Alex Baule wrote: > Im have a situation here with the syntax for doveadm in a unix socket. > > My string have it: > > std::string ask = "d\texpunge\tu\ta...@exemplo.com.br > \tmailbox\t\\*\tsavedbefore\t1s\n"; Looks like there was also a bug, fixed: http://hg.dovecot.org/dovecot-2.0/rev/b724ef3bdc0a So what you need to send is: VERSION\tdoveadm-server\t1\t0 d\tu...@domain\texpunge\tmailbox\t*\tsavedbefore\t1s There is no escaping for '*', in command line you need to do that only because shell otherwise expands it.
Re: [Dovecot] Namespace help
On 2010-11-22 12:16 AM, Joy wrote: > I know that i can change the default namespace configuation of dovecot > to work with courier-imap namespace but not willing to do that so > suggest me something which can help me doing the same. Just setup both - the ones already configured to use INBOX. will continue to use it, and new ones won't have to specify it... http://wiki2.dovecot.org/Namespaces Scroll down to the section: Backwards Compatibility: Courier IMAP -- Best regards, Charles
Re: [Dovecot] Soft Quota for moving messages
On Sun, 2010-11-21 at 12:11 +0100, Patrick Westenberg wrote: > Miha Vrhovnik schrieb: > > > > "Patrick Westenberg" wrote on 20.11.2010 23:46:14: > >> You can give additional space to e.g. Trash mailbox: > >> quota_rule2 = Trash:storage=100M > >> > > Patrick you sure, that doesn't mean that the trash quota is 100M? > > Haven't tested your version, but for sure I know, that the one below is > > most definitely full quota + 100M > > Trash:storage=+100M > > As far as I remember the "+" is obsolete now. It's the other way around, although both mean the same (for now). +100M is clearer what it means. Perhaps in distant future 100M means exactly 100 MB of quota for that mailbox, not 100 MB additional.
Re: [Dovecot] Confused about Maildir
On 11/22/2010 12:48 AM, Egbert Jan van den Bussche wrote: Op 22-11-2010 1:47, Glen Lee Edwards schreef: I'm trying to configure Dovecot 2.0.7. In the Dovecot Wiki for Maildirs it says that Maildirs are almost always located in ~/Maildir. I'm a Linux end user, not a programmer, so I may be wrong in this; but isn't the notation "~/" used for system users only to reference their home page; /home/? If that's the case, then does that mean that Maildirs can only be used with system users and not with vmail accounts? The home dir is "home" in the Dovecot context - it CAN be the same as the system user home dir - but not necessarily. The home dir is used for storing support files that are needed on a per-user basis, but aren't "pure" mail files. Things like sieve scripts. The notation of ~ is accepted shorthand for "home dir" - and since we're discussing Dovecot, it needs to be interpreted (by the reader of the docs) as "home dir" in the Dovecot context. Took me a little bit to grasp it myself. -- Daniel
Re: [Dovecot] Doveadm
Hi Timo Im have a situation here with the syntax for doveadm in a unix socket. My string have it: std::string ask = "d\texpunge\tu\ta...@exemplo.com.br \tmailbox\t\\*\tsavedbefore\t1s\n"; My Order todo is. Create socket Connect Write this strinng Read the return Close socket. finish my program. But Still i dont get messages to be expunged, if i call bu doveadm command line, works... There is some header to send before the command ? Tks 2010/11/19 Alex Baule > Tks timo! Monday i will do all corrections! > > Em 19/11/2010 22:26, "Timo Sirainen" escreveu: > > On 19.11.2010, at 22.18, Alex Baule wrote: > > > The syntax for doveadm in socket, is the same as the d... > Yes, but use tabs instead of spaces for separating parameters. > >
[Dovecot] What is that error all about: "Timeout leak: 0x4bd230"
Hey dovecot-users, we are running dovecot 1.2.15 and are seeing some odd errors in our logfiles: --- dovecot.log --- 2010-11-22 12:34:56 imapserver local2.warning dovecot dovecot: IMAP(usern...@domain.tld): Timeout leak: 0x4bd230 --- /dovecot.log --- Those errors only appear if connections are done using IMAP (via Horde's IMP Webmail). With POP3 we don't see any of those errors. We actually don't see anything in general being broken or wrong (no errors on the webmail machines, no user complaints), but these errors are constantly being logged. Where would one start to look for the cause? Thanks for your help, Regards Christian
[Dovecot] Troube with GSSAPI auth
Hi all.
I have a troube with GSSAPI (Dovecot 2.0.7) auth:
auth: Debug: client in: AUTH1 GSSAPI service=imap
lip=192.168.1.56rip=192.168.1.2 lport=143 $
auth: Debug: gssapi(?,192.168.1.2): Obtaining credentials for imap@
auth: Info: gssapi(?,192.168.1.2): While acquiring service credentials: An
invalid name was supplied
auth: Info: gssapi(?,192.168.1.2): While acquiring service credentials: Unknown
code krb5 216
Kerberos key imap/hostn...@realm installed, dovecot.conf:
auth_debug = yes
auth_krb5_keytab = /etc/krb5.keytab
auth_mechanisms = gssapi
disable_plaintext_auth = no
first_valid_uid = 1
log_path = /var/log/dovecot.log
log_timestamp = "%Y-%m-%d %H:%M:%S "
mail_gid = 89
mail_location = maildir:/var/spool/mail/%n
mail_privileged_group = mail
mail_uid = 89
service imap-login {
inet_listener imap {
address = *
port = 143
}
}
ssl = no
userdb {
driver = static
}
Any ideas?
Re: [Dovecot] Confused about Maildir
Op 22-11-2010 1:47, Glen Lee Edwards schreef: I'm trying to configure Dovecot 2.0.7. In the Dovecot Wiki for Maildirs it says that Maildirs are almost always located in ~/Maildir. I'm a Linux end user, not a programmer, so I may be wrong in this; but isn't the notation "~/" used for system users only to reference their home page; /home/? If that's the case, then does that mean that Maildirs can only be used with system users and not with vmail accounts? Glen As Patrick mentioned already (and to speak with Timo) ALL user should have a homedir. This is mostly /home/ for real system users. Virtuial users still should have a home dir. On my system that is a NFS share on /disk/mail/vmail// and the Maildir is in /disk/mail/vmail///Maildir. It could had been something colmpletely different! Egbert Jan
