Announcements of new sympa release

[Aumont - Comite Reseaux des Universites <>]

Pleased to announce sympa-3.4 as the conclusion of multiple 3.3.6bX
versions. This version as a long release note compared to last release
3.3.5 and we strongly recommend this upgrade.

Now sympa-4.0 start !

Here are some precision about what should Sympa 4.0 look like.
You are probably waiting for some other features and it's now
time for you to explain your wishes in  ! Your
feed back is important to make priority in Sympa project.


- Data source
   . Remove "user_data_source" list parameter : a database will be
     required, subscription will be possible even if external
     subscribers are defined (with include_xxx).
   . Bounce management will be possible for any email adress even
     external subscribers
   . Cache for external subscriber will be stored in the database
     (growing db files no more used)
   . Cache update is performed by task manager

- Remote include : using https Sympa will be able to include
    lists from remote server (allready in 3.4)

- Interface html style : rewrite html interface style for
  both better ergonomic and pretty interface.

- New template editor wwsympa tool will used to translate or
  customize web templates.

- Merge sympa.conf and wwsympa.conf in a single file.

- SOAP server deamon for integrating Sympa with other applications

- Bounce
    .More automatic bounce managment (auto-deletion).
    .Distribution should start with users without bounce. When sending
     message to bouncing users, Sympa could use a "unique_return_path"
     and "return receipt" header.
    .It should also call sendmail with the appropriate option just
     to copy message in queue.

- Shared :
    .notification and moderation of new upload.
    .Move subdirectories
    .show/hide "expert commands"
    .New e-vote tool

- Meta-list : instentiation of new lists on the fly

- Allow to parse message as template for each subscriber if
  needed.

- Rename list on web interface.

- alternative email stored in user database

- user contextual information on the web interface :
  exemple :

     Last visit October 10th 2pm
     1 new list in topic XX
     5 new mail in YY archive
     2 mails to moderate in list ZZ

- Error management : scenario will set vars in order to
  parse the message or html page error (display the reason
  why to requested action is refused).

- List and Archive expiration

- Manage duplication while ditributing a message to multiple
  lists (that should be usefull for new release announce ;-)

Serge & olivier