Handling bounced emails

There is a try with Simplenews Bounce module, but it's apparently not finished.

U cannot use it i expect. It was a hint on work-in-progress where you can participate.

The modules need a lot of work!

Moving all feature request to 7.x.

I have a related question.

Is there a way for simplenews to simply ignore bounced emails, i.e. not keep sending them forever?
This is very disturbing, people keep getting repeated emails every cron run, because their mail provider sends a bounce message, but some people get the newsletter anyway... dozens of times!

It's ok if people miss one newsletter.

I'm using cron via cpanel.

A mail bounce is, if the mail successfully leaves our server and the receiving server then answers LATER with a bounce mail. Thus, Simplenews records sending of the mail as successfull.

A mail reject is, if the mail is immediately rejected and no delivery occurred... Thus, the local mailserver e.g. immediately knows a mailbox doesn't exist. However this results in a Mail being NOT DELIVERED. Simplenews 6.x-2.x starts handling those cases and marking send as unsuccessful. It stops sending them.

As of the current standards, your case should NEVER happen. Except a receiving mail server is not following the standards.... but it's not our job to handle those cases.

You'll need to provide more report information about exact states, mail headers to allow us finding a bug - if there's any.

Note that this is a feature request for bounce handling. This is NOT a support issue for your related questions.

Sorry, this is a support request:
Is there anyway for simplenews to ignore bounce and automaticaly consider as successfull every email sent?

A note: I'm a newbie - that's for sure - but i did get a "Delivery Status Notification (Failure)" message every cron run, for at least a hotmail account and a gmail account, although the users did get dozens of copies of the messages and got angry. This is just to let you know that in some instances a "Delivery Status Notification (Failure)" doesn't mean the user didn't get the message.

This Task here still will remain a feature request for Bounce handling. You're doing is what we call "hijacking an issue"...

Please add a new task with a title like "Cron never completes! Tries resending mail on every run"

And add more information from your system! I have no cristal ball to guess your technical details that might be the reason for your issues.

Sorry about that, I tought it was related enough.
I imagined cron was *supposed* to retry sending failed messages every run.

I'll start a new issue.

You might take a look at this experimental standalone bounce processing module, and see if it works for you:

http://drupal.org/sandbox/exratione/1484526

Indeed an interesting one.

There's also:
http://drupal.org/project/bounce_handler
and then there's the well known civicrm that processes bounces also:
http://en.flossmanuals.net/civicrm/ch042_system-configuration/

I propose a simple starting point for Simplenews 7.x (Possibly still in Simplenews Bounce 7.x-1.x)... and later possibly push Drupal 8 core native VERP support.

My research 3 years on suggests that there still isn't much of a solution:

https://www.drupal.org/project/bounce has a D7 release but minimally maintained. From reading their module page I would say this module could prevent future sending based on non-delivery reports. However it won't integrate with Simplenews to deactivate the entry in the newsletter subscription list.

https://www.drupal.org/project/simplenews_bmh has a v6 release but only 70 sites using it. The D7 version was reported as 'underway' in July 2013, but no update since.

Of the other modules reported above, bounce_handler has only 1 active D6 site and simplenews_bounce seems to be abandoned.

We've been working for 3 months on a processing framework for incoming mails for Drupal 8:
https://www.drupal.org/project/inmail

I'm sorry we can not provide a satisfying answer for Drupal 6 / 7, but for Drupal 8, the issue is clearly resolved.
Now we are hoping that other projects join forces and depend to inmail and extend from it.
Most importantly, we are discussing this collaboration with the Mailhandler project, see issue:
#2415401: Drupal 8 port: Collaborate with inmail

@miro Thanks for the update - that's good news. Will there be some form of integration via hooks or similar? It would be great if the newsletter subscription list indicated any entries that have been disabled due to bounces.

@AdamPS: No, we don't have counters visible in Simplenews.
I created followups to track and discuss the issues:
#2461915: Show bounced recipient count
#2461911: Show muted recipient count