Empty message-body in replies (fwd)

RT Users
1

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

I hate to bother the list again, but I just wanted to find out if
anyone had any clues regarding this problem?

I have collected a few more examples of the problem since I posted
this message, but I admit I haven’t had all that much time to debug
the problem myself. I can post these to the list if anyone is
interested. I’m still working on being able to reproduce this problem
over and over…

The symptoms seem the same as what had been described in the “MIME
parsing not recursive?” thread that was mentioned on this list in late
August.

My big question is whether this was something that has been fixed in a
newer version of RT? (I’m using 2.0.11.) My guess is no, because I
believe that I’ve seen the same problem with a couple of newer RT
installs that I have setup (2.0.14).

Can anyone think of any other possible workarounds for this bug?
(Maybe MIMEdefang or something like that would offer a temporary
solution until RT is fixed?)

Thanks!

  • -Chris

Chris Tracy chris@telerama.com
Telerama Public Access Internet
Senior Network Engineer
http://www.telerama.com

Hi there,

I just wanted to report that I’m seeing similar problems with RT
2.0.11. We have about 93k tickets in our RT database and have just
noticed this problem in the last month.

From the looks of this, this shouldn’t matter much, but I’m using
FreeBSD 4.6-STABLE with Apache/1.3.26 (Unix) mod_ssl/2.8.10
OpenSSL/0.9.6a mod_perl/1.26 AuthMySQL/2.20 PHP/4.1.2.

My biggest problem is that I’m not able to replicate this problem
readily. Is the condition below the one that has to be met in order
for a reply (sent from RT to the requestor) to show up as blank?

  • If somebody has the temerity to do both of the above then the mail
    has a media type of multipart/mixed, the first part of which has a
    media type of multipart/alternative, which in turn contains the
    actual message. {$Transaction->Content()} is empty, so the
    forwarded mail appears to be messageless.

(http://lists.fsck.com/pipermail/rt-users/2002-July/008947.html)

If it helps, I have one of the blank emails with full headers as well
as the corresponding RT transactions. Does anyone know if this issue
has been resolved in any of the more recent versions of RT?

Thanks!

  • -Chris

Chris Tracy chris@telerama.com
Telerama Public Access Internet
Senior Network Engineer
http://www.telerama.com