The mailing list for listmasters using Sympa

[address@concealed]

During our migration to Sympa, I have noticed some messages being sent with
their subject lines cut off. The symptom was sympa would properly place the
SUBJECT TAG (basically the name of the group), but all other SUBJECT
information would disappear. Subject lines that should read:

[somegroup] hello world

would instead read:

[somegroup

The message would be correctly saved in the archive with the subject line
intact. In fact, when I clicked SEND MESSAGE BACK TO POSTMASTER on a message
known to have been improperly transmitted, the postmaster account would 
receive
a mangled message as described above.

When I upgraded from 5.1 to 5.1.2 this morning, everything appeared to work
properly except now, instead of a mangled subject, that "bad" message doesn't
arrive at all!

The logs record the message being processed by sympa:

Nov  7 08:52:51 mailgroups sympa(command)[4270]: Processing web message for
address@concealed 
Nov  7 08:52:52 mailgroups sympa(command)[4270]: Message for
address@concealed sent 

sendmail indicates it was sent:

Nov  7 09:04:38 mailgroups wwsympa[4318]: [robot mailgroups.nami.org] [client
10.0.0.9] [user address@concealed] [list comm] do_
send_me : list comm, yyyy 2005, mm 11, msgid
address@concealed 
Nov  7 09:04:38 mailgroups wwsympa[4318]: [robot mailgroups.nami.org] [client
10.0.0.9] [user address@concealed] [list comm] sen
d_me: looking for address@concealed in
/address@concealed/2005-11/arc
txt 
Nov  7 09:04:38 mailgroups wwsympa[4318]: [robot mailgroups.nami.org] [client
10.0.0.9] [user address@concealed] [list comm] do_
send_me message /address@concealed/2005-11/arctxt/1
spooled for address@concealed 
Nov  7 09:04:38 mailgroups wwsympa[4318]: [robot mailgroups.nami.org] [client
10.0.0.9] [user address@concealed] [list comm] do_
arc(2005-11, ) 
Nov  7 09:04:38 mailgroups sympa(command)[4270]: Processing web message for
address@concealed 
Nov  7 09:04:38 mailgroups sympa(command)[4270]: Message for
address@concealed sent 

our Exchange 2003 server indicates it was received (note, timestamps will not
be in synch. This example is from a later test):

005-11-07 14:29:14 38.250.129.132 mailgroups.nami.org SMTPSVC1 NAMIMAIL
38.250.129.240 EHLO - +mailgroups.nami.org 250 297 24 0 SMTP
2005-11-07 14:29:14 38.250.129.132 mailgroups.nami.org SMTPSVC1 NAMIMAIL
38.250.129.240 MAIL - +From:<address@concealed> 250 50 47 0 SMTP
2005-11-07 14:29:14 38.250.129.132 mailgroups.nami.org SMTPSVC1 NAMIMAIL
38.250.129.240 RCPT - +To:<address@concealed> 250 32 29 0 SMTP
2005-11-07 14:29:14 38.250.129.132 mailgroups.nami.org SMTPSVC1 NAMIMAIL
38.250.129.240 DATA -
+<address@concealed> 250 142 3447 62
SMTP
2005-11-07 14:29:14 38.250.129.132 mailgroups.nami.org SMTPSVC1 NAMIMAIL
38.250.129.240 QUIT - mailgroups.nami.org 240 66 4 0 SMTP

But no message arrives. "regular" messages from other archives that were
properly transmitted to begin with are still properly transmitted to
postmaster.

I'm hoping the upgrade to 5.1.2 has fixed this weird subject problem so it
doesn't happen, but if it hasn't been fixed that means the next user who
triggers it will end up with a message that doesn't go anywhere. My bunch
treats e-mail as slightly MORE important than oxygen, so this is definitely a
worrisome situation.

Please let me know if I need to include more information. This is a repeatable
bug, so if more log info is needed or testing required I can provide that.
Thanks in advance for any help you can provide!

SYMPA.CONF:
============
###\\\\ Directories and file location ////###

## Directory containing mailing lists subdirectories
home    /home/sympa/expl

## Directory for configuration files ; it also contains scenari/ and 
templates/
directories
etc     /home/sympa/etc

## File containing Sympa PID while running.
## Sympa also locks this file to ensure that it is not running more than once.
Caution : user sympa need to write access without special privilegee.
pidfile /home/sympa/sympa.pid

## Umask used for file creation by Sympa
umask   027

## Directory containing available NLS catalogues (Message 
internationalization)
localedir       /home/sympa/locale

## The main spool containing various specialized spools
## All spool are created at runtime by sympa.pl
spool   /home/sympa/spool

## Incoming spool
queue   /home/sympa/spool/msg

## Bounce incoming spool
queuebounce     /home/sympa/spool/bounce

###\\\\ Syslog ////###

## The syslog facility for sympa
## Do not forget to edit syslog.conf
syslog  LOCAL1

## Communication mode with syslogd is either unix (via Unix sockets) or inet
(use of UDP)
log_socket_type unix

## Log intensity
## 0 : normal, 2,3,4 for debug
log_level       0

###\\\\ General definition ////###

## Main robot hostname
domain  mailgroups.nami.org

