Even after rereading URL:http://fsck.com/rtfm/article.html?id=4#27,
I have problems predicting the behavior of RT. Here, I sent a mail to
a ticket and it was refused. I am not the owner but I am the
requestor. Anyway, I am a member of a group which has the global right
to CommentOnTicket and ModifyTicket.
Where can I look to debug? Can I ask RT to dumps the complete set of
rights for the current context?
----- Forwarded message from via RT rt-tech@rt.eureg.org -----Subject: [EUreg #5] Whois server
From: " via RT" rt-tech@rt.eureg.org
Reply-To: rt-tech@rt.eureg.org
To: “‘AdminCc of EUreg Ticket #5’”: ;‘AdminCc of EUreg Ticket #5’:;
Date: Mon, 22 Jul 2002 17:06:13 +0200 (CEST)
X-RT-Loop-Prevention: EUreg
Managed-BY: Request Tracker 2.0.13 (http://www.fsck.com/projects/rt/)
RT-Ticket: EUreg #5
Not set: Request 5 was acted upon.
Transaction: Permission Denied
Queue: Technical
Subject: Whois server
Owner: lubrano
Requestors: bortzmeyer@nic.fr
Status: open
Ticket <URL: http://rt.eureg.org//Ticket/Display.html?id=5 >
----- End forwarded message -----
a message of 43 lines which said:
Here, I sent a mail to a ticket and it was refused.
…
Subject: [EUreg #5] Whois server
From: " via RT" rt-tech@rt.eureg.org
…
Transaction: Permission Denied
OK, the problem is apparently in the email addresses parsing (notice
the lack of an user name before “via RT” above). Some messages are
accepted, not all. For instance, this message was registered by RT:Subject: RE: [ecdiscuss] organization of eu-registry
From: Joe Baptista baptista@dot-god.com
To: Patrizio Menchetti patrizio.menchetti@menchlaw.com
Cc: ecdiscuss@ec-pop.org
Date: Thu, 1 Aug 2002 07:43:15 -0400 (EDT)
while this one was not:
Subject: Re: [ecdiscuss] [marine.chantreau@nic.fr: A washingtonpost.com article from: marine.chantreau@nic.fr]
From: “Patrizio Menchetti” patrizio.menchetti@menchlaw.com
Reply-To: patrizio.menchetti@menchlaw.com
To: ecdiscuss@ec-pop.org
Date: Tue, 06 Aug 2002 13:20:38 +0200
I can only assume that the second syntax (with the quotes) for the
From: address, while perfectly legal, was not recognized by RT.
Stephane Bortzmeyer wrote:
For instance, this message was registered by RT:
Subject: RE: [ecdiscuss] organization of eu-registry
From: Joe Baptista baptista@dot-god.com
To: Patrizio Menchetti patrizio.menchetti@menchlaw.com
Cc: ecdiscuss@ec-pop.org
Date: Thu, 1 Aug 2002 07:43:15 -0400 (EDT)
while this one was not:
Subject: Re: [ecdiscuss] [marine.chantreau@nic.fr: A washingtonpost.com article from: marine.chantreau@nic.fr]
From: “Patrizio Menchetti” patrizio.menchetti@menchlaw.com
Reply-To: patrizio.menchetti@menchlaw.com
To: ecdiscuss@ec-pop.org
Date: Tue, 06 Aug 2002 13:20:38 +0200
I can only assume that the second syntax (with the quotes) for the
From: address, while perfectly legal, was not recognized by RT.
If a message has a Reply-To: header then its contents are used for
identification purposes instead of the From: header. So in the second
message’s case there’s just an e-mail address without a friendly name.
But ‘RT’ should still recognize that, and round here it definitely does
– we have hundreds of such messages which have successfully entered our
queues.
Smylers
GBdirect
a message of 40 lines which said:
If a message has a Reply-To: header then its contents are used for
identification purposes instead of the From: header.
Fair enough.
message’s case there’s just an e-mail address without a friendly name.
But ‘RT’ should still recognize that, and round here it definitely does
queues.
But it does not
a message of 40 lines which said:
message’s case there’s just an e-mail address without a friendly name.
But ‘RT’ should still recognize that, and round here it definitely does
queues.
But it does not
Hrm, I must admit to being slightly disturbed by an RT installaion that
accepts mails from Joe, but not other people. You may wish to provide
more detailed information in order to get this resolved, or contact myself
off list if this is not possible in a public forum.
Regards,
Bruce Campbell RIPE
Systems/Network Engineer NCC
www.ripe.net - PGP562C8B1B Operations/Security