James A Baker wrote: > On Monday, Aug 4, 2003, at 08:36 US/Central, DY wrote:
> I'm not sure this is going to do what you want -- because I'm not > really sure what you want, since Courier doesn't present the filenames > (or any date information in them) to the clients, at least not AFAIK. > Anyway... Are you sure that's what you are trying to fix though? Like I > said, I don't think Courier passes that information (from the filename) > on to any clients. I believe it only passes on 2 types of date > information: a) the INTERNALDATE property of the message (which should > be when it arrived anyway, but might get changed in some situations) > and which Courier stores in the modification time of the file (not the > filename), and b) the date strings embedded in the message itself. > > So, I actually don't see how this is going to help your situation. > Maybe a more precise description of what behavior you *are* seeing, and > what you'd *like* to see instead, would help someone come up with a > more useful suggestion. 'Cause I don't think this is really what you're > looking for either. Well, it seems that courier-imap presents threads to the client in the order of the filenames. So if you move a message that starts a thread into a another folder and back this thread will be shown as the first thread, even if there are threads that were started after this message arrived. This might be also a client problem in sorting the threads, but renaming the message file changes the sorting. Cheers, Juri ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
