I was curious where emails that don’t exist go when RT attempt to send an SMTP notification to an email that no longer exists (but is still left over email address of an old ticket that is updated - i.e.: old/deleted RT user was a “Requestor” of a ticket)?
We have had old employees that have been left and are curious if that’s what may be slowing down our RT server (maybe bad emails are re-queuing up for re-sending).
I guess my question is: How does RT handle bad emails? Does it re-try? Does it have any intelligence built in to delete future sending to a bad email (but still on tickets as “Requestor” or “Owner”)?
I was curious where emails that don’t exist go when RT attempt to send an SMTP notification to an email that no longer exists (but is still left over email address of an old ticket that is updated - i.e.: old/deleted RT user was a “Requestor” of a ticket)?
We have had old employees that have been left and are curious if that’s what may be slowing down our RT server (maybe bad emails are re-queuing up for re-sending).
I guess my question is: How does RT handle bad emails? Does it re-try? Does it have any intelligence built in to delete future sending to a bad email (but still on tickets as “Requestor” or “Owner”)?
So are you saying that it does a query on the “RT user list” to determine if it should/shouldn’t send an email to that user?
If an RT user is disabled or deleted, wouldn’t it still attempt to send to that user/email since it’s still attached to an old ticket (update to this particular old ticket of course)?
Anyone out there have a snip of the code where it handles this?
I was curious where emails that don’t exist go when RT attempt to send an SMTP notification to an email that no longer exists (but is still left over email address of an old ticket that is updated - i.e.: old/deleted RT user was a “Requestor” of a ticket)?
We have had old employees that have been left and are curious if that’s what may be slowing down our RT server (maybe bad emails are re-queuing up for re-sending).
I guess my question is: How does RT handle bad emails? Does it re-try? Does it have any intelligence built in to delete future sending to a bad email (but still on tickets as “Requestor” or “Owner”)?
I guess my question is: How does RT handle bad emails? Does it re-try? Does it have any intelligence built in to delete future sending to a bad email (but still on tickets as “Requestor” or “Owner”)?
RT doesn’t have any re-trying logic in it. It simply delivers to the
local MTA (or whatever you have configured) and lets that deal with it.
Deleted users are no longer attached to old tickets. You can always remove the email address associated with disabled users so that it does not try to email.
Understand the difference in deleted and disabled. Deleted - removed from the mySQL database and therefore no longer associated at all in historical relationships, Disabled - just cannot access RT, but still exists in the database. I would edit the user information to remove the email address if you are following a best practice and just disabling the users.
Just my $0.02 worth.From: Andy GOKTAS [mailto:andy.goktas@state.or.us]
Sent: Monday, October 17, 2011 4:57 PM
To: Izz Abdullah; rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Old Email/RT user accounts and SMTP nofication…Emailsgo to NeverNeverLand?
So are you saying that it does a query on the “RT user list” to determine if it should/shouldn’t send an email to that user?
If an RT user is disabled or deleted, wouldn’t it still attempt to send to that user/email since it’s still attached to an old ticket (update to this particular old ticket of course)?
Anyone out there have a snip of the code where it handles this?
Thanks,
Andy Goktas
Izz Abdullah Izz.Abdullah@hibbett.com 10/17/2011 2:45 PM >>>
Probably only if you have disabled the user from within RT itself.
If an RT consumer is disabled or deleted, wouldn’t it still try to ship to that user/e mail since it’s nevertheless attached to an antique ticket with fake mail from Owlymail (replace to this precise antique price ticket of path)?