public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Singer <steven.singer@csr.com>
To: bluez-users@lists.sourceforge.net
Cc: "Desai, Keyur Rajnikant" <kdesai@mail.smu.edu>
Subject: [Bluez-users] Mailing list gateway corrupting messages (was: L2CAP connectionless)
Date: Tue, 17 Feb 2004 15:47:59 +0000	[thread overview]
Message-ID: <403237AF.5030501@csr.com> (raw)
In-Reply-To: <38F76B90B82C0A4A822651EACE4FF8E9C23322@s31xs2>

We're getting messages from Keyur Desai blocked by our corporate
filters. One such message was titled "L2CAP connectionless" and was
sent on 16th of February. A direct link is:

http://sourceforge.net/mailarchive/forum.php?thread_id=3903638&forum_id=1883

I've also appended an edited version to the end of this message.

The problem appears to be that the original mail message was sent in
MIME Base64 encoding (no problem there - it's completely legal), however,
the mailing list gateway is appending text to the end (the usual SF.net
advert and mailing list info). Since the text is appended to the end of
a Base64 section, mail clients are intepreting it as Base64 encoded data.
Since the data has not been Base64 encoded this results in the message
appearing to contain lots of garbage characters. This is what trips up
our corporate filters.

Netscape and Outlook both show a lot of garbage characters at the end
of the message. More tellingly, Sourceforge's own web list interface
(the link I gave above) also shows some garbage characters (though it
gives up after three).

A colleague also reports a similar problem with MIME quoted-printable
messages. The Sourceforge appended text also contains equals signs.
This trips up quoted-printable decoders (most clients just show a few
incorrect characters - breaking the advertising link, however, mh
spots the illegal quoting and refuses to display the entire message).

This is a known bug in Mailman 2.0 (tracker ID 617930). It was reported
in October 2002 and is fixed in mailman 2.1:

https://sourceforge.net/tracker/?func=detail&atid=100103&aid=617930&group_id=103

Apparently, judging by the X-Mailman-Version headers in the mailing
list messages, we're still using Mailman 2.0 (2.0.9-sf.net).

Is there any way to change this? Sourceforge's issues list at:

http://sourceforge.net/docman/display_doc.php?docid=17790&group_id=1

says:

  Software Upgrades

    [...]

    Mailing list services will be upgraded, though the exact time frame has
    not yet been determined. This upgrade will include Mailman upgrades and
    additional anti-spam mechanisms (we know what needs to be done, but have
    not yet scheduled the resources to perform the implementation).

Is there a known workaround? I've tried to search Sourceforge's support
requests, but it's not being very helpful.

	- Steven
------------------------------------------------------------------------
[...]
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64
Message-ID: <38F76B90B82C0A4A822651EACE4FF8E9C23322@s31xs2>
[...]
From: "Desai, Keyur Rajnikant" <kdesai@mail.smu.edu>
To: <bluez-users@lists.sourceforge.net>
[...]
Subject: [Bluez-users] L2CAP connectionless
[...]
Date: Mon, 16 Feb 2004 02:34:19 -0600
[...]

SGkgLA0KIA0KSSBhbSAganVzdCB3b25kZXJpbmcgaG93IEwyQ0FQIGNvbm5lY3Rpb25sZXNzIG1v
ZGUgd29ya3MNCiANCndoZW4gaSBkbyBhIC4vbDJ0ZXN0IC1zIC1EIEJEX0FERFIgaXQgaGFzIHRv
IHVzZSB0aGUgY29ubmVjdCBtZXRob2QuDQogDQpBbHNvIHdoZW4gdGhlIC1EIG9wdGlvbiBjYXVz
ZXMgdGhlIHNvY2tldCB0byBiZSBzZXQgdG8gU09DS19ER1JBTSAgSSBjYW5ub3QgdW5kZXJzdGFu
ZCB3aGF0IHRoZSANCmhhbmRsZXIgKHMpIGZ1bmN0aW9uIGRvZXMNCiANCkkgdHJpZWQgdG8gc2lu
Z2xlIHN0ZXAgdXNpbmcgeHhnZGIgYnV0IGl0IHdvdWxkIGFsd2F5cyBza2lwIHRoZSBoYW5kbGVy
KHMpIGZ1bmN0aW9uLg0KIA0KQW55IHdvcmRzIG9mIHdpc2RvbSBvbiB0aGlzID8NCiANCkJlc3Qg
UmVnYXJkcw0KRGVzYWkNCg==


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
------------------------------------------------------------------------

-- 




**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  parent reply	other threads:[~2004-02-17 15:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-16  8:34 [Bluez-users] L2CAP connectionless Desai, Keyur Rajnikant
2004-02-16  9:01 ` Marcel Holtmann
2004-02-16 21:43   ` Michel Planques
2004-02-16 23:00     ` Marcel Holtmann
2004-02-17 15:47 ` Steven Singer [this message]
2004-02-17 16:56   ` [Bluez-users] Mailing list gateway corrupting messages (was: L2CAP connectionless) Marcel Holtmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=403237AF.5030501@csr.com \
    --to=steven.singer@csr.com \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=kdesai@mail.smu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox