search for: norrskenkonsult

...76 Dec 10 15:22 dovecot.index.log -rw------- 1 peter peter 193660 Dec 3 12:50 dovecot.index.log.2 drwx------ 2 peter peter 512 Dec 10 15:06 new drwx------ 2 peter peter 512 Dec 10 15:04 tmp Thanks in advance, Peter -- Peter Lindgren, dataingenj?r E-post: peter "at" norrskenkonsult punkt com http://www.norrskenkonsult.com

...a mail folder .INBOX without cur, new and tmp subfolders, and the .imap.index files were rather old (feb 2006). Is this an old relic from early dovecot versions (I once ran 0.99 on this old server)? Or is it old client software? There are no data in it. TIA, Peter -- Peter Lindgren http://www.norrskenkonsult.com

...auth default { mechanisms = cram-md5 digest-md5 passdb passwd { } userdb passwd { } user = root } I have restarted (SIGTERM) dovecot to be sure that dovecot is restarted. I still run 1.0beta3 on OpenBSD. TIA, Peter -- Peter Lindgren, dataingenj?r E-post: peter "at" norrskenkonsult punkt com http://www.norrskenkonsult.com

...rc/auth/db-ldap.o # find . -name 'db-ldap.*' -print ./src/auth/db-ldap.c ./src/auth/.deps/db-ldap.Po ./src/auth/db-ldap.o I didn't find a db-ldap.h anywhere in /usr either. Any hints? I run OpenBSD 3.7 on sparc. /Peter -- Peter Lindgren, dataingenj?r E-post: peter "at" norrskenkonsult punkt com http://www.norrskenkonsult.com

...the last time I resorted to kill processes but I felt I had missed something... the install page (http://wiki.dovecot.org/BasicInstall) says to kill it, it feels a little crude; no nicer signals to send? Bear with me, please... /Peter -- Peter Lindgren, dataingenj?r E-post: peter "at" norrskenkonsult punkt com http://www.norrskenkonsult.com

...39;s a wiki, is it ok to just edit the pages, or should I post here first? I thought I'd check with Timo and you guys first, maybe I missed that page that describes the signals... If it's ok, I can edit or add a new page. /Peter -- Peter Lindgren, dataingenj?r E-post: peter "at" norrskenkonsult punkt com http://www.norrskenkonsult.com

...server is in production) isn't that delicate, several hours downtime is OK. There's a backup server that can receive any mail I might loose during downtime, which can be copied though IMAP later. Thanks for any input! /Peter -- Peter Lindgren, dataingenj?r E-post: peter "at" norrskenkonsult punkt com http://www.norrskenkonsult.com

...tructure and user names must match between the two systems # * Source dovecot must be at least version 1.0.x # * Destination dovecot must be 1.1.x # * Only dovecot data folders and files are copied, neither dovecot indices nor Sieve scripts etc. # # Originally created by Peter Lindgren <peter at norrskenkonsult.com> # Use this script at your own risk. No warranties whatsoever, of any kind! # Basic settings: The first one you must definitely change, it's where you have mounted the old server's home: SOURCEBASE=/mnt/casiopea-home DESTBASE=/home # Just an abbreviation: MD=Maildir # Change field...

...1.0.rc29 did not store the message size in the file name as later versions. When will Dovecot do the check and rename the files to include the message size? There are some folders with quite large number of messages, the largest is some 45,000 messages. TIA, /Peter -- Peter Lindgren http://www.norrskenkonsult.com

Hi, I'm using Dovecot v1.0.beta5 (NetBSD 3.0, i386) and Mozilla Thunderbird 1.5 (XP, i386). My dovecot.conf is pretty simple, because I just use dovecot for me as the only user. However, when I try to move a 'larger' amount of mails (>200) from my local TB-mbox to the remote IMAPS-storage, the process hangs after about 150 - 160 transferred mails (the 'blocking' mail

...new folder, and then copy the cur folder contents? The files that Dovecot creates in an empty folder have different contents, will Dovecot update them when the user retrieves the mails in that folder? Or, can I just make a symlink to the old Maildir somewhere? Peter -- Peter Lindgren peter at norrskenkonsult.com 0703-393940

Anyone aware of a Web User Interface or GUI to allow users to create simple/common-type sieve scripts? I found the sieve testing and have used it as I play; plus mangesieve (and Net:ManageSieve.pm) but want to allow users to build so some clicking and maybe a little typing and then end up with some filters. So before I go invent this wheel I'd like to know what others are doing? TIA,

Hello, is http://xi.rename-it.nl down? Apticron shows me permanently errors. -- Mit freundlichen Gr??en, with kind regards, Jim Knuth --------- Wenn ein wirklich gro?er Geist in der Welt erscheint, kann man ihn untr?glich daran erkennen, da? sich alle Dummk?pfe gegen ihn verb?nden. (Jonathan Swift)

...old-school, but isn't /etc and /var, respectively, a better default than /usr/local? Should require two new variables in the configure script, though. (and yes, I know I set them with --sysconfdir=/etc --localstatedir=/var --sharedstatestatedir=/var ) /Peter -- Peter Lindgren http://www.norrskenkonsult.com

...on between signed and unsigned passdb-bsdauth.c: In function `bsdauth_preinit': passdb-bsdauth.c:59: warning: implicit declaration of function `auth_cache_parse_key' passdb-bsdauth.c:60: warning: assignment makes pointer from integer without a cast /Peter -- Peter Lindgren http://www.norrskenkonsult.com

http://dovecot.org/releases/1.1/dovecot-1.1.11.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.11.tar.gz.sig Hopefully this v1.1 release will last a few months. - IMAP: PERMANENTFLAGS list didn't contain \*, causing some clients not to save keywords. - dbox: INTERNALDATE and save date was returned wrong for converted maildir files. - auth: Using "username" or

http://dovecot.org/releases/1.1/dovecot-1.1.11.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.11.tar.gz.sig Hopefully this v1.1 release will last a few months. - IMAP: PERMANENTFLAGS list didn't contain \*, causing some clients not to save keywords. - dbox: INTERNALDATE and save date was returned wrong for converted maildir files. - auth: Using "username" or

Hi all, Merging the two large recent threads, my recommendation is as follows: * The Release Candidates for 1.0 should be bug fixes only. * Each new Feature, or a Feature Set, goes in a separate branch. * That branch is tested by those who need/want that feature. * When testing is completed, the branch is merged into the main trunk. This way, we will have fairly well tested features/feature sets