- dovecot - dovecot.org

Re: [Dovecot] Expunge is not expunging unless it is called twice
by Bill Boebel 03 May '06

03 May '06

On Tue, May 2, 2006 18:21, Timo Sirainen <tss(a)iki.fi> said: > > Dovecot is requiring two "expunge" calls before it deletes an email. It just >> seems to ignore the first expunge call, leaving the email file in the maildir cur/ >> folder. Any idea why? I even waited 10 seconds after setting the Deleted flag, >> but still the first expunge call did nothing.... > > Fixed now. > I have tested this and works now. Thanks, Bill

1 0

[Dovecot] help server crash
by Luis Atala 03 May '06

03 May '06

chek this out how can i fix this pple? http://channels.debian.net/paste/2475 http://channels.debian.net/paste/2476 pls i need help

3 11

[Dovecot] dovecot, procmail, postfix & SpamAssassin working together
by Paul Matthews 03 May '06

03 May '06

Hi there, i'm trying to get dovecot, procmail, postfix & SpamAssassin working together http://www.linuxquestions.org/questions/showthread.php?t=441062 But i'm not having a lot of luck, a question about dovecot, what kind of mail box am i using? mbox? if so does anyone know if procmail can use mbox? /etc/dovecot.conf protocols = imap pop3 imap_listen = [::] pop3_listen = [::] imaps_listen = pop3s_listen = log_path = /var/log/dovecot.log login = imap login = pop3 default_mail_env = mbox:/home/CATHEDRAL/%u/mail:INBOX=/var/spool/mail/%u auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = pam auth_user = root -- Paul Matthews I.T Trainee | The Cathedral School Ph (07) 47222 194 | Fax (07) 47222 111 PO Box 944 Aitkenvale Q 4814 E: paul.matthews(a)cathedral.qld.edu.au W: www.cathedral.qld.edu.au Anglican coeducation | Day and Boarding | Early Childhood to Year 12 Educating for life-long success **************************************************************************** **************************************************************************** *********************************** IMPORTANT NOTICE REGARDING CONFIDENTIALITY This electronic email message is intended only for the addressee and may contain confidential information. If you are not the addressee, you are notified that any transmission, distribution or photocopying of this email is strictly prohibited. The confidentiality attached to this email is not waived, lost or destroyed by reasons of a mistaken delivery to you.

2 1

Re: [Dovecot] FreeBSD 6 - DirectAdmin - dovecot
by Floris van den Berg 03 May '06

03 May '06

Jim Trigg schreef: > On Tue, May 2, 2006 1:27 pm, Floris van den Berg wrote: > >> Jim Trigg schreef: >> >>> On Tue, May 2, 2006 10:45 am, Floris van den Berg wrote: >>> >>> >>>> Jim Trigg schreef: >>>> >>>> >>>>> On Tue, May 2, 2006 1:15 am, Floris van den Berg wrote: >>>>> >>>>> >>>>> >>>>>> Since version 1.0 I experience strange problems with dovecot. At the >>>>>> moment I have beta 7 installed. I use FreeBSD 6.0. >>>>>> >>>>>> * Pop3 works >>>>>> * Imap works, but only when i telnet to localhost >>>>>> * In all other cases I can't connect to the server. Tried with >>>>>> squirrelmail, uebimau and thunderbird. Squirrelmail after a long >>>>>> time >>>>>> waiting: "ERROR: Connection dropped by IMAP server." >>>>>> >>>>>> >>>>> What happens if you try to telnet to the imap port other than >>>>> localhost? >>>>> >>>>> >>>>> >>>> Hi, that works too. It didn't work before because i didn't properly >>>> disable the firewall. >>>> >>>> >>> Do the mail clients work now, then, or do we need to keep >>> troubleshooting? >>> >>> >> Webmail still doesn't work. Other clients however do work. >> I still have no clue what's wrong :( >> > > Actually, here are all of my imap-related entries from Squirrelmail's > config.php -- what is different in your setup? > > $imapServerAddress = 'localhost'; > $imapPort = 143; > $imap_server_type = 'other'; > $imap_auth_mech = 'login'; > $use_imap_tls = false; > No difference. It's getting weirder and weirder. 1) imap works fine when i connect to this dovecot from a remote client (e.g. thunderbird or scripts provided above) 2) everything works fine when i use the troubled box and connect to a remote dovecot server, using telnet and the scripts provided above. 3) the scripts above do work when used with localhost but they are extremely slow. It takes about 1,5 to 2 minutes to complete just to perform a login/logout sequence. Seems to be something wrong with connecting to localhost on that port. Can't pinpoint what it is. Oh by the way, results do not differ when the firewall is enabled or disabled. Floris

