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”)?