Hi all,
When we send email to an address that doesn't exist, ie, that bounces,
RT doesn't record the problem in the ticket. So we could be in a
situation where we think that everyone knows about the ticket, but the
email address was wrong in the CC list.
Likewise we may be waiting for someone to
On Mon, Jan 25, 2010 at 02:15:47PM +0100, L B wrote:
Hi all,
When we send email to an address that doesn't exist, ie, that bounces,
RT doesn't record the problem in the ticket. So we could be in a
situation where we think that everyone knows about the ticket, but the
email address was wrong
I think it's difficult for bounced emails because there is no standard
regarding this kind of emails, so it's hard to stop loops, but it
should be easier for out of office messages. The problem is that, I
think, we need to parse the email content to get a ticket number
unless the out of office
On Mon, Jan 25, 2010 at 03:19:40PM +0100, L B wrote:
I think it's difficult for bounced emails because there is no standard
regarding this kind of emails, so it's hard to stop loops, but it
should be easier for out of office messages. The problem is that, I
think, we need to parse the email
On Mon, Jan 25, 2010 at 07:38:38AM -0600, Kenneth Marshall wrote:
RT handles bounces by ignoring them to prevent loops as you
suggested. It would be neat to have some error handling that would
update the ticket with the message statuses without sending E-mail.
You could disable bad addresses,
See rtbouncehandler on the wiki.
It works well, although it does double the amount of notices
you receive for SPAM messages since they typically use bogus addresses
which cannot receive auto-responses.
--
Cambridge Energy Alliance: Save money. Save the planet.
