On 5/23/2012 2:50 PM, Thomas Sibley wrote:
On 05/23/2012 01:54 PM, Jeff Blaine wrote:
What's in your mail logs?
Absolutely nothing worthwhile :(
Can you send us your apache error logs?
Honest, there's nothing there to send you. Nothing in error logs
at all per-correspondence. Nothing bad in error logs at RT
startup.
Here's the ssl_access_log info from a reply, which is all
I have to show for the attempt:
xx.yy.44.251 - - [23/May/2012:15:44:14 -0400] "GET
/Ticket/Update.html?Action=Respond&id=54826 HTTP/1.1" 200 14631
xx.yy.44.251 - - [23/May/2012:15:44:19 -0400] "POST /Ticket/Update.html
HTTP/1.1" 302 365
xx.yy.44.251 - - [23/May/2012:15:44:21 -0400] "GET
/Ticket/Display.html?id=54826&results=47c7103ceafa17814c73bfbd05661ca1
HTTP/1.1" 200 41286
There's nothing in the mail queue and there's nothing in
/var/log/maillog, which we have configured in /etc/syslog.conf
as:
mail.* -/var/log/maillog
Are you running with selinux enabled?
Nope.
I'll point out, too, for more data ... that before I did the
patching yesterday, I did a:
mkdir SAVE
cp -rp bin lib share local etc SAVE
Looking at the new lib/RT/Interface/Email.pm from the patch, and
looking at the diff IN the patch file itself, I saw nothing
requiring any new code or DB references, so tried dropping the
old "SAVE/lib/RT/Interface/Email.pm" file back in place. It bought
me nothing.
