RT3.0.8pre2 (elixus version) email question

First off, I hope everyone had/is having/is about to have a great holiday
season…

Secondly, I gave up on trying to get http://www.databasment.org/rt to
work. I hope someone figures it out, but hey :slight_smile:

Now, when I try to email general@databasement.org I get:

Dec 26 14:09:05 mint postfix/local[65422]: 6BBDA33C2B:
to=general@databasement.org, relay=local, delay=231, status=deferred
(temporary failure. Command output: RT server error. The RT server which
handled your email did not behave as expected. It said: temporary failure
)

My /etc/aliases has:
general: “|/usr/local/rt3/bin/rt-mailgate --queue general --action
correspond --url http://rt.databasement.org/

Manually running rt-mailgate:

./rt-mailgate --queue general --action correspond --url

http://rt.databasement.org/ < ~ges/RT_SiteConfig.pm
RT server error.

The RT server which handled your email did not behave as expected. It said:

temporary failure

Any ideas? :-/

thanks
G.

The original portions of this message are the copyright of the author
©1998-2002 Glenn E. Sieb. ICQ UIN: 300395 IRC Nick: Rainbear “All
acts of Love and Pleasure are Her rituals”-Charge of the Goddess

./rt-mailgate --queue general --action correspond --url

http://rt.databasement.org/ < ~ges/RT_SiteConfig.pm
RT server error.
The RT server which handled your email did not behave as expected. It said:
temporary failure

Any ideas? :-/

You’re not handing it a properly formatted email, it probably doesn’t
like that.

There might be more interesting things in your RT log.

-R

Robert Spier said:

./rt-mailgate --queue general --action correspond --url

http://rt.databasement.org/ < ~ges/RT_SiteConfig.pm
RT server error.
The RT server which handled your email did not behave as expected. It
said:
temporary failure

Any ideas? :-/

You’re not handing it a properly formatted email, it probably doesn’t
like that.

There might be more interesting things in your RT log.

Dec 26 15:19:18 mint RT: DBD::Pg::st execute failed: ERROR: parser: parse
error at or near “NULL” at character 34 at
/usr/local/lib/perl5/site_perl/5.8.1/DBIx/SearchBuilder/Handle.pm line
410. (/usr/local/rt3/lib/RT.pm:247)
Dec 26 15:19:18 mint RT: RT::Handle=HASH(0xa070a6c) couldn’t execute the
query ‘SELECT * FROM Users WHERE Name ?’ at
/usr/local/lib/perl5/site_perl/5.8.1/DBIx/SearchBuilder/Handle.pm line
417. (/usr/local/rt3/lib/RT.pm:247)
Dec 26 15:36:28 mint RT: DBD::Pg::st execute failed: ERROR: parser: parse
error at or near “NULL” at character 34 at
/usr/local/lib/perl5/site_perl/5.8.1/DBIx/SearchBuilder/Handle.pm line
410. (/usr/local/rt3/lib/RT.pm:247)
Dec 26 15:36:28 mint RT: RT::Handle=HASH(0xa070a30) couldn’t execute the
query ‘SELECT * FROM Users WHERE Name ?’ at
/usr/local/lib/perl5/site_perl/5.8.1/DBIx/SearchBuilder/Handle.pm line
417. (/usr/local/rt3/lib/RT.pm:247)

Hadn’t caught this the first time 'round… however, I am able to do
things like sign into RT and create queues, users, etc…

Thanks for your help, Robert! Hopefully I can figure this out :-/
Glenn
The original portions of this message are the copyright of the author
(c)1998-2002 Glenn E. Sieb. ICQ UIN: 300395 IRC Nick: Rainbear
“All acts of Love and Pleasure are Her rituals”-Charge of the Goddess

Dec 26 15:36:28 mint RT: RT::Handle=HASH(0xa070a30) couldn’t execute the
query ‘SELECT * FROM Users WHERE Name ?’ at
/usr/local/lib/perl5/site_perl/5.8.1/DBIx/SearchBuilder/Handle.pm line
417. (/usr/local/rt3/lib/RT.pm:247)
Hadn’t caught this the first time 'round… however, I am able to do
things like sign into RT and create queues, users, etc…

Are you sure those errors showed up from the email submission? Those
look iike the login/logout issues we’ve been seeing.

-R

Robert said:

Dec 26 15:36:28 mint RT: RT::Handle=HASH(0xa070a30) couldn’t execute the
query ‘SELECT * FROM Users WHERE Name ?’ at
/usr/local/lib/perl5/site_perl/5.8.1/DBIx/SearchBuilder/Handle.pm line
417. (/usr/local/rt3/lib/RT.pm:247)
Hadn’t caught this the first time 'round… however, I am able to do
things like sign into RT and create queues, users, etc…

Are you sure those errors showed up from the email submission? Those
look iike the login/logout issues we’ve been seeing.

