similar to: per-mailbox message limits

Hi, I was just looking at the "CRAN Daily Package Check Results" [http://cran.r-project.org/src/contrib/checkSummary.html], and realized there are 1000 packages on CRAN as of today (look at row 3 in the table below). Yet another quite extraordinary milestone in R history. Last updated on 2007-04-12 11:48:32 Results for installing and checking packages using the three current flavors

We are now starting testing R 2.13.0/alpba/beta/RC and testing and feedback would be appreciated (whereas reports on problems immediately after release will try our patience). Sources are available at http://cran.r-project.org/src/base-prerelease/ Windows binaries at http://cran.r-project.org/bin/windows/base/rtest.html and Mac binaries at http://r.research.att.com/, specifically

On Sat, 2007-04-07 at 08:40 +0200, Kurt Hornik wrote: > Dear maintainers of CRAN packages, > > This concerns the packages <snip /> > > And now keep the updates rolling in ... Dear R Developers, I was recently emailed by the CRAN maintainers about warnings for my two packages, analog and cocorresp, that are on CRAN. I have built both packages (the versions on CRAN plus

G'day all, looking at http://cran.at.r-project.org/web/checks/check_results_Sleuth2.html I noticed that r-prerel-* and r-devel-* issue notes. Apparently, now examples are more thoroughly checked by R CMD check and the note pointed out that a package used in the examples was not declared. This was easily fixed by adding 'Suggests: lattice' to the DESCRIPTION file (now this change has

Just released by the CPSC on their recalls mailing list; please forward to any venues where you feel operators or resellers of the SoundStation might be, with this preface included. My 2W had a battery with the part code 1520-07804-002; its date code was GP0806, and therefore predates the recall period. Cheers, -- jra ----- Begin forwarded message ----- This message consists of the following:

Hi, I am new to the dovecot source and would like to know why the mailbox_module_context has a pointer to the mail_storage_module_register and not to a mailbox_module_register. From what I have understood, if a context is first added to the mailbox.module_contexts array using the mail_storage_module_register and then a context is added to the mail_storage.module_contexts and then a third context

Hi Timo..... Trying to resolve my problem with the references in copying a email between Folders (when i move from inbox -> sent for example), i got some doubt. My plugin create a new ostream in v->save_begin, and i start a function from my library to create the reference, but when the email is been copying, the new email don't pass in this function, and i don't start my function

Here is what I get when I try to compile the antispam plugin agaisnt Dovecot 2.1 ************** mailbox.c: In function 'antispam_save_begin': mailbox.c:138:12: error: 'struct mail_save_context' has no member named 'copying' mailbox.c: In function 'antispam_save_finish': mailbox.c:174:12: error: 'struct mail_save_context' has no member named

Hello, Last dovecot available version on Ubuntu 11.10 AMD64 is dovecot 2.0.13. dovecot-antispam package is compiled for dovecot 2.0.15. So, i'm trying to compile a new dovecot antispam plugin. I followed dovecot wiki but i'm running into this error : Successfully compiled dspam.c (plugin). mailbox.c: In function 'antispam_save_begin': mailbox.c:138:12: error: 'struct

Hi, I'm new to this list, so first thanks for the dovecot tool! So far, it has been great to work with. Currently, I'm developing a scrambler plugin for dovecot, that should stores the mails encrypted. To do that, I've created the scrambler_ostream and scrambler_istream that does the encryption and that I hook in the mail storage process. The scrambler_ostream is stacked on top

Hello, I am working on fixing dovecot-antispam to work with dovecot 2.0. I am down to three errors/warnigns that concern me. The one I need help from those more familiar with dovecot internals is in the subject. What happened to mailbox_open? Did it disappear? Did it get renamed? It appears that I am needing to override some methods: if (need_folder_hook) { /* override

Looking at mail_filter_mailbox_allocated() of src/plugins/mail-filter/mail-filter-plugin.c: if ((class_flags & MAIL_STORAGE_CLASS_FLAG_OPEN_STREAMS) == 0 && (class_flags & MAIL_STORAGE_CLASS_FLAG_BINARY_DATA) != 0 && muser->out_socket_path != NULL) v->save_begin = mail_filter_mail_save_begin; it seems that a backend with

Hello everyone..... I Made some tests in zlib plugin, and in ostream file (ostream-zlib.c) in o_stream_zlib_sendv function, have it: stream->ostream.offset += bytes; In struct mail_save_context, have saved_physical_size and it can be updated, acording with the observation. /* if non-zero, overrides the physical size that should be saved. for example when using zlib plugin, this

Version: 2.0.2 OS: Mac OS X 10.5.8 IMAP Client: Apple Mail.app on 10.5.8 Since upgrading to 2.0.2 I've noticed one user ends up with 4-5 imap processes all using as much CPU as they can get. I know of one other person who is seeing this on a FreeBSD server (that person moved back to dovecot 1.2 which 'solved' the problem there). I didn't notice anything in the list archive

Hi Timo !! I rewrite the copy function from mailbox (using a plugin) My rewrite is like this: static int emexis_antispam_copy(struct mail_save_context *ctx, struct mail *mail){ struct mailbox *box = ctx->transaction->box; union mailbox_module_context *zbox = EMEXIS_CONTEXT(box); struct mail_private *_mail = (struct mail_private *)mail; union mail_module_context *zmail =

Hi, I?d like to extend the mail_log plugin to log the uid and keywords of a mail delivered by LDA. The keywords are set by the sieve plugin. I added a mail_log_save_finish() function hook listed below. However, the uid of the mail is always zero and trying to get the keywords results in assertion failure, probably because the message is not committed yet: Feb 13 08:07:42 ha-test1 deliver(test1

> > Can you do > > p *box $1 = {name = 0x5555557e1f18 "Junk", vname = 0x5555557e1f10 "Junk", storage = 0x5555557e1860, list = 0x5555557e1050, v = { is_readonly = 0x7ffff76e5a50 <fail_mailbox_is_readonly>, enable = 0x7ffff76e5a60 <fail_mailbox_enable>, exists = 0x7ffff76e5a70 <fail_mailbox_exists>, open = 0x7ffff76e5e60

dovecot 1.1b16 Feb 19 23:32:41 hill dovecot: IMAP(username): Disconnected for inactivity bytes=29831/872 Feb 19 23:32:41 hill dovecot: IMAP(username): file message-parser.c: line 764 (message_parser_parse_next_block): assertion failed: (ctx->input->eof) Feb 19 23:32:41 hill dovecot: child 60831 (imap) killed with signal 6 # gdb /usr/local/libexec/dovecot/imap imap.60831.hill.core GNU

Hi! I've now seen this assertion failure from lmtp (most frequent), pop3 (next frequent), and imap (rarely). It didn't start happening until the number of accounts on the server was increased into the 10k-25k range. It happens when index->file_lock is a read lock and mail_index_lock is called asking for a write lock. Dovecot 2.x dies at the assertion on line 62 of mail-index-lock.c

Latest from Mercurial. Dovecot crashes with 'mail_log' and 'notify' plugins enabled when deleting a message: [08:22] root spectre:~# gdb /usr/lib/dovecot/imap /tmp/core GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and