1 0

[Dovecot] Dovecot-1.0.beta7 Build Fedora 3 Error REMOVE
by Luke Jackson 03 May '06

03 May '06

Sorry about the double post and I did search google but it didn't provide me with the information i needed. You can delete the last 2 posts I was forced to use google as I was not receving emails from the list at ljackson at luteck.com Thanks for your help hope to be more informed next time I post. -Luke

1 0

[Dovecot] Dovecot-1.0.beta7 Build Fedora 3 Error
by Luke Jackson 03 May '06

03 May '06

Hello I'm attempting to configure Dovecot with mysql support so I'm able to have a single database of users and point both postfix and dovecot to this db. I currently have an rpm src that I have download and placed in my RPMBUILDROOT of my linux box. Next I configured the .spec file and attempted to run a rpmbuild -bb Near the end of the install phase I receive an error which has me stumped. I ran rpmbuild again and used the -bi --short-circuit options and logged the output for you to see. Any help would be greatly appreciated..... rpmbuild -bi --short-circuit dovecot-fc5.spec Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.44599 Making install in src make[1]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src' Making install in lib make[2]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib' make[3]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib' make[3]: Nothing to be done for `install-exec-am'. make[3]: Nothing to be done for `install-data-am'. make[3]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib' make[2]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib' Making install in lib-dict make[2]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-dict' make[3]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-dict' make[3]: Nothing to be done for `install-exec-am'. make[3]: Nothing to be done for `install-data-am'. make[3]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-dict' make[2]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-dict' Making install in lib-sql make[2]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-sql' make[3]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-sql' make[3]: Nothing to be done for `install-exec-am'. make[3]: Nothing to be done for `install-data-am'. make[3]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-sql' make[2]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-sql' Making install in lib-ntlm make[2]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-ntlm' make[3]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-ntlm' make[3]: Nothing to be done for `install-exec-am'. make[3]: Nothing to be done for `install-data-am'. make[3]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-ntlm' make[2]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-ntlm' Making install in lib-settings make[2]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-settings' make[3]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-settings' make[3]: Nothing to be done for `install-exec-am'. make[3]: Nothing to be done for `install-data-am'. make[3]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-settings' make[2]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-settings' Making install in lib-charset make[2]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-charset' make[3]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-charset' make[3]: Nothing to be done for `install-exec-am'. make[3]: Nothing to be done for `install-data-am'. make[3]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-charset' make[2]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-charset' Making install in lib-mail make[2]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-mail' make[3]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-mail' make[3]: Nothing to be done for `install-exec-am'. make[3]: Nothing to be done for `install-data-am'. make[3]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-mail' make[2]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-mail' Making install in lib-imap make[2]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-imap' make[3]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-imap' make[3]: Nothing to be done for `install-exec-am'. make[3]: Nothing to be done for `install-data-am'. make[3]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-imap' make[2]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-imap' Making install in lib-index make[2]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-index' make[3]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-index' make[3]: Nothing to be done for `install-exec-am'. make[3]: Nothing to be done for `install-data-am'. make[3]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-index' make[2]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-index' Making install in lib-storage make[2]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage' Making install in index make[3]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage/index' Making install in maildir make[4]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage/index/maildir' make[5]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage/index/maildir' make[5]: Nothing to be done for `install-exec-am'. make[5]: Nothing to be done for `install-data-am'. make[5]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage/index/maildir' make[4]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage/index/maildir' Making install in mbox make[4]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage/index/mbox' make[5]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage/index/mbox' make[5]: Nothing to be done for `install-exec-am'. make[5]: Nothing to be done for `install-data-am'. make[5]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage/index/mbox' make[4]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage/index/mbox' Making install in dbox make[4]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage/index/dbox' make[5]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage/index/dbox' make[5]: Nothing to be done for `install-exec-am'. make[5]: Nothing to be done for `install-data-am'. make[5]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage/index/dbox' make[4]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage/index/dbox' make[4]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage/index' make[5]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage/index' make[5]: Nothing to be done for `install-exec-am'. make[5]: Nothing to be done for `install-data-am'. make[5]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage/index' make[4]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage/index' make[3]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage/index' Making install in subscription-file make[3]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage/subscription-file' make[4]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage/subscription-file' make[4]: Nothing to be done for `install-exec-am'. make[4]: Nothing to be done for `install-data-am'. make[4]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage/subscription-file' make[3]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage/subscription-file' Making install in register make[3]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage/register' make install-am make[4]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage/register' make[5]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage/register' make[5]: Nothing to be done for `install-exec-am'. make[5]: Nothing to be done for `install-data-am'. make[5]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage/register' make[4]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage/register' make[3]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage/register' make[3]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage' make[4]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage' make[4]: Nothing to be done for `install-exec-am'. make[4]: Nothing to be done for `install-data-am'. make[4]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage' make[3]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage' make[2]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-storage' Making install in lib-auth make[2]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-auth' make[3]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-auth' make[3]: Nothing to be done for `install-exec-am'. make[3]: Nothing to be done for `install-data-am'. make[3]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-auth' make[2]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/lib-auth' Making install in auth make[2]: Entering directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/auth' /bin/sh ../../libtool --mode=link --tag=CC gcc -std=gnu99 -O2 -g -march=i386 -mcpu=i686 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -I/usr/kerberos/include -o dovecot-auth auth.o auth-cache.o auth-client-connection.o auth-master-connection.o auth-master-listener.o auth-module.o auth-request.o auth-request-handler.o auth-stream.o auth-worker-client.o auth-worker-server.o db-ldap.o db-sql.o db-passwd-file.o main.o mech.o mech-anonymous.o mech-plain.o mech-login.o mech-cram-md5.o mech-digest-md5.o mech-ntlm.o mech-gssapi.o mech-rpa.o mech-apop.o passdb.o passdb-blocking.o passdb-bsdauth.o passdb-cache.o passdb-ldap.o passdb-passwd.o passdb-passwd-file.o passdb-pam.o passdb-checkpassword.o passdb-shadow.o passdb-vpopmail.o passdb-sql.o userdb.o userdb-blocking.o userdb-ldap.o userdb-passwd.o userdb-passwd-file.o userdb-prefetch.o userdb-static.o userdb-vpopmail.o userdb-sql.o libpassword.a ../lib-settings/libsettings.a ../lib-ntlm/libntlm.a ../lib-sql/libsql.a ../lib/liblib.a -lcrypt -lpam -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lresolv -lldap -L/usr/lib/mysql -lmysqlclient -lz -lm -export-dynamic -ldl gcc -std=gnu99 -O2 -g -march=i386 -mcpu=i686 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -I/usr/kerberos/include -o dovecot-auth auth.o auth-cache.o auth-client-connection.o auth-master-connection.o auth-master-listener.o auth-module.o auth-request.o auth-request-handler.o auth-stream.o auth-worker-client.o auth-worker-server.o db-ldap.o db-sql.o db-passwd-file.o main.o mech.o mech-anonymous.o mech-plain.o mech-login.o mech-cram-md5.o mech-digest-md5.o mech-ntlm.o mech-gssapi.o mech-rpa.o mech-apop.o passdb.o passdb-blocking.o passdb-bsdauth.o passdb-cache.o passdb-ldap.o passdb-passwd.o passdb-passwd-file.o passdb-pam.o passdb-checkpassword.o passdb-shadow.o passdb-vpopmail.o passdb-sql.o userdb.o userdb-blocking.o userdb-ldap.o userdb-passwd.o userdb-passwd-file.o userdb-prefetch.o userdb-static.o userdb-vpopmail.o userdb-sql.o -Wl,--export-dynamic libpassword.a../lib-settings/libsettings.a ../lib-ntlm/libntlm.a ../lib-sql/libsql.a ../lib/liblib.a -lpam -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lldap -L/usr/lib/mysql /usr/lib/mysql/libmysqlclient.a -lcrypt -lnsl -lc -lnss_files -lnss_dns -lresolv -lz -lm -ldl make[2]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src/auth' make[1]: Leaving directory `/usr/src/redhat/BUILD/dovecot-1.0.beta7/src' RPM build errors: /BUILD/dovecot-1.0.beta7/src/lib/sha1.c:233: first defined here /usr/bin/ld: Warning: size of symbol `sha1_result' changed from 190 in ../lib/liblib.a(sha1.o) to 126 in /usr/lib/mysql/libmysqlclient.a(sha1.o) collect2: ld returned 1 exit status make[2]: *** [dovecot-auth] Error 1 make[1]: *** [install-recursive] Error 1 make: *** [install-recursive] Error 1 error: Bad exit status from /var/tmp/rpm-tmp.44599 (%install) Bad exit status from /var/tmp/rpm-tmp.44599 (%install) Thanks, -m3