Good point… there are no errors being logged in the RT log… (syslog)… I
have it set to “Emergency” which, from what I see in RT_Config.pm, should
set the log to log everything, which oddly makes no sense… I’d think
that debug would do that, and “emergency” only show you things like
panics…

shrug :slight_smile:

Thanks, Robert!
Glenn
The original portions of this message are the copyright of the author
©1998-2002 Glenn E. Sieb. ICQ UIN: 300395 IRC Nick: Rainbear
"All acts of Love and Pleasure are Her rituals"-Charge of the Goddess

Good point… there are no errors being logged in the RT log… (syslog)… I
have it set to “Emergency” which, from what I see in RT_Config.pm, should
set the log to log everything, which oddly makes no sense… I’d think
that debug would do that, and “emergency” only show you things like
panics…

Yeah, that doesn’t sound right at all. debug is “everything”.
“emergency” is the lowest level.

Have you tried your test with a “well formed email”?

(i.e… some basic headers, a newline, and a simple body?)

-R

Robert Spier said:

Good point… there are no errors being logged in the RT log… (syslog)…
I have it set to “Emergency” which, from what I see in RT_Config.pm,
should set the log to log everything, which oddly makes no sense…
I’d think that debug would do that, and “emergency” only show you
things like panics…

Yeah, that doesn’t sound right at all. debug is “everything”.
“emergency” is the lowest level.

nod It’s wrong in the RT_Config.pm then :-/

Have you tried your test with a “well formed email”?

If Mozilla and Squirrelmail aren’t sending “well formed emails” then a
whole boatload of us are in trouble, yes? :slight_smile:

Especially since they work fine with other installs of RT… :-/

(i.e… some basic headers, a newline, and a simple body?)

Jup…

Thanks,
G.

(Here’s what the email looks like, for arguments sake:)
Message-ID: 3FEE30F4.1000906@wingfoot.org
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b)
Gecko/20030827
X-Accept-Language: en-us, en
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Testing again

The original portions of this message are the copyright of the author
(c)1998-2002 Glenn E. Sieb. ICQ UIN: 300395 IRC Nick: Rainbear
“All acts of Love and Pleasure are Her rituals”-Charge of the Goddess

Yeah, that doesn’t sound right at all. debug is “everything”.
“emergency” is the lowest level.

nod It’s wrong in the RT_Config.pm then :-/

Well, it’s not wrong, just slightly confusing. The “level” refers to
"importance". In theory debug messages are less important than
emergency messages.

I started making a patch, but wasn’t happy with any of the minor
adjustments to it, and didn’t want to rewrite the whole paragraph.
Your attempt is welcomed.

Have you tried your test with a “well formed email”?

If Mozilla and Squirrelmail aren’t sending “well formed emails” then a
whole boatload of us are in trouble, yes? :slight_smile:

Yes.

Well… this brings us back to where we started.

:slight_smile:

The mail gateway is working for everyone else, and that email doesn’t
look too odd, so I’m not sure whats going on. Any luck pulling
something from the debug logs?

There are definitely debug messages you should see from email
creation, some of them relate to character decoding. if you’re not
seeing any of those, it means its failing early on. If you turn
LogToScreen to debug (this will send things to your apache log) do you
get anything there? That’s also where you’d see weird perl issues.

-R

Robert Spier said:

Well, it’s not wrong, just slightly confusing. The “level” refers to
“importance”. In theory debug messages are less important than
emergency messages.

Um… ok… I’ll see what I can come up with that’s more clear, perhaps :slight_smile:
I’ll just email said paragraph to list, maybe?

Well… this brings us back to where we started.

:slight_smile:

The mail gateway is working for everyone else, and that email doesn’t
look too odd, so I’m not sure whats going on. Any luck pulling
something from the debug logs?

There are definitely debug messages you should see from email
creation, some of them relate to character decoding. if you’re not
seeing any of those, it means its failing early on. If you turn
LogToScreen to debug (this will send things to your apache log) do you
get anything there? That’s also where you’d see weird perl issues.

Ok… I’ve debug’d those settings:

tail -f /usr/local/rt3/var/log/rt.log

[Sun Dec 28 06:43:38 2003] [debug]: Converting ‘us-ascii’ to ‘utf-8’ for
text/plain - Testing #4
(/usr/local/rt3/lib/RT/I18N.pm:200)

tail -f /var/log/vhost/databasement.org-error_log

[Sun Dec 28 06:43:38 2003] [debug]: Converting ‘us-ascii’ to ‘utf-8’ for
text/plain - Testing #4
(/usr/local/rt3/lib/RT/I18N.pm:200)

tail -f /var/log/messages

(nothing)

and my mailq still says:

mailq

-Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
4E85B33C2B 1290 Sat Dec 27 20:25:19 ges@wingfoot.org
(temporary failure. Command output: RT server error. The RT server which
handled your email did not behave as expected. It said: temporary failure
) general@databasement.org

Thanks, again for your help!
Glenn
The original portions of this message are the copyright of the author
(c)1998-2002 Glenn E. Sieb. ICQ UIN: 300395 IRC Nick: Rainbear
“All acts of Love and Pleasure are Her rituals”-Charge of the Goddess

Aha!

In share/html/REST/1.0/NoAuth/mail-gateway

Change the line that says:

temporary failure

to

temporary failure - <% error %>

and try again.

-R

Robert Spier said:

Aha!

In share/html/REST/1.0/NoAuth/mail-gateway

Change the line that says:

temporary failure

to

temporary failure - <% error %>

and try again.

Here 'tis…

Thanks again,
G.

mailq

-Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
4E85B33C2B 1290 Sat Dec 27 20:25:19 ges@wingfoot.org
(temporary failure. Command output: RT server error. The RT server which
handled your email did not behave as expected. It said:

System error

error:  Error during compilation of /usr/local/rt3/share/html/REST/1.0/NoAuth/mail-gateway:
Bareword "error" not allowed while "strict subs" in use at /usr/local/rt3/share/html/REST/1.0/NoAuth/mail-gateway line 36.

context:  <td align="left" valign=") general@databasement.org <p>– 1 Kbytes in 1 Request.</p> <p>The original portions of this message are the copyright of the author<br> (c)1998-2002 Glenn E. Sieb. ICQ UIN: 300395 IRC Nick: Rainbear<br> “All acts of Love and Pleasure are Her rituals”-Charge of the Goddess</p>
... 
32:  my ( $status, $error, $Ticket ) = RT::Interface::Email::Gateway(\%ARGS);
33:  </%init>
34:  <%flags>
35:  inherit => undef # inhibit UTF8 conversion done in /autohandler
36:  </%flags>
37:  % if ($status == -75 ) {
38:  temporary failure - <% error %>
39:  % }
40: 

Glenn Sieb wrote:

Robert Spier said:

Aha!

In share/html/REST/1.0/NoAuth/mail-gateway

Change the line that says:

temporary failure

to

temporary failure - <% error %>

Warning: a “$” is missing : “<% $error %>” instead of “<% error %>”.

You can also insert the following just after the “<%init>” line :

$m->error_format(‘text’);

This should force output of error report in plain text instead of html.

Guillaume Perréal.

Responsable informatique,
Cemagref, groupement de Lyon,
France.

Tél: (+33) 4.72.20.87.87.
Fax: (+33) 4.78.47.78.75.
Site: http://www.lyon.cemagref.fr/

Guillaume Perr�al said:

Warning: a “$” is missing : “<% $error %>” instead of “<% error %>”.

You can also insert the following just after the “<%init>” line :

$m->error_format(‘text’);

This should force output of error report in plain text instead of html.

Thanks, Guillaume!

The new, improved output:

mailq

-Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
4E85B33C2B 1290 Sat Dec 27 20:25:19 ges@wingfoot.org
(temporary failure. Command output: An Error Occurred =================
500 Can’t connect to rt.databasement.org:80 (connect: Invalid argument) )
general@databasement.org

Thanks again!
Glenn
The original portions of this message are the copyright of the author
(c)1998-2002 Glenn E. Sieb. ICQ UIN: 300395 IRC Nick: Rainbear
“All acts of Love and Pleasure are Her rituals”-Charge of the Goddess

Glenn Sieb said:

The new, improved output:

mailq

-Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
4E85B33C2B 1290 Sat Dec 27 20:25:19 ges@wingfoot.org
(temporary failure. Command output: An Error Occurred =================
500 Can’t connect to rt.databasement.org:80 (connect: Invalid argument) )
general@databasement.org

Ok… seeing this now… I tried telnetting to that address’ port 80… and
I’m getting connection refused. I’m looking into it, as I can certainly
browse that page, and log in and all that good stuff…

Thanks for all of your help, guys!
Glenn

The original portions of this message are the copyright of the author
(c)1998-2002 Glenn E. Sieb. ICQ UIN: 300395 IRC Nick: Rainbear
“All acts of Love and Pleasure are Her rituals”-Charge of the Goddess

Glenn Sieb said:

Ok… seeing this now… I tried telnetting to that address’ port 80… and
I’m getting connection refused. I’m looking into it, as I can certainly
browse that page, and log in and all that good stuff…

Ok. Got it… A) restart apache… that stopped happening… B) correct a
grr typo.

Thanks for all of your help, guys!

Glenn
The original portions of this message are the copyright of the author
©1998-2002 Glenn E. Sieb. ICQ UIN: 300395 IRC Nick: Rainbear
"All acts of Love and Pleasure are Her rituals"-Charge of the Goddess