similar to: False "new mail" warning from Thunderbird, using RC23

Hello, Very sorry for disturbing you that much, don't know if I will be able to work on NHW next months... As usual for those interested, I have released the NHW v0.3.0-rc23 new version. I continue to fine-tune the nhw_kernel weights.This new version has then more precision and a better visual quality. More at: https://nhwcodec.blogspot.com/ Cheers, Raphael -------------- next part

http://dovecot.org/releases/dovecot-1.0.rc23.tar.gz http://dovecot.org/releases/dovecot-1.0.rc23.tar.gz.sig Documentation is probably the only important thing left before v1.0. * deliver doesn't ever exit with Dovecot's internal exit codes anymore. All its internal exit codes are changed to EX_TEMPFAIL. * mbox: X-Delivery-ID header is now dropped when saving mails. * mbox: If

http://dovecot.org/releases/dovecot-1.0.rc23.tar.gz http://dovecot.org/releases/dovecot-1.0.rc23.tar.gz.sig Documentation is probably the only important thing left before v1.0. * deliver doesn't ever exit with Dovecot's internal exit codes anymore. All its internal exit codes are changed to EX_TEMPFAIL. * mbox: X-Delivery-ID header is now dropped when saving mails. * mbox: If

Just updated one of my proxy boxes to the latest nightly (20070217), restarted the dovecot process and got a bit of errors showing up for each pop3/imap connection. Feb 19 11:14:00 marbella dovecot: pop3-login: Login: user=<user1 at host.com>, method=PLAIN, rip=209.33.217.218, lip=204.17.177.60 Feb 19 11:14:00 marbella dovecot: POP3(user1 at host.com): Set pop3_uidl_format in config file

Feb 27 14:17:46 wurfel dovecot: imap-login: Login: user=<USER>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Feb 27 14:17:46 wurfel dovecot: IMAP(USER): file mbox-sync-update.c: line 387 (mbox_sync_update_header): assertion failed: (ctx->mail.uid != 0 || ctx->pseudo) This is happening for dozens of users. Anyone have a suggestion of what to adjust? It was happening somewhat

I had our production systems running on rc23, however we ran into problems when the server was under heavy load. Eventually, the server would begin to freeze all imap connection after authentication (according to the logs). A user would connect, authentication would succeed, and then the connection would sit until timing out. No error logs were produced. Upgrading to rc24 did not

http://dovecot.org/nightly/dovecot-latest.tar.gz Would be nice to get some testing before the actual release. I've now finally gone through all the "TODO" mails in this list and my INBOX and fixed pretty much every problem I know of. There are still some mbox bugs, but I can't really get them fixed unless someone figures out how to reproduce them

As in subject, if you for instance create a simple passwd-file with: test at domain.tld:{plain}pass:20000:10::/home/regular/.test::userdb_mail=maildir:%h/maildir Dovecot (rc23 & 27) will expand %h to empty string, and try to make a directory under / Mar 14 14:25:28 rasengan dovecot: IMAP(test at domain.tld): mkdir(/maildir/cur) failed: Permission denied Mar 14 14:25:28 rasengan dovecot:

I've not been able to roll out rc23 yet (tonight, I hope) but I just saw a crash which I'm not sure I've seen reported before, following a server outage (that is to say, the server came back up and one of the users had a dovecot core). #0 0x0005d720 in mail_cache_transaction_reset (ctx=0xcf928) at mail-cache-transaction.c:71 No locals. #1 0x0005e8bc in mail_cache_add

Hi all, I've installed rc23 in a new testing machine, and i've had some permission problems related to dovecot-master.conf. As I have my master passwords in that file, I don't want it to be world readable. dovecot -n shows that auth_user is nobody, so setting the permissions to nobody.whatever 640 solves the problem. Anyway, I've tried to change the auth_user setting with no

I updated to the latest rc25 and started getting these messages(over and over again). This is on a Solaris 10 box and I tried compiling with gcc and sun c. I backed down to rc23 and the messages went away and everything works. Any body have an idea on what could be wrong? thank you dovecot: Mar 04 21:14:33 Error: child 467 (imap) killed with signal 6 dovecot: Mar 04 21:14:33 Error:

Hi, I have an Asterisk 1.2.9.1 box on a Debian distro with mISDN drivers. I installed the new driver (0.3.1-rc30) on our pbx but since no voice was passing I decided to go back to old version (0.3.1-rc23). Last friday everything seemed to work fine but now every incoming call drops after 3-4 seconds while Asterisk console is showing these messages: Apr 23 12:42:39 DEBUG[7625]:

Hi, I have an Asterisk 1.2.9.1 with chan_misdn 0.3.1-rc23 and a beronet octoBRI on a Debian box I have to set up instead of an old legacy PBX. My problem is I get only the base DNID and not the extensions (the last two digits) in Asterisk but the old PBX got all the DNID number so I think it is the card. Is there anybody experiencing a problem like this? How can I solve it? Any ideas? TIA

Patch: http://dovecot.org/list/dovecot-cvs/2007-February/007760.html Nightly snapshot should be ready in a few minutes. I'll release rc23 tomorrow. Night. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL:

i use last dovecot rc23 with users/passwords in mysql 1) How can i define a sql query for each auth mechanism ? 2)Why i can't set "default_pass_scheme = login" in my dovecot-sql.conf? : dovecot: Feb 21 09:46:22 Info: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=127.0.0.1 rip=127.0.0.1 resp=AGFkaUBhZHJpYW4uZXUAcGFyb2xh dovecot: Feb 21

Hi all, I'm in my final steps with my testing server using rc23 in a x86 RHEL4 machine. Everything is working quite well, but still are some LDAP related issues I'd like to clarify: - I'm using auth_bind and auth_bind_userdn. So pass_filter isn't used, and pass_attrs are never searched. Is this true or am I missing something? - Is there a choice for the userdb bind/queries

Hi. I'm having problems with chan_mISDN configuration. Line "echotraining=yes" causes warning, when Asterisk is parsing misdn.conf and I'm confused why the PBX doesn't accept the setting. No matter which section I try to offer it, it is always invalid or out of range. The setting itself is supposed to be valid, it is in the sample configuration file of chan_mISDN 0.3.1.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, for testing I have different filesystems on various block devices, which I mount on /mnt/mailcache as needed; however, the indexes and caches are located on /var/cache, hence, they get out of sync easily. No offense. Hoever, the web page (http://dovecot.org/bugreport.html) states that every signal 11 is a bug and will be fixed, so here it

I am using Donlp2 package to solve a non-linear problem, but there's an error I always meet: Error in matrix(unlist(value, recursive = FALSE, use.names = FALSE), nrow = nr, : attempt to set an attribute on NULL I have been suffering from this bug for a long time. I'll be very grateful if somebody could help me -_- -- View this message in context:

R 0.63.2, compiled using SGI cc and f90 on Irix 6.5 gives: > is.na(NA) [1] TRUE # OK > is.na(c(1,NA)) [1] FALSE FALSE # expected FALSE TRUE > is.nan(NaN) [1] FALSE # expected TRUE > is.nan(1/0) [1] FALSE # ditto The above functions work correctly for R compiled with gcc and g77 on an Irix 6.2 system. The Irix 6.5 release notes