Thanks to Mimi for the answers, they do fit perfectly with what I have discovered.
I never made the mistake of expecting Chandler 1.x to be a full-featured e-mail client, but it *is* hard for me (personally) to shake off just one learnt behaviour: * the Apple Mail 'Sent' collection as an IMAP repository for all things sent. In an ideal world I periodically aim to clear this Sent collection, to move each message to an appropriate hierarchy, but it doesn't happen. Without hierarchies: I have grown to dislike the Google Mail approach, which prevents or discourages users from creating/nesting mailboxes. In a Google Mail flatness, it's not sufficiently easy for me to: * find what I require * filter out what's not required * weed. As the mass of stored mail increases, so the ease decreases. Now, to Chandler: only time will tell whether as the mass of things (notes) increases, I remain pleased with Chandler's suitability. My gut feeling is that it will scale very well without becoming complicated. In terms of scope, I have been hesitant about using any Chandler Desktop feature that inovlves Out/SMTP, mainly because of few bugs relating to IMAP (some of which are peculiar to my situation). The recent caladmin-l discussion 'Vacations causing attendees calendar to be blocked', and this image http://n2.nabble.com/file/n2117914/Chandler_IA_18.png (copied from <http://chandlerproject.org/pub/Projects/NutshellCartoons/Chandler_IA.pdf>) will probably be my springboard to appreciating e-mail in Chandler Desktop. Regards Graham -- View this message in context: http://n2.nabble.com/Get-started%3A-get-email-into-Chandler%3A-discrepancies-noted%2C-help-required-tp1690157p2117914.html Sent from the Chandler users mailing list archive at Nabble.com. _______________________________________________ [email protected] mailing list unsubscribe here: http://lists.osafoundation.org/mailman/listinfo/chandler-users Chandler wiki: http://chandlerproject.org/wikihome
