Dnia 2012-11-06, wto o godzinie 14:02 -0500, Kevin Falcone pisze:
On Fri, Nov 02, 2012 at 05:00:13PM +, Giuseppe Sollazzo wrote:
this might be a very silly problem but today we had an exchange with a
supplier.
The supplier triggers an automatic email creation notification which
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/11/12 09:39, Robert Wysocki wrote:
Leaving aside the original issue - why is that? Is this behavior
hardcoded or is it a question od default scrips?
I guess that the reason is that there are two systems, A and B.
We are A and use RT.
B is
On Wed, Nov 07, 2012 at 10:39:21AM +0100, Robert Wysocki wrote:
Dnia 2012-11-06, wto o godzinie 14:02 -0500, Kevin Falcone pisze:
You can delete the email address from the user of that system (leaving
their username set to the email address) which means RT will never
send them email.
On Wed, Nov 07, 2012 at 09:54:53AM +, Giuseppe Sollazzo wrote:
I guess that the reason is that there are two systems, A and B.
We are A and use RT.
B is configured to send a confirmation e-mail whenever it receives
anything from A.
A sends a print-out of the e-mail it receives to B.
Dnia 2012-11-07, śro o godzinie 10:12 -0500, Kevin Falcone pisze:
On Wed, Nov 07, 2012 at 10:39:21AM +0100, Robert Wysocki wrote:
Leaving aside the original issue - why is that? Is this behavior
hardcoded or is it a question od default scrips?
When email comes in, RT loads by the email
On Fri, Nov 02, 2012 at 05:00:13PM +, Giuseppe Sollazzo wrote:
this might be a very silly problem but today we had an exchange with a
supplier.
The supplier triggers an automatic email creation notification which
gets back to us, triggering a RT response, and so on.
To stop the loop, I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
this might be a very silly problem but today we had an exchange with a
supplier.
The supplier triggers an automatic email creation notification which
gets back to us, triggering a RT response, and so on.
To stop the loop, I had to deleted
