[pkg-horde] Bug#538066: ingo1 "Source" filter produces bad maildrop filter lines

[David Ehle]

Package: ingo1
Version: 1.2-1
Severity: important



-- System Information:
Debian Release: 5.0.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages ingo1 depends on:
ii  horde3                   3.2.2+debian0-2 horde web application framework

Versions of packages ingo1 recommends:
ii  php5-imap          5.2.6.dfsg.1-1+lenny3 IMAP module for php5

Versions of packages ingo1 suggests:
ii  imp4                          4.2-4      webmail component for horde framew
pn  php-net-sieve                 <none>     (no description available)

-- no debconf information

Hello,
This may have been addressed upstream, but it appears that the Destination
and Source filter on choices in Ingo produce lines similar to this:
##### sourcetest #####
if( \
   /^From,Sender,Reply-to,Resent-from:\s*.*user at host\.some\.domain\.edu/:h \
)
exception {
   to "${DEFAULT}/.ttt/"
}

The syntax /^From,Sender,Reply-to,Resent-from:  while "legal" appears to be
trying to match that string literally rather than anything in the list.

This means that it basically just doesn't work.
I saw some traffic on the INGO1 mailing list about a similar problem for the
"Destination" filter choice having the same problem. From the look of it
both Destination and Participant are both effected in the Debian/Lenny
release:

46: ##### fromtest #####
 47: if( \
 48:    /^From:\s*.*ehle at agni\.phys\.iit\.edu/:h \
 49: )
 50: exception {
 51:    to "${DEFAULT}/.ttt/"
 52: }
 53: 
 54: ##### desttest #####
 55: if( \
 56:    /^To,Cc,Bcc,Resent-to:\s*.*user at some\.domain\.edu/:h \
 57: )
 58: exception {
 59:    to "${DEFAULT}/.ttt/"
 60: }
 61: 
 62: ##### New Rule #####
 63: if( \
 64:
 /^To,Cc,Bcc,Resent-to,From,Sender,Reply-to,Resent-from:\s*.*user at host\.domain/:h
 /\
 65: )
 66: exception {
 67:    to "${DEFAULT}/.ttt/"
 68: }

If there is an upstream patch, could it be integrated into the debian
package and the package made availabe?

If this will need to wait till the next debian release, can you provide
assistance in fixing the problem in a way that will not overwritten the next
time I upgrade ingo1 with aptitude?

Thanks!!