Right, Now that clients aren't going to be sending any more cheques, time and sanity are converging so I finally get time to do some housekeeping and development.
I had a look at the current road-map, unless somebody else plans to, the X-DBMail-PhysMessageID looks straightforward enough for one of my inabilities, especially as I need to figure gmime out properly anyway. The other thing I was thinking about which doesn't appear on the road-map or discussion list a mechanism for delivering system messages to the user. Shoot me if it exists, I haven't been able to look at the code for many months. What I see as needed is a mechanism which begins with an administrator inserting a message into a bulletins table. This is then delivered once to each user upon connection. This would require another hook in the POP3 and IMAP daemons to check for bulletins that require delivery, and then include that in the messages to be downloaded. This hook could also then be used to address the problem of warning users near their quota, or indeed users who have exceeded their quota. For pop3d, this should be straightforward enough to append the virtual message to the list of available messages and ensure that RETR, DELE etc. know what is real, and what isn't. Conceptually though, the bulletin should probably be prepended, as presumably it is of import - "You're all fired...". IMAP is a different kettle of potatoes however. First off, I've never used it, so my thinking is quite fuzzy here. With POP3, you assume the user has/will read the bulletin once the RETR command has been received. You them mark that user as having seen that bulletin, and don't give it to them again. Also, with pop3d (I assume), the list of messages is generated at the start of the session, so new messages which arrive don't appear until the next session. With IMAP however, you're dealing on a client level, so you can know when they've actually read the message. Therefore it strikes me that that is exactly what it should be, and would also mean things like SORT etc. don't require awareness of 'virtual' messages. This does though re-introduce the absurdity of filling up people's quotas with quota warnings. I'm assuming imapd is constantly doing new SELECTs, and that working around virtual messages would be over elaborate. Can someone help my thinking on this, especially with IMAP? -- Feargal Reilly, Codeshifter, Chrysalink Systems. ICQ: 109837009 | YIM/AIM: ectoraige | MSN: [EMAIL PROTECTED] PGP Key Id: 0xE9D33740 (expires 22-Nov-2005) Visit http://ie.bsd.net/ - BSDs presence in Ireland.
pgpTB03yJyjI8.pgp
Description: PGP signature
