I’ve installed RT RC1 from scratch, created users, renaming the
root user in the process (maybe that’s the problem).
Sending mail as valid user creates ticket as desired.
Chapter 4, Section Users, “Whenever someone new submits a
request, RT automatically creates a non-staff account for that
person.”.
That’s cool, but sending message from an hithertofore unknown
user generates
RT could not load a valid user, and RT’s configuration does
not allow for the creation of a new user for your email.
Googling that error message commes up with nothing, neither does
searching for it in rt-devel archives, which makes me think I’ve
broken something.
Looking at the source for lib/RT/Interface/Email.pm didn’t help
much either.
rt-mailgate docs say
However, you will need first of all to create an RT user for the
mail gateway and assign it a password; this helps to ensure that
mail coming into the web server did originate from the gateway.
which that is not further explained. It does make me hope that
maybe it wasn’t I who broke things by renaming the root user?
In any case, the two documentation snippets seem contradictory
to me, and that’s why I’m writing.
What should I do to solve my problem?
#include <std_disclaim.h> Lorens Kockum
Grant “Everyone” the right to ‘CreateTickets’ in that queue.On Tue, Mar 18, 2003 at 10:57:54AM +0100, Lorens Kockum wrote:
I’ve installed RT RC1 from scratch, created users, renaming the
root user in the process (maybe that’s the problem).
Sending mail as valid user creates ticket as desired.
Chapter 4, Section Users, “Whenever someone new submits a
request, RT automatically creates a non-staff account for that
person.”.
That’s cool, but sending message from an hithertofore unknown
user generates
RT could not load a valid user, and RT’s configuration does
not allow for the creation of a new user for your email.
Googling that error message commes up with nothing, neither does
searching for it in rt-devel archives, which makes me think I’ve
broken something.
Looking at the source for lib/RT/Interface/Email.pm didn’t help
much either.
rt-mailgate docs say
However, you will need first of all to create an RT user for the
mail gateway and assign it a password; this helps to ensure that
mail coming into the web server did originate from the gateway.
which that is not further explained. It does make me hope that
maybe it wasn’t I who broke things by renaming the root user?
In any case, the two documentation snippets seem contradictory
to me, and that’s why I’m writing.
What should I do to solve my problem?
–
#include <std_disclaim.h> Lorens Kockum
rt-devel mailing list
rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel
Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.
Grant “Everyone” the right to ‘CreateTickets’ in that queue.
Now that you say it, that seems very intuitive 
Thank you.
I can’t test right now, since I seem to have fallen into a
very slow query (when changing the name of a queue), I’ll
debug it a bit to see.> On Tue, Mar 18, 2003 at 10:57:54AM +0100, Lorens Kockum wrote:
rt-mailgate docs say
However, you will need first of all to create an RT user for the
mail gateway and assign it a password; this helps to ensure that
mail coming into the web server did originate from the gateway.
This would then simply be using a .htaccess file?
#include <std_disclaim.h> Lorens Kockum
I’ve been trying to track down some ISO-8859 vs. UTF-8 problems.
When I installed RT3 I set outgoing mail to ISO-8859, and
configured most things, like AutoReplies. Problems with outgoing
mail being in UTF-8 but the Content-Type being ISO.
Tried to change back, neglecting the auto-repiles for the
moment.
I’m sending mail to a queue and looking at mail received by
queue AdminCC.
Still problems. Decided to play with @EmailInputEncodings
$EmailOutputEncoding (well, there are only two or three values
to play with – I would like ISO-8859-15 for the currency sign).
Got things the other way around (outcoming mail being ISO but
Content-Type being UTF-8)…
Using fastcgi, first apachectl graceful, then stopping and
starting server between changes. After some time using fixed
manually encoded/checked files sent directly to smtp server to
eliminate sending MUA from problem list.
Looking at Autoreplies entirely iso (model plus transaction
content) but labelled utf, when original mail was utf, made
me think that mabe some magic was looking at the beginning,
converting transaction content and forgetting label, but then I
manage to get one that has utf content and utf label in spide
of iso model… that’s good! But it didn’t survive an apache
stop/start.
What have I broken? Are there indicators in the database
(except for text like templates)? Does FastCgi need more than an
apache stop-start to . . . I don’t know where to look.
If anyone has any clues, I’d appreciate it greatly. French is no
fun without accents.
G’night all.
#include <std_disclaim.h> Lorens Kockum