How do you file bug reports for this software, anyhow? The “bug
reporting” link from Best Practical’s website just shows me a list of
(presumably) open bugs.
Quick summary to see if anyone else has run into this.
I’ve got a spam message (saved if anyone is interested) that has nothing
but <<< No Message Collected >>> in the body that was generating this
error report trying to get through the mailgate:
RT server error. The RT server which handled your email did not behave as expected. It said:
System error
error:
Can’t call method “as_string” on an undefined value at /opt/rt3/lib/RT/Attachment_Overlay.pm line 163.
163: my $Body = $Attachment->bodyhandle->as_string;
(I’ve got the whole report saved, too.)
Irritating thing was that it ended up in a deferred delivery loop, and
every attempt that was made to deliver resulted in my Ticket ID index
being incremented, but the tickets not being available for viewing.
[crit]: Transaction not committed. Usually indicates a software fault.
Data loss may have occurred (/opt/rt3/bin/webmux.pl:131)
was logged every time the message broken message failed to deliver. The
result of all this is that my ticket #s are weirdly ordered now, with
lots of tickets that can not be opened filling in various gaps.
Thanks!
Mick Szucs mick@onramp.ca
Onramp Network Services Inc.