## Listmasters email list comma separated
## Sympa will associate listmaster privileges to these email addresses (mail
and web interfaces). Some error reports may also be sent to these addresses.
# was listmaster address@concealed
listmaster      address@concealed

## Local part of sympa email adresse
## Effective address will be [EMAIL]@[HOST]
email   sympa

## Default lang (cs | de | el | en_US | fr | hu | it | ja_JP | nl | oc | pt_BR
| tr)
lang    us

## Who is able to create lists
## This parameter is a scenario, check sympa documentation about scenarios if
you want to define one
create_list     public_listmaster

## Sympa commands priority
sympa_priority  1

## Default priority for list messages
default_list_priority   5

## Secret used by Sympa to make MD5 fingerprint in web cookies secure
## Should not be changed ! May invalid all user password
cookie  491243852

## The default maximum size (in bytes) for messages (can be re-defined for 
each
list)
max_size        5242880

## Specify which rfc2369 mailing list headers to add
# was rfc2369_header_fields ARRAY(0x9906844)
rfc2369_header_fields   help,subscribe,unsubscribe,post,owner,archive

## Specify header fields to be removed before message distribution
# was remove_headers ARRAY(0x9906874)
remove_headers 
Return-Receipt-To,Precedence,X-Sequence,Disposition-Notification-To

###\\\\ Errors management ////###

## Bouncing email rate for warn list owner
bounce_warn_rate        30

## Bouncing email rate for halt the list (not implemented)
## Not yet used in current version, Default is 50
bounce_halt_rate        50

## Task name for expiration of old bounces
expire_bounce_task      daily

## Welcome message return-path
## If set to unique, new subcriber is removed if welcome message bounce
welcome_return_path     owner

## Remind message return-path
## If set to unique, subcriber is removed if remind message bounce, use with
care
remind_return_path      owner

###\\\\ MTA related ////###

## Path to the MTA (sendmail, postfix, exim or qmail)
## should point to a sendmail-compatible binary (eg: a binary named 'sendmail'
is distributed with Postfix)
sendmail        /usr/sbin/sendmail

## Maximum number of recipients per call to Sendmail
nrcpt   25

## Max. number of different domains per call to Sendmail
avg     10

## Max. number of Sendmail processes (launched by Sympa) running 
simultaneously
## Proposed value is quite low, you can rise it up to 100, 200 or even 300 
with
powerfull systems.
maxsmtp 40

###\\\\ Pluggin ////###

## Path to the antivirus scanner engine
## supported antivirus : McAfee/uvscan, Fsecure/fsav, Sophos, AVP and Trend
Micro/VirusWall
# antivirus_path        /usr/local/uvscan/uvscan

## Antivirus pluggin command argument
# antivirus_args        --secure --summary --dat /usr/local/uvscan

###\\\\ S/MIME pluggin ////###

## Path to OpenSSL
## Sympa knowns S/MIME if openssl is installed
# was openssl 
openssl /usr/bin/openssl

## The directory path use by OpenSSL for trusted CA certificates
# was capath 
capath /etc/pki

##  This parameter sets the all-in-one file where you can assemble the
Certificates of Certification Authorities (CA)
cafile  /home/sympa/bin/etc/ca-bundle.crt

## User CERTs directory
ssl_cert_dir    /home/sympa/expl/X509-user-certs

## Password used to crypt lists private keys
# key_passwd    your_password

###\\\\ Database ////###

## Database type (mysql | Pg | Oracle | Sybase)
## be carefull to the case
# was db_type 
db_type mysql

## Name of the database
db_name sympa

## The host hosting your sympa database
db_host localhost

## Database user for connexion
db_user [user]

## Database password (associated to the db_user)
## What ever you use a password or not, you must protect the SQL server (is it
a not a public internet service ?)
db_passwd       [password]

## Database private extention to user table
## You need to extend the database format with these fields
# db_additional_user_fields     age,address

## Database private extention to subscriber table
## You need to extend the database format with these fields
# db_additional_subscriber_fields       billing_delay,subscription_expiration

###\\\\ Web interface ////###

## Sympa's main page URL
wwsympa_url     http://mailgroups.nami.org/sympa

css_path /home/sympa/css/style.css
css_url http://mailgroups.nami.org/sympa/css/style.css

#colors
color_4 #000066
color_6 #FF9912
#color_6 #FFFFFF
#color_9 #FFFFFF

#commands turned off
misaddressed_commands ignore

#antivirus
antivirus_path  /usr/local/bin/clamscan
antivirus_args  --stdout

#forking
distribution_mode fork

#max SMTP processes
maxsmtp 500

============
GROUP CONFIGURATION 
(This is the group whose archive holds the mangled message)
============

visibility noconceal

review private

reply_to_header
apply forced
value sender

default_user_options
reception html
visibility noconceal

web_archive
access private

serial 3

subject comm./marketing 

subscribe owner

send privateoreditorkey

status open

available_user_options
reception html,mail,nomail,txt

clean_delay_queuemod 15

rfc2369_header_fields archive,help,owner,post,subscribe,unsubscribe

owner
reception mail
profile privileged
email address@concealed

archive
period year
access owner

unsubscribe open_notify

topics national

update
email address@concealed
date 04 Nov 2005 at 15:52:36
date_epoch 1131137556

custom_subject comm