I'm seriously considering using the bounce email processing logic from Mailman. (Warning: this is potentially controversial) Thoughts on the actual text processing of bounced emails O EBH will first be developed for Drupal 5.x, with a 6.x version to follow. (Maybe we should even use the same module name?) O EBH can be a replacement for the current Bounced Email module. O EBH will require a working email server and an accessible mailbox, probably using IMAP(s) or POP(s). EBH periodically (via cron) open this mailbox and processes the emails within it. O Emails sent out by Drupal will have a return-path address set to a preconfigured mailbox. Of course, comments, suggestions, and opinions on the feature set are welcome. This is because I would prefer that EBH not store every single email sent out by the website. O Tag each bounced email with the original email which caused that bounce. O EBH will provide a way to list users with more than 3 bounced emails (so administrators can take the appropriate action) O Statistics are to be provided on bounced emails. So, for example, privileged users can view the bounce counts for simplenews subscribers which may not necessarily be user accounts. simplenews), EBH can display a list of the bounced emails associated with each email address. O For some modules which also store and use email addresses (ie. O EBH can also display individual bounce emails.ĮBH may optionally handle the following secondary use cases: O For each account, privileged users can view a count and a list of bounced emails associated with that account. O Privileged users can view a list of all bounced emails resulting from emails sent by the website. More on Bounced Email below.ĮBH will handle the following main use cases: The only thing that might have been relevant was Bounced Email, but that looks like a dead module. If I am incorrect in this observation, please let me know. See, for example, a previous post of mine which didn't elicit anything. I've been aware for the last year or so that Drupal core doesn't have any facilities to handle bounced emails. For convenience, let's call the proposed module EBH for now. The reverse bounty proposal is a module to handle bounced emails, and optionally to integrate statistics on bounced emails. Depending on the response, I may follow through, or postpone the idea. Or you can use your regular mailbox and set eMail Bounce Handler to remove the bounces once processed.I'd like to post up some thoughts on an idea for a reverse bounty and gather some preliminary opinions from other people. When you send a message with MaxBulk Mailer you can set an 'Error-To' address with a specific mailbox and then process it later with eMail Bounce Handler. eMail Bounce Handler connects to a mailbox of yours via POP3 or IMAP to process the emails and extract the bounces (delivery errors). It doesn't need MaxBulk Mailer and never connects to it anyways. No SMTP involved here.ĮMail Bounce Handler is an autonomous software. eMail Bounce Handler never sends emails, it only fetches them. Note that SMTP is the protocol for sending emails. Question: Where are the instructions for all the settings for eMail Bounce Handler? When I purchased, I assume I just run the program and it connects to my MaxBulk Mailer.ĭo not see instructions here: for all the settings I see in this app.īut it says to CREATE a pop account? Should this be the incoming credentials I am using for my SMTP account? OR is a new account being created somewhere?Īnswer: eMail Bounce handler is like an email client but it only fetches emails.Īs a result, it can use either the POP3 or IMAP protocols. How to get started with eMail Bounce Handler How to get started with eMail Bounce Handler Knowledge Base ▸ eMail Bounce Handler Please enable JavaScript to view the comments powered by Disqus.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |