I am using the message stack for various notifications. We also route mail to Amazon SES to handle delivery (not the Drupal module, I think we have it integrated directly with sendmail on the server). Our subscription however is on probation due a number of bounced messages because of user's changing emails over time.
Is there a suggested approach to handle this in the message notify framework? I have a jury rigged method of preventing some methods of message subscriptions, but as a long-term plan, I'd like a method of blacklisting bounced emails altogether. I was looking at https://www.drupal.org/project/bounce, but I'm not entirely sure it will fit in with our architecture with the AWS SES integrated on the server level.
I am using the message stack for various notifications. We also route mail to Amazon SES to handle delivery (not the Drupal module, I think we have it integrated directly with sendmail on the server). Our subscription however is on probation due a number of bounced messages because of user's changing emails over time.
Is there a suggested approach to handle this in the message notify framework? I have a jury rigged method of preventing some methods of message subscriptions, but as a long-term plan, I'd like a method of blacklisting bounced emails altogether. I was looking at https://www.drupal.org/project/bounce, but I'm not entirely sure it will fit in with our architecture with the AWS SES integrated on the server level.