From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/5301 Path: news.gmane.org!not-for-mail From: =?iso-8859-1?q?Lars_Tobias_B=F8rsting?= Newsgroups: gmane.emacs.gnus.user Subject: Re: Gnus is losing IMAP articles Date: Wed, 06 Jul 2005 17:00:55 +0200 Organization: Norwegian university of science and technology Message-ID: <8jfk6k4c72w.fsf@alpakka.stud.ntnu.no> References: <4nmzp1dnh1.fsf@lifelogs.com> <8jf8y0kdruo.fsf@alpakka.stud.ntnu.no> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1138671047 26892 80.91.229.2 (31 Jan 2006 01:30:47 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 31 Jan 2006 01:30:47 +0000 (UTC) Original-X-From: nobody Tue Jan 17 17:35:05 2006 Original-Path: quimby.gnus.org!newsfeed.gazeta.pl!newsfeed.pionier.net.pl!newsfeed.gamma.ru!Gamma.RU!newsfeed.icl.net!newsfeed.fjserv.net!news.tele.dk!news.tele.dk!small.news.tele.dk!uninett.no!ntnu.no!not-for-mail Original-Newsgroups: gnu.emacs.gnus Original-NNTP-Posting-Host: alpakka.ntnu.no Original-X-Trace: orkan.itea.ntnu.no 1120662055 32025 129.241.56.34 (6 Jul 2005 15:00:55 GMT) Original-X-Complaints-To: usenet@itea.ntnu.no Original-NNTP-Posting-Date: Wed, 6 Jul 2005 15:00:55 +0000 (UTC) User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (usg-unix-v) Cancel-Lock: sha1:rsa8ktoGOn5w2R6R8bcYtkRQmE0= Original-Xref: bridgekeeper.physik.uni-ulm.de gnus-emacs-gnus:5443 Original-Lines: 18 X-Gnus-Article-Number: 5443 Tue Jan 17 17:35:05 2006 Xref: news.gmane.org gmane.emacs.gnus.user:5301 Archived-At: Edi Weitz writes: > Well, certainly not Exchange because I use Courier on a Linux server > as my IMAP server. How could I find out what the UIDVAILIDITY value > is and if it is wrong? Oh, right, I confused you with Christian Lynbech which uses Exchange. Sorry'bout that. In Courier you can find the UIDVALIDITY value in every maildir folder in the uiddb file called "courierimapuiddb". It is the second field in the first line of the file. But Courier handles this correctly, so the problem lies not with Courier. -- Regards, Lars Tobias