[rt-users] Content-Type weirdness with NotifyWithAttachment

[Lynoure Rajamäki]

On Mon, 2002-12-16 at 07:52, Phil Homewood wrote:

> This is set in MIME::Entity, in particular the "make_boundary" sub.
> This generates a boundary with ten leading dashes (which agrees with
> the twelve dashes you see in your boundary.) However these ten dashes
> are absent in the Content-Type header. Why? I don't know. But that
> should at least give you a starting point. :-) Good luck...

That was my mistake, it seemed to be that way in the Content-Type as
well. Confusing. Anyway, I got rid of the extra hyphens.But it seems
that the content type and encoding of the first part
{$Transaction->Content()} is left unset and it seems to me (poor perl
newbie) that there is no way to set it afterwards. I have found out a
way to add {$Transaction->Content()} as a plain text attachment but then
there will be an extra empty attachment above that and alas, things are
broken that away. (So a way of removing an attachment would be good
too.)

Postfix and exim seem to fix the messages not including
Content-Transer-Encoding or Content-Type for the first message, qmail
and sendmail instead seem to assume it's no multipart.

This is such a weird problem that I almost feel embarrashed about it
(and my non-existent perl skills) but I have had the same attachment
behaviour on two different RT installations now.

-- 
Lynoure Rajamäki
lynoure at otaverkko.fi