Jeffrey Boone

My feedback

  1. 101 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    21 comments  ·  Feature Requests » Feature Enhancements  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jeffrey Boone supported this idea  · 
  2. 201 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    62 comments  ·  Feature Requests » New Idea  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Jeffrey Boone commented  · 

    As a consumer, I need to be able to produce a reliable list of email addresses that did not receive an email from a given set of batches (ie. domain + tag + timeframe), regardless if it was because of a permanent fail/bounce, soft-fails & timeout, delayed bounce, suppression, etc. Understandably, I would need to wait until the batches have completed or timed out before producing this extract.

    ---

    I would like to see an option to apply a filter to the events in the front-end (as I can do already), and then download the details of all the returned log entries as a CSV file.

    For instance, if I look for permanent fails for one domain over a short timeframe, I'd like the ability to export the timestamps, addresses, event type, and related messages to a CSV file. The same would go for any temporary failures, deliveries, etc.

    I would also like that download option to be for all matching entries; not just those displayed on the current screen or limited by API result size. For example, if I have 100,000 log entries that match the criteria, I'd like to see all 100,000 in the one CSV file. Understandably, that may need to be sent to a background processing thread, similar to how the bounce export is currently done.

    The extract should include any email addresses that were already rejected because of a prior filter in Mailgun (ie. hard-bounces or complaints), as well as any that had a delayed bounce.

    Thank you! :)

    Jeffrey Boone supported this idea  · 
  3. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Feature Requests » Dev Suggestion  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jeffrey Boone supported this idea  · 
  4. 4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Feature Requests » Feature Enhancements  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jeffrey Boone supported this idea  · 

Feedback and Knowledge Base