Very good news. Thank you for the great work you are doing.
I'll update to this version.

On Wed, Jun 4, 2008 at 10:52 AM, Bas van der Vlies <[EMAIL PROTECTED]> wrote:
>
> 2008-05-30
>    * Fixed debian control file. Package can be build on any platform
> and
>      not only on i386 platforms:
>
>      Author: Christian Iversen ci add sikkerhed dot org
>      Applied by: Bas van der Vlies
>
>    * We now use the trac configuration parser routine
>      Author: andrei2102 add gmail dot com
>      Applied by: Bas van der Vlies
>
>    * Added new command line option -n/--dry-run. This option only show
>      what commands will be executed.
>      Author: Bas van der Vlies
>
>    * the default values for tickets can now also be set in
>     'email2trac.conf'. So you can use different values when an email
>      is converted to a ticket. The ticket value is set to this rules
>       - email2trac.conf
>       - trac.ini
>
>      email2trac.conf use same format as trac.ini, eg email2trac.conf:
>        [project]
>        default_component : test
>
>      closes request #55, for more info see:
>      - https://subtrac.sara.nl/oss/email2trac/wiki/
> Email2tracConfiguration
>
>       Requested by: greg dot deakyne at etapestry dot com
>       Implemented by: Bas van der Vlies
>
>    * Fixed a bug in ticket_update. It failed when project did not have
>      ticket component field,  closes bug #62
>      Reported by: gernot dot hillier add siemens dot com
>      Fixed by: Bas van der Vlies
>
>    * run_email2trac.c:
>       - can no longer segfault after a failed malloc.
>       - after set*id failure, you'll get a diagnostic (or at least
>         nonzero exit status) and it won't attempt the exec.
>
>      Author: Jim Meyering jim add meyering dot net
>      Applied by: Bas van der Vlies
>
>   * Made some approvements to spam function:
>       - If the he X-Spam-Score header is present, but has no value
>          email2trac will crash, closes #63
>
>       - Added config option which header field we must check
>         for determing if mail is Spam, eg:
>          - spam_header : X-Spam-Level (default: X-Spam-Score)
>
>      Author: email2trac at bulk dot squeakyblue dot com
>      Applied by: Bas van der Vlies
>
>    * black_list  is now a configuration option and is used to deny
>      email addesses, default value is: MAILER-DAEMON@
>
>      Can specifiy more then one email adress seperated by ',', eg:
>      black_list : [EMAIL PROTECTED], [EMAIL PROTECTED]
>
>      closes #39, #56
>
>      Author: Bas van der Vlies
>
>    * if mailto_link + german umlaut problem is fixed, closes #60
>      Reported by: alex at pirsig dot net
>      Fixed by: Bas van der Vlies
>
>
>
> ========= Info about the package
>
> https://subtrac.sara.nl/oss/email2trac
>
> the latest stable email2trac package is available from:
>                 ftp://ftp.sara.nl/pub/outgoing/email2trac.tar.gz
>
> email2trac - utilities
> ----------------------
>
> This is a release of the SARA package email2trac that contains utilities
> that we use to convert emails to trac tickets. The initial setup was
> made
> by Daniel Lundin from Edgewall Software. SARA has extend the initial
> setup,
> with the following extensions:
>
>      - HTML messages
>      - Attachments
>      - Use commandline options
>      - Config file is used to control the behaviour of the email2trac
>        software
>      - Unicode support for special characters in the headers of an
> email
>        message
>      - Ticket updates via mail
>
> Comments or Suggestions mail them to:
>        email2trac <[EMAIL PROTECTED]>
>
> http://www.sara.nl for more info about SARA.
>
>
> --
> Bas van der Vlies
> [EMAIL PROTECTED]
>
>
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to