Hi folks
I have recently experienced this same problem too, and would like to comment
on what I did as a workaround. To recap on the problem:
Outgoing email is not sent by RT, and " Outgoing email recorded " does not
appear on the ticket. Restarting Apache resolves this temporarily. It is
definit
*My problem with the RT-System has been resolved!*
I've added an additional debug-level and got this:
-- snip --
Jan 3 12:30:08 rt RT:
<[EMAIL PROTECTED]> #450/6880 - Scrip
7 (/usr/share/request-tracker3.6/lib/RT/Action/SendEmail.pm:238)
Jan 3 12:30:08 rt RT:
<[EMAIL PROTECTED]> Debug: Afte
Re sending emails from Rt
if your mailserver is postfix, you might need to add the hostname of the
server running RT to the 'relayhosts' variable in postfix.
or the equivalent in sendmail.cf
regards
Oliver
On Thu, 3 Jan 2008, Alexander Rudolf Gruber wrote:
Thanks for the many replies everyon
Thanks for the many replies everyone and a happy new year 2008!
I've been away over the holidays and now I'm trying to resolve that
matter for good :-)
My replies to the respective postings are below.
Best wishes and thanks for your help!
Alexander
PS: I messed up my first posting of that messa
We had the problem of RT not sending mails to anybody too. But I don't
think that there were messages about that in rt.log because the fault
was that somebody changed the IP of the mailserver. So all mails sent by
RT stayed in the spool of postfix unless I corrected the postfix
configuration wi
Stephen,
AHHH! Kool. I just learned something. Then I really can't see
why RT can't find a recipient unless there is some disconnection between
what RT is looking for and where it looks for it. Alexander said there
were no changes to RT. The scrips are triggering, RT is looking, noth
At Thursday 12/20/2007 01:26 PM, Kenneth Crocker wrote:
Alexander,
I agree. If RT could not access the DB, then a lot of
things would not be working. However, my point was really that
based on the content of the error message, RT thinks that it hasn't
FOUND the recipient. There could,
Alexander,
I agree. If RT could not access the DB, then a lot of things would not
be working. However, my point was really that based on the content of
the error message, RT thinks that it hasn't FOUND the recipient. There
could, and probably are, many possible reasons for that. Perhaps afte
Kenneth Crocker schrieb:
Alexander,
IT could be that RT isn't getting to the User table for some
reason. The error message isn't saying it can't find a function or
some module isn't responding. It is just saying that it can't find a
recipient. Since recipients are (usually) some form of
Joop schrieb:
Alexander Rudolf Gruber wrote:
*Hi Everyone,
*
I've got a serious problem with our RT installation, which has worked
smoothly for over 6 months and then stopped sending emails (any kind
of emails: corresponcende, cc, owner change notifications etc.)
The weird thing is that ther
Alexander,
IT could be that RT isn't getting to the User table for some reason.
The error message isn't saying it can't find a function or some module
isn't responding. It is just saying that it can't find a recipient.
Since recipients are (usually) some form of user, I would look into the
Alexander Rudolf Gruber wrote:
*Hi Everyone,
*
I've got a serious problem with our RT installation, which has worked
smoothly for over 6 months and then stopped sending emails (any kind
of emails: corresponcende, cc, owner change notifications etc.)
The weird thing is that there where no prio
*Hi Everyone,
*
I've got a serious problem with our RT installation, which has worked
smoothly for over 6 months and then stopped sending emails (any kind of
emails: corresponcende, cc, owner change notifications etc.)
The weird thing is that there where no prior changes in queues, no new
use
13 matches
Mail list logo
