Guaranteed way to cause uidvalidity problem

[Bryan Ischo <bischo@plumbdesign.com>]

Hi.  I have found a repeatable way to cause the uidvalidity problem.

Today I added the following line to my .gnus:

(setq gnus-outgoing-message-group "nnimap:INBOX.Sent")

The Sent folder already contains 1300+ sent emails from when I was
using Netscape as my mail client.

Now when I send a new mail, I get a gcc: line that works well - it
causes the mail to also be put into my Sent folder.  However, the
following then always occurs:

I go to my Sent folder and do a M-g to get new messages.  There is
1 new message.  I read the message, then q to exit the group.  Then
I type M-g on the Sent folder again, and I get a warning that
the folder is not uidvalid.  I can fix this using the previous
suggestion of gnus-group-clear-data and then G-p and removing the
uidvalidity clause, and then everything is fine with that group,
until I send another email, and then the process repeats.

These uidvalidity issues are the most frustrating part of using
nnimap with gnus.  Does anyone have any suggestions at all for
fixing this problem?

The server is Courier IMAP, and it seems to change uidvalidity much
more frequently than other servers.  How can we make nnimap deal with
uidvalidity changes gracefully?

Thank you, and best wishes,
Bryan

p.s. Ironic, but this email itself will cause me uidvalidity grief
since it is being gcc:'ed to my Sent folder ...

-- 
________________________________________________________________________
        
        p l u m b d e s i g n 
 
        Bryan Ischo | Software Developer 
        157 chambers st ny ny 10007
        p.212-285-8600 x233 f.212-285-8999