On Thu, 3 Jun 2004, Gordon Henderson wrote:
[David Skoll wrote:]
> > But I believe you have stumbled on a bug in MIMEDefang. I will look
> > at fixing it today and release a beta.
I just ran a test and it worked fine for me. Here's my filter:
sub filter_end ($) {
my($entity) = @_;
append_text_boilerplate($entity, "\n=====\nTest Boilerplate\n", 0);
}
This is what I sent to the server:
Data
354 Enter mail, end with "." on a line by itself
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: Test
Boilerplate.
.
250 2.0.0 i53FwYpR005054 Message accepted for delivery
And the resulting message was a proper MIME message with MIME boundary
(see below.) So I'm unable to duplicate the problem.
Regards,
David.
Return-Path: <[EMAIL PROTECTED]>
Received: from o ([192.168.10.12])
by shishi.roaringpenguin.com (8.12.10/8.12.10) with SMTP id i53FwYpR0050
54
for <[EMAIL PROTECTED]>; Thu, 3 Jun 2004 11:58:46 -0400
Date: Thu, 3 Jun 2004 11:58:35 -0400
Message-Id: <[EMAIL PROTECTED]>
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: Test
Content-Type: multipart/mixed; boundary="----------=_1086278340-4966-0"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.42
This is a multi-part message in MIME format...
------------=_1086278340-4966-0
Content-Disposition: inline
Boilerplate.
=====
Test Boilerplate
------------=_1086278340-4966-0--
_______________________________________________
Visit http://www.mimedefang.org and http://www.canit.ca
MIMEDefang mailing list
[EMAIL PROTECTED]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
