[rt-users] RT4.0.6. not receiving any emails or routing them via rt-mailgate
On 24 July 2012 00:39, Thomas Sibley t...@bestpractical.com wrote: On 07/22/2012 05:47 AM, Hesan Yousif wrote: Technical details of temporary failure: The recipient server did not accept our requests to connect. Learn more at http://support.google.com/mail/bin/answer.py?answer=7720 [(21) mail.xxx.xx.xx. [13x.xxx.xx.xx]:25: Connection timed out] Your error is right there: Connection timed out. Google's mail servers couldn't connect to your MX on port 25. That's not an RT problem. My logs don't seem to track anything coming in, (syslog of RT, apache etc). Trying to send a queue in from the command line of the RT server produces this result: cat /usr/bin/test | /opt/rt4/bin/rt-mailgate --debug --queue rt-su-activities --url http://xxx.xxx/rt /opt/rt4/bin/rt-mailgate: temp file is '/tmp/WOZb2ZyjA1/8ulux8kHGM' /opt/rt4/bin/rt-mailgate: connecting to http://xxx.xxx/rt/REST/1.0/NoAuth/mail-gateway not ok - Could not load a valid user /opt/rt4/bin/rt-mailgate: no message passed on STDIN Er, you're passing a _binary_ (/usr/bin/test) into rt-mailgate. What do you expect to happen? No message passed on STDIN is correct... you didn't pass a valid email, just garbage. Dude, no need to be harsh! I was trying to set a test into rt-mailgate -if that was incorrect then apologies. Point is any mail sent into RT is not being routed into a queue and mail is receiving a timed out mail delivery failure. Are you able to assist in a constructive manner please? Hesan
Re: [rt-users] Running rt-server with SSL certificate
Actually, there is nothing about RT. You have to look how to run web-server with SSL. For ex. module for apache is mod_ssl. RT in this case is simply a backend (like php, perl, python) that generates you content. On Tue, Jul 24, 2012 at 1:47 PM, Mayk Backus bac...@nlcom.nl wrote: Helle List, Is there a how-to that explains on how to run rt-server with a ssl certificate. We have a wildcard cert that we want to use on our RT installation. Any tips are greatly appreciated. Thank you in advance, Regards, Mayk Backus Nlcom -- Jack Zabolotnyi Arces Network, LLC e: jzabolot...@arces.net w: http://www.arces.net PGP key: 2048R/7F2AB658 2012-07-02 PGP fingerprint: 4C7E 00A8 5210 F3D9 0509 C70E 87C8 666E 7F2A B658
Re: [rt-users] Running rt-server with SSL certificate
Hi, Thank you for the quick reply. We start RT with the rt-server command located in the sbin directory of RT. It's a own kind of daemon of RT that listens on a port. Thanks again, regards, Mayk Van: Jack Zabolotnyi jzabolot...@arces.net Datum: Tue, 24 Jul 2012 14:16:21 +0200 Aan: Mayk Backus bac...@nlcom.nl CC: rt-users@lists.bestpractical.com Onderwerp: Re: [rt-users] Running rt-server with SSL certificate Actually, there is nothing about RT. You have to look how to run web-server with SSL. For ex. module for apache is mod_ssl. RT in this case is simply a backend (like php, perl, python) that generates you content. On Tue, Jul 24, 2012 at 1:47 PM, Mayk Backus bac...@nlcom.nl wrote: Helle List, Is there a how-to that explains on how to run rt-server with a ssl certificate. We have a wildcard cert that we want to use on our RT installation. Any tips are greatly appreciated. Thank you in advance, Regards, Mayk Backus Nlcom -- Jack Zabolotnyi Arces Network, LLC e: jzabolot...@arces.net w: http://www.arces.net http://www.arces.net/ PGP key: 2048R/7F2AB658 2012-07-02 PGP fingerprint: 4C7E 00A8 5210 F3D9 0509 C70E 87C8 666E 7F2A B658
Re: [rt-users] Running rt-server with SSL certificate
On 24 Jul 2012, at 13:20, Mayk Backus wrote: Hi, Thank you for the quick reply. We start RT with the rt-server command located in the sbin directory of RT. It's a own kind of daemon of RT that listens on a port. That's only intended for development and experimental use, really. For production use, you should run RT from a real web server. The documentation that's included in the tar ball describes how to integrate it with Apache. Regards, Tim -- The Wellcome Trust Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE.
[rt-users] Extension and create Cfs at instalation of it
Hi list, does any one has a hint for me how I can create Cfs during the installation of an extension. Cheers, Björn
Re: [rt-users] Extension and create Cfs at instalation of it
On Tue, Jul 24, 2012 at 5:11 PM, Björn Schulz bjoern.sch...@desy.de wrote: Hi list, does any one has a hint for me how I can create Cfs during the installation of an extension. with etc/initialdata file. see RTIR's file for an example. Cheers, Björn -- Best regards, Ruslan.
Re: [rt-users] Extension and create Cfs at instalation of it
wow quick thx Ruslan have a great Day Björn On 24.07.12 15:15, Ruslan Zakirov wrote: On Tue, Jul 24, 2012 at 5:11 PM, Björn Schulz bjoern.sch...@desy.de wrote: Hi list, does any one has a hint for me how I can create Cfs during the installation of an extension. with etc/initialdata file. see RTIR's file for an example. Cheers, Björn
[rt-users] Limit Owner dropdown to only privileged users
Hello, RT Version - 4.0.2 The dropdown we see for selecting the owner of a ticket is currently populated with all the users of the system, including unprivileged users who have been auto created by emailing the system. How do I limit the dropdown to only include privileged users? Alternatively, how do I prevent auto creation of unprivileged users? I don't really see the point of users being created automatically when people email in. Thanks, Alex -- View this message in context: http://old.nabble.com/Limit-Owner-dropdown-to-only-privileged-users-tp34203861p34203861.html Sent from the Request Tracker - User mailing list archive at Nabble.com.
Re: [rt-users] Limit Owner dropdown to only privileged users
Take a look at the rights you assigned to the group Everyone You may have granted the OwnTicket right to Everyone, either at a global level (http://fpt-service.fpt.local/Admin/Global/GroupRights.html) or at a queue level (http://fpt-service.fpt.local/Admin/Queues/GroupRights.html?id=XX) This morning I bumped into the same problem. But in my case, this problem affected only one queue: OwnTicket was granted to Everyone at queue level. Hope this helps :) Alberto Scotto Blue Reply Via Cardinal Massaia, 83 10147 - Torino - ITALY phone: +39 011 29100 al.sco...@reply.it www.reply.it -Original Message- From: rt-users-boun...@lists.bestpractical.com [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Alex Dyas Sent: martedì 24 luglio 2012 15:58 To: rt-users@lists.bestpractical.com Subject: [rt-users] Limit Owner dropdown to only privileged users Hello, RT Version - 4.0.2 The dropdown we see for selecting the owner of a ticket is currently populated with all the users of the system, including unprivileged users who have been auto created by emailing the system. How do I limit the dropdown to only include privileged users? Alternatively, how do I prevent auto creation of unprivileged users? I don't really see the point of users being created automatically when people email in. Thanks, Alex -- View this message in context: http://old.nabble.com/Limit-Owner-dropdown-to-only-privileged-users-tp34203861p34203861.html Sent from the Request Tracker - User mailing list archive at Nabble.com. -- The information transmitted is intended for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.
Re: [rt-users] Limit Owner dropdown to only privileged users
On the group rights for each queue, ensure you have removed ALL rights for 'Everyone' and 'Unprivileged', then you should have user groups for your helpdesk. This (These) groups would be assigned permissions to the queue such as 'modify ticket'. I don't think you would want to prevent the autocreation of users that email in. They need to be a user to be the requestor of a ticket. -Original Message- From: rt-users-boun...@lists.bestpractical.com [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Alex Dyas Sent: Tuesday, July 24, 2012 8:58 AM To: rt-users@lists.bestpractical.com Subject: [rt-users] Limit Owner dropdown to only privileged users Hello, RT Version - 4.0.2 The dropdown we see for selecting the owner of a ticket is currently populated with all the users of the system, including unprivileged users who have been auto created by emailing the system. How do I limit the dropdown to only include privileged users? Alternatively, how do I prevent auto creation of unprivileged users? I don't really see the point of users being created automatically when people email in. Thanks, Alex -- View this message in context: http://old.nabble.com/Limit-Owner-dropdown-to-only-privileged-users-tp34203861p34203861.html Sent from the Request Tracker - User mailing list archive at Nabble.com.
Re: [rt-users] Limit Owner dropdown to only privileged users
Scotto, Izz, Thanks, as you both suggested I have reviewed my group privileges and indeed 'Everyone' has OwnTicket checked. Fixed! Thanks! Alex On 24/07/12 16:13, Scotto Alberto wrote: Take a look at the rights you assigned to the group Everyone You may have granted the OwnTicket right to Everyone, either at a global level (http://fpt-service.fpt.local/Admin/Global/GroupRights.html) or at a queue level (http://fpt-service.fpt.local/Admin/Queues/GroupRights.html?id=XX) This morning I bumped into the same problem. But in my case, this problem affected only one queue: OwnTicket was granted to Everyone at queue level. Hope this helps :) Alberto Scotto Blue Reply Via Cardinal Massaia, 83 10147 - Torino - ITALY phone: +39 011 29100 al.sco...@reply.it www.reply.it -Original Message- From: rt-users-boun...@lists.bestpractical.com [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Alex Dyas Sent: martedì 24 luglio 2012 15:58 To: rt-users@lists.bestpractical.com Subject: [rt-users] Limit Owner dropdown to only privileged users Hello, RT Version - 4.0.2 The dropdown we see for selecting the owner of a ticket is currently populated with all the users of the system, including unprivileged users who have been auto created by emailing the system. How do I limit the dropdown to only include privileged users? Alternatively, how do I prevent auto creation of unprivileged users? I don't really see the point of users being created automatically when people email in. Thanks, Alex -- View this message in context: http://old.nabble.com/Limit-Owner-dropdown-to-only-privileged-users-tp34203861p34203861.html Sent from the Request Tracker - User mailing list archive at Nabble.com. -- The information transmitted is intended for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. -- Alex Dyas, Manager - Systems Administration Tel: +41 22 348 30 15 www.linalis.com | twitter.com/linalis | www.linkedin.com/company/linalis Expert en Services, Formation et Recrutement BI et Applications Web (CMS, CRM) Partenaires certifies de Pentaho (BI), Jedox (Palo), Acquia (Drupal), SugarCRM et Infobright
[rt-users] Linking Articles to Tickets fails for other users
Hi, when linking an article to a ticket, everything works for the person doing the linking. If someone else tries to open the ticket he gets the following error message: Can't call method Id on an undefined value at /usr/share/request-tracker4/lib/RT/URI/fsck_com_article.pm line 135. Things we tried: - Checking the URI o This turned out be wrong, as the OrganizationName was incorrect. o Corrected it o The URI now looks legit, but still the problem persists - Debug log o Nothing turns up in the debug-log This is it, I can provide more information if someone points me to it... Best, JD
[rt-users] Installing RT 3.8.12 on Centos 5.5
Hello, I'm a Perl-skilled developer, new to RT, installing RT 3.8.12 on a CentOS 5.5 server. I was able to login to username=root password=password to bring up the RT-at-a-glance cite from a browser on the server. But when I try it from a browser on another client (Kubuntu 9.04) in my office with the same URL, I don't get a login window, but get he default (no website) response page from the server. I'm using the following vhost code in httpd.conf: VirtualHost rt.metacalculus.net:80 ServerName rt.metacalculus.net ServerAdmin ad...@rt.metacalculus.net DocumentRoot /opt/rt3/share/html AddDefaultCharSet UTF-8 PerlRequire /opt/rt3/bin/webmux.pl Directory /opt/rt3/share/html Order Allow,Deny Allow from all SetHandler perl-script PerlResponseHandler RT::Mason /Directory /VirtualHost When I look at the index.html page in the document root, I get the You are almost there message: You haven't yet configured your webserver to run RT. You appear to have installed RT's web interface correctly, but haven't yet configured your web server to run the RT server which powers the web interface. The next step is to edit your webserver's configuration file to instruct it to use RT's mod_perl, FastCGI or SpeedyCGI handler. If you need commercial support, please contact us at sa...@bestpractical.com. It seems there must be a problem with the Mason wrapping chain. Does anybody have a clue as to what is wrong? Thanks in advance, beartham -- Joseph 'Bear' Thames MetaCalculus, LLC and Meta Science Foundation (505) 977-9024 - Cell Phone beart...@gmail.com
Re: [rt-users] Installing RT 3.8.12 on Centos 5.5
On 07/24/2012 10:45 AM, Joseph Thames wrote: I'm a Perl-skilled developer, new to RT, installing RT 3.8.12 on a You should install 3.8.13 not 3.8.12, since 3.8.13 fixes deployment bugs. That said, if you're starting a new install, why are you still on the 3.8 series and not 4.0.6? VirtualHost rt.metacalculus.net:80 ServerName rt.metacalculus.net ServerAdmin ad...@rt.metacalculus.net DocumentRoot /opt/rt3/share/html AddDefaultCharSet UTF-8 PerlRequire /opt/rt3/bin/webmux.pl Directory /opt/rt3/share/html Order Allow,Deny Allow from all SetHandler perl-script PerlResponseHandler RT::Mason /Directory /VirtualHost Directory /opt/rt3/share/html should be Location /
Re: [rt-users] mailgate status 75
Can some one please help? I'm clueless :( m 23.07.2012 19:16, schrieb Matthias Henze: Hi, I use fetchmail with mailgate as MDA. With some mails I get: MDA returned non zero status 75. How can I fix this? TIA Matthias -- MHC SoftWare GmbH Fichtera 17 96274 Itzgrund/Germany voice: +49-(0)9533-92006-0 fax: +49-(0)9533-92006-6 e-mail: i...@mhcsoftware.de HR Coburg: B2242 Geschäftsführer: Matthias Henze
Re: [rt-users] mailgate status 75
On 07/24/2012 10:59 AM, Matthias Henze wrote: Can some one please help? I'm clueless :( m 23.07.2012 19:16, schrieb Matthias Henze: Hi, I use fetchmail with mailgate as MDA. With some mails I get: MDA returned non zero status 75. How can I fix this? 75 is a temporary failure code that tells the MTA (fetchmail) to retry delivery. Look at your RT or fetchmail logs for more info about why it's temporarily failing.
Re: [rt-users] mailgate status 75
Am 24.07.2012 20:09, schrieb Thomas Sibley: On 07/24/2012 10:59 AM, Matthias Henze wrote: Can some one please help? I'm clueless :( m 23.07.2012 19:16, schrieb Matthias Henze: Hi, I use fetchmail with mailgate as MDA. With some mails I get: MDA returned non zero status 75. How can I fix this? 75 is a temporary failure code that tells the MTA (fetchmail) to retry delivery. Look at your RT or fetchmail logs for more info about why it's temporarily failing. Well ... RT logs nothing. I've set: Set($LogToFile, 'debug'); Set($LogToFileNamed, 'rt.log'); Set($LogDir, '/var/log/request-tracker4'); and fetchmail logs (translated from German): Jul 24 20:19:40 server fetchmail[10027]: 1 messagage for support at mail.mhc.loc (138771 Bytes). Jul 24 20:19:40 server fetchmail[10027]: message supp...@mail.mhc.loc:1 of 1 read (138771 Bytes) (log message incomplete) Jul 24 20:19:40 server fetchmail[10027]: MDA returned non zero status 75. Jul 24 20:19:40 server fetchmail[10027]: not deleted -- MHC SoftWare GmbH Fichtera 17 96274 Itzgrund/Germany voice: +49-(0)9533-92006-0 fax: +49-(0)9533-92006-6 e-mail: i...@mhcsoftware.de HR Coburg: B2242 Geschäftsführer: Matthias Henze
Re: [rt-users] mailgate status 75
On 07/24/2012 11:34 AM, Matthias Henze wrote: Well ... RT logs nothing. I've set: Set($LogToFile, 'debug'); Set($LogToFileNamed, 'rt.log'); Set($LogDir, '/var/log/request-tracker4'); You've restarted RT since then? That is, you're seeing other debug messages? If rt-mailgate gets to RT, then you'll see logs. If rt-mailgate never gets to RT, then you'll need to bump up fetchmail's logging. Try adding --debug to your rt-mailgate invocation.
Re: [rt-users] mailgate status 75
Am 24.07.2012 20:39, schrieb Thomas Sibley: On 07/24/2012 11:34 AM, Matthias Henze wrote: Well ... RT logs nothing. I've set: Set($LogToFile, 'debug'); Set($LogToFileNamed, 'rt.log'); Set($LogDir, '/var/log/request-tracker4'); You've restarted RT since then? Restarted apache ... as afaik this is the way to restart RT. That is, you're seeing other debug messages? If rt-mailgate gets to RT, then you'll see logs. Sorry, no log output ... even if I use the web interface. If rt-mailgate never gets to RT, then you'll need to bump up fetchmail's logging. Try adding --debug to your rt-mailgate invocation. No new log entries ... When I tell fetchmail to be verbose I see: /usr/bin/rt-mailgate: temp file is '/tmp/P1i3k63lRt/bJsSdLS5vw' /usr/bin/rt-mailgate: connecting to http://rt.mhc.loc/rt//REST/1.0/NoAuth/mail-gateway An Error Occurred = 500 Internal Server Error /usr/bin/rt-mailgate: undefined server error -- MHC SoftWare GmbH Fichtera 17 96274 Itzgrund/Germany voice: +49-(0)9533-92006-0 fax: +49-(0)9533-92006-6 e-mail: i...@mhcsoftware.de HR Coburg: B2242 Geschäftsführer: Matthias Henze
Re: [rt-users] mailgate status 75
On 07/24/2012 11:59 AM, Matthias Henze wrote: When I tell fetchmail to be verbose I see: /usr/bin/rt-mailgate: temp file is '/tmp/P1i3k63lRt/bJsSdLS5vw' /usr/bin/rt-mailgate: connecting to http://rt.mhc.loc/rt//REST/1.0/NoAuth/mail-gateway An Error Occurred = 500 Internal Server Error /usr/bin/rt-mailgate: undefined server error Look in your apache error logs.
[rt-users] User exists but does not show up under Users in the web interface
Hello, I'm not sure how to modify this user. The user exists but does not show up under Users in the web interface. When I login to the database, I can find the user and it says, Autocreated when added as a watcher How can I modify users who were autocreated? The list of users says, Privileged users Is there a way to display unprivileged users. I could edit the database directly, but I think I recall reading that could cause some database corruption, and much larger problems. Thanks, Sandra
Re: [rt-users] User exists but does not show up under Users in the web interface
Hi Sandra, I ran in to something simmiler what I did was under tools configure users, I hade to tick Include disabled users in search and selected the user that I what to modify. In the Modify the user Chamara under access control I had to tick Let this user access RT (this would be already selected) Let this user be granted rights (Privileged) Hope this helps Regards From: Sandra Wittenbrock san...@hpcrd.lbl.gov To: rt-users@lists.bestpractical.com Sent: Wednesday, 25 July 2012, 5:27 Subject: [rt-users] User exists but does not show up under Users in the web interface Hello, I'm not sure how to modify this user. The user exists but does not show up under Users in the web interface. When I login to the database, I can find the user and it says, Autocreated when added as a watcher How can I modify users who were autocreated? The list of users says, Privileged users Is there a way to display unprivileged users. I could edit the database directly, but I think I recall reading that could cause some database corruption, and much larger problems. Thanks, Sandra
Re: [rt-users] Installing RT 3.8.12 on Centos 5.5
Hi Below is a section of my RT since I had something similar DocumentRoot /usr/local/rt-ora/share/html Location / Order allow,deny Allow from all SetHandler perl-script PerlResponseHandler Plack::Handler::Apache2 PerlSetVar psgi_app /usr/local/rt-ora/sbin/rt-server /Location Perl use Plack::Handler::Apache2; Plack::Handler::Apache2-preload(/usr/local/rt-ora/sbin/rt-server); /Perl /VirtualHost Hope it helps Regards From: Joseph Thames beart...@gmail.com To: rt-users@lists.bestpractical.com Sent: Tuesday, 24 July 2012, 23:15 Subject: [rt-users] Installing RT 3.8.12 on Centos 5.5 Hello, I'm a Perl-skilled developer, new to RT, installing RT 3.8.12 on a CentOS 5.5 server. I was able to login to username=root password=password to bring up the RT-at-a-glance cite from a browser on the server. But when I try it from a browser on another client (Kubuntu 9.04) in my office with the same URL, I don't get a login window, but get he default (no website) response page from the server. I'm using the following vhost code in httpd.conf: VirtualHost rt.metacalculus.net:80 ServerName rt.metacalculus.net ServerAdmin ad...@rt.metacalculus.net DocumentRoot /opt/rt3/share/html AddDefaultCharSet UTF-8 PerlRequire /opt/rt3/bin/webmux.pl Directory /opt/rt3/share/html Order Allow,Deny Allow from all SetHandler perl-script PerlResponseHandler RT::Mason /Directory /VirtualHost When I look at the index.html page in the document root, I get the You are almost there message: You haven't yet configured your webserver to run RT. You appear to have installed RT's web interface correctly, but haven't yet configured your web server to run the RT server which powers the web interface. The next step is to edit your webserver's configuration file to instruct it to use RT's mod_perl, FastCGI or SpeedyCGI handler. If you need commercial support, please contact us at sa...@bestpractical.com. It seems there must be a problem with the Mason wrapping chain. Does anybody have a clue as to what is wrong? Thanks in advance, beartham -- Joseph 'Bear' Thames MetaCalculus, LLC and Meta Science Foundation (505) 977-9024 - Cell Phone beart...@gmail.com
Re: [rt-users] mailgate status 75
Am 24.07.2012 22:27, schrieb Thomas Sibley: On 07/24/2012 11:59 AM, Matthias Henze wrote: When I tell fetchmail to be verbose I see: /usr/bin/rt-mailgate: temp file is '/tmp/P1i3k63lRt/bJsSdLS5vw' /usr/bin/rt-mailgate: connecting to http://rt.mhc.loc/rt//REST/1.0/NoAuth/mail-gateway An Error Occurred = 500 Internal Server Error /usr/bin/rt-mailgate: undefined server error Look in your apache error logs. Thanks, found: [Wed Jul 25 07:25:10 2012] [warn] [client 192.168.100.13] mod_fcgid: HTTP request length 137135 (so far) exceeds MaxRequestLen (131072) fixed, works. -- MHC SoftWare GmbH Fichtera 17 96274 Itzgrund/Germany voice: +49-(0)9533-92006-0 fax: +49-(0)9533-92006-6 e-mail: i...@mhcsoftware.de HR Coburg: B2242 Geschäftsführer: Matthias Henze
