similar to: Test migration (IMAP copy) and INTERNALDATE?

Displaying 20 results from an estimated 1000 matches similar to: "Test migration (IMAP copy) and INTERNALDATE?"

2006 Apr 19
0
[patch] Re: Test migration (IMAP copy) and INTERNALDATE?]
I haven't been able to find what is responsible for altering the time on APPENDed mail, but was able to come up with a temporary workaround ... simply calling utime() later on in the process resolves it. Below is my patch. Steve --- dovecot-1.0.beta7-orig/src/lib-storage/index/maildir/maildir-save.c 2006-03-25 05:53:43.000000000 -0500 +++
2008 Mar 06
4
Wrong message information reported shortly after delivery
Hi, If an IMAP fetch is issued some "short" time after a message was delivered with dovecot deliver then dovecot reports wrong (zero) values for that new message. Afterward, it reports the information OK. This causes problems to our IMAP client. The problem is easily reproduced with a large message on a slow machine. I'm using dovecot 1.0.10 Here's a sample trace: 1 uid fetch
2017 Sep 13
2
What INTERNALDATE does dovecot with mbox storage set on a COPY'd message?
>>>>> Aki Tuomi <aki.tuomi at dovecot.fi>: > On 09.09.2017 12:33, Steinar Bang wrote: >> When a message is copied to a folder on dovecot with mbox storage, is >> the mtime of the saved mbox file set to the time of the save? [snip!] > Internaldate is picked from the separating 'From' line in mbox file. > "From user at example.org Thu Oct 20
2017 Sep 09
2
What INTERNALDATE does dovecot with mbox storage set on a COPY'd message?
When a message is copied to a folder on dovecot with mbox storage, is the mtime of the saved mbox file set to the time of the save? Or is the mtime set to the Date: field of the source message that is saved? If there is a difference in the behaviour, do someone know the dovecot version number where the change happened? The reason I'm asking is a problem reported on the Gnus imap client in
2008 Nov 26
1
INTERNALDATE call, timezone randomly changes
Hi guys, I've run into an odd little problem. We use SquirrelMail as the basis for our webmail. Recently I've had a user complaining that the "Received" time on mail in the Sent folder has changed between logins. The change is always been by +1 hours or -5 hours. While checking, our developer had a time changed by +2 hours. On refresh it changed back. He poked through the code
2005 Feb 13
2
dovecot-stable: NIL from in envelope request
Using the latest dovecot-stable (20050213) with pine, I get an empty "from" header in my e-mails. This doesn't happen with 1.0.59-test, nor did it happen with the first dovecot-stable (20050131). A partial connection log is below: 1.0-test59: IMAP DEBUG 15:23:32 2/13: 00000007 FETCH 1:41 (UID ENVELOPE BODY.PEEK[HEADER.FIELDS (Newsgroups Content-MD5 Content-Disposition
2008 Jul 16
4
changing INTERNALDATE or similar
I have a question which others must have encountered. I switched from uw-imap to dovecot-imap a few months ago and moved my fairly large mail archive (~15 yrs) by simply mounting both accounts in a mail app and simply copying my folders over. This worked well, and all my mail is in order when I view it in evolution or thunderbird on any number of machines. However, since our company uses MS
2004 Mar 07
1
imap internaldate
I think I found a bug in dovecot which I'm not sure where to fix. (I may even have found a reference to it in an archived list message from Jul 2003.) Here is the situation: dovecot (dovecot-0.99.10.4) running with an imap server on an mbox system is queried by a local client program, like Mail.app, and is told the "Received" date of the message (presumably sent through
2015 Jun 30
4
Outlook 2013 not fetching new mail/synchronization issues
Hi all, Robert, Jerry, There were new emails overnight and both Thunderbird and Roundcube displayed them. I enabled Outlook debug mode and please find 2 logs of Send/Receive with no new emails. Scroll below to see 3rd log with "workaround" and mails downloaded. "Intializing connection [1C7E2830] IMAP: 08:53:03 [db] Setting internal codepage to 1200 IMAP: 08:53:03 [db]
2020 May 25
3
child killed by signal 6
Hello, from time to time I keep getting problems with some emails causing signal 6. I've already reported those, but it seems not to be easy to find the cause. From the logs, it seems to occur in sieve implementation. I've checked the email envelopes tody by accident, probably this part of my telnet session might help: a11 fetch 1 all * 1 FETCH (RFC822.SIZE 16750 INTERNALDATE
2005 Feb 28
3
Dovecot response to "FETCH" command
Hi folks. I just converted my site from UW+mbox to dovecot+maildir (stable-test59, 2005/02/25). For the most part, everything is great. The server seems faster and less memory intense than the UW server (this part has made me very happy). And it's definitely more user friendly to me than Courier. There is one thing however... A few of my users are using the web based mail reader
2009 Jul 21
1
Problem with INTERNALDATE when the year in localtime and GMT different
In my thought utc_offset function in src/lib/utc-offset.c returns wrong offset value when the year in localtime and GMT different. /* max offset of 24 hours */ if (ltm.tm_yday < gtm.tm_yday) offset = -24 * 60; else if (ltm.tm_yday > gtm.tm_yday) offset = 24 * 60; else offset = 0; I think this code should be modified as followings. /* max offset of 24 hours */ if ((ltm.tm_year ==
2017 Sep 11
0
What INTERNALDATE does dovecot with mbox storage set on a COPY'd message?
On 09.09.2017 12:33, Steinar Bang wrote: > When a message is copied to a folder on dovecot with mbox storage, is > the mtime of the saved mbox file set to the time of the save? > > Or is the mtime set to the Date: field of the source message that is > saved? > > If there is a difference in the behaviour, do someone know the dovecot > version number where the change
2017 Sep 14
0
What INTERNALDATE does dovecot with mbox storage set on a COPY'd message?
On 13.09.2017 23:59, Steinar Bang wrote: >>>>>> Aki Tuomi <aki.tuomi at dovecot.fi>: >> On 09.09.2017 12:33, Steinar Bang wrote: >>> When a message is copied to a folder on dovecot with mbox storage, is >>> the mtime of the saved mbox file set to the time of the save? > [snip!] >> Internaldate is picked from the separating 'From'
2007 Sep 02
4
IMAP: Disconnected: BUG: Unknown internal error (Dovecot 1.0.3)
Hi, I am getting the following error in the server mail logfile: > Sep 2 18:39:44 h648123 dovecot: IMAP(<account>)(<PID>): Disconnected: BUG: Unknown internal error (mail_debug is on, but there is not really much context for this in the log file, ie. no log events for several minutes, and then it appears, all of a sudden). On the client side, it looks like this (with some
2015 Jan 14
1
Questions regarding imaptest
Hi, The measurements were created under the following conditions : ? operating system : Red Hat Enterprise Linux Server release 6.6 (Santiago) kernel in version 2.6.32-504.el6.x86_64 ? virtual server (VMware) with an Intel(R) Xeon(R) 4vCPU E5649 x 2,526 GHz (2 cores per virtual socket) and 4 GB RAM ? 7,200 RPM SATA 1TB (FC SAN IBM System Storage N3400) ? all file systems had been formated in
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
2014 Feb 20
1
dovecot with maildir not using mtime on reindex
Hi. It seems that dovecot is using the current time, not a maildir file's mtime for INTERNALDATE when a message is re-indexed: $ cd Index $ rm -rf .INBOX $ cd ../Maildir/cur $ stat * File: `1392914632.P54451Q0M08633.smtpin01,S=2215,W=2249:2,' Size: 960 Blocks: 8 IO Block: 1048576 regular file Device: 36h/54d Inode: 11132959 Links: 1 Access: (0600/-rw-------)
2020 May 25
1
child killed by signal 6
On 25/05/2020 12:06, Aki Tuomi wrote: >> On 25/05/2020 13:00 Peter Nabbefeld <peter.nabbefeld at gmx.de> wrote: >> >> >> Hello, >> >> from time to time I keep getting problems with some emails causing >> signal 6. I've already reported those, but it seems not to be easy to >> find the cause. From the logs, it seems to occur in sieve
2006 Jun 08
8
Trash expire plugin
Dovecot will soon have a plugin which allows running a nightly cronjob to expunge mails from configured mailboxes which have been in there for a configurable amount of time. For example the configuration could be: plugin { # Trash 7d, Spam 30d expire = Trash 7 Spam 30 } It also supports using Dovecot's lib-dict to keep track of the mailboxes and their oldest mail's timestamp, so that