The problems continue…this is what my bounces look like right now:
The original message was received at Thu, 3 Apr 2003 23:52:37 -0600
from clickalyzer.com [66.216.96.108]
----- The following addresses had permanent fatal errors -----
“|/usr/bin/rt-mailgate --debug --queue bugs --action correspond --url
https://support.clickalyzer.com/”
(reason: 9)
(expanded from: bugs@support.clickalyzer.com)
----- Transcript of session follows -----
Connecting to https://support.clickalyzer.com//REST/1.0/NoAuth/mail-gateway
at /etc/smrsh/rt-mailgate line 158, <> chunk 1.
Undefined subroutine &RT::CanonicalizeAddress called at
/usr/local/rt3/lib/RT/Interface/Email.pm line 287.
Stack:
[/usr/lib/perl5/site_perl/5.6.1/HTML/Mason/Request.pm:281]
[/usr/local/rt3/lib/RT/Interface/Email.pm:287]
[/usr/local/rt3/lib/RT/Interface/Email.pm:574]
[/usr/local/rt3/share/html/REST/1.0/NoAuth/mail-gateway:33]
[/usr/local/rt3/share/html/REST/1.0/autohandler:27]
[/usr/local/rt3/share/html/autohandler:62]
RT server error.
The RT server which handled your email did not behave as expected. It
said:
Undefined subroutine &RT::CanonicalizeAddress called at
/usr/local/rt3/lib/RT/Interface/Email.pm line 287.
Stack:
[/usr/lib/perl5/site_perl/5.6.1/HTML/Mason/Request.pm:281]
[/usr/local/rt3/lib/RT/Interface/Email.pm:287]
[/usr/local/rt3/lib/RT/Interface/Email.pm:574]
[/usr/local/rt3/share/html/REST/1.0/NoAuth/mail-gateway:33]
[/usr/local/rt3/share/html/REST/1.0/autohandler:27]
[/usr/local/rt3/share/html/autohandler:62]
554 5.3.0 unknown mailer error 9
smime.p7s (2.79 KB)
Are you running RT 3.0.0 or an earlier version?
Can you paste us line 287 of /usr/local/rt3/lib/RT/Interface/Email.pm?On Fri, Apr 04, 2003 at 12:05:44AM -0600, Jonathan Mischo wrote:
The problems continue…this is what my bounces look like right now:
The original message was received at Thu, 3 Apr 2003 23:52:37 -0600
from clickalyzer.com [66.216.96.108]
----- The following addresses had permanent fatal errors -----
“|/usr/bin/rt-mailgate --debug --queue bugs --action correspond --url
https://support.clickalyzer.com/”
(reason: 9)
(expanded from: bugs@support.clickalyzer.com)
----- Transcript of session follows -----
Connecting to https://support.clickalyzer.com//REST/1.0/NoAuth/mail-gateway
at /etc/smrsh/rt-mailgate line 158, <> chunk 1.
Undefined subroutine &RT::CanonicalizeAddress called at
/usr/local/rt3/lib/RT/Interface/Email.pm line 287.
Stack:
[/usr/lib/perl5/site_perl/5.6.1/HTML/Mason/Request.pm:281]
[/usr/local/rt3/lib/RT/Interface/Email.pm:287]
[/usr/local/rt3/lib/RT/Interface/Email.pm:574]
[/usr/local/rt3/share/html/REST/1.0/NoAuth/mail-gateway:33]
[/usr/local/rt3/share/html/REST/1.0/autohandler:27]
[/usr/local/rt3/share/html/autohandler:62]
RT server error.
The RT server which handled your email did not behave as expected. It
said:
Undefined subroutine &RT::CanonicalizeAddress called at
/usr/local/rt3/lib/RT/Interface/Email.pm line 287.
Stack:
[/usr/lib/perl5/site_perl/5.6.1/HTML/Mason/Request.pm:281]
[/usr/local/rt3/lib/RT/Interface/Email.pm:287]
[/usr/local/rt3/lib/RT/Interface/Email.pm:574]
[/usr/local/rt3/share/html/REST/1.0/NoAuth/mail-gateway:33]
[/usr/local/rt3/share/html/REST/1.0/autohandler:27]
[/usr/local/rt3/share/html/autohandler:62]
554 5.3.0 unknown mailer error 9
Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.
yes, I’m running rt3, and line 287 is:
$Address = RT::CanonicalizeAddress($Address);
in:
sub ParseCcAddressesFromHead {
my %args = ( Head => undef,
QueueObj => undef,
CurrentUser => undef,
@_ );
my (@Addresses);
my @ToObjs = Mail::Address->parse($args{'Head'}->get('To'));
my @CcObjs = Mail::Address->parse($args{'Head'}->get('Cc'));
foreach my $AddrObj (@ToObjs, @CcObjs) {
my $Address = $AddrObj->address;
$Address = RT::CanonicalizeAddress($Address);
next if ($args{'CurrentUser'}->EmailAddress =~ /^$Address$/i);
next if ($args{'QueueObj'}->CorrespondAddress =~ /^$Address$/i);
next if ($args{'QueueObj'}->CommentAddress =~ /^$Address$/i);
next if (RT::IsRTAddress($Address));
push (@Addresses, $Address);
}
return (@Addresses);
}From: “Jesse Vincent” jesse@bestpractical.com
To: “Jonathan Mischo” jon@clickalyzer.com
Cc: rt-users@lists.fsck.com
Sent: Friday, April 04, 2003 12:41 AM
Subject: Re: [rt-users] Mailgate failure, bug, or misconfig?
Are you running RT 3.0.0 or an earlier version?
Can you paste us line 287 of /usr/local/rt3/lib/RT/Interface/Email.pm?
The problems continue…this is what my bounces look like right now:
The original message was received at Thu, 3 Apr 2003 23:52:37 -0600
from clickalyzer.com [66.216.96.108]
----- The following addresses had permanent fatal errors -----
“|/usr/bin/rt-mailgate --debug --queue bugs --action correspond --url
https://support.clickalyzer.com/”
(reason: 9)
(expanded from: bugs@support.clickalyzer.com)
----- Transcript of session follows -----
Connecting to
https://support.clickalyzer.com//REST/1.0/NoAuth/mail-gateway
at /etc/smrsh/rt-mailgate line 158, <> chunk 1.
Undefined subroutine &RT::CanonicalizeAddress called at
/usr/local/rt3/lib/RT/Interface/Email.pm line 287.
Stack:
[/usr/lib/perl5/site_perl/5.6.1/HTML/Mason/Request.pm:281]
[/usr/local/rt3/lib/RT/Interface/Email.pm:287]
[/usr/local/rt3/lib/RT/Interface/Email.pm:574]
[/usr/local/rt3/share/html/REST/1.0/NoAuth/mail-gateway:33]
[/usr/local/rt3/share/html/REST/1.0/autohandler:27]
[/usr/local/rt3/share/html/autohandler:62]
RT server error.
The RT server which handled your email did not behave as expected. It
said:
Undefined subroutine &RT::CanonicalizeAddress called at
/usr/local/rt3/lib/RT/Interface/Email.pm line 287.
Stack:
[/usr/lib/perl5/site_perl/5.6.1/HTML/Mason/Request.pm:281]
[/usr/local/rt3/lib/RT/Interface/Email.pm:287]
[/usr/local/rt3/lib/RT/Interface/Email.pm:574]
[/usr/local/rt3/share/html/REST/1.0/NoAuth/mail-gateway:33]
[/usr/local/rt3/share/html/REST/1.0/autohandler:27]
[/usr/local/rt3/share/html/autohandler:62]
554 5.3.0 unknown mailer error 9
–
Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.
yes, I’m running rt3, and line 287 is:
I believe that you’re running a beta or release candidate, but not RT
3.0.0. Because that code is different in 3.0.0. We fixed this bug before
we released the software
Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.