[rt-users] no To: header in AdminCC's mails
Hi all, I was sure this would have come up somewhere but i can't make a search produce any results. This also tells me that it's most likely my error if no-one else has the problem Mails to "AdminCC" are sent as a BCC, but there is no To: or CC: fields, so spam filtering marks all the mails as spam. 1.2 MISSING_HEADERSMissing To: header 1.9 REPLYTO_WITHOUT_TO_CC REPLYTO_WITHOUT_TO_CC I have made a workaround solution by putting a To: header in the admincc template that sends the mail to a /dev/null mailbox, but that's hardly ideal. Below are the full headers of the mail thanks in advance for any suggestions Woody. Return-Path: Received: from deliver ([unix socket]) by math.xxx.net (Cyrus v2.3.16-Fedora-RPM-2.3.16-13.el6_6) with LMTPA; Mon, 07 Dec 2015 08:30:55 + X-Sieve: CMU Sieve 2.3 Received: from bodge.xxx.org ([xxx.xxx.xxx.xx]) by math.xxx.net with esmtp (Exim 4.72) (envelope-from ) id 1a5rCA-0001wG-7Q; Mon, 07 Dec 2015 08:30:55 + Received: from www-data by bodge.x.org with local (Exim 4.82) (envelope-from ) id 1a5rC4-0001D1-VW; Mon, 07 Dec 2015 08:30:49 + Subject: Re: Fw: WTG Jeep Cherokee 2006 From: works...@xxx.com Reply-To: works...@xxx.com In-Reply-To: References:<56654142.3090...@xxx.com> Message-ID: X-RT-Loop-Prevention: WT X-RT-Ticket: WT #82786 X-Managed-BY: RT 4.2.9 (http://www.bestpractical.com/rt/) X-RT-Originator: step...@xxx.org Content-Type: multipart/mixed; boundary="--=_1449477048-4190-15" Precedence: bulk Date: Mon, 07 Dec 2015 11:30:48 +0300 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Score: 2.5 (++) X-Spam-Report: Spam detection software, running on the system "math.xxx.net", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Ticket URL: http://rt.xxx.com/Ticket/Display.html?id=82786 Hi Woody, No idea whether it has been skimmed before. The previous owner is not contactable, so I cannot check with him. He had it from new, and I'm not aware of any earlier problems. [...] Content analysis details: (2.5 points, 5.0 required) pts rule name description -- -- -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low trust [xx.xx.xx.xx listed in list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record 1.2 MISSING_HEADERSMissing To: header 0.0 TVD_FW_GRAPHIC_NAME_MID BODY: Medium sized image attachment name 0.0 HTML_MESSAGE BODY: HTML included in message 1.9 REPLYTO_WITHOUT_TO_CC REPLYTO_WITHOUT_TO_CC This is a multi-part message in MIME format... =_1449477048-4190-15 Content-Type: multipart/alternative; boundary="--=_1449477048-4190-14" This is a multi-part message in MIME format... =_1449477048-4190-14 RT-Attach-Message: yes Content-Type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 Ticket URL: http://rt.xxx.com/Ticket/Display.html?id=82786 Hi Woody, Regards,
Re: [rt-users] Debugging RT code....
On 7 Dec 2015, at 20:01, Gary Greene wrote: I’m working on updating the rt-reminders.pl to work with the newer API, and I’m getting the following error when running it from command-line: rt:~/bin # /root/bin/rt-reminders.pl -r Can't call method "warn" on an undefined value at /usr/lib/perl5/vendor_perl/5.20.1/RT.pm line 954. We’re running RT 4.2.12 on openSUSE 13.2. Any ideas would be helpful. Get a stack trace. Something called a deprecated method in an odd way such that RT=>Deprecated() couldn't figure out a caller name.
[rt-users] Debugging RT code....
I’m working on updating the rt-reminders.pl to work with the newer API, and I’m getting the following error when running it from command-line: rt:~/bin # /root/bin/rt-reminders.pl -r Can't call method "warn" on an undefined value at /usr/lib/perl5/vendor_perl/5.20.1/RT.pm line 954. We’re running RT 4.2.12 on openSUSE 13.2. Any ideas would be helpful. Thanks. -- Gary L. Greene, Jr. Sr. Systems Administrator IT Operations Minerva Networks, Inc. Cell: +1 (650) 704-6633 signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [rt-users] Trouble/Error with Web deployment httpd/apache/mod_fcgid
Quotes are fixed now if you follow the "View this message in context:" URL in the previous email from this thread... -- View this message in context: http://requesttracker.8502.n7.nabble.com/Trouble-Error-with-Web-deployment-CentOS-httpd-mod-fcgid-tp60979p61072.html Sent from the Request Tracker - User mailing list archive at Nabble.com.
Re: [rt-users] Trouble/Error with Web deployment httpd/apache/mod_fcgid
Bill Cole-8 wrote > That's odd. The RT configure script should have figured out a better > ownership/permissions model and generated a Makefile that did the right > thing for you. There is some stuff in RT that's 640 or 750, but if > fixperms did the wrong thing it was because configure couldn't determine > the right owner and/or group, not because the apache user wasn't in the > right group. > > > REPLY: > I flubbed up from the begining and just discovered what my first mistake > was (fixable mistake but very annoying)...when I ran ./configure I should > have passed it as such being that I'm installing on RHEL/CentOS...anyone > installing on RHEL/CentOS take note this could save you a lot of time if > you configure this way from the get go I believe: */ > ./configure --with-web-user=apache --with-web-group=apache /* > > Since the default on RHEL/CentOS is to use the apache:apache user and > group and not www/www-data/nobody as far as I know and with other > distributions. > > *** > > That's slightly odd: I'd expect that to get you the default (httpd.conf) > document root. > > I STRONGLY recommend a long read of the Apache docs. Particularly: > > https://httpd.apache.org/docs/2.4/dns-caveats.html > https://httpd.apache.org/docs/2.4/vhosts/details.html > https://httpd.apache.org/docs/2.4/vhosts/name-based.html > > > REPLY: > > Duly noted...The first link helped me immensely! Thank you! I changed my > VirtualHost to use my server's IP address rather than the FQDN > > instead of > > That seemed to do the trick and stop the majority of the strangeness I was > experiencing. The rest was permissions issues due to my first mistake > above from what I can tell. > > After I installed & enabled the RT-IR addon for RT I had to fix the > permissions here also due to my first mistake as well: > > From /opt/rt4/var/mason_data/ . chown -R apache:apache * > > This got RT-IR working. > > *** > > That sounds like it could be an iptables issue, except that I'd expect > an error complaining about the connection. > > Apache's logs should be helpful if you're getting a connection and > making a request but then not getting anything back. > > REPLY: > > Again you're on point sir. I suspected this may be iptables as well but > was slightly caught off guard as my defauly policy for the INPUT & FORWARD > chains were ACCEPT...I did not notice the default DENY rule at the bottom > of the INPUT chain that FILTERS traffic that doesn't match rules above > itI re-hashed my iptables rulebase with default DENY for INPUT & > FORWARD and provisioned proper rules above to allow operations of > RT/RT-IR. > > > *** > > > Seems reasonable, but I'd suggest 3 things: > > 1. Set( $DatabaseHost, '' ); > This causes RT to connect over the mysql local socket rather than > TCP to localhost:3306, which means slightly better performance and one > more network listener you can kill (unless you need that mysqld for > other things that aren't local or are too dumb to use sockets) > > 2. Remove any mention of WebBaseURL. Unless you have RT behind a proxy > or have Apache doing HTTPS on a port other than 443, the code in > RT_Config.pm will build the correct value for you. > > 3. Set( $WebPort, '443' ); > Yes, that also means you will need to set up HTTPS in Apache. > However, if your RT is serving anything other than you on the same host > (don't laugh, I've seen that) you're going to want it only every using > TLS. Even more true if you have it on a campus network of a major public > university known to operate intensive network sniffing and scanning > projects as research. > > > REPLY: > > Great stuff. I def. implemented item #1 here as this is a better way to > go for my sandbox and for my dev RT/RT-IR servers. > > Item #2 I also went ahead and did as recommend as that makes sense. > > Item #3 That is the plan once I get to the part where I am building my > production server...I will be setting up apache to use our SSO > implementation here that requires SSL/TLS at our super scanning major > university (I've nothing to do with that research other than dealing with > some of its fallout on occasion so trust me I totally understand what you > mean.) > > From what I've read thus far setting up https/TLS may be a challenge with > RT/RT-IR especially with getting rt-mailgate/e-mail ticket creation > working which is in scope for us so these two things will be my next > challengeand I'm sure you'll see posts from me here about in the very > near future : ) > > On that notethis is the best resource i've found on setting up > rt-mailgate/e-mail ticketing...is there something better out there or an > example config/tutorial I do not know about ye
[rt-users] Can't locate RT/Calendar.pm - Compilation Error
Hi, I installed MyCalendar Extension and after I selected on my dashboard, RT show me this error on my dashboard "An internal RT error has occurred. Your administrator can find more details in RT's log files." (RT 4.2.12 ; Centos 6.7.) Looking into my logs: [25525] [Fri Dec 4 16:56:28 2015] [error]: Error during compilation of /opt/rt4/share/html/Elements/MyCalendar: Can't locate RT/Calendar.pm in @INC (@INC contains: /opt/rt4/sbin/../local/lib /opt/rt4/sbin/../lib /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at /opt/rt4/share/html/Elements/MyCalendar line 41. Stack: [/opt/rt4/share/html/Elements/MyCalendar:41] [RT/Calendar.pm:41] [/usr/local/share/perl5/HTML/Mason/Interp.pm:817] [/usr/local/share/perl5/HTML/Mason/Interp.pm:445] [/usr/local/share/perl5/HTML/Mason/Request.pm:1127] [/usr/local/share/perl5/HTML/Mason/Request.pm:1060] [/usr/local/share/perl5/HTML/Mason/Request.pm:1239] [/opt/rt4/share/html/Elements/MyRT:96] [/opt/rt4/share/html/index.html:78] [/opt/rt4/sbin/../lib/RT/Interface/Web.pm:681] [/opt/rt4/sbin/../lib/RT/Interface/Web.pm:369] [/opt/rt4/share/html/autohandler:53] BEGIN failed--compilation aborted at /opt/rt4/share/html/Elements/MyCalendar line 41. Stack: [/opt/rt4/share/html/Elements/MyCalendar:41] [/usr/local/share/perl5/HTML/Mason/Interp.pm:817] [/usr/local/share/perl5/HTML/Mason/Interp.pm:445] [/usr/local/share/perl5/HTML/Mason/Request.pm:1127] [/usr/local/share/perl5/HTML/Mason/Request.pm:1060] [/usr/local/share/perl5/HTML/Mason/Request.pm:1239] [/opt/rt4/share/html/Elements/MyRT:96] [/opt/rt4/share/html/index.html:78] [/opt/rt4/sbin/../lib/RT/Interface/Web.pm:681] [/opt/rt4/sbin/../lib/RT/Interface/Web.pm:369] [/opt/rt4/share/html/autohandler:53] Stack: [/usr/local/share/perl5/HTML/Mason/Interp.pm:450] [/usr/local/share/perl5/HTML/Mason/Request.pm:1127] [/usr/local/share/perl5/HTML/Mason/Request.pm:1060] [/usr/local/share/perl5/HTML/Mason/Request.pm:1239] [/opt/rt4/share/html/Elements/MyRT:96] [/opt/rt4/share/html/index.html:78] [/opt/rt4/sbin/../lib/RT/Interface/Web.pm:681] [/opt/rt4/sbin/../lib/RT/Interface/Web.pm:369] [/opt/rt4/share/html/autohandler:53] (/opt/rt4/sbin/../lib/RT/Interface/Web/Handler.pm:208) A quick help will be appreciated as we are missing critical requests. Thanks.