similar to: 1.0-test80

Displaying 20 results from an estimated 10000 matches similar to: "1.0-test80"

2005 Aug 23
2
Weird internaldate behavior with 1.0-test80 and mbox folder
Has anyone else encountered weird date behavior with mbox-style folders? I am nearly ready to bite the bullet and convert my UW imap hierarchy (which is in mbx format) to Dovecot. In so doing, I need to convert each UW-specific mbx-format mailboxes to the more portable mbox format, which Dovecot can read. (This is done with the 'mbxcvt' utility that's part of UW.) I am then
2018 Mar 21
0
Race condition when setting flags (\Deleted) + expunge quickly, leaving mails not deleted
Thank you for your thorough report, we'll look into it. Aki On 20.03.2018 16:56, Tomas Forsman wrote: > Hello. > > I seem to have found a race condition, when setting flags on multiple emails > rapidly. 5 commands including login to reproduce. Problem found using mutt in > real world usage. > > Seems to happen both with UID STORE 1:3 and UID STORE 1,2,3 .. > > I
2018 Apr 22
1
Race condition when setting flags (\Deleted) + expunge quickly, leaving mails not deleted
On 21 March, 2018 - Aki Tuomi wrote: > Thank you for your thorough report, we'll look into it. Has anyone managed to reproduce this (using my transcript for example)? With mutt, I get this problem.. If I set 'imap_pipeline_depth=0' in .muttrc, I can't seem to reproduce it anymore. /Tomas -- Tomas Forsman, stric at cs.umu.se, http://people.cs.umu.se/stric/ `- SysAdmin at
2005 Jul 12
1
1.0-test77
http://dovecot.org/ It's hot in here. Something like 25-30c for many days now. My brains don't work in that heat. So, this is still not an 1.0-alpha1. I'll put it out when I think the release will actually be fully working :) Changes since test76: - Fixes to FETCHing MIME body parts, especially with message/rfc822 attachments. We hadn't been handling this entirely correctly
2018 Mar 20
2
Race condition when setting flags (\Deleted) + expunge quickly, leaving mails not deleted
Hello. I seem to have found a race condition, when setting flags on multiple emails rapidly. 5 commands including login to reproduce. Problem found using mutt in real world usage. Seems to happen both with UID STORE 1:3 and UID STORE 1,2,3 .. I have tried with the following packages, with a minimized config in a throwaway vm: https://packages.debian.org/stretch/dovecot-core Package:
2010 May 01
1
My dovecot does not store Thunderbird flags
Hi all, my Dovecot 1.1.20 does not store flags (I mean, Thunderbird Labels like ToDo, Important and so on..) When logging in via telnet, I get: . examine INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft NonJunk $MDNSent Junk $Forwarded NotJunk receipt-handled $Label7 $label1 $label2 $label3 $label4 $label5 expired_2w expired_2m delete rimandata forwarded) * OK [PERMANENTFLAGS ()]
2017 May 24
0
[imaptest] Explaining errors
On 23 May 2017, at 12.10, aduprat <aduprat at linagora.com> wrote: > > Hi, > > I'm an Apache James committer and we are curious to use imaptest in order to validate our IMAP protocol implementation. > I'm using the nightlybuild : imaptest-20170506 > > > I follow the examples given in the /T/ /est IMAP server compliancy/ examples
2005 Jun 30
6
1.0-test75 and roadmap for v1.0
http://dovecot.org/test/ Keywords are finally stored in maildir filenames and listed in "dovecot-keywords" file. It should be possible to just rename 0.99.x's .customflags file to dovecot-keywords (but it can't be renamed back after modification). Also fixed another uid/sequence mixup bug with setting keywords in general (in mbox too). Fixed SHA1 checksum generation with
2005 Aug 16
0
test80: in production, occasional assert
Timo, Test-80, running on our production IMAP server. Setup: Solaris 9, compiled with gcc 4.0.1, mbox format, configured like so: VERSION=test80 CC=gcc CFLAGS="-g -O" CPPFLAGS=-I/opt/openssl/include LDFLAGS=-L/opt/openssl/lib \ ./configure --prefix=/opt/dovecot.$VERSION --with-ssl=openssl \ --with-ssldir=/opt/openssl/ssl --with-rawlog --enable-debug > configure.out Still seeing
2005 Sep 10
0
"$default_mail_env/cur" not found with passwd-file authentication on v1.0-test80
hi all, i've built dovecot: Sep 09 18:04:24 Info: Dovecot v1.0-test80 starting up on OSX 10.4.2. in addition to pgsql auth, which is working 4 me, i'd like to step-by-step verify simple passwd-file authentication/testing. unfortunately, i'm having a problem with the login process NOT FINDING the ".../cur" dir. here are the details .... my config includes: ...
2003 Aug 04
0
Windows 2000 Bug in GMT +/- n Timezones (PR#3644)
Tracking down this bug was joint work with Jermoe Asselin (jerome at hivnet.ubc.ca) and Patrick Connolly (p.connolly at hortresearch.co.nz). We collectively were able to determine that this is a problem in Windows 2000 but not in Linux. Timezones of the form GMT-5, GMT+3, etc. do not work properly in Windows 2000 for nearby dates in daylight savings time although they do work for nearby dates
2005 Aug 16
2
test80: assert/core debug info
Timo, Attached is gdb information from core dumps related to the following assert in test-80: IMAP(username): file mbox-sync-update.c: line 442 (mbox_sync_update_header_from): assertion failed: (ctx->mail.uid == 0 || ctx->mail.uid_broken || ctx->mail.uid == mail->uid) My setup: Solaris 9, mbox format. test-80 compiled with gcc 4.0.1 using the following configure options: CC=gcc
1999 Jan 06
0
FW: SUGGESTION: allow TZ to be specified at time of mount (PR#124 25)
Dear John, >Samba fully honours Unix timezone info. All my sites run their Linux hardware clocks >set at GMT. Under Red Hat Linux, or Caldera, SuSE, or PHT TurboLinux, the Linux >"timeconfig" command can be used to do this. The timezone for the server is >selected appropriately I ran timezone and found it had hardware clock set to GMT and TZ set to GB. Setting TZ to GMT had
1998 Dec 04
1
timezones not properly reflected on timestamps of files
I have read the documentation, performed the diagnostic tests, checked the archives, so if the answer is there, please accept my apologies in advance and simply direct me. I am running redhat Linux 2.0.3 and using smbmount to mount several directories from NT3.51 servers which are distributed gloablly in different timezones. Once mounted the files all have local timestamps which makes syncing
2000 Jun 06
0
Fw: Time Synchronisation
Thank you very much, it was the setting on the RS6000. Whoever originally setup our box didn't specify the BST time offset correctly. The system was reading TZ=GMT0BST0,M3.5.0,M10.5.0 Thanks to everyone that contributed to solving a simple and obvious error !!!! :) Mike ________________________________________________________________________________________ >From "John Ryan"
2009 May 11
1
inconsistent results for axis.POSIXct
Some time ago, I posted a note about what I considered to be a bug in axis.POSIXt() for R 2.8.x, relating to whether timezones in the data are obeyed on the axes. A link to that note, and to a quick and helpful response, is at the following URL http://www.nabble.com/patch-for-axis.POSIXct-%28related-to-timezones%29-td22338700.html#a22338700 Note that R 2.9.0 has been adjusted to help with
2005 Jul 08
1
add inotify support to dovecot
Hi, attached patch against test76 adds inotify support and the --with-notify=... configure option that defaults to the current check for dnotify using no special method if dnotify cannot be compiled, and can be set to none, dnotify and inotify. If it is set to dnotify or inotify, failure to compile a test program results in an error. Also, it adds | file change notification method ..... :
2003 Jul 31
4
timezones
I have some questions and comments on timezones. Problem 1. # get current time in current time zone > (now <- Sys.time()) [1] "2003-07-29 18:23:58 Eastern Daylight Time" # convert this to GMT > (now.gmt <- as.POSIXlt(now,tz="GMT")) [1] "2003-07-29 22:23:58 GMT" # take difference > now-now.gmt Time difference of -5 hours Note that the difference
2005 Aug 22
2
Re: Dovecot inotify problem
Hi Reuben, I hope you don't mind me copying the dovecot list again. > dovecot: Aug 21 04:08:22 Error: IMAP(reuben): inotify_rm_watch() failed: > Invalid argument Odd. > This is with a 2.6.13-rc6-mm1 release. I've posted to LKML because there is > also a kernel stack produced at one point which looks inotify related (but the > messages above are contant). > See
2018 Aug 05
1
Assertion failure with IMAP NOTIFY
Hi, For a few weeks I've been running a custom notification script[1] that uses IMAP NOTIFY. The script uses a single connection, sets up a NOTIFY watch on a couple of mailboxes + automatic FETCH for the selected mailbox. If a status update arrives for a different mailbox, it selects that box and fetches the mail. Today I got the following error in the log: > Aug 5 14:56:12 karif