Inline Text Signature and attachment-only mail

[Julian Field]

At 15:15 10/10/2002, you wrote:
>yesterday I went into production with MailScanner-3.23-5 for about 500 users
>and got only a few complaints.
>
>One user received a mail with an empty body and two text/plain attachments.
>Mailscanner inserted the "Inline Text Signature" into the first attachment.
>The user got some trouble from this, because the attachment was used as
>input for some program
>which disliked the signature.

I have fixed this in Version 4, and ported the fix back to version 3.


>I could reproduce this behaviour; see below for an example message.
>
>MailScanner uses SignCleanMessage to insert the signature into the first
>part of a multipart message.
>
>MailScanner shouldn't insert a signature into an attachment which is marked
>with
>         Content-Disposition: attachment; filename="something.txt"
>
>Viele Grüße
>
>-- Heinz Knutzen
>
>Datenzentrale Schleswig-Holstein
>Altenholzer Str. 10-14, 24161 Altenholz, Germany
>http://www.dzsh.de/
>mailto:heinz.knutzen at dzsh.de
>Tel: +49.431.3295.581 Fax: +49.431.3295.410
>
>Example:
>
>MIME-Version: 1.0
>Content-Type: multipart/mixed;
>         boundary="----=_NextPart_000_0008_01C26FB5.E9EB2260"
>
>This is a multi-part message in MIME format.
>
>------=_NextPart_000_0008_01C26FB5.E9EB2260
>Content-Type: text/plain;
>         name="test1.txt"
>Content-Transfer-Encoding: quoted-printable
>Content-Disposition: attachment;
>         filename="test1.txt"
>
>Test 1
><<<--- Signature is inserted here
>
>------=_NextPart_000_0008_01C26FB5.E9EB2260
>Content-Type: text/plain;
>         name="test2.txt"
>Content-Transfer-Encoding: quoted-printable
>Content-Disposition: attachment;
>         filename="test2.txt"
>
>Test 2
>
>------=_NextPart_000_0008_01C26FB5.E9EB2260--

--
Julian Field                Teaching Systems Manager
jkf at ecs.soton.ac.uk         Dept. of Electronics & Computer Science
Tel. 023 8059 2817          University of Southampton
                             Southampton SO17 1BJ