This is the standard way to manage bounced mails.
With BMH bounced emails can be easily identified, and then users whose email bounced could be unsubscribed by Drupal.
http://sourceforge.net/projects/bmh/

Comments

momper’s picture

subscribe

sapelzin’s picture

subscribe

mattcasey’s picture

sub

weseze’s picture

I will try this in my personal development site. If it works good I will push this in the module.

weseze’s picture

It's a great framework and it handles bounced mails like it promises. But I fear it will not be flexible enough to do everything that our module might need to do in the future... I will delve into the code a bit deeper and see what's possible.
I believe the best approach would be to reuse some of the code in there to better suit a more generic mail handling.

Things that I don't see possible with BMH:

  • Handling a sent (test) newsletter to check if everything is working ok: return-path, reply-to, sender, ...
  • Handling an "unsubscribe me" reply
  • Deleting all mails in the inbox after a readout
  • Custom saving/handling of the mail itself: how to save/process the body of an email?
  • ...

Also I'm not seeing much development going on in the BMH project, so I'm assuming it is somewhat dead? (but still very useful)

philippejadin’s picture

I haven't looked at the BMH code, but imho what can have some value inside it is the code that guess if a return email is temporary error or a definitive one. (User unknown is <> than mailbox full)

The storage of emails and all would probabnly be done using Drupal DB access anyway. (even maybe using the watchdog?)

weseze’s picture

I've done some more work here and decided to just use BMH to speed up the development. You can see the work in the 2.x release of the module. Should be online shortly (waiting on the cron run)

weseze’s picture

Status: Active » Closed (fixed)