1 0

[Dovecot] "0" quota and Maildir++
by Apps Lists 03 May '06

03 May '06

Hi Timo. I saw the "0" quota should be interpreted as unlimited in the ChangeLog from yesterday's snapshot. I just tested and it's still seeing zero as zero. I am unable to append any messages. Can you double-check this feature? Thanks! Steve

2 2

[Dovecot] Unoffical Survey - What MTA/Spam filtering do you use?
by Marc Perkel 03 May '06

03 May '06

I like this unofficial survey of hardware but wondering what MTA and spam filtering everyone is using. I do front end spam filtering for other servers as well. (junkemailfilter.com) I'm using Exim 4.61 SpamAssassin 3.11 Some version of DSpam that I'm experimenting with Most of my spam filtering happens on the Exim level. My mail spam filter server is: AMD 3800 Dual Core Athlon 2 100gb SATA drives 4 gigs ram 64 bit Fedora Core 4 2 backup servers on higher MX recored that are similar configuration.

18 38

[Dovecot] timeout_remove and "Timeout leak" problems
by David Friedlander 03 May '06

03 May '06

Hello, I have run into troubles trying to jump from 1.0alpha5 (basically running smoothly) to 1.0beta5 and/or beta7. I am seeing errors such as the following set for nearly every user. dovecot: May 01 16:21:02 Info: IMAP(joeuser): Disconnected: Logged out dovecot: May 01 16:21:02 Error: IMAP(joeuser): file ioloop.c: line 153 (timeout_remove): assertion failed: (*timeout != NULL) dovecot: May 01 16:21:03 Info: IMAP(joeuser): Disconnected: Logged out dovecot: May 01 16:21:03 Warning: IMAP(joeuser): Timeout leak: 0x111acc dovecot: May 01 16:21:03 Error: child 20607 (imap) killed with signal 6 (INBOX is on local RAID disks while home directory (hence, ~/Maildir) is on a NetApp NFS file server.) While I tweaked settings for the differences between the 1.0a5 conf file and the beta conf file, things are fundamentally the same between them. The other critical element to this is that imap-login sessions are being left around and the load average climbs inexorably. (It reached 50 on this dual dual-core machine before I killed things off and started the daemon from scratch.) This occurs for users using a whole array of clients: Thunderbird, SquirrelMail, Eudora, Apple Mail, etc. How can I track this down or can someone please help me figure out what is happening here? (I have been unable to find answers between the mailing list archives and Google.) Thanks in advance, David P.S. The only item of note from examining ioloop.c was the differences between the alpha and beta source code: alpha5: void timeout_remove(struct timeout *timeout) { i_assert(timeout != NULL); timeout->destroyed = TRUE; } beta7: void timeout_remove(struct timeout **timeout) { i_assert(*timeout != NULL); (*timeout)->destroyed = TRUE; *timeout = NULL; }

