[rt-users] RT 4.2.1 not creating new, internal users
I've just stood up a new RT instance using AD authentication. This works
and as a new user logs in an RT user is created and added to the Privileged
group ($AutoCreate,{Privileged=>1})
I'm trying to test RT and Postfix via telnet. Postfix is receiving the
email, but I'm getting a couple errors.
>From /var/log/maillog:
Jan 14 01:41:02 zen-rt postfix/local[10173]: 5F44F808B3: to=,
relay=local, delay=2249, delays=2243/5/0/0.11, dsn=4.3.0, status=deferred
(temporary failure. Command output: HTTP request failed: 500 No Host option
provided. Your webserver logs may have more information or there may be a
network problem. )
>From /var/log/httpd/error_log:
[9561] [Tue Jan 14 05:52:47 2014] [warning]: Use of uninitialized value
$NewSubject in scalar chomp at /opt/rt4/sbin/../lib/RT/Interface/Email.pm
line 1330. (/opt/rt4/sbin/../lib/RT/Interface/Email.pm:1330)
[9561] [Tue Jan 14 05:52:47 2014] [error]: Couldn't parse or find sender's
address (/opt/rt4/sbin/../lib/RT/Interface/Email/Auth/MailFrom.pm:74)
[9561] [Tue Jan 14 05:52:47 2014] [error]: Could not record email: Could
not load a valid user (/opt/rt4/share/html/REST/1.0/NoAuth/mail-gateway:75)
[9561] [Tue Jan 14 05:55:49 2014] [error]: Could not load a valid user: RT
could not load a valid user, and RT's configuration does not allow
for the creation of a new user for this email (r...@example.com).
You might need to grant 'Everyone' the right 'CreateTicket' for the
queue general. (/opt/rt4/sbin/../lib/RT/Interface/Email.pm:245)
[9561] [Tue Jan 14 05:55:50 2014] [error]: Could not load a valid user: RT
could not load a valid user, and RT's configuration does not allow
for the creation of a new user for your email.
(/opt/rt4/sbin/../lib/RT/Interface/Email.pm:245)
[9561] [Tue Jan 14 05:55:50 2014] [error]: Could not record email: Could
not load a valid user (/opt/rt4/share/html/REST/1.0/NoAuth/mail-gateway:75)
I have granted the CreateTicket right to the Everyone group.
I have the $AutoCreateNonExternalUsers option set to 1. From what I
understand this should create users who are not AD authenticated. Perhaps
I'm wrong about this. Is there another option I should be using instead of
or in addition to this one?
-Mathew
"When you do things right, people won't be sure you've done anything at
all." - God; Futurama
"We'll get along much better once you accept that you're wrong and neither
am I." - Me
[rt-users] [rt-announce] RT 4.2.2 released
RT 4.2.2 -- 2014-01-13 -- We are pleased to announce that RT 4.2.2 is now available. http://download.bestpractical.com/pub/rt/release/rt-4.2.2.tar.gz http://download.bestpractical.com/pub/rt/release/rt-4.2.2.tar.gz.asc SHA1 sums 72faa454a02240cf21a94633b880e2158325efa1 rt-4.2.2.tar.gz e45c6d244cd0b8e5c5cec57f4ceb8207d6a2ed81 rt-4.2.2.tar.gz.asc This release is primarily a bugfix release; of particular note is that it contains schema changes for MySQL. Though the changes are limited, it is especially important to take, and verify you can recover from, a database backup prior to upgrading. Also notable is that this release fixes a bug in 4.2.0 and 4.2.1 where failures of the HTML-to-text conversion would silently cause mail to fail to be sent. When using the rich text editor, RT will also now quote the the HTML parts of email, and not simply their text equivalents. Other changes include: Documentation * Wording fixes in Shredder * Clean up examples in Lifecycles documentation * Document additional indexes that increase performance of Shredder * Replace a suggested GnuPG option with one which is not deprecated * Note that errors reported from the GnuPG infrastructure may be caused by GnuPG not being configured, but having been automatically enabled. Database * Ensure that even disabled scrips get the same id-to-name change that other scrips got during the 4.0 -> 4.2 upgrade. * On MySQL, alter the character set of all columns used to store email addresses to UTF-8 * Ensure that invalid byte sequences that may have snuck into the database previously (on earlier versions on MySQL, for instance) are not blindly interpreted as UTF-8 when retrieved from the database. As a result, invalid bytes will be returned from the API as the four characters "\xHH", where HH is the hexadecimal encoding of the byte. * Ensure that all data containing non-ASCII is quoted-printable encoded for PostgreSQL, instead of merely all data not claiming to be "text/plain" * Additional warnings prevention on Oracle; tests now pass cleanly * Allow fully-automated database upgrades using --upgrade-from and --upgrade-to options to rt-setup-database * Clean out any remaining traces of RTFM that lingered in custom fields and custom field values that were disabled at the time of the previous upgrade step. * Bullet-proof a 3.8 -> 4.0 upgrade step for Scrips with no Condition Serializer/importer * Install rt-serializer and rt-importer into sbin/ * Ensure that incremental upgrade steps only run on incremental serializations, not all exports * Fix a runtime error in the incremental upgrade path to 4.2 * Ensure that inflated Users and Groups are created with the same id as their Principal * Disable in-memory record caching when serializing and importing to improve performance * Only search non-Disabled custom fields when looking up BasedOn in initialdata files * Set up logging properly; warnings are now displayed during serialization and importing Email * Don't die if HTML -> text conversion throws an error, which would silently prevent outgoing mail from being sent. Instead, fall back to just sending text/html with no text/plain * Replying to an HTML mail with the rich text editor will now quote the HTML part, not the equivalent text version. * Set a transfer encoding on outgoing dashboards; this resolves issues with long lines when using the Sendmail MTA. * Cope with mangled and overly-quoted recipient headers occasionally generated by Outlook. General user UI * Stop localizing custom field names, for consistency * Show a useful error on "show outgoing mail" if the user has no rights to see the page, rather than displaying an empty page. * Adjust UI to not block header on "show outgoing email" page * Hide the Take and Steal menu items if you already own the ticket, closing a regression in 4.2.0 and above. * Autocompletion custom fields now properly autocomplete when placed in custom field groupings * Improve rendering on Internet Explorer 6 * Fix cascaded custom fields on Internet Explorer 8 and below. * Fix third-level cascading custom fields, broken in 4.2.1 * Minor rendering bugs with Charts placed on homepages and dashboards * Whitelist "show outgoing email" and chart results from CSRF protection * RT 4.0.7 introduced a performance regression when building ticket searches that query Links; switch back to a much better-indexed query. * Fix "Clone ticket" functionality with Select-multiple custom fields. * Show the queue ID for the current queue in the ticket edit page, even if the user does not have SeeQueue; this prevents the user from accidentally changing the queue. * Respect custom field groupings on user preferences page Query Builder * Warnings avoidance for searches with more than 1000 results. * Allow IS NULL to search for dates which are unset * Properly quote CF names c
[rt-users] [rt-announce] RT 4.0.19 released
RT 4.0.19 -- 2014-01-13
---
We are pleased to announce RT 4.0.19 is now available.
http://download.bestpractical.com/pub/rt/release/rt-4.0.19.tar.gz
http://download.bestpractical.com/pub/rt/release/rt-4.0.19.tar.gz.sig
SHA1 sums
ce7bae429ed56603fef9e7a46d976d1ea9ed1e14 rt-4.0.19.tar.gz
fefb23bb549f94e65e803de295e747f143384557 rt-4.0.19.tar.gz.sig
This release is primarily a bugfix release; of particular note is that
it contains schema changes for MySQL, the first notable such in the 4.0
series. Though the changes are limited, it is especially important to
take, and verify you can recover from, a database backup prior to
upgrading.
Other changes of note:
Documentation
* Add documentation for rt-crontool
* Clean up examples in Lifecycles documentation
* Document additional indexes that increase performance of Shredder
* Replace a suggested GnuPG option with one which is not deprecated
* Note that errors reported from the GnuPG infrastructure may be caused
by GnuPG not being configured, but having been automatically enabled.
Database
* On MySQL, alter the character set of all columns used to store email
addresses to UTF-8
* Ensure that invalid byte sequences that may have snuck into the
database previously (on earlier versions on MySQL, for instance) are
not blindly interpreted as UTF-8 when retrieved from the database.
As a result, invalid bytes will be returned from the API as the four
characters "\xHH", where HH is the hexadecimal encoding of the byte.
* Ensure that all data containing non-ASCII is quoted-printable encoded
for PostgreSQL, instead of merely all data not claiming to be
"text/plain"
* Additional warnings prevention on Oracle; tests now pass cleanly
* Allow fully-automated database upgrades using --upgrade-from and
--upgrade-to options to rt-setup-database
* Clean out any remaining traces of RTFM that lingered in custom fields
and custom field values that were disabled at the time of the
previous upgrade step.
* Bullet-proof a 3.8 -> 4.0 upgrade step for Scrips with no Condition
Email
* Set a transfer encoding on outgoing dashboards; this resolves issues
with long lines when using the Sendmail MTA.
* Cope with mangled and overly-quoted recipient headers occasionally
generated by Outlook.
General user UI
* When using the back button to return to a reply page with the rich
text editor, contents will no longer be doubly HTML-encoded
* Improve rendering on Internet Explorer 6
* Fix cascaded custom fields on Internet Explorer 8 and below.
* Support cascaded selects for all Select render types (dropdown,
select box, radio buttons, checkboxes)
* Minor rendering bugs with Charts placed on homepages and dashboards
* Add "mark as seen" functionality to SelfService ticket display pages
* Link the ModifyPeople page when the user has Watch or WatchAsAdminCc
* Whitelist "show outgoing email" and chart results from CSRF
protection
* RT 4.0.7 introduced a performance regression when building ticket
searches that query Links; switch back to a much better-indexed
query.
* Fix "Clone ticket" functionality with Select-multiple custom fields.
* Show the queue ID for the current queue in the ticket edit page, even
if the user does not have SeeQueue; this prevents the user from
accidentally changing the queue.
Query Builder
* Support CF.Foo in addition to CF.{Foo} and '__CF.{Foo}__' in format
strings. This follows the trend of allowing brace-less forms
whenever possible.
* Ensure that format strings from the Query Builder escape quotes
correctly, and correctly parse existing formats with quotes.
* Autocomplete CF values for custom fields of type "Autocomplete" in
the Query Builder.
* Warnings avoidance for searches with more than 1000 results.
Admin
* Fix real-time updating of Theme CSS on Internet Explorer 8 and below
* Fix a minor display bug in the CF Admin pages, where the queue number
instead of queue name would be displayed in requests shortly after
server startup.
* Add "Extra Info" as a possible field for "More About Requestor"
iCal
* Ensure that iCal dates are formatted with a leading space on the
first nine days of each month, for correctness.
* Show iCal dates (when omitting times) in the user's timezone, not UTC
REST
* Prevent a server error when attempting to guess content-type in the
REST interface.
Development
* Custom Action and Condition packages (as supplied by extensions;
these are not the text entry boxes in the UI) are now loaded at
server startup time, to catch compile-time errors in such classes
early as well as reducing RT's memory footprint on mod_perl.
Previously, these errors would have logged errors only when their
Scrip failed to fire. This restores the behavior found in RT 3.8,
which was mistakenly removed in RT 4.0.0.
* rt-dump-metadata has slightly more documentation and options
* Additional callbacks, incl
[rt-users] Using Fetchmail to pipe mail into RT.
Hi, I am installing Request Tracker 4.2 on CentOS 6.5 with Perl, Apache, and MySQL. I am using Fetchmail as the MDA, and Postfix as the MTA. Google apps is being used as our main email system. So far I have resolved all dependencies and initialized the database and got the website going. I can log on as root and navigate the RT site just fine from another workstation. I had to follow the official documentation and do some wiki reading and intensive googling to get me where I am at now. I need some clear cut instructions on how to successfully pipe emails into RT. Is the /etc/aliases list required? Or can I just use ./fetchmailrc by itself? /etc/default/fetchmail is not created by default. How can I manually pipe emails into my RT instance? What syntax would I use for that? I googled around and could not find anything about that. Here is what my fetchmailrc configuration file looks like.. set daemon 30; poll pop.gmail.com proto pop3 username "jri...@cmhshare.org" password "mypassword" mda "/usr/bin/perl /opt/rt4/bin/rt-mailgate --url https://localhost/ \ --queue general --action correspond" keep ssl Question: at --url https://localhost/ <--is that supposed to be the FQDN or leave it as localhost? I can fetch email's from an external email server (Gmail) with success using fetchmail. However, nothing is appearing in the queue's on the RT site. The queue's name is the same name in the ./fetchmailrc config which is 'general'. I have viewed all the official documentation on the Best Practical site as well as the wiki and still no luck. I have been battling to get the email part working for 4 days now. If you need any extra information I will be happy to provide it. Thanks in advance and I look forward to your assistance. -- *Joshua Riden* *Operations Support TechnicianInformation Services * *Comprehensive Life Resources* *Email: **jri...@cmhshare.org* *Desk: x5844* *Mobile: **(253) 355-9877*
[rt-users] Question arround scrip and custom condition on comment
Hello everyone I'm wondering how to do something simple. I would like to call a script not "on" comment but after the comment insert in the database. Actually this is my condition : return 0 unless $self->TransactionObj->Type eq "Comment"; return 1; But the script is called when I click "on comment", how about after the comment insert in the database ? (with all the transaction done). Thank you very much Kind regards / Cordialement *Alexandre Leprevost* Project Engineer / Delivery Team 4 rue de l´Abreuvoir 92 400 Courbevoie France a...@efficientip.com Tel : +33 (0)1 75 84 88 98 Fax : +33 (0)9 57 88 09 40 www.efficientip.com
Re: [rt-users] db migration from mysql to postgres
Hi, thanks for the quick response, after sbin/rt-setup-database --action create,schema,acl --prompt-for-dba-password the import went flawlessly, Matthias Am 12.01.2014 um 21:24 schrieb Alex Vandiver : > On Sun, 2014-01-12 at 20:42 +0100, Matthias Peplow wrote: >> I found out the following: >> >> 1. rt-serializer and rt-import are not installed automatically, had to >> copy them from my build directory manually to the RTs sbin directory > > Already fixed in 4.2.2rc1. > >> 2. the import fails, as it is expecting the .dat files not in >> /my/backup/directory but in /my/backup/directory//my/backup/directory >> >> adding a symbolic link works as a workarround but this seems to be a >> bug. Not using the —directory switch works as well. > > Looks like a bug, yes. File it on issues.bestpractical.com? > >> 3. the import fails right at the beginning with >> >> DBD::Pg::st execute failed: ERROR: relation "users" does not exist >> LINE 1: SELECT * FROM Users WHERE LOWER(Name) = LOWER($1) > > http://docs.bestpractical.com/rt-importer#CLONED_DATA > > - Alex >
Re: [rt-users] How to notify owner about their responses?
You can use NotifyActor in RT_StiteConfig W dniu 2014-01-13 15:45, Ivan Osipov pisze: Hello all. Now I'm using scrip "On Correspond" -> "Notify Owner and AdminCcs", but when ticket owner reply to customer he does not receive email about their response. When other RT user send reply to customer (without assigning), then owner receive email about other RT user reply to customer. How I can notify owner about their responses?
[rt-users] How to notify owner about their responses?
Hello all. Now I'm using scrip "On Correspond" -> "Notify Owner and AdminCcs", but when ticket owner reply to customer he does not receive email about their response. When other RT user send reply to customer (without assigning), then owner receive email about other RT user reply to customer. How I can notify owner about their responses? -- Best regards, Ivan Osipov
[rt-users] REST mail-gateway using 100% cpu
Hello, I got this process im my apache POST //REST/1.0/NoAuth/mail-gateway HTTP/1.1 It hangs there until I kill it manualy, because it takes 100% of server cpu. Is the any way to fix it, cause I don't understand the reason why it behaves so. -- View this message in context: http://requesttracker.8502.n7.nabble.com/REST-mail-gateway-using-100-cpu-tp56255.html Sent from the Request Tracker - User mailing list archive at Nabble.com.
Re: [rt-users] Apache FastCGI and # of db connections
On Fri, Jan 10, 2014 at 07:13:28PM -0500, Alex Vandiver wrote: > On Fri, 2014-01-10 at 11:45 +0100, Václav Ovsík wrote: > > I have a question regarding behaviour of FastCGI processes and database > > connections. While preparing upgrade of RT 3.8.16 to RT 4.2.1 I noticed > > a change of FastCGI usage in the RT. > > Thanks for bringing this to our attention. This is a bug which affects > RT 4.0 and 4.2; the 4.0/fewer-active-handles branch resolves the issue. I have applied changes from your new branch and database handles are OK now. > > I did not study Plack too much - only look at > > http://search.cpan.org/~miyagawa/Plack-1.0030/lib/Plack/Handler/FCGI.pm > > and there is approach a bit different. One daemon is started standalone > > (forking to a number of processes) and Apache is configured to connect > > to this daemon > > FastCgiExternalServer /tmp/myapp.fcgi -socket /tmp/fcgi.sock > > This is a valid alternate deployment strategy, which comes with the > benefit that one can restart one RT server without affecting others, by > restarting its fastcgi process. However, it requires additional system > configuration to ensure that these processes are started at server > startup time, and so forth, which is why this is not the deployment > suggested in RT's documentation, which we aim to keep as simple as > possible. I understand it. > > Should I really increase PostgreSQL max_connections to 100 and don't > > bother with it? > > Until a version of RT is released with the above branch, increasing the > max_connections is likely your best bet. The additional connections > will consume some small amount of memory each, but this is likely > negligible, and will have no performance impact. > - Alex I have GIT versioned installed RT files, so no problem to apply some changes directly into installed RT instances. Thanks for quick response and good job! Best Regards -- Zito
Re: [rt-users] Using Runit and spawn-fcgi
Hello, On 11/01/2014 11:10 PM, Steven Hopps wrote: > I am trying to use RT4 under nginx. I'm using the following command to > start it: > > exec spawn-fcgi -n -u www-data -g www-data -a 127.0.0.1 -p 9000 -- > /opt/rt4/sbin/rt-server.fcgi > > If I run this command from the command line, it works. However if I > tell runit to execute the same command, I get bad gateway when trying > to create tickets. It does allow me to login and access the website > however. > On our system we are using an init script (etc/init.d/rt4) which does the following to start RT4: RTPATH="/opt/rt4/" RTUSER=www-data SOCKET_FILE=/opt/rt4/var/nginx/fcgi.sock # if you want to use a IP connection instead, please modify the su line to start it with -p or --port option instead of the --socket one. PID_FILE=/opt/rt4/var/nginx/fastcgi.pid case $1 in start) echo -n "Starting RT: " cd $RTPATH export FCGI_SOCKET_PATH RTUSER_GROUP="`id -gn $RTUSER 2>/dev/null`" if [ -n "$RTUSER_GROUP" ] then touch $PID_FILE $SOCKET_FILE; chown $RTUSER:$RTUSER_GROUP $PID_FILE $SOCKET_FILE fi su $RTUSER -c "/opt/rt4/sbin/rt-server.fcgi --pidfile=$PID_FILE --socket=$SOCKET_FILE 2> /dev/null" & echo "Started." ;; > There's two points of weirdness I'm hoping I can get help > understanding. First, why am I able to access RT but not create > tickets, and second, why do I get different results using runit to > execute the script than if I run the script manually at the prompt? > > Nicolas
[rt-users] RT4 - Howto customize the width of the queue selection box in the top-right corner - rudder theme
Hi, Can anyone give me some tips on how to make the queue selection box at the top-right corner slightly wider (using rudder theme) in RT 4.2.1 Tried playing around with the "topactions" class in the CSS files, but no luck. Thank you. Regards, Carl
