Re: [Dovecot] convert old configuration file with doveconf : Unknown setting
test-mail:/tmp# /usr/local/dovecot2/bin/doveconf -n -c ./
dovecot.old.conf
# 2.0.beta4 (6891d20929ca): ./dovecot.old.conf
doveconf: Warning: Obsolete setting in ./dovecot.old.conf:26:
login_dir has been removed
doveconf: Warning: Obsolete setting in ./dovecot.old.conf:29:
login_chroot has been replaced by service { chroot }
doveconf: Fatal: Error in configuration file ./dovecot.old.conf line
29: Unknown setting: chroot
I think this is fixed nowadays? At least I can't reproduce it
anymore..
Yes it is fixed for login_chroot. Thank you.
It does not understand the old 1.1 setting "ssl_disable".
Yeah, I only added v1.2 settings. But I guess I might as well add
older
settings too. Added ssl_disable now.
login_user, login_process_size, login_process_per_connection,
login_processes_count, login_max_processes_count,
login_max_connections, mail_drop_priv_before_exec, max_mail_processes
and mail_process_size does not work too. Are they 1.1 settings ?
Regards,
--
Guillaume de Lafond
Aqua Ray SARL
Re: [Dovecot] get the messages ID after APPEND
On 04/16/2010 10:56 PM Christian Fischer wrote: > Timo Sirainen schrieb: >> v1.1+ supports UIDPLUS extension that gives you the UID immediately in >> the APPEND reply. > This sounds great! > Do you know where to get the Packages for debian lenny? http://packages.debian.org/source/lenny-backports/dovecot > And which configuration is needed afterwards? http://wiki.dovecot.org/Upgrading and file:///usr/share/doc/dovecot-common/README.Debian Regards, Pascal -- The trapper recommends today: c01dcofe.1010...@localdomain.org
Re: [Dovecot] mysql log entry
On Apr 16, 2010, at 4:09 AM, Timo Sirainen wrote: > On Tue, 2010-04-13 at 16:24 -0700, Terry Barnum wrote: >> I'm sure this is a really newbie question, but I notice in /var/log/mail.log >> that there are between 3 and 15 of the following log entries every day for >> the last five days, which is far back as my logs go--what do they mean? >> >> Apr xx hh:mm:ss mail dovecot[109]: auth-worker(default): mysql: Connected to >> localhost (postfix) >> >> Is it dovecot connecting to mysql for password or user info? If so, wouldn't >> it be more frequent? I've got 20 users with some connecting from outside >> many times per day. > > Dovecot uses persistent connections to MySQL. Above probably means that > a new auth-worker process was created and it connected to MySQL. > Auth-worker processes also die away automatically after idling for a > while. If your server had more traffic, the worker processes wouldn't > die and so new worker processes wouldn't be created either, and you > wouldn't get those messages. Thank you very much Timo. It's what I hoped was going on but as a new dovecot user it's quite reassuring to hear it from the actual, real life auth(oritative)-worker! -Terry
Re: [Dovecot] get the messages ID after APPEND
Timo Sirainen schrieb: On Fri, 2010-04-16 at 15:37 +0200, Christian Fischer wrote: Hi there! I am new to imap "Command Line" and trying to write a script doing the following on a dovecot imap server: - APPEND a message (e.g. to Drafts) - get the ID to reopen the message for reading In short: How do i get the ID back from the APPEND command or which command has to be invoked to get the uid of the newly added message? By ID do you mean message's IMAP UID? dovecot --version 1.0.15 v1.1+ supports UIDPLUS extension that gives you the UID immediately in the APPEND reply. This sounds great! Do you know where to get the Packages for debian lenny? And which configuration is needed afterwards? Thank you thank you thank you! With v1.0 you'd have to do something ugly like selecting the mailbox and searching for the message based on Message-ID: header or something..
Re: [Dovecot] Problems with masteruser
Thank you for your answer! I'll try to use it for my autoconfiguration
script after weekends)) I use AD as userdb and passdb and have a group
mailboxes, but main users for this mailboxes hasn't got any password. And I
need automatically subscribe my users to new group maiboxes. So
"full-access" masteruser is really good for me[?]
2010/4/16 Timo Sirainen
> On Fri, 2010-04-16 at 16:57 +0400, Неворотин Вадим wrote:
> > I've add
> >
> > $ENV{'MASTER_USER'} = $ENV{'USER'};
> >
> > to my postlogin-imap script, and it looks like that all is working, thank
> > you!!! I'll test it next week, but as I see ACL and base operations work,
> so
> > I think that all other works too))
> >
> > But what does it mean when I return in master_user field current user's
> > name?)))
>
> It means exactly what you do in your post-login script. It sets
> master_user to same as user.
>
> > But if I return in master_user not a current user name, but
> > something else?))) What master_user field control?))) (Sorry, I can't
> find
> > any information about this feature[?])
>
> master_user is used for the ACL checks. Currently it doesn't do anything
> else. So if you set master_user to "foo", it uses foo's ACLs when
> determining access to mailboxes. There's nothing special about master
> users after login, they're just usernames as any other usernames are.
>
>
<<349.gif>>
[Dovecot] 2.0 beta4 latest hg: segfault with virtual plugin
Hello Timo,
latest 2.0 hg version (changeset a6b050cc4a9a) segfaults when selecting
a virtual mailbox. Backtrace and dovecot -n are attached.
Please let me know if I can help with anything else to debug this.
Regards,
e-frog
Core was generated by `dovecot/imap'.
Program terminated with signal 11, Segmentation fault.
#0 0xb745d876 in array_get_modifiable_i (array=0x9de57f8, count_r=0xbfa2f314)
at ../../../src/lib/array.h:198
198 *count_r = array->buffer->used / array->element_size;
(gdb) bt full
#0 0xb745d876 in array_get_modifiable_i (array=0x9de57f8, count_r=0xbfa2f314)
at ../../../src/lib/array.h:198
198 *count_r = array->buffer->used / array->element_size;
(gdb) bt full
#0 0xb745d876 in array_get_modifiable_i (array=0x9de57f8, count_r=0xbfa2f314)
at ../../../src/lib/array.h:198
No locals.
#1 0xb745e8ad in virtual_config_free (mbox=0x9de56a8) at virtual-config.c:393
bboxes = 0x9de58a0
i = 3215127352
count = 3077046260
#2 0xb7460db8 in virtual_mailbox_free (box=0x9de56a8) at virtual-storage.c:326
mbox = 0x9de56a8
#3 0xb746c5d3 in fts_mailbox_free (box=0x9de56a8) at fts-storage.c:71
fbox = 0x9de5c88
#4 0xb76a4142 in mailbox_free (_box=0xbfa2f3f0) at mail-storage.c:637
box = 0x9de56a8
#5 0xb7609374 in cmd_getquotaroot (cmd=0x9ab8c18) at imap-quota-plugin.c:116
client = 0x9ab8810
quser = 0x9ab5820
ns = 0x9ab4550
box = 0x0
iter = 0x0
root = 0x0
mailbox = 0x9aba4d0 "virtual/ungelesen"
storage_name = 0x9aba4d8 "ungelesen"
name = 0x9ab40c0 "user"
quotaroot_reply = 0x9a92460
quota_reply = 0x9a92510
#6 0x080581c1 in client_command_input (cmd=0x9ab8c18) at imap-client.c:646
client = 0x9ab8810
command = 0x8058eb1
__FUNCTION__ = "client_command_input"
#7 0x080583f4 in client_command_input (cmd=0x9ab8c18) at imap-client.c:696
client = 0x9ab8810
command = 0x9a9ae5c
__FUNCTION__ = "client_command_input"
#8 0x080584f7 in client_handle_next_command (client=0x9ab8810,
remove_io_r=0xbfa2f4ee) at imap-client.c:737
size = 36
#9 0x08058575 in client_handle_input (client=0x9ab8810) at imap-client.c:749
_data_stack_cur_id = 3
ret = 9
remove_io = false
handled_commands = false
__FUNCTION__ = "client_handle_input"
#10 0x080586cc in client_input (client=0x9ab8810) at imap-client.c:788
cmd = 0x0
output = 0x9ab1f8c
bytes = 36
__FUNCTION__ = "client_input"
#11 0xb7656455 in io_loop_handler_run (ioloop=0x9a9a358) at ioloop-epoll.c:212
ctx = 0x9a9a478
events = 0x9a9a4b8
event = 0x9a9a4b8
list = 0x9ab45c8
io = 0x9ab45a0
tv = {tv_sec = 1799, tv_usec = 999117}
events_count = 6
t_id = 2
msecs = 180
ret = 1
i = 0
j = 0
call = true
#12 0xb7655182 in io_loop_run (ioloop=0x9a9a358) at ioloop.c:350
No locals.
#13 0xb763f254 in master_service_run (service=0x9a9a2a8, callback=0x806302a
) at master-service.c:480
No locals.
#14 0x08063277 in main (argc=1, argv=0x9a9a1c0) at main.c:357
set_roots = {0x8066380, 0x0}
service_flags = MASTER_SERVICE_FLAG_KEEP_CONFIG_OPEN
storage_service_flags = MAIL_STORAGE_SERVICE_FLAG_DISALLOW_ROOT
postlogin_socket_path = 0x0
username = 0x0
c = -1
dovecot -n
# 2.0.beta4 (a6b050cc4a9a): /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-21-generic-pae i686 Ubuntu lucid (development branch)
auth_debug = yes
auth_socket_path = /var/run/dovecot/auth-userdb
auth_username_format = %Ln
deliver_log_format = msgid=%m: from=%f: %$
dict {
dictionary = mysql:/etc/dovecot/dovecot-dict-sql.conf
}
disable_plaintext_auth = no
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
mail_debug = yes
namespace {
hidden = no
inbox = yes
list = yes
location =
prefix =
separator = /
subscriptions = yes
type = private
}
namespace {
location = virtual:/etc/dovecot/virtual:INDEX=~/.maildir/control
prefix = virtual/
separator = /
subscriptions = no
type = private
}
passdb {
args = /etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
plugin {
fts = squat
fts_squat = partial=4 full=10
quota = dict:user::proxy::dictionary
sieve = ~/.dovecot.sieve
sieve_dir = ~/.sieve
sieve_global_dir = /etc/dovecot/sieve-global/
}
postmaster_address = postmas...@ubuntu-test
protocols = imap lmtp managesieve
quota_full_tempfail = yes
sendmail_path = /usr/lib/sendmail
service auth {
unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0666
user = postfix
}
unix_listener auth-userdb {
mode = 0666
}
}
service dict {
unix_listener dict {
mode = 0666
}
}
service lmtp {
unix_listener /var/spool/postfix/dovecot-lmtp {
group = postfix
mode = 0660
user = postfix
}
}
service managesieve-login {
inet_listener sieve
Re: [Dovecot] zlib Plugin Dovecot 2.0
On 16.4.2010, at 19.15, Alex Baule wrote: > This iov is every line from the new emaill to save ? > > Or this is a email block with X bytes ? > > In my function to write email, i split the email by \n, to save it splited, > and if the iov is splited by \n, is good for me. You can't assume anything about iov. iov_count is typically 1, but can be much more. Each block's length can be from 1 byte to anything (typically less than 8kB I guess).
Re: [Dovecot] zlib Plugin Dovecot 2.0
Ok !
That's easy.
In the sendv rewrite, have this:
for (i = 0; i < iov_count; i++) {
if (o_stream_emexis_send_chunk(emexis_stream, iov[i].iov_base,
iov[i].iov_len) < 0)
return -1;
bytes += iov[i].iov_len;
}
This iov is every line from the new emaill to save ?
Or this is a email block with X bytes ?
In my function to write email, i split the email by \n, to save it splited,
and if the iov is splited by \n, is good for me.
2010/4/16 Timo Sirainen
> On Fri, 2010-04-16 at 18:34 +0300, Timo Sirainen wrote:
> > On Fri, 2010-04-16 at 09:55 -0300, Alex Baule wrote:
> >
> > > Part of reading I already migrated, only that the piece of writing (the
> new
> > > part in the plugin) I need to understand some things about the
> operation in
> > > order to migrate and redo the same functions with the separation of
> body /
> > > header
> >
> > So you also want to add support for the split operating directly during
> > saving new mails?
> >
> > I guess you can copy&paste most of the code from zlib-plugin.c and just
> > implement a new ostream. ostream-bzlib.c should give a good example. You
> > just need to implement:
>
> Oh, and the output ostream that you get from create() is the one that
> ends up in the maildir. So I guess you should be writing headers there,
> and write the body to another file some other way.
>
>
Re: [Dovecot] 2.0beta4 and latest Mercurial: Folder not SELECT-able until LIST-ed
On 16/04/10 16:25, Timo Sirainen wrote: Before RC1, sure. But I'm lagging behind in emails pretty badly. Still something like 100 messages to read and possibly reply to. Sorry; hope I didn't come across as to much of a spoiled brat. I was just getting frustrated not knowing if anyone would even look at it. Anyway, fixed: http://hg.dovecot.org/dovecot-2.0/rev/8d45d4884019 http://hg.dovecot.org/dovecot-2.0/rev/960c6936ba6a That did it; seems to be working great now. Both my simple test-config and my more complex "real" configuration. Really looking forward to continuing my testing. Thank you! Bob
Re: [Dovecot] zlib Plugin Dovecot 2.0
On Fri, 2010-04-16 at 18:34 +0300, Timo Sirainen wrote: > On Fri, 2010-04-16 at 09:55 -0300, Alex Baule wrote: > > > Part of reading I already migrated, only that the piece of writing (the new > > part in the plugin) I need to understand some things about the operation in > > order to migrate and redo the same functions with the separation of body / > > header > > So you also want to add support for the split operating directly during > saving new mails? > > I guess you can copy&paste most of the code from zlib-plugin.c and just > implement a new ostream. ostream-bzlib.c should give a good example. You > just need to implement: Oh, and the output ostream that you get from create() is the one that ends up in the maildir. So I guess you should be writing headers there, and write the body to another file some other way. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] zlib Plugin Dovecot 2.0
On Fri, 2010-04-16 at 09:55 -0300, Alex Baule wrote: > Part of reading I already migrated, only that the piece of writing (the new > part in the plugin) I need to understand some things about the operation in > order to migrate and redo the same functions with the separation of body / > header So you also want to add support for the split operating directly during saving new mails? I guess you can copy&paste most of the code from zlib-plugin.c and just implement a new ostream. ostream-bzlib.c should give a good example. You just need to implement: - sendv(): this works similar to writev() syscall. Here you need to keep read the input bytes and track when the message header ends and write to different files before/after that. - flush(): If you do any buffering, flush it here. That's about it. Much simpler than istreams! signature.asc Description: This is a digitally signed message part
Re: [Dovecot] flags, keywords in a shared mailbox setup
On Fri, 2010-04-16 at 17:06 +0200, Thomas Hummel wrote: > On Fri, Apr 16, 2010 at 03:02:47PM +0300, Timo Sirainen wrote: > > > If you don't share control directory, keywords can get more or less > > broken because different users have different mappings for maildir > > char<->keyword name. So you should share the control directory. > > > > > [Note : isn't it the same event with no shared mailboxes but with one > > > user using several clients ?] > > > > Exactly. Probably not much of a problem. > > Why not much of a problem ? Because I haven't yet heard complains about this from people? > Sure there will be only one mapping but cannot the > keyword meaning be different between different user agent of even the same > user > ? Can't we end up in a message tagged as "important" in a client being tagged > as > "personnal" in another client ? Dunno. There are two possibilities here: a) Client uses "Important" and "Personal" keywords -> no problem here. b) Client 1 uses $Label1 keyword to mean "Important", while client 2 uses $Label1 to mean "Personal". I know TB used to use $Label* keywords. I don't know if it still does. I don't know if any other client maps them to conflicting names. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] convert old configuration file with doveconf : Unknown setting
On Fri, 2010-04-02 at 23:23 +0200, de Lafond Guillaume wrote:
> test-mail:/tmp# /usr/local/dovecot2/bin/doveconf -n -c ./
> dovecot.old.conf
> # 2.0.beta4 (6891d20929ca): ./dovecot.old.conf
> doveconf: Warning: Obsolete setting in ./dovecot.old.conf:26:
> login_dir has been removed
> doveconf: Warning: Obsolete setting in ./dovecot.old.conf:29:
> login_chroot has been replaced by service { chroot }
> doveconf: Fatal: Error in configuration file ./dovecot.old.conf line
> 29: Unknown setting: chroot
I think this is fixed nowadays? At least I can't reproduce it anymore..
> It does not understand the old 1.1 setting "ssl_disable".
Yeah, I only added v1.2 settings. But I guess I might as well add older
settings too. Added ssl_disable now.
signature.asc
Description: This is a digitally signed message part
Re: [Dovecot] ACLs and public folders
On Wed, 2010-03-31 at 12:39 +0200, hyperba...@gmx.de wrote: > Dear list, > > I am using dovecot 1.0.15 on Debian Lenny. I have a public folder, I use ACL > / vfile (without public ACL), and I use maildir / vmail. Now I have two > questions: > > 1) http://wiki.dovecot.org/ACL states: "Mailboxes in public namespaces don't > have owners, so by default no-one can access them." The same document, when > explaining the meaning of the k flag in the ACLs, states: "Mailboxes can be > created (or renamed) under this mailbox (there is no recursion, so creating a > mailbox under this mailbox's child uses only the child's ACLs)" See if the docs now make more sense (I'm not entirely sure if it works like this in v1.0, but in more recent versions it should): k : create : Mailboxes can be created (or renamed) directly under this mailbox (but not necessarily under its children, see ACL Inheritance section above) ACL Inheritance Every time you create a new mailbox, it gets its ACLs from the parent mailbox. If you're creating a root-level mailbox, it uses the namespace's default ACLs. There is no actual inheritance, however: If you modify parent's ACLs, the child's ACLs stay the same. There is currently no support for ACL inheritance. The default ACLs are read from "dovecot-acl" file in the namespace's mail root directory (e.g. /var/public/Maildir). signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Mbox corruption - Inbox beginning with 'FFrom' or 'FrFrom'
On Tue, 2010-03-30 at 14:56 +0200, Henri Khou wrote: > -Dovecot.log : ar 29 11:00:06 Error: POP3(user_login): Couldn't init > INBOX: Mailbox isn't a valid mbox > -The mailbox start with either 'FFrom or 'FrFrom' I haven't seen these since v0.99. Are you using also Dovecot deliver? Is anything else than Dovecot modifying the mbox files? I don't really have any great ideas, other than some locking problem if something besides Dovecot does changes.. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] flags, keywords in a shared mailbox setup
On Fri, Apr 16, 2010 at 03:02:47PM +0300, Timo Sirainen wrote: > If you don't share control directory, keywords can get more or less > broken because different users have different mappings for maildir > char<->keyword name. So you should share the control directory. > > > [Note : isn't it the same event with no shared mailboxes but with one > > user using several clients ?] > > Exactly. Probably not much of a problem. Why not much of a problem ? Sure there will be only one mapping but cannot the keyword meaning be different between different user agent of even the same user ? Can't we end up in a message tagged as "important" in a client being tagged as "personnal" in another client ? -- Thomas Hummel | Institut Pasteur | Pôle informatique - systèmes et réseau
Re: [Dovecot] dovecot-auth question
On Mon, 2010-04-05 at 10:20 -0400, rmcg...@math.purdue.edu wrote: > passdb: > driver: pam > userdb: > driver: passwd > - > > We recently moved to dovecot and after few little configuration problem > our dovecot seems to be running without problems for the most part, but I > am seeing the following error in /var/adm/messages about ever 3 minutes. > > Apr 5 09:13:23 gauss.math.purdue.edu dovecot-auth[14359]: [ID 293258 > user.error] libsldap: Status: 49 Mesg: openConnection: simple bind failed > - Invalid credentials This message comes from pam_ldap or nss_ldap (or whatever other pam/nss plugin that tries to use LDAP). You can't do anything about them on Dovecot's side. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] dovecot 1.2.11 + virtual plugin + deliver
On Wed, 2010-04-07 at 17:56 +0200, Stef Simoens wrote: > Ideally, I would like to "hide" the virtual namespace for deliver; but > even if I put the namespace definition in the protocol imap-section, it > is still seen by deliver... This is possible in v2.0. > >> Namespace 'virtual.': virtual : Root mail directory doesn't exist: > >> /var/vmail/domain.org/username/virtual This doesn't happen in v2.0, virtual storage is created automatically. For v1.2.. you could create a separate dovecot-deliver.conf that doesn't have the virtual namespace and use deliver -c /etc/dovecot-deliver.conf. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Per-user flags for shared folders
On Thu, 2010-04-08 at 00:20 +0400, Неворотин Вадим wrote: > As I see in 2.0 there willn't be ability to control which flags should be > shared, and which should be per-user. But may be there is some plans to > implement settings to control that? > > It'll be great if you can write in dovecot-shared file which flags should be > per-user. I've been planning on doing that for a long time, but haven't gotten around to it.. > And my idea is easy to implement :) Only add here: > > 305 shared_path = t_strconcat(box->path, "/dovecot-shared", NULL); > 306 if (stat(shared_path, &st) == 0) > 307 box->private_flags_mask = MAIL_SEEN; > > in maildir-storage.c some code for reading a mask from dovecot-shared file. > Unfortunatelly I'm not a good programmer, so I can't make a patch myself((( System flags are easy, but keywords are more problematic probably. It probably should be possible to define what existing keywords are private and also if the default for them should be shared or private. Maybe in general the configuration for both flags/keywords should be "private, except .." or "shared, except .." signature.asc Description: This is a digitally signed message part
Re: [Dovecot] windows live mail + dovecot and nfs
On Fri, 2010-04-09 at 12:11 +0400, Anes Muhametov wrote: > dovecot: IMAP(u...@domain): > unlink_directory(/storage/vol1/mail/domain/user/Maildir/..DOVECOT-TRASHED) > failed: Directory not empty Yeah, unfortunately this happens with NFS. Hmm. I fixed this now in v2.0: http://hg.dovecot.org/dovecot-2.0/rev/c2f00a85a177 A similar fix could probably be written for v1.2 (maildir-storage.c: maildir_list_delete_mailbox()) but I'm trying to avoid adding any non-critical changes to v1.2. signature.asc Description: This is a digitally signed message part
[Dovecot] RETRACT: Re: 2.0beta4 doesn't respond to DONE after untagged FETCH during IDLE
Having applied Timo's patch to my "OK Still here" problem and removing mine, I am no longer having the problem with exiting IDLE after receiving an untagged FETCH. I'm not sure how the two are related, but for whatever reason, this problem isn't happening anymore. If it happens again, I'll raise the issue again. In the meantime, I have no reason to believe it a problem with 2.0beta4. Sorry for the confusion. Dan. Daniel I. Applebaum wrote: Using K-9 Mail to IDLE on a test folder "MyIncTmp". When there is a flag change on a message in the folder, which generates an untagged FETCH, K-9 Mail responds with a DONE, but dovecot does not exit IDLE state (LOG 1). However, if a new message is delivered, generating an untagged EXISTS, K-9 Mail responds the same way, with a DONE, and dovecot does exit IDLE state. (LOG 2) You can also see in LOG 1 that the "OK Still here" continues to be sent, corroborating that dovecot is still in IDLE state. I hope this information is helpful. Sincerely, Dan. LOG 1: failure to exit IDLE after untagged FETCH 04-16 08:25:48.911: VERBOSE/k9(10160): Sending IMAP command IDLE on connection conn1127686952 04-16 08:25:48.921: VERBOSE/k9(10160): conn1127686952>>> 13 IDLE 04-16 08:25:48.921: VERBOSE/k9(10160): Sent IMAP command IDLE with tag 13 for conn1127686952 04-16 08:25:49.191: VERBOSE/k9(10160): <<< #+# [idling] 04-16 08:25:49.201: VERBOSE/k9(10160): conn1127686952<<<#+# [idling] 04-16 08:25:49.201: VERBOSE/k9(10160): Got async response: #+# [idling] 04-16 08:25:49.201: DEBUG/k9(10160): Idling dantest:MyIncTmp/Thread-24/conn1127686952 04-16 08:25:49.201: DEBUG/k9(10160): Considering releasing WakeLock for Pushing 04-16 08:25:49.201: DEBUG/k9(10160): Releasing WakeLock for Pushing for thread Thread-24 04-16 08:25:54.491: VERBOSE/k9(10160): <<< #null# [16, FETCH, [FLAGS, [\Seen, \Recent]]] 04-16 08:25:54.491: VERBOSE/k9(10160): conn1127686952<<<#null# [16, FETCH, [FLAGS, [\Seen, \Recent]]] 04-16 08:25:54.491: VERBOSE/k9(10160): Got async response: #null# [16, FETCH, [FLAGS, [\Seen, \Recent]]] 04-16 08:25:54.501: DEBUG/k9(10160): Acquired WakeLock for Pushing for thread Thread-24 04-16 08:25:54.501: DEBUG/k9(10160): Got useful async untagged response: #null# [16, FETCH, [FLAGS, [\Seen, \Recent]]] for dantest:MyIncTmp/Thread-24/conn1127686952 04-16 08:25:54.501: VERBOSE/k9(10160): conn1127686952>>> DONE 04-16 08:26:54.571: DEBUG/k9(10160): Acquired WakeLock for Pushing for thread Thread-24 04-16 08:26:54.581: ERROR/k9(10160): Error 'Read timed out' 04-16 08:26:54.581: ERROR/k9(10160): java.net.SocketTimeoutException: Read timed out 04-16 08:27:00.141: VERBOSE/k9(10160): Sending IMAP command NOOP on connection conn1127686952 04-16 08:27:00.141: VERBOSE/k9(10160): conn1127686952>>> 14 NOOP 04-16 08:27:00.141: VERBOSE/k9(10160): Sent IMAP command NOOP with tag 14 for conn1127686952 04-16 08:27:26.651: VERBOSE/k9(10160): conn1127686952<<<#null# [OK, Still, here] LOG 2: successful exit from IDLE after untagged EXISTS 04-16 08:28:35.271: INFO/k9(10160): About to IDLE for dantest:MyIncTmp/Thread-24/conn1126759992 04-16 08:28:35.271: VERBOSE/k9(10160): Sending IMAP command IDLE on connection conn1126759992 04-16 08:28:35.281: VERBOSE/k9(10160): conn1126759992>>> 10 IDLE 04-16 08:28:35.281: VERBOSE/k9(10160): Sent IMAP command IDLE with tag 10 for conn1126759992 04-16 08:28:35.531: VERBOSE/k9(10160): <<< #+# [idling] 04-16 08:28:35.531: VERBOSE/k9(10160): conn1126759992<<<#+# [idling] 04-16 08:28:35.531: VERBOSE/k9(10160): Got async response: #+# [idling] 04-16 08:28:35.531: DEBUG/k9(10160): Idling dantest:MyIncTmp/Thread-24/conn1126759992 04-16 08:28:35.531: DEBUG/k9(10160): Considering releasing WakeLock for Pushing 04-16 08:28:35.531: DEBUG/k9(10160): Releasing WakeLock for Pushing for thread Thread-24 04-16 08:28:51.621: VERBOSE/k9(10160): <<< #null# [18, EXISTS] 04-16 08:28:51.621: VERBOSE/k9(10160): conn1126759992<<<#null# [18, EXISTS] 04-16 08:28:51.621: VERBOSE/k9(10160): Got async response: #null# [18, EXISTS] 04-16 08:28:51.621: DEBUG/k9(10160): Acquired WakeLock for Pushing for thread Thread-24 04-16 08:28:51.631: DEBUG/k9(10160): Got useful async untagged response: #null# [18, EXISTS] for dantest:MyIncTmp/Thread-24/conn1126759992 04-16 08:28:51.631: VERBOSE/k9(10160): conn1126759992>>> DONE 04-16 08:28:51.631: VERBOSE/k9(10160): <<< #null# [1, RECENT] 04-16 08:28:51.631: VERBOSE/k9(10160): conn1126759992<<<#null# [1, RECENT] 04-16 08:28:51.631: VERBOSE/k9(10160): Got async response: #null# [1, RECENT] 04-16 08:28:51.901: VERBOSE/k9(10160): <<< #10# [OK, Idle, completed.] 04-16 08:28:51.901: VERBOSE/k9(10160): conn1126759992<<<#10# [OK, Idle, completed.] 04-16 08:28:51.901: VERBOSE/k9(10160): Got async response: #10# [OK, Idle, completed.]
[Dovecot] RETRACT: Re: 2.0beta4 doesn't respond to DONE after untagged FETCH during IDLE
Having applied Timo's patch to my "OK Still here" problem and removing mine, I am no longer having the problem with exiting IDLE after receiving an untagged FETCH. I'm not sure how the two are related, but for whatever reason, this problem isn't happening anymore. If it happens again, I'll raise the issue again. In the meantime, I have no reason to believe it a problem with 2.0beta4. Sorry for the confusion. Dan. Daniel I. Applebaum wrote: Using K-9 Mail to IDLE on a test folder "MyIncTmp". When there is a flag change on a message in the folder, which generates an untagged FETCH, K-9 Mail responds with a DONE, but dovecot does not exit IDLE state (LOG 1). However, if a new message is delivered, generating an untagged EXISTS, K-9 Mail responds the same way, with a DONE, and dovecot does exit IDLE state. (LOG 2) You can also see in LOG 1 that the "OK Still here" continues to be sent, corroborating that dovecot is still in IDLE state. I hope this information is helpful. Sincerely, Dan. LOG 1: failure to exit IDLE after untagged FETCH 04-16 08:25:48.911: VERBOSE/k9(10160): Sending IMAP command IDLE on connection conn1127686952 04-16 08:25:48.921: VERBOSE/k9(10160): conn1127686952>>> 13 IDLE 04-16 08:25:48.921: VERBOSE/k9(10160): Sent IMAP command IDLE with tag 13 for conn1127686952 04-16 08:25:49.191: VERBOSE/k9(10160): <<< #+# [idling] 04-16 08:25:49.201: VERBOSE/k9(10160): conn1127686952<<<#+# [idling] 04-16 08:25:49.201: VERBOSE/k9(10160): Got async response: #+# [idling] 04-16 08:25:49.201: DEBUG/k9(10160): Idling dantest:MyIncTmp/Thread-24/conn1127686952 04-16 08:25:49.201: DEBUG/k9(10160): Considering releasing WakeLock for Pushing 04-16 08:25:49.201: DEBUG/k9(10160): Releasing WakeLock for Pushing for thread Thread-24 04-16 08:25:54.491: VERBOSE/k9(10160): <<< #null# [16, FETCH, [FLAGS, [\Seen, \Recent]]] 04-16 08:25:54.491: VERBOSE/k9(10160): conn1127686952<<<#null# [16, FETCH, [FLAGS, [\Seen, \Recent]]] 04-16 08:25:54.491: VERBOSE/k9(10160): Got async response: #null# [16, FETCH, [FLAGS, [\Seen, \Recent]]] 04-16 08:25:54.501: DEBUG/k9(10160): Acquired WakeLock for Pushing for thread Thread-24 04-16 08:25:54.501: DEBUG/k9(10160): Got useful async untagged response: #null# [16, FETCH, [FLAGS, [\Seen, \Recent]]] for dantest:MyIncTmp/Thread-24/conn1127686952 04-16 08:25:54.501: VERBOSE/k9(10160): conn1127686952>>> DONE 04-16 08:26:54.571: DEBUG/k9(10160): Acquired WakeLock for Pushing for thread Thread-24 04-16 08:26:54.581: ERROR/k9(10160): Error 'Read timed out' 04-16 08:26:54.581: ERROR/k9(10160): java.net.SocketTimeoutException: Read timed out 04-16 08:27:00.141: VERBOSE/k9(10160): Sending IMAP command NOOP on connection conn1127686952 04-16 08:27:00.141: VERBOSE/k9(10160): conn1127686952>>> 14 NOOP 04-16 08:27:00.141: VERBOSE/k9(10160): Sent IMAP command NOOP with tag 14 for conn1127686952 04-16 08:27:26.651: VERBOSE/k9(10160): conn1127686952<<<#null# [OK, Still, here] LOG 2: successful exit from IDLE after untagged EXISTS 04-16 08:28:35.271: INFO/k9(10160): About to IDLE for dantest:MyIncTmp/Thread-24/conn1126759992 04-16 08:28:35.271: VERBOSE/k9(10160): Sending IMAP command IDLE on connection conn1126759992 04-16 08:28:35.281: VERBOSE/k9(10160): conn1126759992>>> 10 IDLE 04-16 08:28:35.281: VERBOSE/k9(10160): Sent IMAP command IDLE with tag 10 for conn1126759992 04-16 08:28:35.531: VERBOSE/k9(10160): <<< #+# [idling] 04-16 08:28:35.531: VERBOSE/k9(10160): conn1126759992<<<#+# [idling] 04-16 08:28:35.531: VERBOSE/k9(10160): Got async response: #+# [idling] 04-16 08:28:35.531: DEBUG/k9(10160): Idling dantest:MyIncTmp/Thread-24/conn1126759992 04-16 08:28:35.531: DEBUG/k9(10160): Considering releasing WakeLock for Pushing 04-16 08:28:35.531: DEBUG/k9(10160): Releasing WakeLock for Pushing for thread Thread-24 04-16 08:28:51.621: VERBOSE/k9(10160): <<< #null# [18, EXISTS] 04-16 08:28:51.621: VERBOSE/k9(10160): conn1126759992<<<#null# [18, EXISTS] 04-16 08:28:51.621: VERBOSE/k9(10160): Got async response: #null# [18, EXISTS] 04-16 08:28:51.621: DEBUG/k9(10160): Acquired WakeLock for Pushing for thread Thread-24 04-16 08:28:51.631: DEBUG/k9(10160): Got useful async untagged response: #null# [18, EXISTS] for dantest:MyIncTmp/Thread-24/conn1126759992 04-16 08:28:51.631: VERBOSE/k9(10160): conn1126759992>>> DONE 04-16 08:28:51.631: VERBOSE/k9(10160): <<< #null# [1, RECENT] 04-16 08:28:51.631: VERBOSE/k9(10160): conn1126759992<<<#null# [1, RECENT] 04-16 08:28:51.631: VERBOSE/k9(10160): Got async response: #null# [1, RECENT] 04-16 08:28:51.901: VERBOSE/k9(10160): <<< #10# [OK, Idle, completed.] 04-16 08:28:51.901: VERBOSE/k9(10160): conn1126759992<<<#10# [OK, Idle, completed.] 04-16 08:28:51.901: VERBOSE/k9(10160): Got async response: #10# [OK, Idle, completed.]
Re: [Dovecot] Dovecot 2.0 beta 4 errors reported
On Fri, 2010-04-09 at 11:10 -0500, Ken A wrote: > 1. When I delete a parent folder that contains sub folders, I get this > error message pop up in Thunderbird 3.04: > > > "The current command did not succeed. The mail server responded: > > [CANNOT] Mailbox GUIDs are not permanent without index files." Could you get the IMAP traffic from what TB actually sends? I tried a few different ways and couldn't get this error. (It's not possible to issue IMAP DELETE command to a folder that has subfolders, that gives a different error.) Use either TB's own logs or http://wiki.dovecot.org/Debugging/Rawlog > 2. segfault reported in the system log (unrelated to the error above): > > kernel: pop3[6794]: segfault at 0028 rip 00403489 > > rsp 7fff20a24a20 error 4 This should have been logged in Dovecot's logs also. Anyway, I'd need to get gdb backtrace to be able to fix it. http://dovecot.org/bugreport.html signature.asc Description: This is a digitally signed message part
Re: [Dovecot] 2.0beta4 and latest Mercurial: Folder not SELECT-able until LIST-ed
On Fri, 2010-04-16 at 15:38 +0200, B. Johannessen wrote: > On 10 April 2010 23:09, B. Johannessen wrote: > > Have a look at the attached dialog. It shows the folder > > "shared/a...@db.org/Archive" not being SELECT-able until after it's been > > mentioned in a LIST response. > > It's been almost a week now, and still no feedback on this. I'm > obviously new to Dovecot, so I have no idea what to expect, but I > consider this to be a bug in 2.0beta4. As such I would hope someone > was interested in fixing it before RC1. Before RC1, sure. But I'm lagging behind in emails pretty badly. Still something like 100 messages to read and possibly reply to. Anyway, fixed: http://hg.dovecot.org/dovecot-2.0/rev/8d45d4884019 http://hg.dovecot.org/dovecot-2.0/rev/960c6936ba6a signature.asc Description: This is a digitally signed message part
Re: [Dovecot] 2.0.beta4 "OK Still here" not flushed?
Timo Sirainen wrote: Hmm. I'm not entirely sure when it would be broken, since I couldn't reproduce it. But I think this fixes it: http://hg.dovecot.org/dovecot-2.0/rev/ffc28ea81538 Thanks! That patch does fix the problem for me and I now get the "OK Still here" messages without my change to flush all outbound messages. Dan.
Re: [Dovecot] get the messages ID after APPEND
On Fri, 2010-04-16 at 15:37 +0200, Christian Fischer wrote: > Hi there! > > I am new to imap "Command Line" and trying to write a script doing the > following on a dovecot imap server: > - APPEND a message (e.g. to Drafts) > - get the ID to reopen the message for reading > > In short: How do i get the ID back from the APPEND command or which > command has to be invoked to get the uid of the newly added message? By ID do you mean message's IMAP UID? > dovecot --version > 1.0.15 v1.1+ supports UIDPLUS extension that gives you the UID immediately in the APPEND reply. With v1.0 you'd have to do something ugly like selecting the mailbox and searching for the message based on Message-ID: header or something.. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Problems with masteruser
On Fri, 2010-04-16 at 16:57 +0400, Неворотин Вадим wrote:
> I've add
>
> $ENV{'MASTER_USER'} = $ENV{'USER'};
>
> to my postlogin-imap script, and it looks like that all is working, thank
> you!!! I'll test it next week, but as I see ACL and base operations work, so
> I think that all other works too))
>
> But what does it mean when I return in master_user field current user's
> name?)))
It means exactly what you do in your post-login script. It sets
master_user to same as user.
> But if I return in master_user not a current user name, but
> something else?))) What master_user field control?))) (Sorry, I can't find
> any information about this feature[?])
master_user is used for the ACL checks. Currently it doesn't do anything
else. So if you set master_user to "foo", it uses foo's ACLs when
determining access to mailboxes. There's nothing special about master
users after login, they're just usernames as any other usernames are.
signature.asc
Description: This is a digitally signed message part
[Dovecot] 2.0beta4 doesn't respond to DONE after untagged FETCH during IDLE
Using K-9 Mail to IDLE on a test folder "MyIncTmp". When there is a flag change on a message in the folder, which generates an untagged FETCH, K-9 Mail responds with a DONE, but dovecot does not exit IDLE state (LOG 1). However, if a new message is delivered, generating an untagged EXISTS, K-9 Mail responds the same way, with a DONE, and dovecot does exit IDLE state. (LOG 2) You can also see in LOG 1 that the "OK Still here" continues to be sent, corroborating that dovecot is still in IDLE state. I hope this information is helpful. Sincerely, Dan. LOG 1: failure to exit IDLE after untagged FETCH 04-16 08:25:48.911: VERBOSE/k9(10160): Sending IMAP command IDLE on connection conn1127686952 04-16 08:25:48.921: VERBOSE/k9(10160): conn1127686952>>> 13 IDLE 04-16 08:25:48.921: VERBOSE/k9(10160): Sent IMAP command IDLE with tag 13 for conn1127686952 04-16 08:25:49.191: VERBOSE/k9(10160): <<< #+# [idling] 04-16 08:25:49.201: VERBOSE/k9(10160): conn1127686952<<<#+# [idling] 04-16 08:25:49.201: VERBOSE/k9(10160): Got async response: #+# [idling] 04-16 08:25:49.201: DEBUG/k9(10160): Idling dantest:MyIncTmp/Thread-24/conn1127686952 04-16 08:25:49.201: DEBUG/k9(10160): Considering releasing WakeLock for Pushing 04-16 08:25:49.201: DEBUG/k9(10160): Releasing WakeLock for Pushing for thread Thread-24 04-16 08:25:54.491: VERBOSE/k9(10160): <<< #null# [16, FETCH, [FLAGS, [\Seen, \Recent]]] 04-16 08:25:54.491: VERBOSE/k9(10160): conn1127686952<<<#null# [16, FETCH, [FLAGS, [\Seen, \Recent]]] 04-16 08:25:54.491: VERBOSE/k9(10160): Got async response: #null# [16, FETCH, [FLAGS, [\Seen, \Recent]]] 04-16 08:25:54.501: DEBUG/k9(10160): Acquired WakeLock for Pushing for thread Thread-24 04-16 08:25:54.501: DEBUG/k9(10160): Got useful async untagged response: #null# [16, FETCH, [FLAGS, [\Seen, \Recent]]] for dantest:MyIncTmp/Thread-24/conn1127686952 04-16 08:25:54.501: VERBOSE/k9(10160): conn1127686952>>> DONE 04-16 08:26:54.571: DEBUG/k9(10160): Acquired WakeLock for Pushing for thread Thread-24 04-16 08:26:54.581: ERROR/k9(10160): Error 'Read timed out' 04-16 08:26:54.581: ERROR/k9(10160): java.net.SocketTimeoutException: Read timed out 04-16 08:27:00.141: VERBOSE/k9(10160): Sending IMAP command NOOP on connection conn1127686952 04-16 08:27:00.141: VERBOSE/k9(10160): conn1127686952>>> 14 NOOP 04-16 08:27:00.141: VERBOSE/k9(10160): Sent IMAP command NOOP with tag 14 for conn1127686952 04-16 08:27:26.651: VERBOSE/k9(10160): conn1127686952<<<#null# [OK, Still, here] LOG 2: successful exit from IDLE after untagged EXISTS 04-16 08:28:35.271: INFO/k9(10160): About to IDLE for dantest:MyIncTmp/Thread-24/conn1126759992 04-16 08:28:35.271: VERBOSE/k9(10160): Sending IMAP command IDLE on connection conn1126759992 04-16 08:28:35.281: VERBOSE/k9(10160): conn1126759992>>> 10 IDLE 04-16 08:28:35.281: VERBOSE/k9(10160): Sent IMAP command IDLE with tag 10 for conn1126759992 04-16 08:28:35.531: VERBOSE/k9(10160): <<< #+# [idling] 04-16 08:28:35.531: VERBOSE/k9(10160): conn1126759992<<<#+# [idling] 04-16 08:28:35.531: VERBOSE/k9(10160): Got async response: #+# [idling] 04-16 08:28:35.531: DEBUG/k9(10160): Idling dantest:MyIncTmp/Thread-24/conn1126759992 04-16 08:28:35.531: DEBUG/k9(10160): Considering releasing WakeLock for Pushing 04-16 08:28:35.531: DEBUG/k9(10160): Releasing WakeLock for Pushing for thread Thread-24 04-16 08:28:51.621: VERBOSE/k9(10160): <<< #null# [18, EXISTS] 04-16 08:28:51.621: VERBOSE/k9(10160): conn1126759992<<<#null# [18, EXISTS] 04-16 08:28:51.621: VERBOSE/k9(10160): Got async response: #null# [18, EXISTS] 04-16 08:28:51.621: DEBUG/k9(10160): Acquired WakeLock for Pushing for thread Thread-24 04-16 08:28:51.631: DEBUG/k9(10160): Got useful async untagged response: #null# [18, EXISTS] for dantest:MyIncTmp/Thread-24/conn1126759992 04-16 08:28:51.631: VERBOSE/k9(10160): conn1126759992>>> DONE 04-16 08:28:51.631: VERBOSE/k9(10160): <<< #null# [1, RECENT] 04-16 08:28:51.631: VERBOSE/k9(10160): conn1126759992<<<#null# [1, RECENT] 04-16 08:28:51.631: VERBOSE/k9(10160): Got async response: #null# [1, RECENT] 04-16 08:28:51.901: VERBOSE/k9(10160): <<< #10# [OK, Idle, completed.] 04-16 08:28:51.901: VERBOSE/k9(10160): conn1126759992<<<#10# [OK, Idle, completed.] 04-16 08:28:51.901: VERBOSE/k9(10160): Got async response: #10# [OK, Idle, completed.]
Re: [Dovecot] 2.0beta4 and latest Mercurial: Folder not SELECT-able until LIST-ed
On 10 April 2010 23:09, B. Johannessen wrote: > Have a look at the attached dialog. It shows the folder > "shared/a...@db.org/Archive" not being SELECT-able until after it's been > mentioned in a LIST response. It's been almost a week now, and still no feedback on this. I'm obviously new to Dovecot, so I have no idea what to expect, but I consider this to be a bug in 2.0beta4. As such I would hope someone was interested in fixing it before RC1. I'm hoping to be able to deploy 2.0 (as a replacement for Courier) for ~15.000 users closely following it's release, but need to have a working server for testing. As this (suspected) bug affects one of the premier reasons we want to switch (sensible shared and public folders), I'm no longer able to continue testing... I'm trying real hard not to sound like an ungrateful git, but I would really appreciate some feedback on this... -- Regards, B. Johannessen
[Dovecot] get the messages ID after APPEND
Hi there! I am new to imap "Command Line" and trying to write a script doing the following on a dovecot imap server: - APPEND a message (e.g. to Drafts) - get the ID to reopen the message for reading In short: How do i get the ID back from the APPEND command or which command has to be invoked to get the uid of the newly added message? Thank you! Christian - dovecot --version 1.0.15 dovecot -n # 1.0.15: /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S ssl_cert_file: /etc/postfix/tls/mail.cert ssl_key_file: /etc/postfix/tls/mail.key disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_privileged_group: mail mail_location: maildir:%h/.EMAIL auth default: mechanisms: plain login passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix
Re: [Dovecot] Problems with masteruser
I've add
$ENV{'MASTER_USER'} = $ENV{'USER'};
to my postlogin-imap script, and it looks like that all is working, thank
you!!! I'll test it next week, but as I see ACL and base operations work, so
I think that all other works too))
But what does it mean when I return in master_user field current user's
name?))) As I understand it increase masteruser's rights to full control of
user's mailbox. But if I return in master_user not a current user name, but
something else?))) What master_user field control?))) (Sorry, I can't find
any information about this feature[?])
2010/4/16 Timo Sirainen
> On Fri, 2010-04-16 at 15:30 +0400, Неворотин Вадим wrote:
> > Hmm[?] For what can I use masterusers, if I even can't read with
> masteruser
> > user's mails from INBOX? And where can I read about masterusers in that
> way.
> > I really can't understand for what there is masterusers if they can't do
> > anything)))
>
> The feature was originally implemented for a voicemail feature. There
> would be a "voicemail" master user that would have permission to write
> new mails to users' "voicemail" mailbox, but nothing else.
>
> You could have a similar "spam" master user that only has access to
> users' "Spam" mailbox (for training spam bayesian or whatever).
>
> Anyway, did you try my suggestion on how to make it work the way you
> wanted? If it doesn't work yet, I can change the code to make it work:
>
> > You could try if having your userdb return
> > master_user=%u field would make it work the way you want.
>
>
<<362.gif>>
Re: [Dovecot] zlib Plugin Dovecot 2.0
Thanks Timo, I have another question about the plugin. Part of reading I already migrated, only that the piece of writing (the new part in the plugin) I need to understand some things about the operation in order to migrate and redo the same functions with the separation of body / header Can you explain to me ? Tks again ! 2010/4/16 Timo Sirainen > On Fri, 2010-04-09 at 11:42 -0300, Alex Baule wrote: > > > I developed a plugin based on the zlib plugin, but want to port it to > > dovecot 2.0. > > > > There are some differences in the 2.0 plugin, which I did not quite > > understand how it works for me to readjust it in my plugin. > > I don't think you need to do (almost?) any changes. v2.0's zlib plugin > is very different from v1.x, but that's because I'm using zlib library > in a different way. Not because of some istream changes. > >
Re: [Dovecot] 2.0.beta4 "OK Still here" not flushed?
On Wed, 2010-04-14 at 22:12 -0500, Daniel I. Applebaum wrote: > Hopefully, > there is a way to specifically flush just the "OK Still here" messages > appropriately. Hmm. I'm not entirely sure when it would be broken, since I couldn't reproduce it. But I think this fixes it: http://hg.dovecot.org/dovecot-2.0/rev/ffc28ea81538 signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Problems with masteruser
On Fri, 2010-04-16 at 15:30 +0400, Неворотин Вадим wrote: > Hmm[?] For what can I use masterusers, if I even can't read with masteruser > user's mails from INBOX? And where can I read about masterusers in that way. > I really can't understand for what there is masterusers if they can't do > anything))) The feature was originally implemented for a voicemail feature. There would be a "voicemail" master user that would have permission to write new mails to users' "voicemail" mailbox, but nothing else. You could have a similar "spam" master user that only has access to users' "Spam" mailbox (for training spam bayesian or whatever). Anyway, did you try my suggestion on how to make it work the way you wanted? If it doesn't work yet, I can change the code to make it work: > You could try if having your userdb return > master_user=%u field would make it work the way you want. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Dovecot 2.0b4 configuration issue, listen config option?
On Fri, 2010-04-16 at 13:43 +0200, Andreas Schulze wrote:
> Am 16.04.2010 13:19 schrieb Timo Sirainen:
> > > or allow ssl only in a protocol section
> >
> > I think you can do that already?
> >
> > ssl = no
> > protocol imap {
> > ssl = yes
> > ..
> > }
> yes, this makes dovecot starting wihout errors,
> but *without* ssl listenport too :-(
Oh. Hmm. That's a bit difficult to change. How about this then:
ssl = yes
protocol pop3 {
ssl = no
}
service pop3 {
inet_listener pop3s {
port = 0
}
}
signature.asc
Description: This is a digitally signed message part
Re: [Dovecot] flags, keywords in a shared mailbox setup
On Thu, 2010-04-15 at 17:48 +0200, Thomas Hummel wrote: > More specifically : > > . is, in 1.2x, the method for having private flags of a shared mailbox still > to have the 'dovecot-shared' file (in order to store flags in indexes) ? dovecot-shared currently only controls \Seen flag. All other flags are always shared. > . how can shared keywords in a shared mailbox even work ? If they're shared > (how ? by pointing CONTROL to the same user-independent location ?), > keywords > known by a client (user1) won't necessary be known or have the same > meaning for > another client (user2), will they ? If you don't share control directory, keywords can get more or less broken because different users have different mappings for maildir char<->keyword name. So you should share the control directory. > [Note : isn't it the same event with no shared mailboxes but with one > user using several clients ?] Exactly. Probably not much of a problem. > But, if they're private, they have to be stored outside the filename : > how can we do that ? Currently you can't. Although changing the code to support it probably wouldn't be too difficult. I need some kind of a design plan for this some day. :) signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Dovecot 2.0b4 configuration issue, listen config option?
Am 16.04.2010 13:43 schrieb Andreas Schulze:
> yes, this makes dovecot starting wihout errors,
> but *without* ssl listenport too :-(
protocols = imap pop3
service imap-login {
inet_listener imap {
address = imap01.t6-isa.de
}
inet_listener imaps {
address = imap01.t6-isa.de
}
}
service pop3-login {
inet_listener pop3 {
address = pop01.t6-isa.de
}
inet_listener pop3s {
address = pop01.t6-isa.de
}
}
protocol imap {
# suggested by Timo
ssl = yes
ssl_cert =
Re: [Dovecot] Thunderbird subscription bug ?
On Fri, 2010-04-02 at 18:06 +0200, Thomas Hummel wrote:
> 25 list "" "#shared/#shared/%"
> 26 list "" "#shared/#shared/%/%"
..
> * NAMESPACE (("" "/")) (("#shared/" "/")) NIL
Those extra #shared/#shared/% LISTs are wrong/unnecessary. You could try
setting hidden=yes to the shared namespace so it won't show up in
NAMESPACE reply.
> * LIST (\Noselect \HasChildren) "/" "#shared"
> 19 OK List completed.
> * LIST (\Noselect \HasChildren) "/" "#shared/doveimap"
> 20 OK List completed.
> 21 OK Lsub completed.
> * LIST (\Noselect \HasChildren) "/" "#shared/doveimap"
> 22 OK List completed.
> * LIST (\Noselect \HasChildren) "/" "#shared/doveimap/folder"
> 23 OK List completed.
These replies are correct.
> So TB doesn't seem to ask for what's behind #shared/doveimap/folder although
> the server tells him it has children...
That's probably intentional. It probably doesn't want to show subfolders
until you've actually clicked the tree-open-button before the folder.
> As a matter of fact, in the subscribe dialog box in th UI, I see
>
> #shared
> doveimap
> folder but with no check box alongside
That's also intentional because it's \Noselect. What's potentially wrong
is if you don't have the [+] button on the left of "folder" so that you
could see its subfolders.
signature.asc
Description: This is a digitally signed message part
Re: [Dovecot] Shared mailboxes unix permissions
On Wed, 2010-03-31 at 19:40 +0200, Thomas Hummel wrote: > Everything gets created with the permission I was expecting, except : > > -rw--- 1 doveimap doveshared 8 Mar 31 18:47 > /courriel/meta/doveimap/dovecot-uidvalidity > -rw--- 1 doveimap doveshared 0 Mar 31 18:44 > /courriel/meta/doveimap/dovecot-uidvalidity.4bb37be4 This has been fixed in v2.0. But they're not all that important, so you can probably just ignore them. > -rw--- 1 doveimap doveshared 0 Mar 31 18:44 > /var/dovecot-test/dict/shared-mailboxes This file is created only once. You can change its permissions and they're preserved afterward. But yeah, its initial permissions should be taken from parent directory. Fixed in v2.0: http://hg.dovecot.org/dovecot-2.0/rev/b3947e64546a signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Dovecot 2.0b4 configuration issue, listen config option?
Am 16.04.2010 13:19 schrieb Timo Sirainen:
> > or allow ssl only in a protocol section
>
> I think you can do that already?
>
> ssl = no
> protocol imap {
> ssl = yes
> ..
> }
yes, this makes dovecot starting wihout errors,
but *without* ssl listenport too :-(
--
Andreas Schulze
Internetdienste | P532
DATEV eG
90329 Nürnberg | Telefon +49 911 319-0 | Telefax +49 911 319-3196
E-Mail info @datev.de | Internet www.datev.de
Sitz: 90429 Nürnberg, Paumgartnerstr. 6-14 | Registergericht Nürnberg, GenReg
Nr.70
Vorstand
Prof. Dieter Kempf (Vorsitzender)
Dipl.-Kfm. Wolfgang Stegmann (stellvertretender Vorsitzender)
Dipl.-Kfm. Michael Leistenschneider
Jörg Rabe v. Pappenheim
Dipl.-Vw. Eckhard Schwarzer
Vorsitzender des Aufsichtsrates: Reinhard Verholen
Re: [Dovecot] Problems with masteruser
Hmm[?] For what can I use masterusers, if I even can't read with masteruser user's mails from INBOX? And where can I read about masterusers in that way. I really can't understand for what there is masterusers if they can't do anything))) 2010/4/16 Timo Sirainen > On Fri, 2010-04-09 at 20:53 +0400, Неворотин Вадим wrote: > > Well, the main idea of master users is to able to log in as normal user > with > > master password. So IMAP client shoudn't know at all that it work with > > masteruser password. And IMAP process must be exactly the same. If you > can > > find difference between login*master and login - then there is a bug in > > master users implementation. I see a big difference > > It's not a bug, it's an intentional feature. What you're requesting is a > different feature. You could try if having your userdb return > master_user=%u field would make it work the way you want. > > <<338.gif>>
Re: [Dovecot] "try MD5-CRYPT scheme instead"?
* Timo Sirainen : > On Fri, 2010-04-16 at 10:30 +0200, Ralf Hildebrandt wrote: > > I'm getting a lot of entries like this in my log: > > > > Apr 16 10:10:18 postamt dovecot: auth(default): > > shadow(doxxxris,141.42.206.38): CRYPT(wrongpassword) != > > '$1$qSe71xxx$09MoMqNyll.wPLCdSaFuA0', try MD5-CRYPT scheme instead > > http://hg.dovecot.org/dovecot-1.2/rev/e4c096fae5ac gets rid of them. > (The "shadow .. CRYPT(..) != '..'" line still gets logged, just not the > "try .. instead".) OK. I was trying to reproduce this and couldn't. But thanks for changing the error message anyway (as usual!) -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: [Dovecot] zlib Plugin Dovecot 2.0
On Fri, 2010-04-09 at 11:42 -0300, Alex Baule wrote: > I developed a plugin based on the zlib plugin, but want to port it to > dovecot 2.0. > > There are some differences in the 2.0 plugin, which I did not quite > understand how it works for me to readjust it in my plugin. I don't think you need to do (almost?) any changes. v2.0's zlib plugin is very different from v1.x, but that's because I'm using zlib library in a different way. Not because of some istream changes. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Problems with masteruser
On Fri, 2010-04-09 at 20:53 +0400, Неворотин Вадим wrote: > Well, the main idea of master users is to able to log in as normal user with > master password. So IMAP client shoudn't know at all that it work with > masteruser password. And IMAP process must be exactly the same. If you can > find difference between login*master and login - then there is a bug in > master users implementation. I see a big difference It's not a bug, it's an intentional feature. What you're requesting is a different feature. You could try if having your userdb return master_user=%u field would make it work the way you want. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Error in SimpleVirtualInstall
On Sat, 2010-04-10 at 15:52 +0200, Simone Neugierig wrote:
> test:{PLAIN}pass
> bill:{PLAIN}secret
> t...@example.com:{PLAIN}hello123
> d...@example.com:{PLAIN}world234
> j...@elsewhere.org:{PLAIN}whee
> j...@elsewhere.org:{PLAIN}mypass
>
> but the syntax used for test and bill didnt work here, i had to add
> the virtual domain to get it working. or else deliver wasnt able to
> recognize the user (unknown user).
If you use "test" and "bill" in passwd file, you need to log in as
"test" and "bill" username (without any @domain). And you must not have
set auth_default_realm. The example above is intended to show that it's
possible to have users with or without domain names.
> Also i would like to suggest to explicitely say that
> protocol lda {
> }
>
> is needed even if it contains nothing.
It's not.. Or shouldn't be.
> or better change the example so that it contains the postmaster address.
That's true. Added.
signature.asc
Description: This is a digitally signed message part
Re: [Dovecot] mysql log entry
On Tue, 2010-04-13 at 16:24 -0700, Terry Barnum wrote: > I'm sure this is a really newbie question, but I notice in /var/log/mail.log > that there are between 3 and 15 of the following log entries every day for > the last five days, which is far back as my logs go--what do they mean? > > Apr xx hh:mm:ss mail dovecot[109]: auth-worker(default): mysql: Connected to > localhost (postfix) > > Is it dovecot connecting to mysql for password or user info? If so, wouldn't > it be more frequent? I've got 20 users with some connecting from outside many > times per day. Dovecot uses persistent connections to MySQL. Above probably means that a new auth-worker process was created and it connected to MySQL. Auth-worker processes also die away automatically after idling for a while. If your server had more traffic, the worker processes wouldn't die and so new worker processes wouldn't be created either, and you wouldn't get those messages. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] dovecot2: authcache statistics
Am 16.04.2010 13:05 schrieb Timo Sirainen: > > Is it possible that dovecot logs statistics on regular intervals ? > Make a cronjob that sends the SIGUSR2 on regular intervals? :) would be nice if dovecot master process would do this ;-) -- Andreas Schulze Internetdienste | P532 DATEV eG 90329 Nürnberg | Telefon +49 911 319-0 | Telefax +49 911 319-3196 E-Mail info @datev.de | Internet www.datev.de Sitz: 90429 Nürnberg, Paumgartnerstr. 6-14 | Registergericht Nürnberg, GenReg Nr.70 Vorstand Prof. Dieter Kempf (Vorsitzender) Dipl.-Kfm. Wolfgang Stegmann (stellvertretender Vorsitzender) Dipl.-Kfm. Michael Leistenschneider Jörg Rabe v. Pappenheim Dipl.-Vw. Eckhard Schwarzer Vorsitzender des Aufsichtsrates: Reinhard Verholen
Re: [Dovecot] "try MD5-CRYPT scheme instead"?
On Fri, 2010-04-16 at 10:30 +0200, Ralf Hildebrandt wrote: > I'm getting a lot of entries like this in my log: > > Apr 16 10:10:18 postamt dovecot: auth(default): > shadow(doxxxris,141.42.206.38): CRYPT(wrongpassword) != > '$1$qSe71xxx$09MoMqNyll.wPLCdSaFuA0', try MD5-CRYPT scheme instead http://hg.dovecot.org/dovecot-1.2/rev/e4c096fae5ac gets rid of them. (The "shadow .. CRYPT(..) != '..'" line still gets logged, just not the "try .. instead".) signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Dovecot 2.0b4 configuration issue, listen config option?
On Thu, 2010-04-15 at 07:46 +0200, Andreas Schulze wrote:
> ssl = yes
> ssl_cert = ssl_key = protocol imap {
> ssl_cert =ssl_key = }
>
> Imagine the config if managesieve should use yet an oher cert...
> This is confusing while reading the config later.
>
> my wish:
> use one cert/key pair for all services
I don't really understand what you're asking. You can use the same
cert/key to all services, but of course that requires that either all of
them use the same hostname or you use alt names. Or are you thinking
something like:
ssl_cert = or allow ssl only in a protocol section
I think you can do that already?
ssl = no
protocol imap {
ssl = yes
..
}
signature.asc
Description: This is a digitally signed message part
Re: [Dovecot] dovecot2: authcache statistics
On Fri, 2010-04-16 at 09:51 +0200, Andreas Schulze wrote: > setting auth_cache_size to nonzero enables caching of authentication data. > The cache hitrate may be logged by sending SIGUSR2 to dovecot/auth process. > Is it possible that dovecot logs statistics on regular intervals ? > ( like http://www.postfix.org/postconf.5.html#anvil_status_update_time ) Make a cronjob that sends the SIGUSR2 on regular intervals? :) signature.asc Description: This is a digitally signed message part
[Dovecot] "try MD5-CRYPT scheme instead"?
I'm getting a lot of entries like this in my log: Apr 16 10:10:18 postamt dovecot: auth(default): shadow(doxxxris,141.42.206.38): CRYPT(wrongpassword) != '$1$qSe71xxx$09MoMqNyll.wPLCdSaFuA0', try MD5-CRYPT scheme instead It seems that changing the password via SquirrelMail (poppasswd) breaks the authentication scheme somewhat. Users cannot log in anymore. -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: [Dovecot] manipulating mails
Thanks a lot, Steffen. Sounds like some work. Catch your free beer(s) if you touch Frankfurt. Sven Steffen Kaiser schrieb: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 15 Apr 2010, Sven wrote: i want to move mails from some specific imap folder to some other folder on the filesystem to precess them further more. but maybe i want to copy the mail and then set the seen flag. i think both can be done via imap, but maybe i want to add some tag/keyword, text or attachment from some processing skript with processing informations thinks getting more complex ... In IMAP storage messages are immutable, per spec. That means: You cannot transparently change the content of a message, e.g. add/remove headers or (parts of) the body, once the message has been delivered. If you do it the IMAP way, each manipulated messages (I mean the content, not the keywords/tags/flags) becomes a new message, hence, the clients might download it again. If you keep that in mind, you can successfully manipulate the content of messages in Maildir by: 1) rename message somewhere else, 2) manipulate it 3) rename it to maildir_mailbox/tmp 4) adjust access permissions 5) rename it to maildir_mailbox/new or ../cur making sure the file gets a new filename stem (part of filename before the colon) than it had originally. If a new file pops up in cur/new, Dovecot assumes a non-Dovecot delivery and re-indexes the file next time the user accesses the mailbox. To manipulate the flags I would use PREAUTH. You can savly remove files from a Maildir. Regards, - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBS8gbtL+Vh58GPL/cAQL5TQf+KOzTvYLPiTLSitOhd4IOawjb9B9+U/Fe jHi4XpgGk4ubs22CQ7yUD6v2ozzRMjqIKDPFvvBvJfRW84G1zB3aj2p6lE0QN7XP ekWhuVkUHSbKwPCcxXvZAXTBv8/nPD45+mz32JyqHVZA/2QG0FDayM6d4mUg29AR EdGxNXd/1SzO12xHAqe+kG3EzhUTY5p3U1/Bfg8YlXutUyIQ+qK9rrEPsuLfWDOy ZdnKCohvR13lq92MJiXosuN56kC8kGsSHj/YVhsdIhNpDP61YE2uuRqJtxd8Ynpu 3VnLFZHIg1dv4GDFgaZP6ul3e7YShVZUgAyZLxCiglL6rBqk3KKnFw== =mG0U -END PGP SIGNATURE-
Re: [Dovecot] manipulating mails
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 15 Apr 2010, Sven wrote: i want to move mails from some specific imap folder to some other folder on the filesystem to precess them further more. but maybe i want to copy the mail and then set the seen flag. i think both can be done via imap, but maybe i want to add some tag/keyword, text or attachment from some processing skript with processing informations thinks getting more complex ... In IMAP storage messages are immutable, per spec. That means: You cannot transparently change the content of a message, e.g. add/remove headers or (parts of) the body, once the message has been delivered. If you do it the IMAP way, each manipulated messages (I mean the content, not the keywords/tags/flags) becomes a new message, hence, the clients might download it again. If you keep that in mind, you can successfully manipulate the content of messages in Maildir by: 1) rename message somewhere else, 2) manipulate it 3) rename it to maildir_mailbox/tmp 4) adjust access permissions 5) rename it to maildir_mailbox/new or ../cur making sure the file gets a new filename stem (part of filename before the colon) than it had originally. If a new file pops up in cur/new, Dovecot assumes a non-Dovecot delivery and re-indexes the file next time the user accesses the mailbox. To manipulate the flags I would use PREAUTH. You can savly remove files from a Maildir. Regards, - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBS8gbtL+Vh58GPL/cAQL5TQf+KOzTvYLPiTLSitOhd4IOawjb9B9+U/Fe jHi4XpgGk4ubs22CQ7yUD6v2ozzRMjqIKDPFvvBvJfRW84G1zB3aj2p6lE0QN7XP ekWhuVkUHSbKwPCcxXvZAXTBv8/nPD45+mz32JyqHVZA/2QG0FDayM6d4mUg29AR EdGxNXd/1SzO12xHAqe+kG3EzhUTY5p3U1/Bfg8YlXutUyIQ+qK9rrEPsuLfWDOy ZdnKCohvR13lq92MJiXosuN56kC8kGsSHj/YVhsdIhNpDP61YE2uuRqJtxd8Ynpu 3VnLFZHIg1dv4GDFgaZP6ul3e7YShVZUgAyZLxCiglL6rBqk3KKnFw== =mG0U -END PGP SIGNATURE-
[Dovecot] Small dovecot.org downtime
dovecot.org gets more memory in a few hours, so it'll be down for a while (maybe max 30 mins?)
[Dovecot] dovecot2: authcache statistics
Hello, setting auth_cache_size to nonzero enables caching of authentication data. The cache hitrate may be logged by sending SIGUSR2 to dovecot/auth process. Is it possible that dovecot logs statistics on regular intervals ? ( like http://www.postfix.org/postconf.5.html#anvil_status_update_time ) Andreas -- Andreas Schulze Internetdienste | P532 DATEV eG 90329 Nürnberg | Telefon +49 911 319-0 | Telefax +49 911 319-3196 E-Mail info @datev.de | Internet www.datev.de Sitz: 90429 Nürnberg, Paumgartnerstr. 6-14 | Registergericht Nürnberg, GenReg Nr.70 Vorstand Prof. Dieter Kempf (Vorsitzender) Dipl.-Kfm. Wolfgang Stegmann (stellvertretender Vorsitzender) Dipl.-Kfm. Michael Leistenschneider Jörg Rabe v. Pappenheim Dipl.-Vw. Eckhard Schwarzer Vorsitzender des Aufsichtsrates: Reinhard Verholen
