Your message dated Sat, 14 Mar 2009 17:33:36 +0100
with message-id <[email protected]>
and subject line fixed in 2.1.12-1
has caused the Debian Bug report #310180,
regarding mailman produces duplicated MIME-Version: 1.0 headers
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
310180: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=310180
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mailman
Version: 2.1.5-8
Severity: normal

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

On multipart/... messages which mailman puts in a multipart/mixed
container to append its footer, the MIME-Version: 1.0 header is
repeated, so that the resulting email contains two MIME-Version headers.

I'm 90% positive that the MIME RFCs specify that there should be only 1
such headers; somebody subscribing to one of my lists discovered the
problem because INN apparently rejects such messages when the mailing
list is gated to a newsgroup (I agree that this violates the 'be
liberal in what you accept' thingy.)

cheers
- -- vbi

- -- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (700, 'testing'), (600, 'unstable'), (60, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.10
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages mailman depends on:
pn  apache | httpd                           Not found.
ii  cron                        3.0pl1-86    management of regular background p
ii  debconf                     1.4.30.13    Debian configuration management sy
ii  libc6                       2.3.2.ds1-21 GNU C Library: Shared libraries an
ii  logrotate                   3.7-3        Log rotation utility
ii  postfix [mail-transport-age 2.1.5-9      A high-performance mail transport 
ii  pwgen                       2.03-1       Automatic Password generation
ii  python                      2.3.5-2      An interactive high-level object-o
ii  ucf                         1.17         Update Configuration File: preserv

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: get my key from http://fortytwo.ch/gpg/92082481

iKcEARECAGcFAkKQWq1gGmh0dHA6Ly9mb3J0eXR3by5jaC9sZWdhbC9ncGcvZW1h
aWwuMjAwMjA4MjI/dmVyc2lvbj0xLjUmbWQ1c3VtPTVkZmY4NjhkMTE4NDMyNzYw
NzFiMjVlYjcwMDZkYTNlAAoJEIukMYvlp/fWaNcAnRX+Gj6AcXM6C8jX2js4PcpC
7KMQAKDJmcgEgco3yzN5kCLG/Wouj3uVYA==
=9L8T
-----END PGP SIGNATURE-----


--- End Message ---
--- Begin Message ---
Version: 1:2.1.12-1

Hi,

I believe this to be fixed in the recent 2.1.12-1 upload, but it was not 
mentioned in the changelog.


cheers,
THijs

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---

Reply via email to