2 1

[Dovecot] Re: mail shown throught outlook, shows todays date
by richs＠whidbey.net 03 May '06

03 May '06

> bclark wrote: > > > The interesting thing is, once I have some mail on the dovecot, > the date > > displayed on Mozilla is correct, but the mail shown throught > outlook, > > shows todays date (thats for all mail). > > Each mail has (at least) two dates : the date it was sent (stored > in the > headers), and the date it arrived (in Maildir, the date of the > file). Most > likely, Mozilla and SquirrelMail are showing the date in the > headers, and Outloo > is showing the arrival date. > > This problem has come up a few times, I believe. As I recall, most > mail clients > allow you to select which date to sort by. If you can't find the > option, it may > be somewhere in this list's archives. > > > Almost seems as Outlook (office 2000) looks at the date / time > stamp of > > the file it self as opposed to opening and reading the mail and > reading > > the necassry tags. > > That's my assessment, also. > > > If anyone could help me understand this (is this a dovecot issue), I > > would really appreciate it. > > I don't believe it's a dovecot issue, per se. > > -- > Curtis Maloney > cmaloney <at> cardgate.net I've been testing Dovecot 1.0beta7 to implement IMAP for the first time, and have had a good experience so far. But like Curtis and Brent, I found that Outlook and Outlook Express display "incorrect" dates on messages uploaded via APPEND. That's because they sort messages using INTERNALDATE: wea3 SELECT "Test Folder" pqng UID FETCH 1:* (UID FLAGS RFC822.SIZE BODY.PEEK[HEADER] INTERNALDATE) Some have created scripts to sync file timestamps with "Date" headers, which conflicts with the concept of "INTERNALDATE". Others ask users to add the "Date Sent" column, but those dates are only revealed after a message is viewed. I'd like to propose the attached patch to add an optional "outlook- dates" IMAP workaround, which returns the message "Date:" even when INTERNALDATE is specified. Since "BODY.PEEK" is being called anyway, our tests didn't reveal any performance impact. Can anyone think of a scenario this would negatively impact? Another option might be to patch the APPEND function? Thanks! Rich Sandberg richs(a)whidbey.net

4 7