That is what the error is indicating, I just cannot seem to determine where
the loop is. If I misconfigured the queue, or if it was in RT_Siteconfig.
Also it is 4.4.1 on Ubuntu 14.04. I am quite sure it is a misconfiguration
on my part but (i tried with RTAddressRegexp configured for the
Dunno if this helps or not, but maybe the bounce is due to it detecting a loop?
 [Fri Jan 20 04:29:36 2017] [critical]: RT Received mail
) from itself.
I have searched through the list archives, and read a ton of posts
regarding bounces but have not been able narrow down what issue I am having
specifically. I have not modified any scrips from default. Have one queue
that is in use "Incident Reports', with the addresses
How do I have RT cancel or abort the creation of new tickets?
I have RT set to create tickets when it gets emails from another ticketing
system. I only want it to create tickets in RT though when it gets a certain
kind of email from that other ticketing system. Currently, RT creates tickets
Jeff - No limit that I'm aware of. If I look at a VM backup in December, the
SQL files actually hit 19GB+ versus the "18 and change". The only other
possibility that it COULD be is I've had to turn on Windows folder compression
because the backups are getting so large their filling the drive. I
I've done as you requested. It looks like I'm hovering around 31MB if I'm
reading it properly: 30828544 . Should I increase the packet size anyways? If I
split my backups into two pieces they appear to run properly. Both resulting
.sql files dhow the "dump complete" text at the end.
Am 19.01.2017 um 13:33 schrieb Cena, Stephen (ext. 300):
> I had that issue initially, and changed the value to 64MB. It was
> originally 4MB, then I increased it to 16MB, it’s been at 64MB for some
You can check your RT database to see whether 64MB is enough by running
I had that issue initially, and changed the value to 64MB. It was originally
4MB, then I increased it to 16MB, it's been at 64MB for some time.
# The maximum size of one packet or any generated or intermediate string, or
any parameter sent by the
# mysql_stmt_send_long_data() C API function.
just a stab in the dark, but could you please check the value set for
max_allowed_packet in the mysqldump section of /etc/mysql/my.cnf (or
whatever your my.cnf file is named)? If you try to dump mysql objects that
are larger than this size, mysqldump will stop; probably with a