Re: [Dovecot] dovecot 1.1.2 assertion
Here go the files
Timo Sirainen wrote:
On Jul 25, 2008, at 2:36 AM, Nuno Lopes wrote:
I've upgraded to last version of dovecot and am now getting the
following assertions:
Jul 25 00:00:34 bld3 dovecot: Panic: IMAP([EMAIL PROTECTED]): file
index-sort-string.c: line 542 (index_sort_add_ids_range): assertion
failed: (left_idx == 0 && right_idx == rightmost_idx)
Can you reproduce this? Could you send that mailbox's dovecot.index
and dovecot.index.log files to me? They don't contain any sensitive
information.
Both bugs are fully reproducible by trying to order a given field.
In the mailbox corresponding to the indexes I send you it happens every
time I try to order by subject.
Would you like me to send you files corresponding to the other bug or
even more examples of this one if I can find them?
Thanks,
--
Nuno Lopes
dovecot.index
Description: Binary data
+ëG
[EMAIL PROTECTED] [EMAIL PROTECTED]@ JHJHJHJH Ê 0 Ë [EMAIL PROTECTED]@ ^HJH^HJH [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED] ¨ª
[EMAIL PROTECTED]@[EMAIL PROTECTED]@ +ëG ø Y Z x a È
b c l d À r u l% v °* w ô/ x D5 y : { à? | E } \J ~ °O U XZ °_ üd Lj o øt Lz ô P ¬ L § ø¤ ¨ <ª © ¯ ª ä´ È· ® л ¯ ,Á ° à ± tÈ ² ÌÍ ³ Ó ´ lØ · ØÛ º á ¼ ¸ã ½ é ¾ `î À ¸ó Á H÷  ìù à ý Ä à Å 4 Æ Ç h
È ´ É Ê L [EMAIL PROTECTED]@[EMAIL PROTECTED]" [EMAIL PROTECTED]@[EMAIL PROTECTED] [EMAIL PROTECTED]<[EMAIL PROTECTED] [EMAIL PROTECTED]@ ÚHJHÚHØH [EMAIL PROTECTED]@ ÚHJHÚHüH [EMAIL PROTECTED]@ HJHHüH [EMAIL PROTECTED]@ HJHHÃH [EMAIL PROTECTED] [EMAIL PROTECTED]@ ÐHJHÐHÃH [EMAIL PROTECTED]@ ÐHJHÐH,H [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED],H [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Í w y { Í w y { [EMAIL PROTECTED]
[EMAIL PROTECTED] [EMAIL PROTECTED]
[EMAIL PROTECTED] [EMAIL PROTECTED]
[EMAIL PROTECTED] [EMAIL PROTECTED]@ HJHHH [EMAIL PROTECTED]@ ¯HJH¯HH [EMAIL PROTECTED]@ ¯HJH¯HÍH [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
[EMAIL PROTECTED] [EMAIL PROTECTED](* [EMAIL PROTECTED]
[EMAIL PROTECTED] 0 Í [EMAIL PROTECTED] [EMAIL PROTECTED]|6Hi6H|6Hi6H [EMAIL PROTECTED]@[EMAIL PROTECTED] [EMAIL PROTECTED]@ 6Hi6H6H6H [EMAIL PROTECTED]@ 6Hi6H6H6H [EMAIL PROTECTED]@ 7Hi6H7H 7H [EMAIL PROTECTED] [EMAIL PROTECTED]@ $ $ 7Hi6H7H 7HùHé [EMAIL PROTECTED]@ +ëG Í [EMAIL PROTECTED], T $ pfHÍ Á ¹ [EMAIL PROTECTED] [EMAIL PROTECTED]
[EMAIL PROTECTED]@ +ëG Î [EMAIL PROTECTED](0 [EMAIL PROTECTED]@[EMAIL PROTECTED]
[EMAIL PROTECTED],[EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]@ $ $ ü`Hü`Hý`Hý`Hý`Hû 0 Ð [EMAIL PROTECTED]@ $ $ ü`Hü`Hý`Hý`H aH+ [EMAIL PROTECTED]@ +ëG Ð [EMAIL PROTECTED] [EMAIL PROTECTED]@ $ $ 4aHaH4aHý`H aH+ [EMAIL PROTECTED] [EMAIL PROTECTED] 0 Ñ [EMAIL PROTECTED]@ $ $ aHaHaHaH aH+ [EMAIL PROTECTED]@ $ $ aHaHaHaHssH` [EMAIL PROTECTED]@ +ëG Ñ [EMAIL PROTECTED]< [EMAIL PROTECTED]@ $ $ aHaHaHaHêwH [EMAIL PROTECTED]@ +ëG Ò [EMAIL PROTECTED] [EMAIL PROTECTED]@ $ $ yHyHaHaHêwH 0 Ó [EMAIL PROTECTED]@ $ $ yHyH yHyHêwH [EMAIL
[Dovecot] Dovecot 1.1.2, SIGABRT on copy mail
Hi folks, with the brandnew release Dovecot 1.1.2, the daemon killed itself with signal 6 (SIGABRT) when trying to save a mail from the INBOX to another folder. The mail client is PINE 4.64. After reconnecting to the IMAP server, the mail was actually copied to the destination folder, but the original mail was still in the INBOX and not flagged as "deleted". This is the panic: Jul 25 02:13:25 linux dovecot: Panic: IMAP(user2): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists(&ibox->recent_flags, uid)) Jul 25 02:13:25 linux dovecot: IMAP(user2): Raw backtrace: imap [0x80cf8e0] -> imap [0x80cf93a] -> imap [0x80cf26c] -> imap [0x809d11a] -> imap(index_mailbox_set_recent_seq+0x3e) [0x809d15e] -> imap(mbox_sync+0x105d) [0x80823fd] -> imap [0x807a454] -> imap(index_transaction_commit+0x4e) [0x809ddfe] -> imap(cmd_copy+0x35f) [0x805b26f] -> imap [0x805fd7c] -> imap [0x805fe25] -> imap [0x80605e5] -> imap(client_input+0x5e) [0x80607fe] -> imap(io_loop_handler_run+0x100) [0x80d7230] -> imap(io_loop_run+0x28) [0x80d63c8] -> imap(main+0x4a1) [0x8068321] -> /lib/libc.so.6(__libc_start_main+0xe0) [0x149390] -> imap [0x805a101] Jul 25 02:13:25 linux dovecot: child 7954 (imap) killed with signal 6 Thus, the daemon died somewhere between successfully saving a copy of the mail from INBOX to the destination folder and flagging it to be deleted in the INBOX. Just a couple of minutes later, Dovecot died again. Wanted to save a message from INBOX to another folder. But this time, the message wasn't written to the destination folder. As before, the original mail in the INBOX didn't change any flags. Jul 25 02:22:07 linux dovecot: Panic: IMAP(user2): file message-parser.c: line 770 (message_parser_parse_next_block): assertion failed: (ctx->input->eof || ctx->input->closed || ctx->input->stream_errno != 0 || ctx->broken) Jul 25 02:22:07 linux dovecot: IMAP(user2): Raw backtrace: imap [0x80cf8e0] -> imap [0x80cf93a] -> imap [0x80cf26c] -> imap(message_parser_parse_body+0) [0x80c8ba0] -> imap(message_parser_parse_body+0x1e) [0x80c8bbe] -> imap [0x8095120] -> imap [0x809528c] -> imap(index_mail_get_special+0x3a7) [0x8095757] -> imap [0x8061b94] -> imap(imap_fetch+0x148) [0x80620f8] -> imap(cmd_fetch+0x28e) [0x805bcae] -> imap [0x805fd7c] -> imap [0x805fe25] -> imap [0x80605e5] -> imap(client_input+0x5e) [0x80607fe] -> imap(io_loop_handler_run+0x100) [0x80d7230] -> imap(io_loop_run+0x28) [0x80d63c8] -> imap(main+0x4a1) [0x8068321] -> /lib/libc.so.6(__libc_start_main+0xe0) [0x149390] -> imap [0x805a101] Jul 25 02:22:07 linux dovecot: child 17931 (imap) killed with signal 6 The error cannot be reproduced with these messages. They can be saved/copied now without problems back and forth. I've tried to send more mail and reproduce the problem, but no success. Works perfectly fine. Dovecot 1.1.2 is running on Fedora 8 Linux 32 Bit with all patches and custom OpenSSL 0.9.8h. [ output of "dovecot -n" ] # 1.1.2: /usr/local/dovecot/etc/dovecot.conf ssl_cert_file: /usr/local/dovecot/etc/dovecot.crt ssl_key_file: /usr/local/dovecot/etc/dovecot.key login_dir: /usr/local/dovecot/var/run/dovecot/login login_executable: /usr/local/dovecot/libexec/dovecot/imap-login mail_location: mbox:~/Mail:INBOX=/var/spool/mail/%u auth default: mechanisms: plain login digest-md5 cram-md5 passdb: driver: passwd-file args: /usr/local/dovecot/etc/dovecot.passwd userdb: driver: passwd-file args: /usr/local/dovecot/etc/dovecot.passwd The problem was reported by a user who continued to work with his mail folders. I was only a few seconds too late to grab a copy of the INBOX and index files. Greetings, Andreas
[Dovecot] dovecot 1.1.2 dbox file_dotlock_open() failed with file
Hi Timo, i have failures like with deleting a folder in the log dovecot: Jul 25 02:12:14 Error: IMAP(.com): file_dotlock_open() failed with file /usr/local/virtual/.../[EMAIL PROTECTED]//dbox-Mails/dovecot.index.log: No such file or directory with short tests i cant see any real problem folder can be created and deleted with thunderbird ( but only with tb-extra-mailbox-sep enabled ) its not a new log entry to dovecot 1.1.2 but this is first time i noticed , by near expection of the log after update, and of course i missed it by playing so much with configs -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria
Re: [Dovecot] dovecot 1.1.2 assertion
On Jul 25, 2008, at 2:36 AM, Nuno Lopes wrote: I've upgraded to last version of dovecot and am now getting the following assertions: Jul 25 00:00:34 bld3 dovecot: Panic: IMAP([EMAIL PROTECTED]): file index-sort-string.c: line 542 (index_sort_add_ids_range): assertion failed: (left_idx == 0 && right_idx == rightmost_idx) Can you reproduce this? Could you send that mailbox's dovecot.index and dovecot.index.log files to me? They don't contain any sensitive information. PGP.sig Description: This is a digitally signed message part
[Dovecot] dovecot 1.1.2 assertion
Hi, I've upgraded to last version of dovecot and am now getting the following assertions: Jul 25 00:00:34 bld3 dovecot: Panic: IMAP([EMAIL PROTECTED]): file index-sort-string.c: line 542 (index_sort_add_ids_range): assertion failed: (left_idx == 0 && right_idx == rightmost_idx) Jul 25 00:00:34 bld3 dovecot: IMAP([EMAIL PROTECTED]): Raw backtrace: imap [0x555d30f0] -> imap [0x555d3157] -> imap [0x555d27d8] -> imap(index_sort_list_finish_string+0xe8e) [0x555a01de] -> imap(index_storage_search_next_nonblock+0x432) [0x5559caa2] -> imap(mailbox_search_next+0x21) [0x555a4051] -> imap(imap_sort+0xdc) [0x55577d3c] -> imap(cmd_sort+0x33d) [0x55570e1d] -> imap(cmd_uid+0x54) [0x55571894] -> imap [0x555722ac] -> imap [0x55572362] -> imap [0x55572b7f] -> imap(client_input+0x62) [0x55572da2] -> imap(io_loop_handler_run+0xf8) [0x555da0c8] -> imap(io_loop_run+0x1d) [0x555d918d] -> imap(main+0x462) [0x5557a552] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x2ae31494c154] -> imap [0x5556c859] in another instance: Jul 25 00:08:48 bld4 dovecot: Panic: IMAP([EMAIL PROTECTED]): file index-sort-string.c: line 607 (index_sort_add_ids_range): assertion failed: (skip > 0) Jul 25 00:08:48 bld4 dovecot: IMAP([EMAIL PROTECTED]): Raw backtrace: imap [0x555d30f0] -> imap [0x555d3157] -> imap [0x555d27d8] -> imap(index_sort_list_finish_string+0xedc) [0x555a022c] -> imap(index_storage_search_next_nonblock+0x432) [0x5559caa2] -> imap(mailbox_search_next+0x21) [0x555a4051] -> imap(imap_sort+0xdc) [0x55577d3c] -> imap(cmd_sort+0x33d) [0x55570e1d] -> imap(cmd_uid+0x54) [0x55571894] -> imap [0x555722ac] -> imap [0x55572362] -> imap [0x55572b7f] -> imap(client_input+0x62) [0x55572da2] -> imap(io_loop_handler_run+0xf8) [0x555da0c8] -> imap(io_loop_run+0x1d) [0x555d918d] -> imap(main+0x462) [0x5557a552] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x2b64897fc154] -> imap [0x5556c859] If this is not enough for you to solve it ... Some problems were solved upgrading from 1.1.1 but these ones remained. Thanks, -- Nuno
Re: [Dovecot] DoveCot IMAP and "inconsistent state" messages
Chris Richards wrote: My other box is Gentoo, and I quite like it. The biggest problem I had with it was that about a year ago when I was give control of it, it hadn't been synced in like 3 years, and it was so woefully out of date that when I tried to emerge -upDN world, it couldn't reliably upgrade because some packages no longer existed, including core packages (and the system profile). I was once in this position with a redhat box and it turned out that you can't even update it from 3 years ago because they make you re-install every couple of years to put on a new OS... I can kind of imagine what might of happened though - was it a hardened profile by any chance? There was some trickiness with upgrading Python a couple of years back (as in if you were that far out of date) where portage needed a newer version than the older one would install. It was fairly simple to work around if you were familiar with the issues, but yes I agree it wasn't ideal. Other than that, the only problem I've had was when a Metalog (sysloger) update came out that caused my entire system to hang at boot because the portage package didn't properly move a couple of files. Sounds like you aren't using vservers yet? I build a minimal server on the bare iron and then immediately tar it up and copy it into /vservers/template. Then I use the vserver project to make it simple to "boot" this chrooted version and customise it a little and that then forms the basis for all my real servers. I usually keep about 3 template servers, one vanila-ish install, another setup for PHP apps, and another for some rails apps. Additionally you can easily test out your latest upgrade by simply copying a vserver somewhere, boot it, run the upgrade and then shut it down again. Bonus points for using a central package dir so that actually when you go back to your proper vserver and run the upgrade it actually uses the binary packages and updates in a few seconds... I bind mount all the dirs in my vservers which contain data to some other central storage. This means for example my dovecot vserver is quite small and quick to take a copy, but when you are inside it I bind mount all my maildirs into place. This makes it much simpler to copy vservers around and boot them up optionally pointing at the same live data as the original vserver (at the same time if you wish) There is nothing stopping you from starting to convert your current servers to this setup. Just get a compatible kernel on there at your next opportunity. Then grab a roughly suitable stage 4 and unpack it somewhere. "boot it" and recompile it to the state you actually want as your base template. Then copy it a couple of times and start moving live services into each vserver one by one. So you can have DNS in one, mail in another, amavis scanning in another, etc. It's probably fairly easy to move services one by one this way without any great hassle and eventually you will be all converted except that the base OS is more messy than it needs. Still it will then be easy to migrate the vservers between real machines and you can clean down that physical server and easily rebuild the base os without anyone noticing... Good luck Ed W
Re: [Dovecot] quota vs. antispam issue
I will test it tomorrow. Thanks for your work. 2008/7/24 Johannes Berg <[EMAIL PROTECTED]>: > On Mon, 2008-07-21 at 15:26 +0300, Timo Sirainen wrote: >> On Mon, 2008-07-21 at 06:48 +0200, Johannes Berg wrote: >> > On Sun, 2008-07-20 at 23:53 +0300, Timo Sirainen wrote: >> > >> > > > Ok, that seems to work, but I think a better alternative would probably >> > > > be to make dest_mail a struct mail ** like the context. >> > > >> > > That'd be an API change and I'd rather not do that for v1.1. But I >> > > suppose it would be the best permanent solution, so I'll do that for >> > > v1.2. >> > >> > Right, yeah, it'd be an API change, though I suppose the only external >> > plugin is probably mine ;) If you wanted to do it you could make some >> > header file declare a macro SAVE_FINISH_HAS_STRUCT_MAIL_PP, but I'm ok >> > with doing it in 1.2, except that means that during 1.1 antispam and >> > quota cannot be used together. >> >> No, this should help with v1.1: >> >> > > http://hg.dovecot.org/dovecot-1.1/rev/8dc6541b4426 >> >> You could then do it like quota plugin and I think it should work. > > Ok, I've committed that, so it should work now. Somebody please test. > > johannes >
Re: [Dovecot] DoveCot IMAP and "inconsistent state" messages
Jul 21 14:27:41 betty dovecot: IMAP(foobar): Maildir /var/vpopmail/domains/foobar.baz/foobar/Maildir sync: UID inserted in the middle of mailbox (4412 > 4385, file = 1214817167.16333_0.betty:2,RST) Show your dovecot -n output? Sorry, should have included that right away. betty - ~ # dovecot -n # 1.0.14: /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S listen: *:9000 disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login login_greeting_capability: yes login_max_processes_count: 256 first_valid_uid: 89 mail_location: maildir:~/Maildir dotlock_use_excl: yes maildir_copy_with_hardlinks: yes maildir_copy_preserve_filename: yes mail_process_size: 512 mail_plugins: quota imap_quota trash lazy_expunge imap_client_workarounds: outlook-idle delay-newmail namespace: type: private inbox: yes namespace: type: private separator: / prefix: .Trash/ location: maildir:~/Maildir/.Trash hidden: yes namespace: type: private separator: / prefix: .Trash/ location: maildir:~/Maildir/.Trash hidden: yes namespace: type: private separator: / prefix: .Trash/ location: maildir:~/Maildir/.Trash hidden: yes auth default: user: vpopmail verbose: yes passdb: driver: checkpassword args: /data/vpopmail/bin/vchkpw userdb: driver: prefetch plugin: quota: maildir trash: /etc/dovecot/dovecot-trash.conf lazy_expunge: .Trash/ .Trash/ .Trash/ I suppose the users don't have direct access to these maildirs, and nothing else besides Dovecot and procmail touches them? No, this is qmail with Vpopmail, so all mail is owned by the vpopmail user. Default MDA is qmail-local, but where procmail filters are enabled, it takes over all local delivery, and never hands it back to qmail-local. I haven't actively looked for a pattern yet, but from the top of my head, all users I can think of experiencing this problem use procmail for delivery. This error means that Dovecot lost that file and thought it was expunged. But sometimes afterwards it saw the file again. Hm. What is the normal scenario where something like this might happen, if there is such a thing? Any help would be greatly appreciated, as none of my testing thus far have made any difference, and I can't seem to find any hints elsewhere. Could upgrading to 1.1 help at all? (I'd rather not try unless I know for sure) v1.1 might not remove the root problem, but it will handle this better by renaming the file and showing it to client as a new message instead of returning "inconsistent state" error. That does sound more graceful. Squirrelmail shows an error for every dropped connection, so the end result is that users are seeing a whole bunch of error messages, without actually experiencing any problems (from what I've heard). I'd prefer to cure the problem, but if I can't, curing the symptom might be adequate. -- -==- -=- -==- Christer Mjellem Strand yitzhaq System administrator ICQ: 9557698 GSM +47 922 000 12 JID: [EMAIL PROTECTED] -==- -=- -==-
Re: [Dovecot] v1.1.2 released
On Thursday, July 24 at 03:05 AM, quoth Timo Sirainen:
+ Added a new maildirlock utility for write-locking Dovecot
Maildir.
Every time I attempt to use this (as root), it exits with a return
code of 143 and my shell prints out "Terminated".
I'm guessing that what happens is a result of this:
/* locked - send a */
if (kill(parent_pid, SIGTERM) < 0)
i_fatal("kill(parent, SIGTERM) failed: %m");
Any idea on how I can fix it?
~Kyle
--
When we blindly adopt any religion, political system, or literary
dogma, we become automatons. We cease to grow.
-- Anais Nin
pgpy6ThcKQkZL.pgp
Description: PGP signature
[Dovecot] Integrate Patch
Is It possible to integrate this patch into next dovecot's releases?
It implements the "-w ( disable webmail [IMAP from localhost*] access
)" option when using vpopmail.
** Patch created following dovecot mailing list information **
Thanks
--
[ ]'s
Aledr - Alexandre
"OpenSource Solutions for SmallBusiness Problems"
diff -Naur ./passdb-vpopmail.c dovecot-1.1.2/src/auth/passdb-vpopmail.c
--- ./passdb-vpopmail.c 2008-06-24 12:12:36.0 -0300
+++ dovecot-1.1.1/src/auth/passdb-vpopmail.c 2008-06-24 12:16:36.0 -0300
@@ -30,8 +30,12 @@
return NULL;
}
+ char *remotehost = net_ip2addr(&auth_request->remote_ip);
+ auth_request_log_info(auth_request, "vpopmail", "remote ip is: %s",remotehost);
+
if (((vpw->pw_gid & NO_IMAP) != 0 &&
- strcmp(auth_request->service, "IMAP") == 0) ||
+ strcmp(auth_request->service, "IMAP") == 0 && strcmp(remotehost, "127.0.0.1") !=0) ||
+ ((vpw->pw_gid & NO_WEBMAIL) != 0 && strcmp(remotehost, "127.0.0.1") == 0) ||
((vpw->pw_gid & NO_POP) != 0 &&
strcmp(auth_request->service, "POP3") == 0)) {
auth_request_log_info(auth_request, "vpopmail",
Re: [Dovecot] how to store flags \Seen into read-only mailbox?
I was looking for workaround, and tried to use one uid for all users, and ACL plugin to give permissions like: --- owner lrwstiekxa anyone rls --- rls should mean read, lookup and write-seen. Read and lookup works, and as soon as I remove these letters I can't read mail folder. But 's' is not working, I'm getting the same: --- 7 OK Store ignored with read-only mailbox. --- in rawlogs I can not find a way for users to keep their own track of what messages have been \Seen in read-only shared folder. -- Sergey Ivanov. - [EMAIL PROTECTED] wrote: > This problem is apparently about changeset > http://hg.dovecot.org/dovecot-1.1/rev/eec74a6ad62e. > This change makes dovecot behaviour different from what is described > in wiki, about sharing and making private /Seen flags, > see http://wiki.dovecot.org/SharedMailboxes?highlight=(flags are > shared or private) > When I've tried to revert it, first time with my client it worked > perfectly. > But then clients were not able to open any mail folders, and imap > processes were dying. > -- >Sergey Ivanov.
Re: [Dovecot] sparc quota bug
On Thu, 2008-07-24 at 09:53 +0200, [EMAIL PROTECTED] wrote: > Hi, > > I am getting the following error: > dovecot: Jul 23 18:04:44 Error: child 7600 (imap) killed with signal 10 Could you get gdb backtrace of this crash? See http://dovecot.org/bugreport.html signature.asc Description: This is a digitally signed message part
Re: [Dovecot] dovecot.conf permissions
On Thu, 2008-07-24 at 10:18 +0200, Dan Horák wrote: > Hi, > > I have a little problem with defining the right permissions for > dovecot.conf. The main problem is that the password for SSL certificates > is stored there and the conf file is world readable by default, which > makes a security problem [1]. It is not a problem to restrict the > permissions to 0600, dovecot will still work, but then deliver cannot > work as it reads the conf too, but it runs under arbitrary user. So my > last iteration is 0640 as permission and root:mail as ownership, but > that expects that deliver is run with group = mail. For the long term > solution I would prefer to move the password into a separate config file > so the permissions can be properly restricted there. What are your > opinions? Config file including will be supported some day. Also you could start Dovecot with -p parameter and specify the password there. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Delivery notifications
Brandon Keepers wrote: Are there any better options? Do you think this will have a significant impact on performance? Am I crazy? Simple solution - in case you are useing maildir: incron (http://inotify.aiken.cz/?section=incron&page=about&lang=en) it's inotify based cron daimon; you can hande new message events this way. Thanks, Brandon Uldis
Re: [Dovecot] Delivery notifications
Brandon Keepers wrote: I'm working on an application that is backed by Postfix 2.3.8 and Dovecot 1.0.13, configured with virtual domains, for handling messaging. I need to be able to send the notification (such as "You've received a new message on SomeAwesomeService. Click here to check it out", It's evil, I know) to a different email address, such as a mobile device. Eventually, we want to do other things like clear web page caches when a message is received, or sending IM notifications, but that's for another day. as you say, it's evil... you can try to reduce the "evilness" by not doing the notification in real time. I mean take few minutes so that you send one notification if you get multiple messages during a short period of time. So basically, we want to notify our application whenever a new mail is received, and it can do all the magical things that it needs to do. I was hoping to get some feedback on the different approaches I'm looking at. From what I can tell, there's not a way to deliver to multiple virtual transports in postfix, so here's the options I see: you can use virtual_alias_maps or one of the bcc options to deliver a copy of the message to a mailbox that does what you want. * Content filter I could set up a "content filter" that just delivers the mail to the application, and then re-injects it back into postfix. This seems like more work than the other options just because I have to worry about re-injecting the message * Intercept delivery Replace the dovecot deliver command with a custom one that calls the dovecot deliver and then passes the message on to the application. I've written a little proof of concept for this and it seems to work, but just seem shady. This is better. just make sure to pass arguments "securely". once you do your notification, simply run dovecot with the same command line args as you would use in master.cf. * Sieve Dovecot supports Sieve, so I could just have a global sieve script that sends the notifications. This is definitely the solution I'm leaning towards. I don't know if you can exec from dovecot-sieve. Are there any better options? Do you think this will have a significant impact on performance? Am I crazy? depends on how much they pay :)
[Dovecot] .files in dovecot-1.1.1
Hi there We had been using the stock Ubuntu Dapper Dovecot which is an early 1.0 beta but just upgraded to 1.1.1 to fix some read flag issues with Horde. Previously dovecot seemed to ignore files beginning with "." in the ~/mail (mbox format) directory but now shows them. There doesn't seem to be any switch in the dovcot.conf file to change this. Any such settings are about maildir. Is there anyway to make dovecot-1.1.1 ignore hidden files? Thanks -- John Baker Network Systems Administrator Marlboro College Phone: 451-7551 off campus; 551 on campus
Re: [Dovecot] how to store flags \Seen into read-only mailbox?
This problem is apparently about changeset
http://hg.dovecot.org/dovecot-1.1/rev/eec74a6ad62e.
This change makes dovecot behaviour different from what is described in wiki,
about sharing and making private /Seen flags,
see http://wiki.dovecot.org/SharedMailboxes?highlight=(flags are shared or
private)
When I've tried to revert it, first time with my client it worked perfectly.
But then clients were not able to open any mail folders, and imap processes
were dying.
--
Sergey Ivanov.
- [EMAIL PROTECTED] wrote:
> Hi,
> I'm trying to use dovecot for storing mailing lists and read-only
> access for users.
> The OS is Solaris, authentication for all readers of these lists are
> from Ldap through PAM, and one local user "listuser" will receive all
> mail and store them into it's folders (Maildirs). These maildirs are
> readable (read-only) for all others and they are shared by setting
> ---
> mail_location:
> maildir:/home/vmail/listuser/Maildir:CONTROL=/home/vmail/%u/Maildir/control:INDEX=/home/vmail/%u/Maildir/index
> ---
> Mail became readable because in each mail folder to be shared there is
> dovecot-shared with mode 064, and all users included into his group.
>
> But this is the problem: how to have flag \Seen stored in read-only
> mailbox? As recorded by rawlog, it is ignored now:
> ---
> bash-3.00# cat 20080724-103219-10616.in
> 3 namespace
> 4 lsub "" "*"
> 5 list "" "INBOX"
> 6 list "" "Trash"
> 7 create "Trash"
> 8 select "OmniTI.FreeLotto.Ops"
> 9 UID fetch 1:* (FLAGS)
> 10 uid store 1:3 +Flags (\Seen)
> 11 IDLE
> DONE
> 12 close
> 13 logout
> bash-3.00# cat 20080724-103219-10616.out
> * OK [RAWLOG TIMESTAMP] 2008-07-24 10:32:19
> * NAMESPACE (("" ".")) NIL NIL
> 3 OK Namespace completed.
> * LSUB () "." "OmniTI.FreeLotto.ODS"
> * LSUB () "." "OmniTI.FreeLotto.Ops"
> 4 OK Lsub completed.
> * LIST (\HasNoChildren) "." "INBOX"
> 5 OK List completed.
> 6 OK List completed.
> 7 NO Internal error occurred. Refer to server log for more
> information. [2008-07-24 10:32:19]
> * FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
> * OK [PERMANENTFLAGS ()] Read-only mailbox.
> * 3 EXISTS
> * 0 RECENT
> * OK [UNSEEN 1] First unseen.
> * OK [UIDVALIDITY 1216906857] UIDs valid
> * OK [UIDNEXT 4] Predicted next UID
> 8 OK [READ-ONLY] Select completed.
> * 1 FETCH (UID 1 FLAGS ())
> * 2 FETCH (UID 2 FLAGS ())
> * 3 FETCH (UID 3 FLAGS ())
> 9 OK Fetch completed.
> 10 OK Store ignored with read-only mailbox.
> + idling
> 11 OK Idle completed.
> 12 OK Close completed.
> * BYE Logging out
> 13 OK Logout completed.
> ---
>
> --
> Sergey ivanov.
Re: [Dovecot] Dovecot 1.1.1 + zlib plugin + mbox crash
On Thu, Jul 24, 2008 at 04:30:28PM +0100, Chris Wakelin wrote: > Chris Wakelin wrote: > >>>I can try this in Solaris 10, but I don't really see why the > >>>OS/architecture should matter. > >> > >>Oh, unless there are some bugs in your zlib version, such as related to > >>seeking.. > > > >Could be, I imagine it's as prehistoric as the bzlib :) > > > > Right, I've tried dovecot-1.1.2 using my own zlib-1.2.3 (and > bzlib-1.0.5) build on Solaris 8: > > ldd lib20_zlib_plugin.so gives > libz.so => /opt/RDGzlib/lib/libz.so > libbz2.so => /opt/RDGbzlib/lib/libbz2.so ... > > and get the same problems. I cannot get Dovecot 1.1.2 to compile at all on Solaris8 with gcc 3.3.4 and newly recompiled versions of bzip2 and zlib libraries. This is the first time I've ever had a problem getting Dovecot to compile under Solaris 8. Making all in zlib make[4]: Entering directory `/usr/local/src/dovecot/dovecot-1.1.2/src/plugins/zlib' /bin/bash ../../../libtool --tag=CC --mode=link gcc -std=gnu99 -O0 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -module -avoid-version -o lib20_zlib_plugin.la -rpath /usr/local/adm/dovecot/lib/dovecot istream-bzlib.lo istream-zlib.lo zlib-plugin.lo -lz -lbz2 -lrt -lnsl -lsocket gcc -shared -Wl,-h -Wl,lib20_zlib_plugin.so -o .libs/lib20_zlib_plugin.so .libs/istream-bzlib.o .libs/istream-zlib.o .libs/zlib-plugin.o -lz -lbz2 -lrt -lnsl -lsocket -lc Text relocation remains referenced against symbol offset in file 0x3ab8 /usr/local/lib/libbz2.a(decompress.o) 0x3abc /usr/local/lib/libbz2.a(decompress.o) 0x3ac0 /usr/local/lib/libbz2.a(decompress.o) fgetc 0x20e8 /usr/local/lib/libbz2.a(bzlib.o) exit0x3c/usr/local/lib/libbz2.a(bzlib.o) __ctype 0x2f60 /usr/local/lib/libbz2.a(bzlib.o) __ctype 0x2f68 /usr/local/lib/libbz2.a(bzlib.o) fopen64 0x3104 /usr/local/lib/libbz2.a(bzlib.o) ungetc 0x2100 /usr/local/lib/libbz2.a(bzlib.o) .div0x8a8 /usr/local/lib/libbz2.a(compress.o) .div0xabc /usr/local/lib/libbz2.a(blocksort.o) .div0xe48 /usr/local/lib/libbz2.a(blocksort.o) ld: fatal: relocations remain against allocatable but non-writable sections collect2: ld returned 1 exit status make[4]: *** [lib20_zlib_plugin.la] Error 1 -- Dean Brooks [EMAIL PROTECTED]
Re: [Dovecot] Delivery notifications
On Jul 24, 2008, at 12:09 PM, Scott Silva wrote: on 7-24-2008 9:03 AM Brandon Keepers spake the following: In my opinion (which is worth every penny you didn't pay for it) If I want notices of my new messages on a phone or other mobile device, I might as well just get the message sent or copied there. I agree 100%, unfortunately I haven't convinced my client of that yet, so I'm doing my due diligence in researching the options. PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] Delivery notifications
on 7-24-2008 9:03 AM Brandon Keepers spake the following: I'm working on an application that is backed by Postfix 2.3.8 and Dovecot 1.0.13, configured with virtual domains, for handling messaging. I need to be able to send the notification (such as "You've received a new message on SomeAwesomeService. Click here to check it out", It's evil, I know) to a different email address, such as a mobile device. Eventually, we want to do other things like clear web page caches when a message is received, or sending IM notifications, but that's for another day. So basically, we want to notify our application whenever a new mail is received, and it can do all the magical things that it needs to do. I was hoping to get some feedback on the different approaches I'm looking at. From what I can tell, there's not a way to deliver to multiple virtual transports in postfix, so here's the options I see: * Content filter I could set up a "content filter" that just delivers the mail to the application, and then re-injects it back into postfix. This seems like more work than the other options just because I have to worry about re-injecting the message * Intercept delivery Replace the dovecot deliver command with a custom one that calls the dovecot deliver and then passes the message on to the application. I've written a little proof of concept for this and it seems to work, but just seem shady. * Sieve Dovecot supports Sieve, so I could just have a global sieve script that sends the notifications. This is definitely the solution I'm leaning towards. Are there any better options? Do you think this will have a significant impact on performance? Am I crazy? Thanks, Brandon In my opinion (which is worth every penny you didn't pay for it) If I want notices of my new messages on a phone or other mobile device, I might as well just get the message sent or copied there. -- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't signature.asc Description: OpenPGP digital signature
[Dovecot] Delivery notifications
I'm working on an application that is backed by Postfix 2.3.8 and Dovecot 1.0.13, configured with virtual domains, for handling messaging. I need to be able to send the notification (such as "You've received a new message on SomeAwesomeService. Click here to check it out", It's evil, I know) to a different email address, such as a mobile device. Eventually, we want to do other things like clear web page caches when a message is received, or sending IM notifications, but that's for another day. So basically, we want to notify our application whenever a new mail is received, and it can do all the magical things that it needs to do. I was hoping to get some feedback on the different approaches I'm looking at. From what I can tell, there's not a way to deliver to multiple virtual transports in postfix, so here's the options I see: * Content filter I could set up a "content filter" that just delivers the mail to the application, and then re-injects it back into postfix. This seems like more work than the other options just because I have to worry about re- injecting the message * Intercept delivery Replace the dovecot deliver command with a custom one that calls the dovecot deliver and then passes the message on to the application. I've written a little proof of concept for this and it seems to work, but just seem shady. * Sieve Dovecot supports Sieve, so I could just have a global sieve script that sends the notifications. This is definitely the solution I'm leaning towards. Are there any better options? Do you think this will have a significant impact on performance? Am I crazy? Thanks, Brandon PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] dovecot.conf permissions
on 7-24-2008 1:18 AM Dan Horák spake the following: Hi, I have a little problem with defining the right permissions for dovecot.conf. The main problem is that the password for SSL certificates is stored there and the conf file is world readable by default, which makes a security problem [1]. It is not a problem to restrict the permissions to 0600, dovecot will still work, but then deliver cannot work as it reads the conf too, but it runs under arbitrary user. So my last iteration is 0640 as permission and root:mail as ownership, but that expects that deliver is run with group = mail. For the long term solution I would prefer to move the password into a separate config file so the permissions can be properly restricted there. What are your opinions? With regards, Dan [1] https://bugzilla.redhat.com/show_bug.cgi?id=436287 You can always have no passwords on ssl certs. Probably just as secure as a world readable password. -- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't signature.asc Description: OpenPGP digital signature
Re: [Dovecot] making IMAP quicker on LAN
Ed W wrote: Andrew Von Cid wrote: Hi all, I keep on hitting this problem when migrating new clients from POP or local IMAP servers (hosted on their LAN's) to my Dovecot setup, which is hosted properly in a data center. People usually complain that it's slower and although they're getting a kick ass mail setup it doesn't look good from their point of view. I'm wondering if there is anything I could do to speed it up on their LAN's. What I mean is probably a caching IMAP proxy or some sort of replication to a local Dovecot server. Is this something Dovecot can do? I'd be really grateful for any opinions on how to tackle this problem. My experience is that most mail clients drag down a LOT of data when you open a folder, hence the bandwidth required is surprisingly large. I also noticed that this data compresses EXTREMELY well. So my company just happens to make a compression proxy for use on seriously slow dialup links (2.4Kbit), but my own experience is that this speeds things up by around a factor of 2 on a typical fast broadband link (compared using Thunderbird) There are various simple ways to test this thesis on your own setup, including a simple straight through proxy in about 20 lines or perl. However, not sure what the best fix is for this problem? There was some discussion a few weeks back that SSL can have a compression layer turned on - Timo pointed out that this was disabled in both Dovecot and also TB. It might be possible to send Timo some money and have it enabled in Dovecot (looked like a very trivial one line fix?) - you could then (fix and) use ssltunnel to get the benefit whilst waiting for your patch to TB to be accepted into mainstream (or if it suits your userbase you could fix the code and distribute a changed version locally? If using Outlook then obviously this isn't possible, but no idea if Outlook already supports compressed SSL?) You could also pay Timo to add support for the compressed IMAP protocol extension, but again you run into the problem that few/no clients support it (at least you have half the problem licked though) Timo is also working on a very clever multi-master imap server replication engine - again probably tipping a few euros his way might speed up that process. This would give you a local cache server Hope those ideas get you started? Good luck Ed W A few IMAP client based things that seem to help are: disable all of the languages you don't need in Thunderbird; configure AppleMail to download only the messages you've read; configure Outlook/Outlook Express to sync at a more reasonable level to limit it from downloading everything every time; or make everyone use mutt/pine. The last isn't realistic but if mutt or pine works fine, then you know some client optimizations will help. Webmail, as long as it isn't loaded with too much graphics, might work better with slow connections. For people connecting to Email while in a Rain Forest, POP seems to be the best option. It also seems to me that fts plugin (free text indexing) improves performance. This might just be wishful thinking on my part. Hope this helps a little. ---Jack
Re: [Dovecot] Dovecot 1.1.1 + zlib plugin + mbox crash
Chris Wakelin wrote: I can try this in Solaris 10, but I don't really see why the OS/architecture should matter. Oh, unless there are some bugs in your zlib version, such as related to seeking.. Could be, I imagine it's as prehistoric as the bzlib :) Right, I've tried dovecot-1.1.2 using my own zlib-1.2.3 (and bzlib-1.0.5) build on Solaris 8: ldd lib20_zlib_plugin.so gives libz.so => /opt/RDGzlib/lib/libz.so libbz2.so => /opt/RDGbzlib/lib/libbz2.so ... and get the same problems. I've tried building on Solaris 10 (using Sun's zlib and bzlib2) and get a similar problem ldd lib20_zlib_plugin.so libz.so.1 => /usr/lib/libz.so.1 libbz2.so.1 => /usr/lib/libbz2.so.1 ... After FETCH 1:167 FULL, FETCH 167 BODY[], FETCH 123 BODY[], FETCH 39 BODY[], FETCH 23 BODY[] :- dovecot: Jul 24 16:02:51 Error: IMAP 28535 xxx.xxx.xxx.xxx : Cached message offset 45576 is invalid for mbox file (read-only mbox stream) dovecot: Jul 24 16:02:51 Error: IMAP 28535 xxx.xxx.xxx.xxx : Cached message offset 45576 is invalid for mbox file (read-only mbox stream) dovecot: Jul 24 16:02:51 Error: IMAP 28535 xxx.xxx.xxx.xxx : Losing sync for mail uid=23 in mbox file (read-only mbox stream) dovecot: Jul 24 16:02:51 Error: IMAP 28535 xxx.xxx.xxx.xxx : Unexpectedly lost From-line at 45576 dovecot: Jul 24 16:02:51 Error: IMAP 28535 xxx.xxx.xxx.xxx : Unexpectedly lost From-line at 45576 dovecot: Jul 24 16:02:51 Error: IMAP 28535 xxx.xxx.xxx.xxx : Couldn't get mbox size dovecot: Jul 24 16:02:51 Info: IMAP 28535 xxx.xxx.xxx.xxx : Disconnected: Internal error occurred. Refer to server log for more information. [2008-07-24 16:02:51] bytes=114/90517 On the SuSE box, it's fine. However, on all three boxes when I use bzip2 instead (i.e. same folder, bzipped) I get a segfault crash after just "FETCH 1:167 FULL" :- dovecot: Jul 24 16:17:29 Error: child 28544 (imap) killed with signal 11 backtrace on the Solaris 8 version: #0 0xff2505a0 in memmove () from /usr/platform/SUNW,Ultra-250/lib/libc_psr.so.1 #1 0xa6d60 in i_stream_compress (stream=0xfc930) at istream.c:301 #2 0xff1414e4 in i_stream_zlib_seek (stream=0xfc930, v_offset=0, mark=true) at istream-zlib.c:173 #3 0xa6920 in i_stream_seek_mark (stream=0xfc958, v_offset=4443332646273026) at istream.c:139 #4 0x4f654 in istream_raw_mbox_seek (stream=0x1142f0, offset=0) at istream-raw-mbox.c:625 #5 0x45cd8 in mbox_file_seek (mbox=0x10e6b8, view=0x4868b0, seq=1, deleted_r=0xffbeee37) at mbox-file.c:171 #6 0x4739c in mbox_mail_seek (mail=0x10edd8) at mbox-mail.c:70 #7 0x474f4 in mbox_mail_get_received_date (_mail=0x, date_r=0xffbeef8c) at mbox-mail.c:103 #8 0x6acf4 in mail_get_received_date (mail=0x, date_r=0xffbeef8c) at mail.c:79 #9 0x2aeb0 in fetch_internaldate (ctx=0x10edd8, mail=0x10edd8, context=0x0) at imap-fetch.c:552 #10 0x2a4fc in imap_fetch_more (ctx=0xf6180) at imap-fetch.c:309 #11 0x2a744 in imap_fetch (ctx=0xf6180) at imap-fetch.c:361 #12 0x23628 in cmd_fetch (cmd=0xf60f0) at cmd-fetch.c:152 #13 0x28784 in client_command_input (cmd=0xf60f0) at client.c:580 #14 0x28628 in client_command_input (cmd=0xf60f0) at client.c:629 #15 0x2880c in client_handle_next_command (client=0xf5e90, remove_io_r=0xffbef2bf) at client.c:670 #16 0x288f4 in client_handle_input (client=0xf5e90) at client.c:680 #17 0x28a40 in client_input (client=0xf5e90) at client.c:725 #18 0xaa1a4 in io_loop_handler_run (ioloop=0xf29e8) at ioloop-poll.c:200 #19 0xa99d4 in io_loop_run (ioloop=0xf29e8) at ioloop.c:308 #20 0x31cf4 in main (argc=0, argv=0xffbef504, envp=0xffbef514) at main.c:293 I could send you the dovecot index files at each stage of the zlib test if that would help? Chris -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, [EMAIL PROTECTED] IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094
Re: [Dovecot] Case sensitve problem
Charles Marcus schrieb: On 7/24/2008, Sven Schmidt ([EMAIL PROTECTED]) wrote: Dovecot 1.0.rc15. I see your specific issue was answered, but it is also highly recommended that you upgrade... this is a VERY old, RC version (in a release that had over 30 (thirty) release candidates)... In fact, the current stable version is 1.1.2. The 1.1.x series has numerous improvements over the 1.0.x series. Its from Debian Etch and latest version.
Re: [Dovecot] Case sensitve problem
On 7/24/2008, Sven Schmidt ([EMAIL PROTECTED]) wrote: Dovecot 1.0.rc15. I see your specific issue was answered, but it is also highly recommended that you upgrade... this is a VERY old, RC version (in a release that had over 30 (thirty) release candidates)... In fact, the current stable version is 1.1.2. The 1.1.x series has numerous improvements over the 1.0.x series. -- Best regards, Charles
[Dovecot] how to store flags \Seen into read-only mailbox?
Hi,
I'm trying to use dovecot for storing mailing lists and read-only access for
users.
The OS is Solaris, authentication for all readers of these lists are from Ldap
through PAM, and one local user "listuser" will receive all mail and store them
into it's folders (Maildirs). These maildirs are readable (read-only) for all
others and they are shared by setting
---
mail_location:
maildir:/home/vmail/listuser/Maildir:CONTROL=/home/vmail/%u/Maildir/control:INDEX=/home/vmail/%u/Maildir/index
---
Mail became readable because in each mail folder to be shared there is
dovecot-shared with mode 064, and all users included into his group.
But this is the problem: how to have flag \Seen stored in read-only mailbox?
As recorded by rawlog, it is ignored now:
---
bash-3.00# cat 20080724-103219-10616.in
3 namespace
4 lsub "" "*"
5 list "" "INBOX"
6 list "" "Trash"
7 create "Trash"
8 select "OmniTI.FreeLotto.Ops"
9 UID fetch 1:* (FLAGS)
10 uid store 1:3 +Flags (\Seen)
11 IDLE
DONE
12 close
13 logout
bash-3.00# cat 20080724-103219-10616.out
* OK [RAWLOG TIMESTAMP] 2008-07-24 10:32:19
* NAMESPACE (("" ".")) NIL NIL
3 OK Namespace completed.
* LSUB () "." "OmniTI.FreeLotto.ODS"
* LSUB () "." "OmniTI.FreeLotto.Ops"
4 OK Lsub completed.
* LIST (\HasNoChildren) "." "INBOX"
5 OK List completed.
6 OK List completed.
7 NO Internal error occurred. Refer to server log for more information.
[2008-07-24 10:32:19]
* FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
* OK [PERMANENTFLAGS ()] Read-only mailbox.
* 3 EXISTS
* 0 RECENT
* OK [UNSEEN 1] First unseen.
* OK [UIDVALIDITY 1216906857] UIDs valid
* OK [UIDNEXT 4] Predicted next UID
8 OK [READ-ONLY] Select completed.
* 1 FETCH (UID 1 FLAGS ())
* 2 FETCH (UID 2 FLAGS ())
* 3 FETCH (UID 3 FLAGS ())
9 OK Fetch completed.
10 OK Store ignored with read-only mailbox.
+ idling
11 OK Idle completed.
12 OK Close completed.
* BYE Logging out
13 OK Logout completed.
---
--
Sergey ivanov.
Re: [Dovecot] Case sensitve problem
Sven Schmidt wrote: Hi! I am using Postfix, Mysql and Dovecot 1.0.rc15. It seems that Dovecot creates new mailboxes for eg. [EMAIL PROTECTED] althoug in the name in databse is [EMAIL PROTECTED] ny logging in pop3. How to solve this problem? Use %L in 'mail_location' of your dovecot.conf, such as: mail_location = maildir:/%Lh/%Ld/%Ln/:INDEX=/%Lh/%Ld/%Ln/ It will convert all upper case to lower case. Reference: http://wiki.dovecot.org/Variables -- Best Regards. Zhang Huangbin - iRedMail: Mail Server Solution for Red Hat(R) Enterprise Linux & CentOS 5.x: http://iRedMail.googlecode.com/
Re: [Dovecot] Case sensitve problem
On 7/24/2008 10:51 AM, Sven Schmidt wrote: Dovecot 1.0.rc15. In fact, the current stable version is 1.1.2. The 1.1.x series has numerous improvements over the 1.0.x series. Its from Debian Etch and latest version. No offense, but thats no excuse for running a very old/buggy version of software... This is precisely what backports is for. I've never even used Debian and it took me all of 5 seconds to find it: http://packages.debian.org/search?keywords=dovecot -- Best regards, Charles
[Dovecot] Case sensitve problem
Hi! I am using Postfix, Mysql and Dovecot 1.0.rc15. It seems that Dovecot creates new mailboxes for eg. [EMAIL PROTECTED] althoug in the name in databse is [EMAIL PROTECTED] ny logging in pop3. How to solve this problem?
Re: [Dovecot] quota vs. antispam issue
On Mon, 2008-07-21 at 15:26 +0300, Timo Sirainen wrote: > On Mon, 2008-07-21 at 06:48 +0200, Johannes Berg wrote: > > On Sun, 2008-07-20 at 23:53 +0300, Timo Sirainen wrote: > > > > > > Ok, that seems to work, but I think a better alternative would probably > > > > be to make dest_mail a struct mail ** like the context. > > > > > > That'd be an API change and I'd rather not do that for v1.1. But I > > > suppose it would be the best permanent solution, so I'll do that for > > > v1.2. > > > > Right, yeah, it'd be an API change, though I suppose the only external > > plugin is probably mine ;) If you wanted to do it you could make some > > header file declare a macro SAVE_FINISH_HAS_STRUCT_MAIL_PP, but I'm ok > > with doing it in 1.2, except that means that during 1.1 antispam and > > quota cannot be used together. > > No, this should help with v1.1: > > > > http://hg.dovecot.org/dovecot-1.1/rev/8dc6541b4426 > > You could then do it like quota plugin and I think it should work. Ok, I've committed that, so it should work now. Somebody please test. johannes signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Quota
Hello. 2008/7/23 Timo Sirainen <[EMAIL PROTECTED]>: > If all your users have the same uid and gid, you can also use: > > export HOME=/home/wanted-user > echo "1 getquotaroot inbox" | dovecot --exec-mail imap > Great, the reply is: * QUOTAROOT "inbox" "" * QUOTA "" (STORAGE 0 1048576) 1 OK Getquotaroot completed. 1GB as in my dovecot.conf (using maildir). I'm retreiving the users from OpenLDAP. There is no field for the quota per user ou domain. How is the better way for me to do that? Create and field in OpenLDAP (Jamm schema) or use the quota dict? Regards, Rodrigo. -- M. Rodrigo Monteiro [EMAIL PROTECTED] "Free as in Freedom, not free as in free beer" Linux User # 403730
Re: [Dovecot] making IMAP quicker on LAN
Andrew Von Cid wrote: Hi all, I keep on hitting this problem when migrating new clients from POP or local IMAP servers (hosted on their LAN's) to my Dovecot setup, which is hosted properly in a data center. People usually complain that it's slower and although they're getting a kick ass mail setup it doesn't look good from their point of view. I'm wondering if there is anything I could do to speed it up on their LAN's. What I mean is probably a caching IMAP proxy or some sort of replication to a local Dovecot server. Is this something Dovecot can do? I'd be really grateful for any opinions on how to tackle this problem. My experience is that most mail clients drag down a LOT of data when you open a folder, hence the bandwidth required is surprisingly large. I also noticed that this data compresses EXTREMELY well. So my company just happens to make a compression proxy for use on seriously slow dialup links (2.4Kbit), but my own experience is that this speeds things up by around a factor of 2 on a typical fast broadband link (compared using Thunderbird) There are various simple ways to test this thesis on your own setup, including a simple straight through proxy in about 20 lines or perl. However, not sure what the best fix is for this problem? There was some discussion a few weeks back that SSL can have a compression layer turned on - Timo pointed out that this was disabled in both Dovecot and also TB. It might be possible to send Timo some money and have it enabled in Dovecot (looked like a very trivial one line fix?) - you could then (fix and) use ssltunnel to get the benefit whilst waiting for your patch to TB to be accepted into mainstream (or if it suits your userbase you could fix the code and distribute a changed version locally? If using Outlook then obviously this isn't possible, but no idea if Outlook already supports compressed SSL?) You could also pay Timo to add support for the compressed IMAP protocol extension, but again you run into the problem that few/no clients support it (at least you have half the problem licked though) Timo is also working on a very clever multi-master imap server replication engine - again probably tipping a few euros his way might speed up that process. This would give you a local cache server Hope those ideas get you started? Good luck Ed W
[Dovecot] making IMAP quicker on LAN
Hi all, I keep on hitting this problem when migrating new clients from POP or local IMAP servers (hosted on their LAN's) to my Dovecot setup, which is hosted properly in a data center. People usually complain that it's slower and although they're getting a kick ass mail setup it doesn't look good from their point of view. I'm wondering if there is anything I could do to speed it up on their LAN's. What I mean is probably a caching IMAP proxy or some sort of replication to a local Dovecot server. Is this something Dovecot can do? I'd be really grateful for any opinions on how to tackle this problem. Many thanks, Andrew.
[Dovecot] dovecot.conf permissions
Hi, I have a little problem with defining the right permissions for dovecot.conf. The main problem is that the password for SSL certificates is stored there and the conf file is world readable by default, which makes a security problem [1]. It is not a problem to restrict the permissions to 0600, dovecot will still work, but then deliver cannot work as it reads the conf too, but it runs under arbitrary user. So my last iteration is 0640 as permission and root:mail as ownership, but that expects that deliver is run with group = mail. For the long term solution I would prefer to move the password into a separate config file so the permissions can be properly restricted there. What are your opinions? With regards, Dan [1] https://bugzilla.redhat.com/show_bug.cgi?id=436287 -- Fedora and Red Hat package maintainer
[Dovecot] sparc quota bug
Hi, I am getting the following error: dovecot: Jul 23 18:04:44 Error: child 7600 (imap) killed with signal 10 How to reproduce: Try to delete or move a mail to another folder. The mail actually gets copied to the other folder but the original isn't removed (when using webmail). If using thunderbird this ends up in an infinite loop creating new mails in the destination folder (without deleting the original) until stopped manually. When turning off quota or commenting out the "quota: dirsize:storage=1048576" entry it works, just no quotas anymore. :-( Details: OS: OpenBSD ARCH: sparc64 FS: ffs Dovecot version: 1.0.15 and 1.1.1 If you need more information, please let me know. @timo: I could provide access to a OpenBSD sparc64 box if it would help debugging the problem. Just send me your public SSH key. # dovecot -n # 1.0.15: /etc/dovecot.conf base_dir: /var/dovecot/ log_path: /var/log/dovecot.log protocols: imaps pop3s listen: XXX.XXX.XXX.XXX ssl_ca_file: /etc/ssl/ca.crt ssl_cert_file: /etc/ssl/mail.crt ssl_key_file: /etc/ssl/private/mail.key login_dir: /var/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_user: _dovecot first_valid_uid: 1 first_valid_gid: 100 last_valid_gid: 100 mail_location: mbox:/home/mail/%u/mbox:INBOX=/home/mail/%u/mbox/inbox:INDEX=/var/dovecot/index/%u mbox_write_locks: fcntl mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota trash mail_plugins(imap): quota imap_quota trash mail_plugins(pop3): quota mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: passdb: driver: bsdauth userdb: driver: passwd plugin: quota: dirsize:storage=1048576 trash: /etc/dovecot-trash.conf # dmesg Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2008 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 4.4-beta (GENERIC.MP) #364: Sun Jul 20 17:33:03 MDT 2008 [EMAIL PROTECTED]:/usr/src/sys/arch/sparc64/compile/GENERIC.MP real mem = 8589934592 (8192MB) avail mem = 8369397760 (7981MB) mainbus0 at root: Sun Fire V440 cpu0 at mainbus0: SUNW,UltraSPARC-IIIi (rev 2.4) @ 1062 MHz cpu0: physical 32K instruction (32 b/l), 64K data (32 b/l), 1024K external (64 b/l) cpu1 at mainbus0: SUNW,UltraSPARC-IIIi (rev 2.4) @ 1062 MHz cpu1: physical 32K instruction (32 b/l), 64K data (32 b/l), 1024K external (64 b/l) cpu2 at mainbus0: SUNW,UltraSPARC-IIIi (rev 2.4) @ 1062 MHz cpu2: physical 32K instruction (32 b/l), 64K data (32 b/l), 1024K external (64 b/l) cpu3 at mainbus0: SUNW,UltraSPARC-IIIi (rev 2.4) @ 1062 MHz cpu3: physical 32K instruction (32 b/l), 64K data (32 b/l), 1024K external (64 b/l) "memory-controller" at mainbus0 not configured "memory-controller" at mainbus0 not configured "memory-controller" at mainbus0 not configured "memory-controller" at mainbus0 not configured schizo0 at mainbus0: "Tomatillo", version 4, ign 700, bus A 0 to 0 schizo0: dvma map c000-dfff, iotdb 5174000-51f4000 pci0 at schizo0 cas0 at pci0 dev 2 function 0 "Sun Cassini" rev 0x20: ivec 0x718, address 00:03:ba:66:75:d1 brgphy0 at cas0 phy 1: BCM5421 10/100/1000baseT PHY, rev. 1 "ppm" at mainbus0 not configured schizo1 at mainbus0: "Tomatillo", version 4, ign 740, bus B 0 to 0 schizo1: dvma map c000-dfff, iotdb 552c000-55ac000 pci1 at schizo1 mpi0 at pci1 dev 2 function 0 "Symbios Logic 53c1030" rev 0x08: ivec 0x740 scsibus0 at mpi0: 16 targets, initiator 7 schizo2 at mainbus0: "Tomatillo", version 4, ign 780, bus A 0 to 0 schizo2: dvma map c000-dfff, iotdb 5694000-5714000 pci2 at schizo2 ebus0 at pci2 dev 7 function 0 "Acer Labs M1533 ISA" rev 0x00 "flashprom" at ebus0 addr 0-f, 290-290 not configured rtc0 at ebus0 addr 70-71: m5819p pcfiic0 at ebus0 addr 320-321 ivec 0x1b iic0 at pcfiic0 "SUNW,i2c-imax" at iic0 addr 0xb not configured "SUNW,i2c-imax" at iic0 addr 0xc not configured admtemp0 at iic0 addr 0x18: max1617, cannot get control register "pca9555" at iic0 addr 0x21 not configured "pca9555" at iic0 addr 0x22 not configured "pca9555" at iic0 addr 0x23 not configured "pca9555" at iic0 addr 0x24 not configured "adm1026" at iic0
