Title: Bounced emails?
Last modified: February 7, 2019

---

# Bounced emails?

 *  [craftbilt](https://wordpress.org/support/users/craftbilt/)
 * (@craftbilt)
 * [7 years, 2 months ago](https://wordpress.org/support/topic/bounced-emails-5/)
 * I have read in ALO newsletter info: “bounce management: the bounced email addresses
   are automatically unsubscribed”.
 * Can I automatically delete bounced emails directly from the list?
    If yes, how
   can I do that? Thanks

Viewing 1 replies (of 1 total)

 *  Plugin Author [eventualo](https://wordpress.org/support/users/eventualo/)
 * (@eventualo)
 * [7 years, 2 months ago](https://wordpress.org/support/topic/bounced-emails-5/#post-11185169)
 * Hi, sorry, the text on the site is old I’ll update it.
    The right updated sentence
   about bounces is on plugin page here [https://wordpress.org/plugins/alo-easymail/](https://wordpress.org/plugins/alo-easymail/):“
   bounce management: you can check the bounced emails and keep your email list 
   clean” For security reason the bounce check is not automatic anymore, you can
   check your bounces periodically visiting the plugin setting page in your blog:
   _Newsletters > Settings > tab Bounces_.

Viewing 1 replies (of 1 total)

The topic ‘Bounced emails?’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/alo-easymail_574f4b.svg)
 * [ALO EasyMail Newsletter](https://wordpress.org/plugins/alo-easymail/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/alo-easymail/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/alo-easymail/)
 * [Active Topics](https://wordpress.org/support/plugin/alo-easymail/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/alo-easymail/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/alo-easymail/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [eventualo](https://wordpress.org/support/users/eventualo/)
 * Last activity: [7 years, 2 months ago](https://wordpress.org/support/topic/bounced-emails-5/#post-11185169)
 * Status: not resolved