$Cambridge: hermes/src/prayer/docs/TODO,v 1.30 2004/11/26 14:13:19 dpc22 Exp $

Short term
===========

Confirm on expunge.

Do something about "a@b, ,c@d" addresses: need to spot INVALID_ADDRESS
and .SYNTAX.ERROR. 

Trying switching off TCP_LINGER as load experiment.
  DONE. DONE forgot that you have done this in case of problems!

Concurrent logins caused by impatient users hitting "Login" twice:
  Possible to isolate?

Page select on list screen should work if you just hit return. Either:
  Split into two separate forms (slightly messy because of current code
  structure).

  Hack cmd_aggregate_tmp to do something if no messages selected and
  page number is != expected value --> probably a better solution.

Clive McDowell patches.

Folder upload/download to Windows box -> CRLF translation

Address book import should cope with QP encoding for comments, addresses.

Better handling for TEXT/PLAIN and TEXT/HTML: download option would be good.
  See message from Robert Whittaker <rjw62@cam.ac.uk> via HelpDesk
    Date: Wed, 28 Jan 2004 12:09:47 +0000
    Subject: Ref 83106: text/plain attachments and hermes webmail

X-Cam-SpamScore should be config option.

Add new iostream stuff to accountd.

saved-messages2 error page

Reflector for /session//compose
  - if can't connect to login session, frontend should bounce back a
    page which contains the structure of the message (with a fairly long
    timeout), so that people can cut and paste text.

  - should just be a case of looking up header fields, laying out message.

Make password change failures more obvious.

Management only interface (e.g: webmail.hermes.cam.ac.uk/manage)

Preference to disable spellchecking for quoted text
  (should be easy with recent versions of ispell).

Javascript on login page to select Login box.

Kiosk mode. (Disable HTML, links on frontend and messages.).

Document prayer_cyclog.

Things causing core dumps that I can't reproduce
================================================

Addressbook bugs reported by in207 (messages via helpdesk received on
07/04/2003 and 14/04/2003).
   - Duplicate items in addressbook
   - Alias Eili vanishes.

Include can cause crash. Binary data maybe?
  - or cancel button?

  Seems okay. Try with IE.

Transfer upload -> inbox broken?

Experiment with browser back button some:
  at least one bug there in combination with list/display. [caching?]

Compose/Resume bug?

Long term wish list
===================

Include X-Cam-Spam-Score information on header output?
  - I don't really see the advantage of doing this.

Include random machine from list as POST target on login screen

Addressbook import:
  Need way to replace existing abook.

Import Entourage addressbooks (CSV?)

Pick login host at random on login screen.

Make Prayer work with Cyrus server
  (including default configuration with dual use mailboxes as futureproofing)

Better prefs file format?

Charsets: Should support UTF-8 as well as ISO-8859-1. (ISO-8859-X, X > 1)?
  - What happens with RFC1522 encoding in abook entries!
  - need to record abook entries with encoding, decode only on display!
  - Propose: use GNU iconv to cast everything which isn't ISO-8859-1 to
    16 or 32 bit Unicode and work with that as multibyte characters.
  - decode actually reasonably straightforward. Only real complication is
    Unicode aware line wrap algorithmns

Implement "cid:" URLs. (See message from Vince dated 03/07/2002 for details).

Better handling for NUL characters (esp when displaying msgs please!)

Do better job of replying/forwarding HTML msgs:
  Look at how Pine processes HTML.

Directory lookup and manipulation (want LDAP?)

Pine style remote addressbook support for Pine <-> Prayer sharing.
 - Import/Export Hermes Pine addressbook 
 - IMSP addressbook support?

Move to received mail folder.

Antiword: Look at IMP

Remove attachments from message a la Pine

Addressbook sorting

cja13 suggests:

  I keep my mail in folders with one folder for each person or organisation I 
  deal with. In each person's folder I store all correspondence with them, 
  received and sent. On Pine, I was able to set up (a) that the default fcc 
  folder was the one for the person I was writing to (b) that the default 
  save (copy) folder was the one for the person I had received from. This 
  made operating my file system extremely easy as these rules covered most 
  normal correspondence.

Prev/Next links on message screen should skip over deleted messages
(user option?)

Code cleanups
=============

Encrypt session URLs?

Stop people logging in multiple times somehow?

Merge os_*.c?

Page substitition:
  Redirect URL cache so that browser history can work even with page
  substitution enabled. Otherwise remove page substiution nonsense entirely.
