Hey folks,

Been a long while since I've posted on here but an interesting question for anybody who uses RT(Request Tracker) w/ Exim:

For some reason when commenting on a ticket and trying to cc our mailing list of support staff, RT is saying that the message has bounced. I checked syslog and came up with this error:

Jun 27 15:38:55 devserv2 RT: Could not record email: Message Bounced (/opt/rt3/share/html/REST/1.0/NoAuth/mail-gateway:73)

If anybody knows why this is occurring, please share the wealth. I've been digging for an answer for a few hours now. Thanks much!

Blue

Went back and did a little more checking of RT's code this morning...

Checked out line 73 of the mail-gateway Perl module and found:

my ( $status, $error, $Ticket ) = RT::Interface::Email::Gateway( \%ARGS );
if ( $status == 1 ) {
*send e-mail*
}
else {
*don't send e-mail and print the aforementioned error to syslog*
}

Traced back to the e-mail gateway module, and after a lot of nasty
checks for loops and malicious senders etc. I checked the Gateway
subroutine and found the check for our error down near the bottom:

if ( $action =~ /^(?:comment|correspond)$/i ) {
my $method = ucfirst lc $action;
my ( $status, $msg ) = $Ticket->$method( MIMEObj => $Message );
unless ($status) {

#Warn the sender that we couldn't actually submit the comment.
MailError(To => $ErrorsTo, Subject => "Message not recorded", Explanation => $msg,
MIMEObj => $Message);
return ( 0, "Message not recorded: $msg", $Ticket );
}
}

Unfortunately this doesn't really help us because it doesn't tell us WHY
the e-mail bounced. My only guess is that something in certain mail
messages is causing the conversion to a MIME object to fail. I'll start
saving these bounced e-mails and see if I can spot a pattern.