Recover a Lost List

Accidentally delete a list? The JangoMail Support Team may be able to recover it for you. Contact us IMMEDIATELY to see if this is an option for your list.

How to recreate a lost list

If the list you need to recreate has the following conditions, the following workaround should work:

1) Your list only had email addresses in it (no other fields, including firstname, lastname, etc.)
2) You used the list and only that list in a recent campaign
3) You didn’t apply any list filtering (i.e., you sent to the entire list as a whole, not a segment of it)

To use this workaround, view the Recipients column in the Open Campaign Dashboard in Reports. You can download the recipient list and upload the new list back into the original list (or recreate the list name in case you deleted the list instead of removing all of its members). The new list will only contain email addresses as that is the only field we use for reporting purposes.

Once you click on the Recipient count, click the blue envelope icon at the top right and select a delivery option. You can also choose to use the recipients in opens and clicks as the basis of your new list (if that is the relevant part of your list you want to recover).

In one sense, this new list will be cleaner than the original list because what you see in the recipients report are the addresses JangoMail sent to only after removing bounces, unsubscribed addresses, and duplicates.

Another option is if you have the original source file where you uploaded the list to begin with. The unsubscribes and bounces stored in JangoMail will still be flagged/removed before sending, but if you had any new members added since the upload, those will need to be added back by some other means. For example, if you used an autoresponder and a web opt-in form and were sending a welcome message to new members, you’ll have the recipient emailaddress in Reports. Granted, it may be tedious to extract all of those single addresses one at a time, so if that is the case for you, we can also do that via a backend query on our end.